Scope and planned capabilities

Truvio ExFlow e-Invoicing solution relies completely on the data posted inside Dynamics 365 Finance, enabling the user to output the invoice data in xml format, sending the payload in a securized way to the e-invoicing network and managing the different responses from the network and business parties - technical responses, business responses and clearance responses if applicable-, exposing this information inside D365 Finance in a friendly manner to the user. Similarly, Account payable invoices are retrieved from the e-invoicing networks and transferred to Truvio ExFlow AP where they can be handled and approved using powerful workflows.

ExFlow e-Invoicing doesn't post any account receivable document or invoice nor extend in any way the posting functionality of the localized version of D365 Finance. Invoicing business processes are thus limited by D365 capabilties (and potential add-ons installed by the user).

In the context of the FR e-invoicing and e-reporting mandate, the D365 Finance capabities affect the user's business process in 2 main aspects:

1. D365 Finance FR capabilities that may or may not support a given invoicing flow (f.ex: multi-vendor invoice).
2. Microsoft Electronic Reporting Configuration that will take invoices posted and construct the FR UBL-CTC compliant xml file.

Components required for enabling compliance with FR e-invoicing and e-reporting mandate using Pagero as PA

Components required:

1. Microsoft D365 Finance update to cover:
   1. E-Invoicing functionality: Planned GA August 2026 on 10.0.48.
   2. E-Reporting functionality. Planned GA September 2026 on 10.0.49
   3. Establishment and Registration ID governance on invoices. Planned GA September 2026 on 10.0.49
   4. Electronic Reporting Configurations to output FR UBL xml e-invoice and e-reporting xml: UBL Sales e-invoice (FR), UBL Sales e-credit note (FR), UBL Project e-invoice (FR), UBL Project e-credit note (FR).
2. Truvio ExFlow Document Integration
   1. Sending and receiving e-invoices using Microsoft D365 ER FR UBL.
   2. AR lifecycle messages generation and AR/AP status communication.
3. Truvio ExFlow AP
   1. import and handling of AP invoices.
   2. AP invoices lifecycle status.

Check with your D365 partner which of your business e-invoicing scenarios can be handled by 1.1 and 1.4 above. Also, some limitations may exist in 3.1.

Scope for Q2 2026 release

Invoice types

Sendind and receiving:

• Invoices based on Sales orders.
• Credit notes based on Sales orders.
• Free text invoices.
• Free text credit notes.
• Project invoices.
• Project credit notes.

Lifecycle status

Sending:

• 210: Refused (from ExFlow AP)
• 212: Payment received. A status message is sent every time a payment (total or partial) is applied to an B2B domestic invoice with Conditional VAT to comply with FR rule that this status must be sent if VAT is due upon payment. Also, when payment settlement is cancelled, the corresponding status is sent. Both cases, the sending is automated using a batch job.

Receiving:
If the lifecycle status code is set (ExFlow Document integration | Setup | Lifecycle status), any code will be handled and presented to the user.

Planned for Q3 2026 release

• Prepayment invoices.
• Sending optional lifecycle statuses.
• Debit notes (if relevant. Under analysis).
• Automated sending of e-reporting via Pagero

AFNOR use cases

Note: AFNOR publishes documentation concerning use cases affecting B2B transactions. The XP Z12-014– B2B use cases applicable within the framework of the Electronic Invoicing Reform in France is one of the relevant documents and it is strongly suggested each customer review it along its Dynamics 365 partner to determine:

1. If a given use case is relevant for its operations
2. If D365 Finance and the associated ER Configuration supports the correct generation of the compliant xml invoice. Be aware that it might be that a business process supported (that is, the invoice is posted correctly representing the operation) might not be covered in the ER Configuration. In this case, the customer will need to request Microsoft for the update or customize appropriatelty the ER Configuration.

The below table summarizes our current understanding of the D365 Finance FR capabilties and potential support of the business operation using ExFlow e-Invoicing. It doesn't guarantee or assume the case it's supported (*) and your assessment with your D365 partner is ALWAYS required.

Features and capabilities provided by Microsoft can change in any update.

