Sovos.com Contact Support

e-invoicing

Compliance Network Implementation Guide

Create a document

The Standard Business Document (SBD) wrapper and document body structure required for submitting invoices and other document types to Sovos.

Every document you submit to Sovos must be wrapped in an SBD. The SBD provides the routing metadata that tells Sovos what you are sending and how to process it.

SBD components

Standard Business Document Header (SBDH)
Routing metadata that includes the sender, receiver, and Malaysia-specific scope values.
Sovos document
The document body. For the Sovos Canonical Invoice (SCI) format, the invoice XML is placed directly in <svs:SovosCanonicalInvoice>. For the local format, the document is Base64-encoded and placed in <svs:SovosLegalDocument>.

SBD structure

The outer structure is the same for all document types. Only the content inside <svs:SovosDocument> changes.

SCI format
CODE 
<StandardBusinessDocument>
  <StandardBusinessDocumentHeader>
    <!-- Routing metadata -->
  </StandardBusinessDocumentHeader>
  <svs:SovosDocument>
    <svs:SovosCanonicalInvoice>
      <Invoice>...</Invoice>
    </svs:SovosCanonicalInvoice>
  </svs:SovosDocument>
</StandardBusinessDocument>
Local Malaysian UBL 2.1 format
CODE 
<StandardBusinessDocument>
  <StandardBusinessDocumentHeader>
    <!-- Routing metadata -->
  </StandardBusinessDocumentHeader>
  <svs:SovosDocument>
    <svs:SovosLegalDocument>
      <enc:Base64Document>
        <enc:EmbeddedDocument id="[Your_DocumentID]"
          fileName="[document.xml]"
          mimeCode="application/xml">
          [Base64-encoded Malaysian UBL 2.1 document]
        </enc:EmbeddedDocument>
      </enc:Base64Document>
    </svs:SovosLegalDocument>
  </svs:SovosDocument>
</StandardBusinessDocument>

Input schema values

Sovos accepts Malaysia invoices in the following formats:

Invoice (SCI)
Use MY-SCI-1.0-INVOICE-1.0.
Invoice (native Malaysian UBL 2.1)
Use MY-UBL-2.1-INVOICE-1.0.

SBDH configuration

Required SBDH elements

Most SBDH elements use fixed values for all Malaysia submissions. The values that vary by document type are noted in the Document type values section.

Sender.Identifier
Your TIN. Set Authority="MY" on the element.
Receiver.Identifier
The buyer's TIN. Set Authority="MY" on the element. For B2C consolidated invoices, use EI00000000010. The value can be empty.
DocumentIdentification.Standard
urn:oasis:names:specification:ubl:schema:xsd:Invoice-2
DocumentIdentification.TypeVersion
2.1
DocumentIdentification.InstanceIdentifier
A unique identifier for this submission, such as your invoice number.
DocumentIdentification.Type
Varies by document type. See the document type values table.
DocumentIdentification.CreationDateAndTime
Submission timestamp in ISO 8601 format, for example 2026-05-01T10:43:09+08:00. Use the Malaysia time zone offset (+08:00).
DocumentIdentification.MultipleType
false
Scope: Country
MY
Scope: CompanyCode
Your TIN.
Scope: ProcessType
Outbound
Scope: SenderDocumentId
Your document reference. Sovos recommends matching the InstanceIdentifier.
Scope: SenderSystemId
Your ERP System ID, defined during setup. Defaults to DefaultSystemERP if not configured.
Scope: Mapping.OutputSchema
UBLInvoice
Scope: Mapping.TransformDocument
SCI-TO-LEGAL_INVOICE
Scope: Transmission.OperationType
SIGNING
Scope: BusinessCategory
B2B
Scope: Version
1.0

Document type values

