Monthly DSN: a reliability process before filing

Quick answer. Making the DSN reliable means checking payroll before sending, then systematically reading the returns on the net-entreprises dashboard. The monthly DSN is due on the 5th or 15th of the following month depending on headcount. Any correction goes through a cancel-and-replace DSN before the deadline, otherwise in the next month's DSN.

The déclaration sociale nominative (DSN), France's unified monthly social filing, is not a simple file upload: it feeds the Urssaf, pension funds, welfare schemes, France Travail and the tax authority for withholding at source. A wrong figure does not stay in your software: it spreads to around ten organisations, which send you anomalies several days after the deadline.

In the files we take over, the most frequent problem is not a missing DSN: it is a DSN filed without review, whose returns nobody reads. Discrepancies pile up, then resurface all at once during an Urssaf audit or when a retirement pension is calculated.

Making the DSN reliable means inserting an internal control between the payroll calculation and the transmission, then a second control after filing. This logic mirrors a payroll consistency check before closing, but focuses here on the quality of the filing, not the payslip.

The DSN covering remuneration paid in a given month is sent by the 5th of the following calendar month when social contributions are paid monthly, or by the 15th in other cases. The deadline depends on headcount and the payroll calendar.

This deadline calendar interlocks with the monthly payroll cycle calendar: DSN quality first depends on when you lock payroll. Payroll closed the day before the deadline leaves no room to fix a blocking return.

An effective control always follows the same order: start from gross pay, work down to contributions, then verify employee identification. Here is the sequence we apply on the firm's files.

1. Reconcile gross payroll with the DSN base. The gross total of your payroll journal must match the DSN aggregate, establishment by establishment. A gap reveals a missing variable, handled separately in payroll variable collection, or a misplaced back-pay item.
2. Check contribution blocks by organisation. Review capped and uncapped bases, Urssaf, pension and welfare rates, and the consistency of the liable headcount. An outdated rate after a collective-agreement update is the most common and most costly error.
3. Verify withholding at source. Compare the applied withholding rates with the latest nominative CRM received from the tax authority. An unupdated rate creates an over- or under-deduction for the employee.
4. Check identifiers. Social security numbers (NIR), dates of birth, contract codes and collective status determine whether each organisation accepts the filing.
5. Verify event signalements. Sick leave, contract endings and returns must appear in the correct month; a missing signalement distorts the employee's rights.

This checklist plugs directly into your software. On a Silae payroll platform, much of this control can be configured upstream, but configuration never replaces a human review.

Filing is only half the job. After transmission, net-entreprises makes available a cascade of returns that must be consulted, especially when they flag an anomaly.

The net-entreprises DSN dashboard cannot search for a filing older than three months. Beyond that, monitoring becomes blind: this is one reason we archive each return as soon as it is closed.

What is a nominative CRM and an identification report?#

A compte rendu métier (CRM), or business return, is feedback through which an organisation flags an error or a suspected error detected on a filing. The tax authority's nominative CRM concerns withholding at source, employee by employee; the financial CRM covers the aggregates. The employee identification report (BIS), on the pension side, checks the declared NIR: when it returns a number other than the one filed, the correction must be applied to the next month's payroll.

Two routes exist, and the choice depends solely on the time left before the deadline. If the correction can be entered in payroll before the eve of the deadline at midnight, you file a cancel-and-replace DSN: several successive cancel-and-replace filings are possible and numbered. After the deadline, the correction is made in the next month's DSN, using the dedicated adjustment blocks.

Adjusting a salary amount follows the same logic as the procedure to correct a payroll error: you document the origin of the gap before correcting the filing.

Multiple establishments. Each establishment has its own aggregate and its own returns. Reconciliation must be done SIRET by SIRET, never on a consolidated total that would hide offsets between sites.

Headcount crossing 50 employees. Moving the deadline from the 15th to the 5th can catch a growing company off guard. Anticipate the calendar change as soon as the threshold is durably crossed to avoid a late filing.

Annual reminder CRM. During March 2026, the Urssaf made available an annual reminder business return (CRM no. 124) summarising the year's anomalies. This annual return is an excellent revealer of recurring gaps that a monthly control should have intercepted.

The underestimated risk is not the rejected DSN, which is visible immediately: it is the accepted DSN that carries unread anomalies. The file goes out, the acknowledgement arrives, and the employer believes the matter is closed while the returns pile up untreated.

The second blind spot concerns traceability. Failure to produce filings on time, omission of employees, or inaccuracy of declared remuneration exposes the employer to penalties under article L133-5-3 of the Code de la sécurité sociale. Article R243-13 sets a penalty equal to 1% of the monthly social security ceiling per employee for an inaccuracy in declared remuneration, and one third of that amount for certain omissions. With a 2026 monthly ceiling of 4,005 euros, the bill adds up fast across a large headcount.

What the administration looks at first are the gaps between declared bases and verifiable payroll items. A documented monthly internal control is, by far, the best protection.

Recently, a director of a services SME came to us after receiving an unexpected Urssaf adjustment. The DSN went out smoothly every month, but nobody read the CRM: an incorrect welfare rate had been repeating for several months, and the returns flagging the gap stayed ignored on the dashboard. The adjustment covered the whole period, interest included.

Our reading is simple: a DSN's reliability is not decided on filing day, but in the review routine around it. A filing without upstream control and without reading the returns is a declaration on credit, whose bill arrives later.

The trade-off we often discuss with clients is internalisation. As long as headcount stays modest and stable, a rigorous checklist and good configuration are enough. As soon as collective agreements overlap or events multiply, securing the process through the firm's payroll and social service, or, for fast-growing structures, an outsourced CFO, becomes the most economical option given the risk.

As a chartered accountant and statutory auditor registered with the French Institute (Ordre des experts-comptables), we treat the DSN as a high-stakes filing, on a par with a tax return: its control must be organised, dated and traced. For the overall mechanics, our article on the complete workings of the 2026 DSN sets the frame.

Hayot Expertise tip. Block two recurring slots in your calendar: a control before filing and a reading of the returns three to four days after. Document each check in a simple grid. This minimal discipline neutralises the vast majority of anomalies before they become an adjustment.