Following a French public invoice from Chorus Pro to acceptance and payment

A Chorus Pro status tells a supplier where an invoice is in a processing workflow. It should be read alongside the invoice details, the buyer's comments and the company's own bank record. Uploading a document, confirming the service and sending a payment instruction are different events. A useful follow-up identifies the event still needed and the party able to resolve it.

For a supplier serving several French public customers, this distinction improves cash planning. An undifferentiated list of “invoices sent” hides requests awaiting supplier action, documents under buyer review and payments already moving through the accounting chain. The finance team needs a more precise account of each material receivable.

Confirm the public-sector route used by the invoice

The French tax administration's explanation of the 2026 public-sector arrangements confirms that Chorus Pro retains its public-sector role. It describes continued direct channels alongside transmission through an approved platform, with exceptions for particular workflows. A supplier should therefore identify the route used for the actual invoice rather than assuming the wider invoicing reform removes its existing public-customer process.

Consider a hypothetical provider of ordinary equipment-maintenance services. It invoices one customer directly through Chorus Pro and another through its accounting provider. The commercial obligation may be similar, but the person investigating a missing status needs to know where the transmission record and buyer feedback can be found.

Maintain that channel information in the customer account record. Include the responsible finance colleague and the reference used to locate the invoice in the relevant system. This allows a query to begin with the actual transmission, instead of asking several teams whether someone remembers sending the document.

Read the stage before deciding who should act

AIFE's invoice-following documentation distinguishes deposit from availability to the recipient. It describes service-fait confirmation and later accounting stages, with some statuses optional according to the recipient's configuration. “Mise en paiement” concerns the payment instruction; it does not mean the supplier's bank has already received the transfer.

For the maintenance company, the first review should identify the latest meaningful event and any attached explanation. A supplier-side draft requires a different action from an invoice awaiting the buyer's supporting-document review. Likewise, a payment instruction should be reconciled with the subsequent bank receipt rather than triggering an immediate duplicate invoice.

Do not treat every missing intermediate status as proof that the underlying action has not occurred. A public customer's configuration affects the information returned. Where the visible record is insufficient, ask a precise question using the invoice reference and the known stage. This is more useful than assuming all customers expose an identical sequence.

Keep the language in the receivables report concrete. “Awaiting confirmation of delivery evidence” gives the account owner a task. “Stuck in Chorus” gives no indication whether the company, buyer or accounting service needs to act.

Connect service fait with the agreed delivery

For a maintenance invoice, the supplier's project record should make the completed service identifiable. The engineer's visit, the equipment covered and the agreed reporting output should connect with the period and amount invoiced. This gives the buyer a practical basis for reviewing the request.

Suppose the hypothetical company has completed two visits under an order, while the invoice description merely says “annual support”. The customer may need to establish whether it is being billed for completed work or a different contractual stage. A clear reference to the agreed deliverable can prevent that uncertainty without adding a large dossier to every invoice.

Operations and finance should agree the evidence handover before the first invoice. The service team knows what it delivered; finance knows the references and billing arrangement. Bringing those records together is more effective than leaving an administrator to reconstruct the service after a query arrives.

A disagreement about performance should remain visible as a commercial issue. Correcting a portal field cannot resolve a genuine dispute about whether the invoiced work meets the agreement. The account owner needs to identify the point of disagreement and coordinate a response using the delivery records and contract.

Use the reform notice for correction behaviour

Older invoice instructions describe an “à recycler” route that allowed certain destination or commitment-reference corrections without changing the invoice number. AIFE's 2026 evolution notice schedules the removal of that status in September 2026 and describes replacement-invoice handling, while preserving a transition for invoices already being recycled. The older recipe should not be assumed available for a newly returned invoice.

The practical response is to read the current status, reason and applicable instructions before making a correction. Keep the original invoice and any replacement linked in the company's own records. This helps finance avoid counting the same underlying service twice or leaving an obsolete request in the expected-cash total.

For the maintenance company, a wrong customer reference is an opportunity to correct the source record as well. If the accounting template contains the error, fixing one returned invoice will not prevent the next month's recurrence. Identify whether the fault came from the order information, customer setup or manual entry, then correct that specific cause.

Separate a request for missing supporting information from a rejected invoice requiring replacement. The supplier should respond to the actual reason given, with enough internal review to ensure the revised material still matches the contract and the completed service.

Preserve the history needed for an effective query

A useful payment query brings together the invoice, its transmission history and the commercial facts behind it. Record the relevant reference, amount, service period, latest status and action already taken. The recipient can then investigate a defined case rather than reconstructing it from a general complaint about unpaid work.

For the hypothetical supplier, one colleague could maintain a weekly exception list covering only invoices that need attention. The list would separate supplier corrections from buyer clarifications and payments awaiting reconciliation. Routine invoices can remain in the accounting system without creating unnecessary manual reporting.

Where an invoice concerns a subcontract or a group arrangement, identify the relevant validation relationship as well. The guides to DC4 and subcontract payment preparation and French groupements explain why the supplier's contractual role matters. A workflow question is easier to resolve when the finance team knows which party must review the request.

After receiving an answer, record the agreed next step and its owner. If the buyer requests a particular document, send that document through the specified route and retain the evidence. If the issue concerns scope, involve the person responsible for the contract before finance changes the amount or description.

Reconcile the payment with the receivable

The final event for the supplier is the receipt and reconciliation of money. Match the transfer to the relevant invoice or invoices and investigate any difference using the contractual record. An adjustment, recovery or partial amount needs an explanation in the ledger so the remaining balance is understood.

The maintenance business should be able to distinguish work invoiced, requests still under review and cash received. That supports a more credible forecast for payroll and purchasing than treating an upload confirmation as a collection date. It also helps management identify recurring causes of delay that the company can address in its own delivery and invoicing process.

Chorus Pro provides valuable visibility, but its usefulness depends on reading that visibility accurately. Follow the invoice's current stage, use the applicable correction instructions and keep the commercial evidence attached to the request. The resulting process gives each colleague a specific action and gives the business a reliable view of what remains to be collected.