AFNOR Use case ID	AFNOR Use case description	Can the transaction be represented/accounted for in standard D365 Finance for FR? (*)	In scope for Truvio E-invocing flow
1	Case No. 1: Multi-order/Multi-delivery	Partially. Standard D365 can consolidate invoices and account for the revenue/tax; AFNOR line-level multi-order/multi-delivery semantics may require ER/format mapping.	Yes, with MS accounts receivable and by sending invoices with Document Integration.
2	Case 2: Invoice already paid by the BUYER or a third-party PAYER at the time the invoice is issued	Yes for accounting. Payment status generation for AFNOR/PPF requires the e-invoicing layer.	Yes, with MS accounts receivable and by manually sending invoices with Document Integration.
3	Case 3: Invoice payable by a third-party PAYER known at the time of invoicing	Partially. Accounting can be represented through payments and settlement; structured third-party PAYER data and lifecycle delegation require extension/PA mapping.	Yes, with MS accounts receivable and by sending invoices with Document Integration.
4	Case 4: Invoice payable by the buyer and partially covered by a third party known at the time of invoicing (subsidy, insurance, etc.)	Partially. Multiple payments/settlements are standard; AFNOR third-party payer blocks and VAT-rate payment detail need mapping/extension.	Yes, with MS accounts receivable and by sending invoices with Document Integration.
5	Case No. 5: Expenses paid by employees with invoices in the company's name	Yes for accounting, mostly AP-side. France e-invoice receipt/routing may require AP e-invoicing integration.	e-reporting by MS N/A for ExFlow AP or DI
6	Case No. 6: Expenses paid by employees without an invoice addressed to the company (simple receipt or invoice made out to the employee's name and address)	Partially. Expense can be recorded; VAT deductibility and later invoice request require process controls.	e-reporting by MS N/A for ExFlow AP or DI
7	Case No. 7: Invoice following a purchase paid for with a corporate card (purchasing card)	Partially. Corporate card expense accounting is standard; AFNOR already-paid invoice and Payment received lifecycle require e-invoicing mapping.	e-reporting by MS N/A for ExFlow AP or DI
8	Case No. 8: Invoice payable to a third party determined at the time of invoicing (factoring, cash pooling)	Partially. Revenue and receivable accounting are standard; factored invoice type, payee block and status sharing require extension.	Yes, with MS accounts receivable (Note:depending on customer factoring mode) and by sending invoices with Document Integration.
9	Case No. 9: Invoice payable to a third party known at the time of invoicing, who also manages the order/receipt, or even invoicing (Distributor / Depositary)	Partially. Core accounting is possible; third-party operational roles require project-specific configuration/integration.	Not supported (pending more evaluation).
10	Case No. 10: Invoice payable to a third-party payee unknown at the time the invoice was created, in particular a factoring company (case of subrogation)	Partially/requires customization for full AFNOR flow. Standard D365 can track collections and settlement but not reissue posted invoice payee through lifecycle status.	Not supported with Document integration.
11	Case No. 11: Invoice to be received and processed by a third party on behalf of the BUYER	Partially. D365 can support delegated AP workflow/users; electronic-address delegation to PA/third party is external.	Yes, using intercompany and Invoice accounts.
12	Case No. 12: Transparent intermediary managing invoices for its principal BUYER	Partially. Accounting can remain with buyer; transparent intermediary access and PA delegation require integration.	Not supported (pending more evaluation).
13	Case No. 13: Invoice payable by a third party: subcontracting with direct payment or payment delegation	Partially. Project/vendor/customer accounting can be represented; direct-payment lifecycle semantics require customization/PA.	Not supported (pending more evaluation). Lifecycle status for encaisée would miss data when direct payment to subcontractor.
14	Case No. 14: Invoice payable by a third party: joint contracting case B2B	Partially/project-specific. Standard D365 can account invoices/payments, but AFNOR co-contracting roles are not standard.	Not supported with Document integration.
15	Case No. 15: Sales invoice following an order (and possible payment) by a third party on behalf of the BUYER ( )	Partially. D365 supports invoice account/delivery/payment handling; third-party orderer/payer semantics need extension.	Not supported with Document integration.
16	Case No. 16: Expense invoice for reimbursement of the sales invoice paid by the third party	Partially. Representation depends on whether it is AP reimbursement, AR recharge, or expense recovery.	N/A Out of e-invoicing reform per AFNOR Z12-014.
17a	Case No. 17a: Invoice payable to a third party, payment intermediary (e.g., on Marketplace)	Partially. Payment/fee accounting is standard; marketplace intermediary lifecycle role requires integration.	Not supported (pending more evaluation) It may require manual process.
17b	Case No. 17b: Invoice payable to a third party, payment intermediary, and third-party invoicing under an invoicing mandate	Partially/requires integration. Standard D365 can post the financial result; mandate handling and issuer identity require custom/ISV.	Not supported (pending more evaluation) It may require manual process.
18	Case No. 18: Management of debit notes	Yes.	Not supported with Document integration.
19a	Case No. 19a: Invoice issued by a third-party invoicing with an invoicing mandate	Partially. D365 can post seller AR invoices; mandate-based external issuance requires integration/control.	Not supported (pending more evaluation).
19b	Case No. 19b: Self-billing	No, Partially/not native end-to-end. D365 can account the seller’s AR invoice or buyer’s AP invoice; automated self-billed AR import usually requires customization.	Not supported with Document integration.
20	Cases 20 and 21: Pre-payment invoice and final invoice after advance payment	Yes.	Planned, avaliable from MS version 10.0.49.
21	Cases 20 and 21: Pre-payment invoice and final invoice after advance payment	Yes.	Yes
22a	Case No. 22a: Invoice paid with early payment discount for services for which VAT is payable upon receipt of payment	Partially. Cash discounts and settlement are standard; VAT-on-receipt lifecycle/payment detail requires configuration and e-invoicing mapping.	Yes
22b	Case No. 22b: Invoice paid with allowance for deliveries of goods (or provision of services with VAT option on debits)	Yes, mostly.	Yes
23	Case No. 23: Self-billing flow between an individual and a professional	No for standard end-to-end AFNOR flow. D365 can post accounting documents manually, but this is not a standard France D365 self-billing flow.	Not supported with Document integration.
24	Case No. 24: Management of Deposit (“Arrhes”)	Partially. Accounting for deposits/prepayments is supported; legal distinction of arrhes requires configuration/process.	Deposits are outside the scope of VAT; they are not covered by e-invoicing or e-reporting.
25	Case No. 25: Management of vouchers and gift cards	Partially. D365 Commerce supports gift cards; Finance-only requires accounting design/integration.	Not supported, not applicable for D365 Finance.
26	Case No. 26: Invoices with contractual reservation clauses	Partially. Clause can be represented as text/terms; structured AFNOR semantic mapping may require ER.	Not supported, Not standard D365 ER Configuration customization needed.
27	Case No. 27: Management of toll tickets sold to a taxable entity	Partially/industry-specific.	Not supported with Document integration. Industry specific.
28	Case No. 28: Management of restaurant bills issued by a SELLER subject to tax established in France	Partially/usually outside core Finance.	Not supported. Industry specific. Depending on D365 Finance flow, transactions will be reported in e-reporting.
29	Case No. 29: Single Taxable Entity within the meaning of Article 256 C of the CGI	Partially. Accounting and tax registrations can be configured; mandate-specific routing/reporting may need customization.	Planned, Pending feature from MS version 10.0.49.
30	Case No. 30: VAT already collected - Transactions initially processed in B2C e-reporting, subject to a retrospective invoice	Partially. Invoice can be issued, but preventing double VAT/e-reporting requires controls.	Not supported (pending more evaluation). Check ER Configuration S7,B7.
31	Case No. 31: ""Mixed"" invoices mentioning a main transaction and an ancillary transaction	Yes with configuration, but AFNOR classification may require ER mapping.	e-reporting by MS N/A for ExFlow AP or DI
32	Case No. 32: Monthly payments	Partially. Recurring invoices and payment schedules are supported; AFNOR monthly-payment reporting needs design.	AFNOR Z12-014 Feb2026: still under discussion in France.
33	Case No. 33: Transactions subject to the margin scheme -profit	Partially/custom tax design.	Yes, Note: Requires specific tax setup in D365.
34	Case No. 34: Partial payment receipt and cancellation of payment receipt	Yes for accounting; partially for lifecycle/status cancellation.	Yes
35	Case No. 35: Author's notes	Partially/custom.	AFNOR Z12-014 Feb2026: still under discussion in France.
36	Case No. 36: Transactions subject to professional secrecy and exchanges of sensitive data	Partially. Security and accounting are supported; payload minimization requires process/ER design.	Yes, Supported but D365 security and GDPR compliance and Pagero account access needed.
37	Case No. 37: SEP (Sociétés en Participation)	Partially/project-specific.	Not supported (pending more evaluation).
38	Case No. 38: Invoices with sub-lines and line groupings	No, confirmed by MS that the ER Configs are not supporting it. D365 can represent components/lines; AFNOR sub-line XML structure requires ER customization.	Yes, NOTE: It has been confirmed by MS that the ER Configs are not supporting it. D365 can represent components/lines; AFNOR sub-line XML structure requires ER customization.
39	Case No. 39: Transparent intermediary consolidating sales from multiple Sellers for the same buyer – Multi-Vendor Invoice	No, for true AFNOR multi-vendor invoice in standard Finance. Separate documents can be accounted; single legal multi-seller invoice requires custom/ISV.	Not supported with Document integration.
40	Case No. 40: Grouped payments, netting, or compensation in the event of cross-purchases/sales	Partially. Accounting netting can be represented; AFNOR lifecycle/reporting for grouped compensation may require extension.	Not supported, To be investigated.
41	Case No. 41 Barter Companies	Partially. Invoices and offsets can be accounted; barter-company-specific flow requires process/customization.	Not supported, Industry specific.
42	Case No. 42: Tax exemption management	Yes, with correct tax setup; specialized exemption operator scenarios may need mapping.	Yes, Supported from ExFlow perspective as long as D365 Finance tax and e-reporting are setup correctly.
43	Case No. 43: E-reporting for international B2B	Partially. Cross-border invoices can be accounted in D365; France Flow 10 e-reporting requires e-reporting integration.	Yes, Supported using: - eReporting - If desired, sending xborder e-invoices via Peppol (or other networks) - Tax coding will be required
43a	Case No. 43a: Triangular transactions	Partially. Tax/accounting can be configured; e-reporting classification needs ER/PA mapping.	Yes, Supported using: - eReporting - If desired, sending cross border e-invoices via Peppol (or other networks) - Tax coding will be required
43b	Case No. 43b: Stock transfers treated as intra-Community supply	Partially. Inventory and intercompany flows exist; VAT/e-reporting treatment requires configuration/design.	e-reporting N/A applicable for ExFlow
44	Case No. 44: Transactions with entities established in the DROMs/COMs/TAAFs	Partially. D365 can account transactions using country/region/tax setup; France mandate classification needs dedicated rules.	Yes, Supported. D365 Finance Tax setup and customization of ER Configuration is required by Customer or D365 partner.