Reports

DPAE declarations (France)

Track and file the hiring declarations for your employees in France: list of declarations, creation, detail view with APE code check, and setup prerequisites.

3 min readUpdated on July 1, 2026

The DPAE (Déclaration préalable à l'embauche) is the French requirement to declare an employee to the URSSAF before their first day of work. Shyfter centralises these declarations: you can see which ones are pending, sent, validated or rejected, and you can create them manually. This screen is located under Documents → DPAE; it applies to French accounts (in Belgium, the Dimona plays this role).

Prerequisite: complete the DPAE settings

Before you can send DPAE declarations, your establishment's information must be filled in. As long as anything is missing, a "DPAE settings incomplete" banner appears at the top of the page and specifies what still needs to be completed (for example the APE/NAF code and the URSSAF code). The Open DPAE settings button takes you straight to the configuration screen (Settings ⚙️ → HR → DPAE: URSSAF integration, automatic sending, SIRET, APE/NAF code, URSSAF code, occupational health code).

The list of declarations

Each row corresponds to one DPAE and shows:

  • Employee: the person concerned.
  • Contract start date: the declared start date and time.
  • Contract type: for example a permanent contract (CDI).
  • Status: the state of the declaration (for example Validated or Rejected).
  • Urgency: the urgency level (for example Overdue if the deadline has passed).
  • Submitted by: the submission reference.

At the top, filters by Status, by Urgency and a search let you target, for example, rejected declarations to fix or hires whose deadline has passed.

Creating a DPAE

The Create a DPAE button opens a panel:

  • User: the employee to declare (required). Their profile must contain the necessary data (identity, date of birth, social security number, address, and so on).
  • Start date and Start time: required.
  • End date: optional (depending on the contract type).
  • Contract type: for example a permanent contract (required).
  • Hours/week: the weekly volume.

Confirm with Save. If the DPAE settings are not complete, the warning banner stays visible and the declaration cannot be sent until the missing codes are filled in.

The detail of a DPAE

Clicking a declaration opens its detail, in three blocks:

  • Employer: SIRET, name, address, postal code, city, APE code.
  • Employee: first name, last name, date of birth, social security number, address, postal code, city, email, phone.
  • Declaration information: start date, end date, contract type, hours/week.

At the bottom, three actions: Delete, Edit and Re-check the APE code (useful if the APE code has not yet been retrieved or needs to be revalidated).

Email notifications

You do not need to keep an eye on the page at all times: as soon as the URSSAF returns a response, Shyfter sends a notification email to the address configured for your account. Two cases:

  • DPAE accepted: the email subject is "DPAE Accepted - [employee name]" and confirms that the declaration went through.
  • DPAE rejected: the subject becomes "DPAE Rejected - [employee name]", and the email details the anomalies returned by the URSSAF, that is the explanation of the reason for rejection. The URSSAF return file(s) (XML) are attached to the email.

These same anomalies are also stored on the declaration and visible in its detail, which lets you understand the error and correct it.

Correcting a rejected DPAE

If a declaration is rejected, open its detail: the anomalies point to the data at fault (often an establishment code such as the APE code, or a piece of information from the employee's profile). Correct it, then resend the declaration. The Re-check the APE code button is useful when the rejection comes from a missing or not-yet-validated APE code.

Did this article answer your question?
Can't find what you're looking for?
Support
© 2026 Shyfter · shyfter.com