Sylae, the portal of the Agency for Services and Payment (ASP), centralizes the management of subsidized contracts for French employers. Since the overhaul of the employment information system, the platform relies on a unique ASP Connect account, which changes the login procedure. The stakes are no longer limited to entering attendance certificates: the consistency between Sylae data and the DSN conditions the payment of aids and exposes to automated corrections by URSSAF.
Consistency between Sylae and DSN: what the substitute DSN changes for employers
Since summer 2026, URSSAF can correct certain persistent anomalies in the nominative social declarations via a mechanism of substitute DSN. This device is activated after several business reports (CRM) that remain unaddressed by the employer.
If the data entered in Sylae (attendance, gross salaries of subsidized contracts) diverges from those transmitted in the DSN, URSSAF can adjust the contribution base. The direct consequence: a modification of the rights of the affected employees and a risk of enhanced control.
For employers managing CUI, apprenticeship contracts, or adult-relay contracts, the quality of the information entered in the Sylae portal is therefore indirectly controlled via the DSN. An entry error on the platform is no longer confined to the payment of the aid: it can impact payroll and trigger an automatic adjustment.
Before any monthly declaration, it becomes necessary to log in to your Sylae ASP account to verify that the amounts and periods exactly match the payslips transmitted in the DSN.
ASP Connect account and Sylae portal: comparative access table
Accessing Sylae goes through ASP Connect, a unique identifier that provides access to several ASP applications. Here are the differences between the two access layers.
| Criterion | ASP Connect | Sylae Portal |
|---|---|---|
| Role | Centralized authentication | Management of subsidized contracts and employment aids |
| Identifier | Email address of the account | Same identifier (via ASP Connect) |
| Password | Defined at the creation of the ASP Connect account | Identical (no separate password) |
| Two-factor authentication | Enabled since March 2026 for changes to payment details | Inherited from ASP Connect |
| Multi-SIRET management | One account can be linked to multiple establishments | Selection of the establishment after login |
| User profiles | Administrator or delegated user | Entry, consultation, or validation rights depending on the profile |
The two-factor authentication implemented since March 18, 2026 does not apply to every login but is triggered during any modification or addition of bank details. This point frequently causes blocks for employers trying to update a bank account without access to the phone associated with the account.
Linking an establishment to the account
A newly created ASP Connect account does not display any contracts until the establishment (identified by its SIRET) is linked. This step requires having the convention number assigned by the DIRECCTE or the prefecture at the signing of the subsidized contract.
For multi-establishment structures, each SIRET must be linked separately. One administrator account can manage multiple SIRETs, but selection is done manually after login, which requires vigilance when entering monthly certificates.
Common connection errors in Sylae and unlocking procedures
Connection difficulties to the Sylae portal follow recurring patterns. Three situations account for the majority of blocks.
- The temporary password sent by email upon account creation expires after a short period. If the employer does not log in quickly, the link becomes inactive, and a reset procedure must be initiated from the ASP Connect page.
- Password reset emails are filtered by professional anti-spam, especially on corporate email systems configured with strict rules. Check the spam folders and, if necessary, add the domain asp-public.fr to the whitelist.
- Changing the Sylae administrator (departure of an employee, transfer of responsibility) requires intervention with the ASP if the former administrator did not designate a successor before their account was deactivated. The procedure involves a specific contact form, with proof of identity of the new administrator.
Loss of the identifier (email address) is resolved more simply: the ASP can retrieve the account using the SIRET of the establishment and the convention number.
Entering attendance certificates: deadlines and impact on aid payments
The main functionality of Sylae for employers remains the monthly entry of attendance certificates. These certificates condition the payment of the financial aid associated with the subsidized contract.
The portal imposes a submission schedule. A certificate not submitted on time leads to a delay in payment, or even a permanent loss of aid for the concerned period. Employers of CUI contracts are particularly exposed, as the amount of aid is calculated based on the actual hours worked reported each month.
Checks before validation
Each certificate must mention the hours worked, absences, and the gross salary of the employee for the period. Three points deserve particular attention before validation:
- The gross salary entered in Sylae must exactly match that of the payslip, including bonuses and supplements subject to contributions.
- Unpaid absences (sickness, unjustified absence) must be deducted from the hours of attendance, under penalty of overpayment recoverable by the ASP.
- For apprenticeship contracts, periods in training centers count as attendance time and must be included in the certificate.
An aid not declared on time is a lost aid. The Sylae platform does not allow retroactive entry beyond a certain number of months. Regularization then requires direct exchange with ASP services, with no guarantee of success.
The management of subsidized contracts via Sylae is part of a compliance framework that goes beyond simple access to the portal. Employers who handle payroll data and social declarations in parallel have an interest in synchronizing their checks between payroll software, the DSN, and Sylae certificates, rather than treating each tool as a separate silo.
