Standard Business Document structure
Every invoice sent to Sovos must be wrapped in a Standard Business Document (SBD) that contains routing metadata and the invoice in UBL-TR 1.2 format.
Overview
The SBD is the envelope format used to submit invoices to Sovos. The SBD contains:
- Standard Business Document Header (SBDH)
-
Routing metadata such as the sender, receiver, and product ID. For details, see About the Standard Business Document.
- Sovos Document
-
The UBL-TR 1.2 invoice document encoded in Base64. For details, see Sovos Document.
SBD structure
<sbd:StandardBusinessDocument>
<sbd:StandardBusinessDocumentHeader>
<sbd:HeaderVersion>1.0</sbd:HeaderVersion>
<sbd:Sender>...</sbd:Sender>
<sbd:Receiver>...</sbd:Receiver>
<sbd:DocumentIdentification>...</sbd:DocumentIdentification>
<sbd:BusinessScope>...</sbd:BusinessScope>
</sbd:StandardBusinessDocumentHeader>
<svs:SovosDocument>
<svs:SovosLegalDocument>
<enc:Base64Document>
<enc:EmbeddedDocument>[Base64-encoded UBL-TR Invoice]</enc:EmbeddedDocument>
</enc:Base64Document>
</svs:SovosLegalDocument>
</svs:SovosDocument>
</sbd:StandardBusinessDocument>
SBDH configuration requirements
- Sender (seller)
-
The sender identifier uses the Vergi Kimlik Numarası (VKN) number with
Authority="TR". TheContactelement typically also contains the VKN number.<sbd:Sender> <sbd:Identifier Authority="TR">0100478064</sbd:Identifier> <sbd:ContactInformation> <sbd:Contact>0100478064</sbd:Contact> </sbd:ContactInformation> </sbd:Sender> - Receiver (buyer)
-
For e-Arşiv invoices to individuals, use the Türkiye Cumhuriyeti Kimlik Numarası (TCKN) (personal identification number) in the Identifier element. For simplified invoices where the buyer may not have a VKN, you can leave the field empty:
<sbd:Identifier Authority="TR"></sbd:Identifier><sbd:Receiver> <sbd:Identifier Authority="TR">7730357215</sbd:Identifier> <sbd:ContactInformation> <sbd:Contact>7730357215</sbd:Contact> </sbd:ContactInformation> </sbd:Receiver> - Document identification
-
The
InstanceIdentifiermust be aCorrelationID(UUID) and must match theInstanceIdentifierfrom theSenderDocumentIdscope.<sbd:DocumentIdentification> <sbd:Standard>urn:oasis:names:specification:ubl:schema:xsd:Invoice-2</sbd:Standard> <sbd:TypeVersion>2.1</sbd:TypeVersion> <sbd:InstanceIdentifier>A88B1596-AADA-4D5E-81C4-3C92AE0F505F</sbd:InstanceIdentifier> <sbd:Type>Invoice</sbd:Type> <sbd:MultipleType>false</sbd:MultipleType> <sbd:CreationDateAndTime>2025-08-15T20:38:09Z</sbd:CreationDateAndTime> </sbd:DocumentIdentification> - Business scope
-
The
BusinessScopenode contains multipleScopeelements that define processing instructions.Scope Type Description Example Values SenderDocumentId Unique document identifier (UUID) A88B1596-AADA-4D5E-81C4-3C92AE0F505F SenderSystemId Customer system identifier AIRCANADATR, YOURSYSTEMID CompanyCode Sender VKN 0100478064 Country Country code TR ProcessType Document direction outbound, inbound BusinessCategory Transaction type BusinessToBusiness, BusinessToConsumer Mapping.TransformDocument Transformation mapping LEGAL-TO-SCI_INVOICE Mapping.OutputSchema Output format E-Fatura, E-Arsiv BusinessProcess Processing workflow default Important:The
SenderDocumentIdmust be the same as the document UUID. When you resubmit a failed invoice, do not change the UUID.Sample
BusinessScopenode:<sbd:BusinessScope> <sbd:Scope> <sbd:Type>SenderDocumentId</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>A88B1596-AADA-4D5E-81C4-3C92AE0F505F</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>SenderSystemId</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>AIRCANADATR</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>CompanyCode</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>0100478064</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>Country</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>TR</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>ProcessType</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>outbound</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>BusinessCategory</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>BusinessToBusiness</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>Mapping.TransformDocument</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>LEGAL-TO-SCI_INVOICE</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>Mapping.OutputSchema</sbd:Type> <sbd:InstanceIdentifier /> <sbd:Identifier>E-Fatura</sbd:Identifier> </sbd:Scope> <sbd:Scope> <sbd:Type>BusinessProcess</sbd:Type> <sbd:InstanceIdentifier /> <sbd:BusinessService> <sbd:BusinessServiceName>default</sbd:BusinessServiceName> </sbd:BusinessService> </sbd:Scope> </sbd:BusinessScope>
Turkey-specific SBDH requirements
- VKN format
-
10 digits, no separators. For example, 0100478064.
- Time zone
-
Use the Turkey time zone (TRT, UTC+3) for all timestamps.
- Invoice numbering
-
Alphanumeric series with sequential numbering (for example, ABC2025000001), maintained and assigned by Sovos Cloud, based on the document type.
