Professional card or Limosa: decide what a foreign self-employed contractor needs in Belgium

Short answer: A non-EEA self-employed person may need a Belgian professional card unless an exemption applies, while Limosa addresses the declaration of covered work. Determine nationality, status, activity and exemption before onboarding; one document does not replace the other.

Why this needs a separate project decision

The word contractor can refer to a company, employee or genuinely self-employed person. If procurement records only a supplier name, the site team cannot see which personal authorization and declaration questions were actually checked.

The current official source remains authoritative. This guide supports construction companies operating in Belgium, but it is not legal, employment, safety or technical advice.

What the official source establishes

• Belgium applies conditions to foreign nationals starting a self-employed activity.
• A professional card may be required for non-EEA nationals, subject to exemptions and regional handling.
• Limosa separately covers declarations for certain work in Belgium.
• False self-employment and immigration status require competent review beyond a software checkbox.

Apply these points to the exact company, person, contract and project. Keep the source reference and verification date because a concise article cannot replace special conditions, exceptions or later official changes.

Add a control gate to the project

1. Record nationality, residence, legal status and the actual working relationship.
2. Check the current professional-card rule and any documented exemption.
3. Assess Limosa separately for the assignment and activity.
4. Keep decisions, issuer, validity and project dates in distinct fields.
5. Escalate ambiguity before granting site access or approving invoices.

Give every step an owner, deadline and explicit state. Separate prepared, submitted, received, reviewed and released when those states apply. Link release to the dependent task so missing or inconsistent evidence remains visible rather than being buried in a message thread.

Keep the evidence chain readable

A useful file shows what was expected, what was received, who reviewed it and which decision followed. Retain superseded versions as non-current instead of overwriting them. Connect document, person, contract, site and date so another colleague can reconstruct the reasoning.

Limit personal and commercially sensitive data to authorized roles. A project status can confirm that a control is complete while restricted evidence remains available only to people who need it.

Avoid this mistake

Do not infer genuine self-employment or a professional-card exemption from a foreign VAT number alone.

Reopen the control when scope, date, owner, contract, working relationship or official guidance changes. Evidence that was green for one version does not automatically validate the next one.

Frequently asked questions

Can Enfin make the official decision?

No. Enfin can keep project data, documents, tasks, planning and owners together. The competent person verifies the content and performs the formal action through the official route. Enfin does not claim a direct government integration here.

Which dates should the team keep?

Keep preparation, submission, receipt, content review and release as separate events where relevant. One date field cannot reliably represent the full evidence chain.

What if the requirement is unclear?

Block the dependent task, record the exact question and consult the current official source or a qualified adviser. Then store the explanation and resulting decision.

Read next

• construction document version control
• construction project management

Browse the English construction insights, review pricing, or discuss your workflow.