SBDH values

When submitting an invoice, use these values alongside the standard SBDH configuration in Create a Standard Business Document.

InputSchema values

Set Scope: Mapping.InputSchema to one of the following values depending on the file format you are submitting:

Embedding the invoice

How you embed the invoice depends on the format. For SCI format, the invoice XML goes directly inside <svs:SovosCanonicalInvoice>. For all other formats (UBL, CII, Factur-X), the document is Base64-encoded and placed in <svs:SovosLegalDocument>:

SCI format:

<svs:SovosDocument>
  <svs:SovosCanonicalInvoice>
    <Invoice>
      <!-- Invoice XML here -->
    </Invoice>
  </svs:SovosCanonicalInvoice>
</svs:SovosDocument>

All other formats (UBL, CII, Factur-X):

<svs:SovosDocument>
  <svs:SovosLegalDocument>
    <enc:Base64Document>
      <enc:EmbeddedDocument id="[INV-2026-001]"
                           fileName="invoice.xml"
                           mimeCode="application/xml">
        [Base64-encoded invoice XML]
      </enc:EmbeddedDocument>
    </enc:Base64Document>
  </svs:SovosLegalDocument>
</svs:SovosDocument>

Invoice schema

A UBL invoice opens with namespace declarations on the root <Invoice> element, followed by header fields, party blocks, tax totals, monetary totals, and one or more invoice lines.

The cbc: prefix marks simple values (text, dates, codes, amounts). The cac: prefix marks structured blocks (parties, addresses, line items). Both are defined by the namespace declarations and are required for the document to be valid.

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
  xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
  xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">

  <cbc:CustomizationID>urn:cen.eu:en16931:2017</cbc:CustomizationID>
  <cbc:ProfileID>B1</cbc:ProfileID>
  <cbc:ID>INV-2026-001</cbc:ID>
  <cbc:IssueDate>2026-05-01</cbc:IssueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>

  <cac:AccountingSupplierParty>...</cac:AccountingSupplierParty>
  <cac:AccountingCustomerParty>...</cac:AccountingCustomerParty>
  <cac:TaxTotal>...</cac:TaxTotal>
  <cac:LegalMonetaryTotal>...</cac:LegalMonetaryTotal>
  <cac:InvoiceLine>...</cac:InvoiceLine>

</Invoice>

Header fields

Validation

• CustomizationID — Use urn:cen.eu:en16931:2017 for the EN16931 profile.

• ID (invoice number) — Must be unique. The PPF performs a blocking check across the combination of invoice number + issue year + seller SIREN. A match on all three is rejected. Numbers must follow sequential numbering rules per BOFIP BOI-TVA-DECLA-30-20-20-10 (BR-FR-CO-02).

• IssueDate — Must not be a future date (BR-FR-CO-01).

• InvoiceTypeCode — Must be one of the reform-approved codes. Common values: 380 (standard), 381 (credit note), 384 (corrective), 386 (down payment), 389 (self-billed). Full list in AFNOR XP Z12-012.

Seller block

<cac:AccountingSupplierParty>

<cac:AccountingSupplierParty>
  <cac:Party>
    <cbc:EndpointID schemeID="0225">123456789</cbc:EndpointID>
    <cac:PartyIdentification>
      <cbc:ID schemeID="0009">12345678900012</cbc:ID>  <!-- SIRET, optional -->
    </cac:PartyIdentification>
    <cac:PartyName>
      <cbc:Name>Acme SAS</cbc:Name>
    </cac:PartyName>
    <cac:PostalAddress>
      <cbc:StreetName>12 rue de la Paix</cbc:StreetName>
      <cbc:CityName>Paris</cbc:CityName>
      <cbc:PostalZone>75001</cbc:PostalZone>
      <cac:Country>
        <cbc:IdentificationCode>FR</cbc:IdentificationCode>
      </cac:Country>
    </cac:PostalAddress>
    <cac:PartyTaxScheme>
      <cbc:CompanyID>FR40123456789</cbc:CompanyID>
      <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
    </cac:PartyTaxScheme>
    <cac:PartyLegalEntity>
      <cbc:RegistrationName>Acme SAS</cbc:RegistrationName>
      <cbc:CompanyID schemeID="0002">123456789</cbc:CompanyID>
    </cac:PartyLegalEntity>
  </cac:Party>
</cac:AccountingSupplierParty>

Validation

• EndPointID — Required for France e-invoicing. Must begin with the seller's SIREN, e.g. 123456789 or 123456789_site1. schemeID must be 0225. Alphanumeric characters plus -, _, . only. Max 125 characters (BR-FR-13, BR-FR-23, BR-FR-25).

• PartyLegalEntity/CompanyID — Required for France. Exactly 9 digits. Must be registered and active in the PPF Annuaire. schemeID must be 0002 (BR-FR-10).