Type code Document type DocumentIdentification.Type value
01 Invoice Invoice
02 Credit note CreditNote
03 Debit note DebitNote
04 Refund note RefundNote
11 Self-billed invoice SelfBilledInvoice
12 Self-billed credit note SelfBilledCreditNote
13 Self-billed debit note SelfBilledDebitNote
14 Self-billed refund note SelfBilledRefundNote

Complete SBDH example

Values in square brackets must be replaced with your own data. Use all other values exactly as shown.

CODE 
<sbd:StandardBusinessDocumentHeader>
  <sbd:HeaderVersion>1.0</sbd:HeaderVersion>
  <sbd:Sender>
    <sbd:Identifier Authority="MY">[SUPPLIER_TIN]</sbd:Identifier>
  </sbd:Sender>
  <sbd:Receiver>
    <sbd:Identifier Authority="MY">[BUYER_TIN]</sbd:Identifier>
  </sbd:Receiver>
  <sbd:DocumentIdentification>
    <sbd:Standard>urn:oasis:names:specification:ubl:schema:xsd:Invoice-2</sbd:Standard>
    <sbd:TypeVersion>2.1</sbd:TypeVersion>
    <sbd:InstanceIdentifier>[INV-2026-00000001]</sbd:InstanceIdentifier>
    <sbd:Type>Invoice</sbd:Type>
    <sbd:MultipleType>false</sbd:MultipleType>
    <sbd:CreationDateAndTime>[2026-05-01T10:43:09+08:00]</sbd:CreationDateAndTime>
  </sbd:DocumentIdentification>
  <sbd:BusinessScope>
    <sbd:Scope>
      <sbd:Type>Version</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>1.0</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>SenderDocumentId</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>[INV-2026-00000001]</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>SenderSystemId</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>[Your_ERPSystemID]</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>CompanyCode</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>[Your_TIN]</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>Country</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>MY</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>ProcessType</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>Outbound</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>Mapping.TransformDocument</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>SCI-TO-LEGAL_INVOICE</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>Mapping.OutputSchema</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>UBLInvoice</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>BusinessCategory</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>B2B</sbd:Identifier>
    </sbd:Scope>
    <sbd:Scope>
      <sbd:Type>Transmission.OperationType</sbd:Type>
      <sbd:InstanceIdentifier/>
      <sbd:Identifier>SIGNING</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>
</sbd:StandardBusinessDocumentHeader>

For local Malaysian UBL 2.1 format submissions, add the following scope element to skip mapping between the Sovos Canonical Invoice (SCI) and UBL.

CODE 
<sbd:Scope>
  <sbd:Type>Mapping.TransformDocument</sbd:Type>
  <sbd:InstanceIdentifier/>
  <sbd:Identifier>LEGAL-TO-SCI_INVOICE</sbd:Identifier>
</sbd:Scope>

Invoice body

Invoice schema

A Malaysian invoice in the SCI format 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.

XML 
<?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"
  xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2">
  <cbc:ID>[Your unique invoice number]</cbc:ID>
  <cbc:IssueDate>2026-05-01</cbc:IssueDate>
  <cbc:IssueTime>10:43:09</cbc:IssueTime>
  <cbc:InvoiceTypeCode>01</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>MYR</cbc:DocumentCurrencyCode>
  ...
</Invoice>

Header fields

Field XML path Cardinality Description
Invoice number <cbc:ID> 1..1 Unique within the supplier's Tax Identification Number (TIN). It must not be reused, even if the original was rejected.
Issue date <cbc:IssueDate> 1..1 Date the invoice was issued, in the YYYY-MM-DD format. It must not be a future date.
Issue time <cbc:IssueTime> 1..1 Time the invoice was issued, in the HH:MM:SS format. Use Malaysia local time.
Invoice type code <cbc:InvoiceTypeCode> 1..1 Inland Revenue Board of Malaysia (IRBM) document type code such as 01 for invoices.
Document currency <cbc:DocumentCurrencyCode> 1..1 ISO 4217 currency code. Use MYR for domestic invoices.
Validation rules:
ID

