E-Invoicing and E-Reporting FAQs

Accounts Receivable: Issuing customer invoices and receiving payments.

Order Entry: Single order invoicing and credit notes.

Accounts Payable: Receiving vendor invoices (with or without AP Automation) and paying vendors.

Purchasing: Converting purchase orders to vendor invoices (planned availability).

General Ledger: Reconciling B2C journals, and e-reporting.

Invoice: A regular invoice is not sent electronically to the customer.

E-Invoice: The invoice is sent electronically to the customer and routed through your PA for processing.

E-Reporting: The invoice is included in the e-reporting process.

Currently, Intacct only supports UBL for inbound e-invoices.

Yes, e-invoices follow your company's defined approval process as usual.

Company

• Update French tax solution to TVA française - SYS

• Based currency: EUR

• Subscribe to E-Invoicing for France

Entity

• Register Sage PA or another service provider for each entity

• Configure the required legal information (SIREN, SIRET, VAT ID, legal name, address and contact information)

General Ledger

• Create dedicated B2C journals (sales and payments) for e-reporting

• Create dedicated non-offset GL accounts for B2C transactions

• Enable reconciliation on these accounts for B2C reporting purposes

Business Partner

• Configure VAT number (mandatory for domestic B2B customers), ISO country code, SIRET, and the electronic routing identifier where applicable

The electronic address for receiving e-invoices is the SIREN number of your legal entity.

No, but you can connect to a demo PA to test the e-invoicing (but not e-reporting) workflow. In your production company, connect to Sage PA demo for testing, and then switch to Sage PA for live transactions.

1. Create dedicated journals for B2C sales and B2C payments.

   Go to General Ledger > Setup > Journals, create the journals, and classify them as e-reporting journals.

2. Create dedicated 411* GL accounts for B2C transactions.

3. Enable reconciliation on the relevant B2C accounts (typically 411*, 512*, 53*, and 445* accounts).

You can create a new vendor and then assign the e-invoice to the vendor.

There are several reasons why E-Invoice is unavailable.

• You're at the top level: You cannot create e-invoices at the top level. Switch to an entity to create the e-invoice.

• The entity is not enabled: E-Invoicing is not enabled for the entity, or the setup is not completed yet. Finish enabling the entity for E-Invoicing.

• Sales invoice posting is not set to AR: The Order Entry transaction definition for sales invoice transactions does not post to Accounts Receivable. Edit your sales invoice transaction definition to post to Accounts Receivable so that you can create e-invoices in Order Entry.

Disputed: The recipient does not agree with the e-invoice and has raised a query. The e-invoice will ultimately be either approved or refused.

Refused: The recipient has refused the e-invoice, and it will not proceed any further.

See View the status of a sent e-invoice for information about the different statuses.

When a submitted e-invoice has been posted and transmitted, you can no longer modify it. To make a correction, you need to issue a credit note (negative invoice) and then issue a new corrected e-invoice if required.

Create an invoice in Accounts Receivable or create a sales invoice in Order Entry following the e-invoicing flow, and enter negative amounts (sometimes called a "negative invoice") or positive amounts to adjust the customer's due amount. Currently, E-Invoicing does not support AR adjustments.

Under the French Electronic Invoicing Reform (RFE), to correct a payment that was reported incorrectly, reverse the payment to restore the outstanding balance on the original invoice. Reversing the payment using the same amounts and VAT rates as the original payment creates a complete audit trail of the reversal.

1. Go to Accounts Receivable > All > Payments > Posted payments.

2. Select the payment, and select Reverse.

Yes, you can, but there are some additional steps you need to follow when setting up your French entity to allow you to generate UBL files. You also need to be subscribed to AP Automation if you want to receive and process incoming e-invoices.

International B2B invoices are managed through Accounts Receivable. The invoice type must be set to E-Reporting so that these invoices are included in the generated e-reporting submission.

GL account reconciliations is the process in which you manually match debits and credits using unique lettering codes, making it easy to find unmatched entries so that you can focus on exceptions. In this context, it involves matching a customer payment to the original sales transaction. This process is critical for B2C e-reporting for the following reasons:

• Payments recorded directly in the General Ledger do not contain VAT details.

• The applicable VAT rate can only be determined by linking the payment to the original invoice transaction.

• The GL matching date represents the VAT chargeability date for services subject to the VAT-on-collection regime.

• Without GL matching, Intacct cannot produce the mandatory B2C payment allocation by VAT rate required by the DGFiP. As a result, the corresponding e-reporting submission cannot be generated or transmitted.

No. Intacct cannot enforce GL matching. It’s the customer's responsibility to reconcile transactions using GL account reconciliations to ensure that the B2C e-reporting submission is complete, and accurately reflects all reportable transactions.

The B2C sales flow reports aggregated B2C sales data by transaction date, transaction category, and VAT rate, as required by the DGFiP. It covers sales made to final consumers (non-taxable persons). Intacct automatically aggregates eligible GL entries and generates the DGFiP-compliant XML payload.

B2C classification relies on three cumulative criteria:

• The journal is configured as an e-reporting B2C journal

• The GL account is identified as a dedicated B2C account (for example a dedicated 411* account)

• The GL transaction is entered as either B2C Sales or B2C Payment

When these conditions are met, Intacct automatically aggregates transactions according to the DGFiP requirements:

• B2C sales are aggregated by transaction date, transaction category, and VAT rate.

• B2C payments (services subject to VAT on collection) are aggregated by collection date and VAT rate, provided the GL reconciliation has been completed to identify the applicable VAT rate.

The B2C payment flow applies to services subject to VAT on collection. VAT becomes chargeable when payment is received rather than when an invoice is issued. This flow relies on GL account reconciliations(matching) to establish the relationship between the payment and the originating transaction, allowing Intacct to determine the applicable VAT rate for reporting purposes.