• PartyIdentification/ID (SIRET) — If provided, must be exactly 14 digits. schemeID must be 0009. First 9 digits must match the seller's SIREN (BR-FR-09).

Buyer block

<cac:AccountingCustomerParty>

<cac:AccountingCustomerParty>
  <cac:Party>
    <cbc:EndpointID schemeID="0225">987654321</cbc:EndpointID>
    <cac:PartyLegalEntity>
      <cbc:RegistrationName>Buyer Corp SAS</cbc:RegistrationName>
      <cbc:CompanyID schemeID="0002">987654321</cbc:CompanyID>
    </cac:PartyLegalEntity>
    <cac:PostalAddress>
      <cbc:CityName>Lyon</cbc:CityName>
      <cbc:PostalZone>69001</cbc:PostalZone>
      <cac:Country>
        <cbc:IdentificationCode>FR</cbc:IdentificationCode>
      </cac:Country>
    </cac:PostalAddress>
  </cac:Party>
</cac:AccountingCustomerParty>

Validation

• EndpointID — Required for France e-invoicing. Sovos queries the PPF directory with this value to route the invoice to the buyer's PDP. Must begin with the buyer's SIREN. schemeID must be 0225. Alphanumeric characters plus -, _, . only. Max 125 characters. If not found or not active in the PPF directory, the invoice is rejected (BR-FR-12, BR-FR-21, BR-FR-23, BR-FR-25).

• PartyLegalEntity/CompanyID — Required for France e-invoicing scope. Exactly 9 digits. Must be active in the PPF Annuaire. schemeID must be 0002 (BR-FR-11)

Tax total

<cac:TaxTotal>

<cac:TaxTotal>
  <cbc:TaxAmount currencyID="EUR">200.00</cbc:TaxAmount>
  <cac:TaxSubtotal>
    <cbc:TaxableAmount currencyID="EUR">1000.00</cbc:TaxableAmount>
    <cbc:TaxAmount currencyID="EUR">200.00</cbc:TaxAmount>
    <cac:TaxCategory>
      <cbc:ID>S</cbc:ID>
      <cbc:Percent>20</cbc:Percent>
      <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
    </cac:TaxCategory>
  </cac:TaxSubtotal>
</cac:TaxTotal>

Validation

• All amount fields (TaxAmount, TaxableAmount) — Max 19 digits total, max 2 decimal places. Use . as the decimal separator. A - sign counts as one character (BR-FR-DEC-01).

• TaxCategory/ID — France accepts only: S (standard), E (exempt), AE (reverse charge), K (intra-community), G (export), O (out of scope), Z (zero rate) (BR-FR-15).

• TaxCategory/Percent — Express as a percentage, e.g. 20 not 0.20. Must be a France-permitted rate. Most common: 0, 2.1, 5.5, 10, 20. Full list in AFNOR XP Z12-012 (BR-FR-16).

Monetary totals

<cac:LegalMonetaryTotal>

<cac:LegalMonetaryTotal>
  <cbc:LineExtensionAmount currencyID="EUR">1000.00</cbc:LineExtensionAmount>
  <cbc:TaxExclusiveAmount currencyID="EUR">1000.00</cbc:TaxExclusiveAmount>
  <cbc:TaxInclusiveAmount currencyID="EUR">1200.00</cbc:TaxInclusiveAmount>
  <cbc:PayableAmount currencyID="EUR">1200.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>

Validation

All amount fields — Max 19 digits total, max 2 decimal places. Use . as the decimal separator (BR-FR-DEC-01).

Invoice lines

<cac:InvoiceLine>

<cac:InvoiceLine>
  <cbc:ID>1</cbc:ID>
  <cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>
  <cbc:LineExtensionAmount currencyID="EUR">1000.00</cbc:LineExtensionAmount>
  <cac:Item>
    <cbc:Name>Consulting</cbc:Name>
    <cbc:Description>Q1 consulting services</cbc:Description>
    <cac:ClassifiedTaxCategory>
      <cbc:ID>S</cbc:ID>
      <cbc:Percent>20</cbc:Percent>
      <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
    </cac:ClassifiedTaxCategory>
  </cac:Item>
  <cac:Price>
    <cbc:PriceAmount currencyID="EUR">100.00</cbc:PriceAmount>
  </cac:Price>
</cac:InvoiceLine>

Validation

• ID — Must be unique within the invoice.

• InvoicedQuantity — Max 19 digits total, max 4 decimal places (BR-FR-DEC-02).

• LineExtensionAmount — Max 19 digits total, max 2 decimal places (BR-FR-DEC-01).

• ClassifiedTaxCategory/ID — Same allowed values as the header tax block: S, E, AE, K, G, O, Z (BR-FR-15).

• ClassifiedTaxCategory/Percent — Must be a France-permitted rate (BR-FR-16).

Payment means

<cac:PaymentMeans>

