The attestation de vigilance is the document by which URSSAF, the French social-security collector, certifies that a business declares and pays its social contributions. Any client must demand it from subcontractors above a certain contract value, and have it renewed: it is the client's protection against joint liability if the subcontractor turns out to use undeclared labour. For that very reason it gets forged — and it is one of the easiest documents to verify, thanks to the security code URSSAF prints on it.
URSSAF issues the certificate to a business or self-employed person that has paid its contributions when due, or holds and honours a payment plan, or formally disputes the amount. It is downloaded from the business's online account — urssaf.fr, or autoentrepreneur.urssaf.fr for a micro-entrepreneur — and is valid for six months.
The document identifies the business (name, SIRET, address), states its issue date and validity period and, for an employer, the number of employees and the total remuneration declared. It carries a fifteen-character security code: that code is what makes verification possible.
For any contract worth at least €5,000 excluding VAT, the client must obtain the vigilance certificate at signature, then every six months until the work is complete (French labour code, articles L8222-1 and following, D8222-5). A proof of registration comes with it: a K or Kbis extract, proof of entry in the National Business Register, or a quote, advertising document or business letter showing the name, address and registration number.
The stakes are not administrative. If the subcontractor is convicted of undeclared labour and these checks were not made, the client is jointly liable for its unpaid taxes, contributions and wages. A forged certificate accepted without checking protects against nothing.
URSSAF runs a public certificate verification tool. Enter the security code exactly as printed — fifteen characters, no spaces. If URSSAF does not recognise it, it answers that the code matches no certificate currently in force: the code was miscopied, the certificate has expired, or it was altered or fabricated.
If the code is recognised, URSSAF displays the details of the certificate it actually issued: the company name ("identification du diffuseur"), the SIRET of each establishment, the document's certification date and the last period analysed. Compare them line by line with the document you received: a fraudster can paste another company's genuine code onto a certificate fabricated in their own name — the code passes, the comparison does not.
The certificate never comes alone. The SIRET must be the one on the Kbis extract and the invoices; the bank details must be in the same company name — supplier impersonation fraud often starts with a flawless onboarding file. And do not confuse the vigilance certificate with the tax-compliance certificate issued by the tax administration: two documents, two issuers, two checks.
That a business is up to date with its contributions today says nothing about its solvency tomorrow, nor about who is actually writing to you in its name. The certificate expires in six months: put the renewal in the contract's follow-up rather than relying on the subcontractor to remember. TrustyFile examines the file — revisions, edits, SIRET and VAT check digits; the security code is verified on urssaf.fr, and nothing replaces that step.
Free SIRET checker: validates the 14-digit French establishment number with the Luhn formula, including the special rule for La Poste establishments. Runs locally.
Open the tool →
Free SIREN checker: validates the 9-digit French company number with the Luhn formula and derives the intra-EU VAT number it implies. Runs in your browser, nothing is sent.
Open the tool →
Edited amounts, altered dates, swapped bank details: the technical evidence that gives away a tampered invoice PDF, and how to check for it.
Utility, telecom and internet bills used as proof of address: the technical checks that reveal an edited document, and when the checks simply cannot apply.
A PDF keeps a record of its successive saves: incremental revisions, ghost objects, two sets of metadata. Where to look to find out whether a file was edited.
The 2D-Doc barcode on tax notices, pay slips and official certificates: what it contains, what it actually proves, and why it is different from every other check.
Fake pay slips in rental files and loan applications: payroll software fingerprints, arithmetic checks and the French 2D-Doc barcode that expose an edited document.
Payment redirection fraud swaps the bank details on a genuine invoice. IBAN checksum, bank-code consistency and PDF tampering traces: how to check details received by email.
A supplier announces new bank details? How the fraud works, the warning signs in the message and in the attached document, and the checks to run before you pay.
Check a Kbis against the public registers (SIREN, directors, registered office, company status), spot a forged PDF, and know what a genuine Kbis does not prove.
Landlord or agency: verify a tenant's French income-tax notice with the tax office's online service (SVAIR), the signed 2D-Doc code and the other documents in the file.
Analyse a document for free