Review process for 2026 contributions

A review of contributions for 2026 must go beyond just submitting a declaration and making a payment. These actions alone do not ensure the accuracy of the figures. Errors may exist even if the annual total appears balanced, as they could cancel each other out. The review is conducted before the last payment of the year, then completed after the December 2026 social declaration (DSN) is submitted in January 2027 and the returns are examined. This timeline prevents delays in making necessary corrections.

Preparing a working file for verification

To check the 2026 contributions, compile a working file that includes monthly payroll statements, their cumulative totals, and details of the bases, ceilings, and reductions. Include the DSNs actually submitted, replacement declarations, and returns from organizations. Also include a correction history with amounts and periods, as well as supporting documents for the situations under review. Each extraction must be dated and tied to its establishment and period. Keep separate copies of the original submitted statement and the recalculated one for the review. Avoid adding the twelve cumulative amounts from January to December directly.

Transitioning between payroll tools

When switching payroll software or service providers, compare cumulative totals from the old system with those from the new one. Simply resuming gross salary figures is not enough, as previous corrections and reduction data must also align. Two common issues during the transition period are missing DSNs for a payroll month, which leads to declaration failures, and mistakenly issued DSNs by the old provider for months no longer under their responsibility. This can prevent the new provider from correcting errors. The new provider must also check the inter-declaration balance on its dashboard during the first month of sending DSNs for a new SIRET number.

Legal considerations for payroll changes

If the employer and contractual situation remain unchanged, switching payroll tools does not create a new legal calculation period. However, a contract transfer or restructuring requires a separate review. The annual calculation rules and declarative continuity must be taken into account. In practice, reconciling employees and their contracts—not just their numbers—is essential. This includes employees who left during the year. If identifiers have changed, a correspondence between old and new files should be established. Two lists of the same size might still be missing an employee or have a duplicate.

Differences between regularization and correction

Regularization based on a calculation mechanism and correcting a declaration error are distinct processes. The single progressive general reduction (RGDU) is calculated per civil year, for each employee and each employment contract. The Social Security Code explicitly states that the reduction amount is calculated annually for each employee and contract. A regularization at year-end compares the annual reduction with the amounts applied in advance. It also allows for a progressive regularization based on elements cumulated since January or since the employee’s hiring. If a contract ends mid-year, the regularization applies only to the last month or quarter of employment. A significant change in December is not necessarily an error, and the absence of change does not guarantee the accuracy of the annual calculation.

Checking the reference minimum wage (SMIC)

For 2026, the reference minimum wage (SMIC) must be checked. The common law formula uses the annual gross minimum wage, applicable as of January 1, 2026, as defined by decree No. 2026-509 of June 12, 2026. The annual amount must be adjusted for each employee based on their working time and absence periods. The salary ceiling for the reduction is set at three times the SMIC as of January 1, 2026. This choice ignores the SMIC revaluation that occurred on June 1, 2026. The monthly coefficients published by the administration reflect this for a full-time employee paid the SMIC all year in a company with fewer than fifty employees, without bonuses or overtime.

Special rules for contracts ending mid-year

A practical nuance applies to contracts terminated between January 1 and June 30, 2026. Due to the publication schedule of the decree, the formula may not be applied to contributions and charges for these employees. It must be applied to all employees with contracts still in progress as of July 1, 2026. These files must be identified before qualifying any discrepancies as errors. For capped old-age contributions, the rule is different. These contributions are regularized each month. The employer aggregates amounts due since the first day of the year or since the hiring, and calculates contributions on the part of this aggregate that does not exceed the sum of the applicable periodic ceilings. The ceiling rules for these contributions differ from those used for the RGDU.

Reconciliation process and DSN management

The reconciliation compares the recalculated amount with the net declared amount, after considering already transmitted corrections. The collection must cover each establishment, each declared month, and, if applicable, all fractions of DSN. These fractions are not limited to a single establishment and are allowed in specific cases, such as when a company uses multiple payroll systems or manages different employee categories with varying DSN submission deadlines. Each fraction follows its own deadline rules. For each fraction, keep the accepted declaration that has not been replaced. Two mechanisms coexist: a monthly DSN that cancels and replaces the previous declaration, and corrections made through subsequent monthly DSNs. The original declaration does not disappear, which can lead to false discrepancies if not carefully tracked.

Example of reconciliation in practice

Take the example of a review conducted in January 2027, after the December 2026 DSN submission. The reconciliation focuses on 2026 reductions for a single establishment and within the URSSAF perimeter. The sum of individual recalculations, assumed to be correct, reaches 100,000 euros. The declared reductions, excluding a 7,000 euro correction, amount to 112,000 euros. After subtracting the 7,000 euros, the net reduction is 105,000 euros, leaving a 5,000 euro excess to correct. If the 7,000 euros are only in an internal table, the declared reduction remains at 112,000 euros. However, if the net total is already 105,000 euros, the 7,000 euros should not be subtracted again. The negative sign here indicates a decrease in the reduction, not an instruction to make a DSN entry.

Correcting errors and legal consequences

The employer must correct errors in contribution and social charge declarations at the nearest deadline, either on their own initiative or at the request of the recovery organization they belong to. The correction must be accompanied by a payment for the additional contributions and charges. A closing review does not allow waiting until December to address known errors. A provision in the text rewards quick correction by exempting late charges and penalties if certain conditions are met. These include correcting the error at the first deadline following the original submission and ensuring the regularizing payment is less than 5% of the initial contributions. However, two situations are excluded: the omission of employees in the declaration and repeated inaccuracies in salary amounts.

Managing the review process for management

The synthesis for management should distinguish between explained differences, confirmed errors, amounts still to be verified, and points dependent on a document or legal analysis. If a history is missing or the cumulative data does not connect, reconstruct the perimeter and data before concluding on the amount. If the same parameter appears incorrect in multiple files, identify the affected population and measure the effect of the applied rule. If a correction is announced but not found in the declaration, locate the file that carries it and check the returns. If the recalculation depends on an absent document, identify the condition that justifies it and the person responsible for finding the document. If a discrepancy remains unexplained after reconciliations, define the files, periods, and questions to submit for a complementary verification.

Assigning responsibilities and tracking actions

For each discrepancy, designate a pilot and specify who provides the documents, validates the processing, performs the correction, and verifies the return. If the payroll is outsourced, identify the contact at the service provider and the person following the file in the company. An isolated and limited anomaly may only require a limited correction. A contribution audit is particularly useful when multiple establishments are involved, when historical data remains incomplete, or when corrections repeat without a clear cause. The expected result of the audit must be defined. If an error is confirmed, determine which population it affects, the periods involved, and the amount. The deliverable should separate favorable and unfavorable discrepancies, confirmed amounts from those still to be verified, and specify the corrections and necessary documents. A targeted review does not allow declaring unexamined files as compliant. If a common error is identified, search for its effects on the affected population. The closing remains an internal organization stage and does not constitute a validation by URSSAF or close all possibilities for further correction. For management, the decision rests on three answers: which perimeter has been verified, what remains to be quantified or corrected, and who is responsible and by when.