The value must be unique within your TIN. does not generate document numbers. Duplicate document numbers result in IRBM rejection.

IssueDate
The value must not be a future date. Use Malaysia local date (+08:00 offset).
InvoiceTypeCode

The value must match an IRBM-approved document type code.

Seller block

The seller block identifies the supplier in the invoice. Use this table to map your seller registration, name, address, and classification details to the required UBL elements and cardinalities.

Element Cardinality Required Description
PartyIdentification/ID schemeID="TIN" 1..1 Yes Seller's TIN issued by IRBM.
PartyIdentification/ID schemeID="BRN" 1..1 Yes Seller's Business Registration Number (BRN) issued by the Companies Commission of Malaysia (SSM).
PartyIdentification/ID schemeID="SST" 0..1 Include if applicable Sales and Service Tax (SST) registration number.
PartyIdentification/ID schemeID="TTX" 0..1 Include if applicable Tourism Tax registration number.
IndustryClassificationCode 1..1 No MSIC code (five digits). The name attribute must contain the MSIC description.
PartyName/Name 1..1 No Seller's trading name as registered with SSM.
PostalAddress 1..1 No Business address. CountrySubentityCode must use IRBM state codes.
PartyTaxScheme/RegistrationName 1..1 No Legal name exactly as registered with SSM.

The following example shows how to populate the seller block:

CODE 
<cac:AccountingSupplierParty>
  <cac:Party>
    <cac:PartyIdentification>
      <cbc:ID schemeID="TIN">[Your_TIN]</cbc:ID>
    </cac:PartyIdentification>
    <cac:PartyIdentification>
      <cbc:ID schemeID="BRN">[Your_BRN]</cbc:ID>
    </cac:PartyIdentification>
    <cac:PartyIdentification>
      <cbc:ID schemeID="SST">[Your_SST_Number]</cbc:ID>
    </cac:PartyIdentification>
    <cac:IndustryClassificationCode name="[MSIC Description]">
      [MSIC_CODE]
    </cac:IndustryClassificationCode>
    <cac:PartyName>
      <cbc:Name>[Supplier Trading Name]</cbc:Name>
    </cac:PartyName>
    <cac:PostalAddress>
      <cbc:StreetName>[Address Line 1]</cbc:StreetName>
      <cbc:CityName>[City]</cbc:CityName>
      <cbc:PostalZone>[Postal Code]</cbc:PostalZone>
      <cbc:CountrySubentityCode>[State Code]</cbc:CountrySubentityCode>
      <cac:Country>
        <cbc:IdentificationCode>MYS</cbc:IdentificationCode>
      </cac:Country>
    </cac:PostalAddress>
    <cac:PartyTaxScheme>
      <cbc:RegistrationName>[Registered Legal Name]</cbc:RegistrationName>
      <cbc:CompanyID>[Your_TIN]</cbc:CompanyID>
      <cac:TaxScheme><cbc:ID>OTH</cbc:ID></cac:TaxScheme>
    </cac:PartyTaxScheme>
  </cac:Party>
</cac:AccountingSupplierParty>

Buyer block

The buyer block identifies the customer in the invoice. Use this table to map the buyer's identification numbers to the required UBL elements and cardinalities for different scenarios.

Element Cardinality Description
PartyIdentification/ID schemeID="TIN" 1..1 Buyer's TIN. For B2C consolidated invoices, use EI00000000010. For foreign individuals, use EI00000000010 or the passport number with schemeID="PASSPORT".
PartyIdentification/ID schemeID="BRN" 0..1 Buyer's BRN. Required for B2B invoices if the buyer is a registered business.
PartyIdentification/ID schemeID="NRIC" 0..1 Malaysian individual's National Registration Identity Card (NRIC) number. Use it when the buyer is an individual Malaysian citizen.
PartyIdentification/ID schemeID="PASSPORT" 0..1 Passport number for foreign individuals.