<cac:PaymentMeans>
<cbc:PaymentMeansCode name="Virement">30</cbc:PaymentMeansCode>
<cbc:PaymentID>200000008_UC4_2023001</cbc:PaymentID>
<cac:PayeeFinancialAccount>
	<cbc:ID>FR76 1254 2547 2569 8542 5874 660</cbc:ID>
	<cbc:Name>Nom de compte de paiement</cbc:Name>
	<cac:FinancialInstitutionBranch>
		<cbc:ID>BICBANQUE</cbc:ID>
	</cac:FinancialInstitutionBranch>
</cac:PayeeFinancialAccount>
</cac:PaymentMeans>

Validation

• PaymentMeansCode — Required when the <cac:PaymentMeans> block is present. Use UNTDID 4461 codes. Common values for France: 30 (credit transfer), 49 (direct debit), 57 (standing agreement), 58 (SEPA credit transfer).

• PayeeFinancialAccount/ID — Use IBAN format for SEPA payments, e.g. FR7612345678901234567890189.

• FinancialInstitutionBranch/ID — Use BIC/SWIFT format when provided, e.g. BNPAFRPPXXX.

Additional document reference

<cac:AdditionalDocumentReference>

Use <cac:AdditionalDocumentReference> to attach supporting documents to an invoice, such as a PDF visual representation. The block repeats — include one instance per attachment. Under the France e-invoicing mandate, the structured XML is the legally valid invoice. The DGFiP treats any embedded PDF as a visual representation only — it has no legal standing.

<cac:AdditionalDocumentReference>
  <cbc:ID schemeID="[UNTDID-1153-code]">INV-2026-001-attachment</cbc:ID>
  <cbc:DocumentTypeCode>[document-type-code]</cbc:DocumentTypeCode>
  <cbc:DocumentDescription>Invoice PDF representation</cbc:DocumentDescription>
  <cac:Attachment>
    <cbc:EmbeddedDocumentBinaryObject
        mimeCode="application/pdf"
        filename="INV-2026-001.pdf">
      JVBERi0xLjQKJ...
    </cbc:EmbeddedDocumentBinaryObject>
  </cac:Attachment>
</cac:AdditionalDocumentReference>

Validation

• EmbeddedDocumentBinaryObject and ExternalReference/URI are mutually exclusive within a single <cac:Attachment> — use one or the other, not both.

• mimeCode and filename — Both attributes are required when EmbeddedDocumentBinaryObject is present. Permitted MIME types: application/pdf, image/png, image/jpeg, text/csv, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, application/vnd.oasis.opendocument.spreadsheet.

• ID — Max 50 characters (supporting document reference) or 100 characters (invoiced object identifier).

• ID @schemeID — Max three characters.

• DocumentDescription — Max 100 characters.

• @mimeCode — Max 100 characters.

• @filename — Max 100 characters.

• ExternalReference/URI — Max 100 characters.

France-specific fields

These elements use standard UBL structure but carry France-specific values required by the reform.

ProfileID — invoicing framework

<cbc:ProfileID> declares the invoicing context. Required for France.

Code	Description
B1	Goods invoice
S1	Services invoice
M1	Mixed goods and services
B2	Goods invoice — already paid
S2	Services invoice — already paid
B4 / S4 / M4	Final invoice after down payment
S5	Subcontractor services invoice
S6	Co-contractor services invoice
B7 / S7	Invoice already subject to e-reporting

Note — subject-coded notes

<cbc:Note> elements carry structured information when prefixed with a subject code separated by #:

<cbc:Note>#BAR#B2B</cbc:Note>
<cbc:Note>#PMT#Payment by bank transfer to IBAN FR76...</cbc:Note>
<cbc:Note>#AAI#General invoice footer information</cbc:Note>

Subject code	Purpose
BAR	Treatment scope: B2B (e-invoicing), B2BINT (cross-border B2B e-reporting), B2C (B2C e-reporting), OUTOFSCOPE.
PMT	Payment instructions.
PMD	Payment method description.
AAI	General information, e.g. invoice footer text.
AAB	Payment terms.
SUR	Seller remarks.
ABL	Legal information, e.g. trade register number.

Corrective invoices and credit notes

• If InvoiceTypeCode is a corrective type (384 and variants), exactly one prior invoice reference and its issue date must be present at header level (BR-FR-CO-04)

• If InvoiceTypeCode is a credit note (381 and variants), at least one prior invoice reference must be present at header level, or a line-level reference must appear in every invoice line (BR-FR-CO-05)

Complete SBD example

The sample files below are complete, production-ready SBD payloads in the exact format required for POST /v1/documents. Each contains a full SBDH wrapper with the invoice XML Base64-encoded inside <enc:EmbeddedDocument>.

To inspect the invoice XML: decode the Base64 content from <enc:EmbeddedDocument> to view the full structure including all parties, tax totals, and line items. Your own payloads must also Base64-encode the invoice XML before embedding.

Download sample — standard goods invoice (B1)

Download sample — services invoice (S1)