Setting up Electronic Invoicing for France

French electronic invoicing (e-invoicing) enables Certinia to send and receive compliant e-invoices in France through Storecove, supporting B2B, B2G (business-to-government), and B2C document types.

Before you send or receive Accounting documents for France, you must carry out the following configuration tasks. If you are already using Storecove, ignore steps 1 and 2.

Note: The Continuous Transactions Controls (CTC) option from Storecove is required for France. Contact Storecove Support to enable the CTC option.

Step 1: Set up Storecove Electronic Invoicing Connector

Ensure that the Storecove Connector is configured. For more information, see Electronic Invoicing Settings.

Step 2: Enable Electronic Invoicing with Storecove Feature

Make sure that the Electronic Invoicing with Storecove feature is enabled in Feature Console. For more information, see Setting up Electronic Invoicing with Storecove.

This Feature Console page allows you to enable the feature for connecting Certinia applications with Storecove for electronic invoicing purposes.

Step 3: Configure Legal Entities in Storecove

Ensure that a minimum of two distinct legal entities are configured in Storecove: one designated as the sender and the other as the receiver. For more information, see Storecove Help.

Step 4: Set up an Account Extension

For each Account that will receive or send e-invoices, establish an account extension within the Account Extension object. This extension must incorporate the Account's identifier data and E-Invoicing Address Scheme. For more information, see Creating an Account Extension.

For each account you also need to configure the E-Invoicing Document Entity Type field on each Account Extension record to specify the default document entity type for e-invoices sent from or received by that account. This is a new field, and you must manually add it to the Account Extension page layout before it can be populated.

  • Invoice/B2B — Standard business-to-business invoicing. This is the default.
  • Invoice/B2G — Business-to-government invoicing. Use this for accounts that are government entities.
  • Simplified invoice/ticket/B2C — Simplified invoicing for consumers.

You can also override the document entity type on individual sales invoices and sales credit notes using the Document Entity Type field. For more information, see Custom Account Fields, Sales Invoice Fields, and Sales Credit Note Fields.

Step 5: Add Tax Data on the Account Object

Make sure that the Tax Country Code field is explicitly populated with the value "FR" and that the Tax Registration Number field contains the required data within the Account object.

Step 6: Enter E-Invoicing Values for the Accounting Company

Enter the values in the following fields on the Accounting Company object:

  • E-Invoicing Legal Entity Identifier derived from the ID Legal Entity created in Storecove.
  • E-Invoicing Tax Category.

Step 7: Configure Field Mappings

French e-invoicing introduces new field mappings for additional party roles and French-specific fields. See Storecove documentation for more details.

Additional party roles

  • BuyerAgent — The agent acting on behalf of the buyer.
  • PayerParty — The party responsible for payment.
  • PayeeParty — The party to which payment is made.
  • InvoiceeParty — The party that receives and validates the invoice. Required for B2G e-invoicing to identify the government entity.
  • InvoicerParty — The party that issues the invoice.
  • PublicIdentifier — Public identifier details (ID and scheme) for each party role.

For Payable Invoices

  • Reason — The reason for the allowance or charge, free text. Defaults to 'Mutually Agreed' if neither reason nor reasonCode is provided.
  • reasonCode — Coded reason for the allowance or charge.
  • taxExemptionReason — Free-text tax-exemption reason.
  • taxExemptionReasonCode — Coded tax-exemption reason that explains why the tax on the allowance or charge is exempt or zero-rated.
  • Notes — You can map up to three note fields from the invoice header (Note 1, Note 2, Note 3).
  • Notes — You can map up to three note fields from the invoice lines (Note 1, Note 2, Note 3).
  • AdditionalItemProperties — Line-level additional item properties, including name code, value quantity, and value quantity unit code.
  • InvoiceTypeCode — The document type code for invoices.
  • FrCadreDeFacturation — Classifies whether an invoice is for goods, services, or a mixed transaction. This is a mandatory field.

For Payable Credit Notes

  • Reason — The reason for the allowance or charge, free text. Defaults to 'Mutually Agreed' if neither reason nor reasonCode is provided.
  • reasonCode — Coded reason for the allowance or charge.
  • taxExemptionReason — Free-text tax-exemption reason.
  • taxExemptionReasonCode — Coded tax-exemption reason that explains why the tax on the allowance or charge is exempt or zero-rated.
  • Notes — You can map up to three note fields from the credit note header (Note 1, Note 2, Note 3).
  • Notes — You can map up to three note fields from the credit note lines (Note 1, Note 2, Note 3).
  • AdditionalItemProperties — Line-level additional item properties, including name code, value quantity, and value quantity unit code.
  • CreditNoteTypeCode — The document type code for credit notes.
  • FrCadreDeFacturation — Classifies whether an invoice is for goods, services, or a mixed transaction. This is a mandatory field.

For Sales Invoices

  • Reason — The reason for the allowance or charge, free text. Defaults to 'Mutually Agreed' if neither reason nor reasonCode is provided.
  • reasonCode — Coded reason for the allowance or charge.
  • taxExemptionReason — Free-text tax-exemption reason.
  • taxExemptionReasonCode — Coded tax-exemption reason that explains why the tax on the allowance or charge is exempt or zero-rated.
  • Notes — You can map up to three note fields from the invoice header (Note 1, Note 2, Note 3).
  • Notes — You can map up to three note fields from the invoice lines (Note 1, Note 2, Note 3).
  • AdditionalItemProperties — Line-level additional item properties, including name code, value quantity, and value quantity unit code.
  • InvoiceTypeCode — The document type code for invoices.
  • FrCadreDeFacturation — Classifies whether an invoice is for goods, services, or a mixed transaction. This is a mandatory field.

For Sales Credit Notes

  • Reason — The reason for the allowance or charge, free text. Defaults to 'Mutually Agreed' if neither reason nor reasonCode is provided.
  • reasonCode — Coded reason for the allowance or charge.
  • taxExemptionReason — Free-text tax-exemption reason.
  • taxExemptionReasonCode — Coded tax-exemption reason that explains why the tax on the allowance or charge is exempt or zero-rated.
  • Notes — You can map up to three note fields from the credit note header (Note 1, Note 2, Note 3).
  • Notes — You can map up to three note fields from the credit note lines (Note 1, Note 2, Note 3).
  • AdditionalItemProperties — Line-level additional item properties, including name code, value quantity, and value quantity unit code.
  • CreditNoteTypeCode — The document type code for credit notes.
  • FrCadreDeFacturation — Classifies whether an invoice is for goods, services, or a mixed transaction. This is a mandatory field.

For more information on configuring field mappings, see:

Step 8: [Optional] Map the Tax Category at the Line Level

The default Storecove e-invoicing mappings use the tax category from the Accounting Company. To apply a different tax category per invoice line, update the TaxBreakdown[0].TaxCode, TaxBreakdown[1].TaxCode, and TaxBreakdown[2].TaxCode mappings to use the E-Invoicing Tax Category field on the Tax Code (c2g__TaxCategory__c) instead. For more information, see Field Mappings for Sales Invoice to Electronic Invoice and Field Mappings for Sales Credit Note to Electronic Invoice.