The following example shows how to populate the buyer block:

CODE 
<cac:AccountingCustomerParty>
  <cac:Party>
    <cac:PartyIdentification>
      <cbc:ID schemeID="TIN">[Buyer_TIN]</cbc:ID>
    </cac:PartyIdentification>
    <cac:PartyIdentification>
      <cbc:ID schemeID="BRN">[Buyer_BRN]</cbc:ID>
    </cac:PartyIdentification>
    <cac:PartyName>
      <cbc:Name>[Buyer Trading Name]</cbc:Name>
    </cac:PartyName>
    <cac:PostalAddress>
      <cbc:StreetName>[Address Line 1]</cbc:StreetName>
      <cbc:CityName>[City]</cbc:CityName>
      <cac:Country>
        <cbc:IdentificationCode>[Country Code]</cbc:IdentificationCode>
      </cac:Country>
    </cac:PostalAddress>
    <cac:PartyTaxScheme>
      <cbc:RegistrationName>[Buyer Legal Name]</cbc:RegistrationName>
      <cbc:CompanyID>[Buyer_TIN]</cbc:CompanyID>
      <cac:TaxScheme><cbc:ID>OTH</cbc:ID></cac:TaxScheme>
    </cac:PartyTaxScheme>
  </cac:Party>
</cac:AccountingCustomerParty>

Tax total

The tax total block summarizes the total tax due on the invoice and the breakdown by tax category. Use this table to map your calculated tax amounts and rates to the required UBL elements and cardinalities.

Element Cardinality Description
TaxTotal/TaxAmount 1..1 Total tax amount. It must equal the sum of all TaxSubtotal/TaxAmount values.
TaxSubtotal/TaxableAmount 1..1 Net amount subject to this tax rate.
TaxSubtotal/TaxAmount 1..1 Tax amount for this subtotal (TaxableAmount x Percent / 100).
TaxCategory/ID 1..1 Malaysia tax type code.
TaxCategory/Percent 0..1 Tax rate percentage required for taxable categories.

This example shows a single TaxTotal block with one TaxSubtotal for an 8% tax rate, where the total tax amount matches the sum of the subtotals.

CODE 
<cac:TaxTotal>
  <cbc:TaxAmount currencyID="MYR">80.00</cbc:TaxAmount>
  <cac:TaxSubtotal>
    <cbc:TaxableAmount currencyID="MYR">1000.00</cbc:TaxableAmount>
    <cbc:TaxAmount currencyID="MYR">80.00</cbc:TaxAmount>
    <cac:TaxCategory>
      <cbc:ID>02</cbc:ID>
      <cbc:Percent>8</cbc:Percent>
      <cac:TaxScheme><cbc:ID>OTH</cbc:ID></cac:TaxScheme>
    </cac:TaxCategory>
  </cac:TaxSubtotal>
</cac:TaxTotal>

Validation rules:

  • Tax amounts must be calculated at the line item level. The total tax amount is the sum of all line item tax amounts.

  • All monetary amounts must use two decimal places. Use standard rounding (round half up).

  • TaxTotal.TaxAmount must equal the sum of all TaxSubtotal.TaxAmount values.

Monetary totals

The monetary totals block summarizes the invoice amounts before tax, after tax, and the final amount due. Use this table to map your calculated totals to the required UBL elements and cardinalities.

Element Cardinality Description
LineExtensionAmount 1..1 Sum of all invoice line extension amounts before allowances, charges, and tax.
TaxExclusiveAmount 1..1 Total amount excluding tax, after document-level allowances and charges.
TaxInclusiveAmount 1..1 Total amount including tax.
AllowanceTotalAmount 0..1 Total document-level allowances.
ChargeTotalAmount 0..1 Total document-level charges.
PayableAmount 1..1 Amount due for payment.

