The ZZP Pause Changes Nothing About Your Freelancer Risk

What is the freelancer legislation pause? To understand the present context, let’s clarify what changed with the government’s recent announcement.

The Dutch cabinet withdrew part of the proposed freelancer legislation in March 2026. The government called this a pause for “more calm and clarity.”

The government proposed the Wet VBAR to replace the existing Wet DBA framework. The new law was supposed to clarify when someone qualifies as genuinely self-employed. There was an income threshold: freelancers earning below roughly €38 per hour would trigger a reversal of the burden of proof.

Below the rate, the freelancer would be considered an employee. You, the client, would need to prove that they weren’t.

Small businesses responded with hesitation. Organizations representing freelancers reported that members lost contracts due to clients’ concerns about compliance risks. Projects stalled. Assignments disappeared.

The government acknowledged a market freeze and postponed the legislation. Enforcement of current rules continues. The Belastingdienst applies Wet DBA, which remains in effect.

Bottom line: The new framework was delayed. The old framework still applies. Your liability didn’t shrink.

Does enforcement continue during the pause? With that legislative background, let’s look at enforcement now.

Yes. The enforcement moratorium ended on January 1, 2025. The Belastingdienst continues applying Wet DBA rules.

The withdrawal doesn’t suspend liability. Doesn’t eliminate back taxes. Doesn’t reduce your exposure if you misclassify a freelancer.

What disappeared was regulatory clarity. What stays is the enforcement reality.

The Belastingdienst operates independently of political processes. The pause affects proposed legislation. Doesn’t affect the current enforcement authority.

Reality check: Soft enforcement now, hard enforcement soon. The pattern is clear.

How does enforcement work right now? Now that enforcement is clear, see how it is being carried out currently.

The Belastingdienst imposes back taxes retroactively. The lookback period extends up to five years in cases of willful misconduct.

For unintentional violations, the lookback period starts from January 1, 2025. If you’re inspected in 2026, you face one year of exposure. If you’re inspected in 2030, you’ll have 5 years. Liability is not static—it grows over time as enforcement measures increase, raising your financial risk the longer you delay compliance.

A construction industry association reported in early 2025 that inspections are already happening. Members received signals showing active reviews. The enforcement plan highlights “coaching business visits” in 2025. Coaching doesn’t mean immunity.

From 2026 onwards, companies neglecting compliance face punitive fines. From 2027, even unintentional errors trigger penalties.

The timeline:

• 2025: Coaching visits, retroactive liability begins
• 2026: Punitive fines for willful violations
• 2027: Penalties for unintentional errors

Key takeaway: Liability grows over time. Delays increase your exposure.

What financial liability are you facing? Having covered how enforcement works, let’s examine the financial exposure involved.

Misclassification triggers an average back-tax obligation of roughly 33% of the gross annual amount paid to the freelancer. This covers regular wage tax rates and social insurance premiums of roughly 18.5%.

This isn’t a fine. This is the baseline correction.

Example: You paid a freelancer €50,000 over two years. The Belastingdienst reclassifies them as an employee. You owe roughly €16,500 in back taxes. Add penalties for negligence or willful violations. The number grows.

Construction companies report that these accumulated liabilities lead to bankruptcy for some businesses. The exposure is calculable.

There’s another layer: pension obligations. If your industry has a mandatory pension scheme, a reclassified employee should have participated in the plan. You face retroactive pension premium liabilities and potential claims from the pension fund.

The liability isn’t limited to tax. Extends to structural obligations.

Financial breakdown:

• Back taxes: ~33% of gross payments
• Penalties: Variable, increasing from 2026
• Pension obligations: Industry-dependent, retroactive
• Administrative costs: Legal defense, documentation recovery

Key insight: Liability isn’t abstract. Calculable and increases over time.

Why does the €38 per hour threshold matter? As we explore risk factors, this threshold reveals policy direction.

The proposed legislation was paused. The € 38-per-hour threshold reveals the regulatory philosophy.

The government views lower-wage freelancers as more vulnerable to misclassification. The perspective doesn’t disappear with the pause.

When the government introduces the replacement framework (the Zelfstandigenwet), expect similar protections. The ministry estimates 200,000 of the Netherlands’ 1.3 million registered self-employed workers are cases of false self-employment. Roughly 15% of all freelancers.

The regulatory pressure isn’t going away. Being repackaged.

If you hire freelancers earning below €38 per hour, you operate in a higher-risk zone. The burden of proof isn’t legally reversed yet. The enforcement philosophy already treats lower-wage engagements with more scrutiny.

Practical action: Document independence more carefully for lower-paid freelancers. The regulatory environment signals where enforcement attention will focus.

What does structural independence mean in practice? Building on classification criteria, let’s clarify operational significance.

The Belastingdienst doesn’t care what your contract says. They care about how the work happens in practice.

The agency explicitly states: “What is put down on paper does not matter; what matters is how you work in practice.”

Model agreements, once approved by the Tax Administration, give you a false sense of security. Actual working relationships determine classification.

The assessment framework stresses whether “the worker behaves or performs as an entrepreneur in the market.” This includes:

• Reputation: Does the freelancer have a recognizable market visibility?
• Client acquisition: Do they actively seek and win work from multiple clients?
• Number of clients: Are they dependent on one client, or do they maintain a diversified portfolio?
• Engagement duration: Are they working for you continuously for years, or in defined projects?

The amalgamation criterion (whether a freelancer’s activities are “closely connected to the core activities of the company”) has been confirmed by recent case law as an independent criterion in determining employment relationships.

Even an approved model agreement doesn’t protect you if the work performed is strongly embedded in your business structure.

