A correct invoice is not just about one amount and two logos. The information depends on the identity of the parties, the nature of the sale, the tax, the payment conditions and sometimes a purchase order. A checklist fixed in an office model quickly becomes insufficient when the company changes address, regime or processes. The control must start from the master data and the context of the operation, then produce an archived version which can no longer be modified silently after sending.
French framework for international readers
Service Public Entreprendre is France’s official business-information portal. Its invoice guidance describes the French framework and should be read with the actual transaction, tax position and contractual documents. English labels can help a shared-service team review the file, but the legal identity, French registration details and wording required on the issued invoice must remain accurate. This checklist is a preflight, not automated tax advice. For cross-border billing, create a separate review path rather than assuming that every French mandatory detail applies unchanged to the customer’s jurisdiction.
“Controlled anatomy of a B2B invoice” control grid
- date and unique number
- exact identity of the parties
- verified billing address
- understandable description and quantities
- tax or special mention justified
- archived payment conditions and sent version
Alerts specific to accounting and VAT
- copy an old customer invoice
- let the CRM modify an archive
- use incomprehensible internal wording
- omit a known order reference
Scenario: invoice and mandatory information
A service company invoices a new customer. The ERP retrieves the SIREN, the name and the billing address from a form validated from the contract. The project manager confirms the end date of the service and the details of the deliverable. The check indicates that a purchase order exists but has not been completed; the invoice remains blocked until entered. After validation, the PDF and the structured data are frozen. If the customer's address subsequently changes in the CRM, the historical invoice retains the information that was actually issued.
Working method: B2B invoice pre-vol
1. Qualify the operation: sale or service, date of completion, possible deposit, professional or public customer, tax regime and possible sectoral particularity. To validate this step, note “date and unique number”. The risk to avoid is: copying an old customer invoice.
2. Recover the identity of the seller from the validated legal data and that of the customer from the order or contract. Do not use an uncontrolled CRM sheet. To validate this step, note “exact identity of the parties”. The risk to avoid is: letting the CRM modify an archive.
3. Assign a number according to the defined sequence and prevent duplicates. Any correction must keep track of the initial invoice and the corrective document. To validate this step, note “verified billing address”. The risk to avoid is: using incomprehensible internal wording.
4. Accurately describe the goods or services, quantities, prices, discounts and tax. Obscure internal labels must be translated into an understandable description. To validate this step, note “comprehensible description and quantities”. The risk to avoid is: omitting a known order reference.
5. Check the payment date, discount conditions, penalties and special information applicable to the case, from the official source and the General Terms and Conditions. To validate this step, note “tax or special mention justified”. The risk to avoid is: copying an old customer invoice.
6. Generate a preview, have the sensitive fields proofread, then archive the version sent with the channel and date of transmission. To validate this step, note “payment conditions and sent version archived”. The risk to avoid is: letting the CRM modify an archive.
Official reference for invoice
Service Public Entreprendre presents the general invoicing rules and details the mandatory information: date, unique number in a sequence, identity of the seller and the customer, description, amounts, tax, payment date and other information as appropriate. The page also makes special mentions. This official list is the reference to review, because an exempt transaction, a separate billing address or a relationship with a public entity can change the expected information.
Limits of interpretation for invoices
An invoice generated by software is not automatically compliant. A syntactically plausible VAT number is not proof of validity. General information does not cover all specific operations, and an invoice intended for the public sector may require a specific channel and references. Finally, directly modifying a document already sent destroys traceability: the correction must follow the appropriate accounting mechanism.
Read the visual “Controlled anatomy of a B2B invoice”
The visual grid uses the review labels “identities”, “number and dates”, “services”, “tax and amounts”, “payment” and “archive”. Read the cards from left to right and then from top to bottom; no arrow connects them. They organise the topic’s checkpoints without depicting a decision tree or an automatic chronology, and their meaning does not depend on colour.
Instructions for using the “B2B invoice prevol” tool
It reviews general mentions and asks for context for specific mentions. The entries are: transaction type, seller identity, customer identity, number and dates, tax, payment. The expected output is a list of fields present, missing or to be validated by a specialist. The safeguards are explicit: no tax regime guessed; no invented numbers; version sent immutable. When an input is unknown, the tool flags the missing evidence instead of choosing the most favourable outcome.
Decision and operational handoff
Authorize sending when identities, sequence, operation, tax and payment are checked. If a mention depends on a regime that the team does not control, request accounting or tax validation instead of using a default value. Keep the result of the check with the invoice in order to distinguish a master data error from an error specific to the operation.
Official sources checked for invoice
- Service Public Entreprendre — invoicing
- Service Public Entreprendre — mandatory information on an invoice
Sources and method
- Official source 1 — checked on 2026-08-17.
- Official source 2 — checked on 2026-08-17.
Continue in Propecto
Source éditoriale : Propecto. Date de publication : 2026-08-17. Lorsqu'une donnée vient d'une source externe, sa référence est citée dans le corps de l'article.