Usage
Invoices
Section titled “Invoices”When an order reaches the status set in the settings (default Processed), the add-on numbers its invoice, builds the Factur-X (PDF + XML) and checks it. You can also create it from the order page (French e-invoice tab > Create the invoice) or for many orders at once (orders list > select > Actions > Create French e-invoices). Failed, declined, cancelled and incomplete orders get no invoice.
Every invoice belongs to a channel:
| Channel | When | What happens |
|---|---|---|
| Domestic B2B | Seller and buyer are French companies (the buyer entered a valid SIREN) | Sent to your platform as an e-invoice |
| International B2B | The buyer is a business outside France (VAT ID) | Sent to your platform with the processing rule “B2BInt” (e-reporting of international sales) |
| B2C | The buyer is not identified as a business | Kept for the B2C e-reporting; the customer can download it |
| Out of scope | Your seller identity has no SIREN or no French address | Kept as a Factur-X file only |
Orders > French e-invoicing lists every document with filters (status, channel, kind, number / buyer / SIREN), readiness cards (seller, platform, current e-reporting period) and Download PDFs (ZIP).
Statuses
Section titled “Statuses”| Status | Meaning |
|---|---|
| Queued / Sending / Submitted | On its way to the platform |
| Deposited (200) | Accepted by your platform |
| Delivered, Approved | Received or approved by the buyer’s side |
| Refused by buyer (210) | The buyer refused it; create a credit note if needed |
| Rejected (213) | The platform rejected it; fix the data and use Send again (a new submission) |
| Paid (212) | “Payment received” was sent |
| Error | The check failed or the platform refused the request; the reason is shown |
| Waiting | No platform connection yet; it is sent when one exists |
| Manual upload | Upload the PDF in your platform’s portal, then set the status here |
| E-reporting only | B2C sale |
The document page shows the check, the lifecycle events, the lines and totals and the other documents of the order. Rebuild creates the files again with the same number (only before the document reached a platform or a sent e-reporting), for example after you completed your seller identity.
Credit notes
Section titled “Credit notes”Create a credit note on an invoice: enter the quantities and the shipping to credit, or Credit everything still open. Earlier credit notes are already subtracted, so you can never credit more than the invoice. A credit note is refused while the invoice is still being sent. With Credit the whole invoice when the order status becomes set, the credit note is created automatically; if the invoice is still on its way to the platform, it is created by the queue as soon as the platform has answered.
Payment received
Section titled “Payment received”For domestic and international B2B invoices of services, the add-on sends “payment received” (212) with the amounts per VAT rate when the order reaches a “paid” status (SUPER PDP). With the AFNOR API or manual upload, set it in your platform’s portal. Nothing is sent for goods or when you opted for VAT on debits.
B2C e-reporting
Section titled “B2C e-reporting”Orders > French e-invoicing > E-reporting. After each period of your VAT regime the add-on adds up the B2C sales per day, category (goods TLB1, services TPS1, not subject to French VAT TNT1) and VAT rate, credit notes subtracted, and the payments for B2C services per day and rate. Each transmission shows its period, documents, amounts and deadline.
- SUPER PDP and AFNOR API: sent by the cron job (or Send).
- Manual upload: XML downloads the official flux 10 file; upload it in your platform’s portal and press Mark as uploaded.
A document dated in a period that was already sent produces a corrective transmission of that period.
Customers
Section titled “Customers”The customer’s order page shows PDF and XML links for each invoice and credit note (setting Customers can download their invoices). Only the order’s customer can download them.
Multi-Vendor
Section titled “Multi-Vendor”- Marketplace issues the invoices on: one seller identity and connection (the marketplace); vendors see their orders’ documents read-only.
- Off: each vendor fills in Seller identity and Platform connection in the vendor panel and creates, sends and credits its own invoices with its own numbering. The queue, the log and the e-reporting actions stay with the administrator.