eInvoices Management

The bidirectional protocol put in place between the Cegid OD and the Pdp will covert:

The eInvoices and lifecycle messages forward by the Pdp to the Customer, through the Cegid OD.
The eInvoices and lifecycle messages that the Customer sends, through the Cegid OD, to the Pdp.

In the perimeter of this communication process we classify then by its origin.

Pdp originated communication

This communication concerns any information coming from the French eInvoices ecosystem.

This information can be split in two main types but each one will have an specialized message:

Incoming eInvoices: eInvoices and statuses changes coming from the Sellers of the Customer.
Outgoing eInvoices: Changes made by the Buyer in the statuses of the eInvoices produced by the Customer.

Note

Each specialized message is described in Handles an incoming lifecycle event.

External PDP sending lifecycle messages flow

(*) This request MUST bring the Pdp subscription key

Warning

The Token Bearer generated by Cegid Account can be used in several calls, until their expiration, concerning the same Customer perimeter (Addressing line granularity).

We strongly encourages to put in place a cache mechanics and do not perform a new request on every call.

Cegid OD originated communication

This communication concerns any information coming from the Customer needing to be forwarded to French eInvoices ecosystem.

In the same way as above case, this information can be split in two main types and each one will have its specialized message:

Incoming eInvoices: Changes on the statuses, produced by the Customer, on the eInvoices coming from the Sellers.
Outgoing eInvoices: Changes made by the Customer in the statuses of the eInvoices already sent to the Buyer.

The Cegid OD will send each notification to the Callback endpoint registered by the Pdp in the on-boarding process.

Important

The Pdp MUST provide an exclusive endpoint for each on-boarded Customer (at the defined Addressing line level).