This example shows a LegalMonetaryTotal block where the line extension amount, tax-exclusive amount, tax-inclusive amount, and payable amount are all expressed in MYR and aligned with the totals calculated from the invoice lines and tax totals.

CODE 
<cac:LegalMonetaryTotal>
  <cbc:LineExtensionAmount currencyID="MYR">1000.00</cbc:LineExtensionAmount>
  <cbc:TaxExclusiveAmount currencyID="MYR">1000.00</cbc:TaxExclusiveAmount>
  <cbc:TaxInclusiveAmount currencyID="MYR">1080.00</cbc:TaxInclusiveAmount>
  <cbc:PayableAmount currencyID="MYR">1080.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>

Validation rules:

  • TaxInclusiveAmount must be equal to TaxExclusiveAmount plus TaxTotal.TaxAmount.

  • PayableAmount must be equal to TaxInclusiveAmount minus any prepaid amount.

  • All amounts must use two decimal places.

Invoice lines

The invoice lines block lists each item or service on the invoice. Use this table to map your line identifiers, quantities, prices, item details, and tax categories to the required UBL elements and cardinalities.

Element Cardinality Description
InvoiceLine/ID 1..1 A line identifier that must be unique within the invoice and sequential from 1.
InvoicedQuantity 1..1 The unitCode must use UN/CEFACT Recommendation 20 codes such as EA, KGM, MTR, or LTR).
LineExtensionAmount 1..1 Line net amount: Quantity x PriceAmount.
Item/Description 0..1 Detailed item description.
Item/Name 1..1 Short item name.
ClassifiedTaxCategory/ID 1..1 Tax type code for this line.
Price/PriceAmount 1..1 Unit price before tax.

This example shows a single invoice line with quantity, unit price, line extension amount, item details, and tax category populated according to the required UBL elements.

CODE 
<cac:InvoiceLine>
  <cbc:ID>1</cbc:ID>
  <cbc:InvoicedQuantity unitCode="EA">10</cbc:InvoicedQuantity>
  <cbc:LineExtensionAmount currencyID="MYR">1000.00</cbc:LineExtensionAmount>
  <cac:Item>
    <cbc:Description>[Item description]</cbc:Description>
    <cbc:Name>[Item name]</cbc:Name>
    <cac:ClassifiedTaxCategory>
      <cbc:ID>02</cbc:ID>
      <cbc:Percent>8</cbc:Percent>
      <cac:TaxScheme><cbc:ID>OTH</cbc:ID></cac:TaxScheme>
    </cac:ClassifiedTaxCategory>
  </cac:Item>
  <cac:Price>
    <cbc:PriceAmount currencyID="MYR">100.00</cbc:PriceAmount>
  </cac:Price>
</cac:InvoiceLine>

Validation rules:

  • LineExtensionAmount must be equal to InvoicedQuantity x Price/PriceAmount, rounded to two decimal places.

  • The sum of all LineExtensionAmount values must be equal to LegalMonetaryTotal/LineExtensionAmount.

Malaysia-specific fields

Malaysia requires multiple identification schemes per party. Use the following schemeID values:

schemeID Required Description
TIN Yes (supplier and buyer) Tax Identification Number issued by IRBM.
BRN Yes (supplier and buyer, for registered businesses) Business Registration Number issued by SSM.
NRIC Conditional National Registration Identity Card number for Malaysian individuals.
PASSPORT Conditional Passport number for foreign individuals.
ARMY Conditional Malaysian Armed Forces ID number.
SST Conditional Sales and Service Tax registration number.
TTX Conditional Tourism Tax registration number.

Each supplier must include a Malaysia Standard Industrial Classification (MSIC) code in <cac:IndustryClassificationCode>. The name attribute must contain the MSIC description text.

Note:

You can find your MSIC code on your SSM business registration certificate or on the MyInvois portal.

Exchange rate (foreign currency invoices)