Audit trigger: Review your longest-running freelancer relationships. If someone has worked for you continuously for more than 18 months, performs core business functions, and has no other visible clients, you’re carrying exposure.

Why is regulatory uncertainty now permanent? With the operational factors set, consider why clarity remains elusive.

Current  enforcement operates under Wet DBA, introduced in 2016. The proposed Wet VBAR legislation was postponed from January 2025 to at least July 2026. The government has now announced that VBAR will be replaced by the Zelfstandigenwet.

Three legislative structures in less than a decade.

Enforcement resumed before replacement legislation took effect. This creates a structural gap: you must comply with current rules while preparing for future standards that are yet to be defined.

The enforcement plan explicitly states you must comply with “current legislation” until new laws are implemented. Regulatory fluidity is the operational baseline.

Strategic reality: Stop waiting for perfect clarity. Won’t arrive. Build your freelancer management system around principles that survive regulatory transitions.

What conWhat controls should you install now? Given this regulatory environment, let’s move to practical safeguards you can implement.

Don’t control the legislative calendar. You control your documentation and working relationships.

Install these controls before the next inspection:

1. Document operational independence

Create a simple record for each freelancer showing:

• How do they determine their own working methods?
• Evidence of other clients (without violating confidentiality)
• Their business registration and invoicing structure
• Project-based engagement boundaries

2. Audit integration depth

Ask yourself:

• Does this freelancer use your company email address?
• Do they attend all-hands meetings and participate in company culture activities?
• Are they listed on your website as part of the team?
• Do they work from your office daily?

Each “yes” increases integration risk. Reduce visible integration or convert the relationship to employment.

3. Clarify engagement boundaries

Define:

• Project scope and duration
• Deliverables, not hours
• Payment tied to outcomes, not time
• Clear start and end dates

Avoid open-ended, continuous arrangements resembling permanent employment.

4. Review lower-wage relationships first

If you hire freelancers earning below €38 per hour, give priority to those relationships for documentation review. The regulatory philosophy treats these engagements as higher risk.

Either strengthen independence markers or convert to employment.

5. Stop relying on model agreements

Model agreements provide legal language. They don’t provide operational proof. The Belastingdienst assesses reality, not contracts.

Use model agreements as a starting point. Build your defense around documented working practices.

Implementation priority: Start with your highest-risk relationships (longest duration, lowest pay, deepest integration). Work systematically through your freelancer roster.

What are your options?

The pause doesn’t protect you. Enforcement continues. Liability accumulates.

You have two choices:

Option A: Wait for perfect regulatory clarity and hope inspections don’t happen.

Option B: Build structural independence into your freelancer relationships now, using principles for surviving legislative shifts.

Option A feels cheaper today. Option B prevents bankruptcy tomorrow.

The system doesn’t care about your intentions. Measures proof.

Structure is cheaper than recovery.

Frequently Asked Questions

Does the March 2026 pause mean I’m safe from enforcement?

No. The pause affects proposed legislation (Wet VBAR). Current rules (Wet DBA) stay fully active. The Belastingdienst continues enforcement. Your liability didn’t change.

How far back does the Belastingdienst review working relationships?

For unintentional violations, the lookback starts January 1, 2025. For willful misconduct, the lookback extends up to five years. Inspection in 2026 means one year of exposure. Inspection in 2030 means five years.

What happens if the Belastingdienst reclassifies me as a freelancer?

You owe roughly 33% of gross payments in back taxes (wage tax plus social insurance premiums). Add penalties from 2026 onwards. You face potential pension fund liabilities if your industry has mandatory schemes. Administrative costs for legal defense and documentation recovery increase total exposure.

Does a model agreement protect me from reclassification?

No. The Belastingdienst states: “What is put down on paper does not matter; what matters is how you work in practice.” Model agreements provide legal language. Actual working relationships determine classification.

Why are freelancers below €38 per hour considered higher risk?

The regulatory philosophy views lower-wage freelancers as more vulnerable to misclassification. The proposed Wet VBAR would have reversed the burden of proof for this group. The pause delayed the law. The enforcement philosophy stays. Expect higher scrutiny for lower-wage engagements.

What does structural independence look like?

Structural independence means the freelancer operates as a business. They maintain multiple clients. They determine their own working methods. They invoice through a registered business. They work on defined projects with clear start and end dates. They aren’t integrated into your company culture or systems.

When should I convert a freelancer to employee status?

Convert when the relationship shows deep integration: continuous work over 18 months, no other visible clients, performs core business functions, uses company email, attends all-hands meetings, and is listed on your website as a team. If you can’t demonstrate independence, formalize employment.

What is the Zelfstandigenwet?

The Zelfstandigenwet is the replacement framework for the paused Wet VBAR. The government hasn’t released details. Expect similar protections for lower-wage freelancers based on regulatory philosophy. Timeline is undefined.

Key Takeaways

• The legislative pause doesn’t suspend enforcement. Wet DBA stays active. The Belastingdienst continues reviewing working relationships.
• Misclassification costs roughly 33% of gross payments in back taxes, plus penalties from 2026, plus potential pension obligations.
• Contracts don’t determine classification. Working relationships do. Integration depth and client diversity matter more than legal language.
• Freelancers below €38 per hour operate in a higher regulatory risk zone. Document independence more carefully for this group.
• Regulatory clarity won’t arrive. Build your freelancer management system around principles surviving legislative shifts: operational independence, multiple clients, project-based boundaries, and minimal integration.
• Liability accumulates over time. Delay raises exposure. Structure your relationships now before inspection happens.
• The system measures proof, not intentions. Documentation of actual working practices is your defense.