For invoices in currencies other than Malaysian Ringgit (MYR), include the exchange rate to MYR.

CODE 
<cac:TaxExchangeRate>
  <cbc:SourceCurrencyCode>USD</cbc:SourceCurrencyCode>
  <cbc:TargetCurrencyCode>MYR</cbc:TargetCurrencyCode>
  <cbc:CalculationRate>[Exchange rate on invoice date]</cbc:CalculationRate>
</cac:TaxExchangeRate>
Note:

The exchange rate must be the rate on the invoice date.

Digital signature

IRBM requires a valid digital signature on each invoice before submission. applies the digital signature automatically using the certificate you uploaded during credential setup. You don't need to sign invoices yourself.

If you are submitting a pre-signed document in the native Malaysian UBL 2.1 format rather than SCI, the signature must meet certain requirements.
Format
XAdES
Certificate
X.509 from a Malaysian Certificate Authority (CA), valid at time of signing
Location
Embedded in document, not detached

UUID and QR code (post-clearance)

After IRBM clears an invoice, returns the UUID, Long ID, and QR code validation link in the application response. You must include the QR code on all printed and electronic copies of the invoice delivered to the buyer.

Embed the QR code in your invoice PDF and any printed representation so buyers can verify the invoice on the MyInvois portal.

Important:

Do not deliver an invoice to the buyer before you have received the UUID. An invoice without a valid UUID is not legally valid.

Credit notes and other document types

Credit note body

A credit note uses the same SBD wrapper and SBDH structure as an invoice. Use the IRBM document type code 02 for credit notes and reference the original cleared invoice.

CODE 
<Invoice>
  <cbc:ID>[Your unique credit note number]</cbc:ID>
  <cbc:IssueDate>2026-05-10</cbc:IssueDate>
  <cbc:InvoiceTypeCode>02</cbc:InvoiceTypeCode>
  <cac:BillingReference>
    <cac:InvoiceDocumentReference>
      <cbc:ID>[Original Invoice Number]</cbc:ID>
      <cbc:UUID>[IRBM UUID of the original invoice]</cbc:UUID>
      <cbc:IssueDate>2026-05-01</cbc:IssueDate>
    </cac:InvoiceDocumentReference>
  </cac:BillingReference>
  <!-- Remaining structure identical to invoice -->
</Invoice>

Validation rules:

  • BillingReference/InvoiceDocumentReference/ID is required. It must be the number of a previously cleared invoice.

  • BillingReference/InvoiceDocumentReference/UUID is required. It must be the IRBM UUID returned when the original invoice was cleared.

  • IRBM validates that the referenced invoice exists and was cleared.

Debit note body

A debit note uses the same structure as a credit note with document type code 03. Debit notes reference the original invoice and document additional charges.

Use the same BillingReference structure as the credit note, and set <cbc:InvoiceTypeCode>03</cbc:InvoiceTypeCode>.

Self-billed invoice body

The buyer issues a self-billed invoice on behalf of the supplier using document type code 11. The sender and receiver roles in the SBDH are reversed compared to a normal invoice. The buyer becomes the sender and the supplier becomes the receiver.

Use the standard invoice structure but set <cbc:InvoiceTypeCode>11</cbc:InvoiceTypeCode> and update the SBDH accordingly.

CODE 
<Sender>
  <Identifier Authority="MY">BUYER_TIN</Identifier>
</Sender>
<Receiver>
  <Identifier Authority="MY">SUPPLIER_TIN</Identifier>
</Receiver>
Note:

Self-billed credit notes (type code 12), debit notes (type code 13), and refund notes (type code 14) follow the same pattern with a different type code.

Refund note body

A refund note documents the refund of a previously paid amount. Use document type code 04 and add a reference to the original invoice with the same BillingReference structure as the credit note. Set <cbc:InvoiceTypeCode>04</cbc:InvoiceTypeCode>.

Last updated: July 23, 2026