Guidelines for Implementing UBL Invoice

The United NationsElectronic Business Language (UBL) provides a standardized XML format for business documents such as invoices, purchase orders and shipping notices. Implementing UBL correctly ensures interoperability between trading partners, reduces manual data entry and supports automated processing in ERP and accounting systems.

The UBL-Local-Invoice-au-v1.0-wd01 document outlines implementation standards.

1. Scope of the Document

The guideline focuses exclusively on the Australian local adaptation of the UBL Invoice (version1.0). It defines the mandatory and optional XML elements, data types, business rules and profile extensions required for compliance with Australian taxation and reporting regulations.

2. Core Structure of a UBL Invoice

A UBL Invoice consists of several toplevel containers:

• cbc:ID unique invoice identifier.
• cbc:IssueDate date the invoice is issued.
• cac:AccountingSupplierParty seller details.
• cac:AccountingCustomerParty buyer details.
• cac:TaxTotal summary of tax amounts.
• cac:LegalMonetaryTotal totals (net, payable, etc.).
• cac:InvoiceLine one element per invoiced product or service.

3. Mandatory Elements for the Australian Profile

According to the UBL-Local-Invoice-au-v1.0-wd01 profile, the following elements must be present in every invoice:

• cbc:ID must follow the pattern INV-YYYYNNNN.
• cbc:IssueDate ISO8601 format (YYYYMMDD).
• cbc:InvoiceTypeCode value 380 for commercial invoices.
• cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID Australian Business Number (ABN).
• cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID buyers ABN.
• cac:TaxTotal/cbc:TaxAmount GST amount (10% of taxable base).
• cac:LegalMonetaryTotal/cbc:PayableAmount total amount payable including GST.

4. Optional but Recommended Elements

While not required for validation, the following items improve readability and facilitate automated processing:

• cbc:DocumentCurrencyCode default AUD.
• cbc:AccountingCost internal cost centre or project reference.
• cac:Delivery delivery address and scheduled date.
• cac:PaymentTerms net30, net60 etc.
• cac:AllowanceCharge discounts, earlypayment incentives.

5. Validation Rules

Implementation must enforce the following rule set:

1. Unique Invoice ID: The cbc:ID must be unique per supplier across the fiscal year.
2. GST Calculation: If cbc:TaxExclusiveAmount is present, GST is calculated as TaxExclusiveAmount 0.10. The result must match cac:TaxTotal/cbc:TaxAmount.
3. Currency Consistency: All monetary values must use the same cbc:DocumentCurrencyCode unless a foreigncurrency transaction is explicitly flagged.
4. ABN Validation: Both supplier and customer ABNs must satisfy the standard Australian checksum algorithm.
5. Date Logic: cbc:IssueDate cannot be later than cbc:DueDate (if provided).

6. Mapping to Business Systems

Most ERP packages support UBL outofthebox or through addons. When mapping:

• Map internal invoice numbers to cbc:ID.
• Populate cbc:IssueDate from the system posting date.
• Extract tax totals from the GST calculation engine and assign them to cac:TaxTotal.
• Use the systems party master records to fill ABN fields.
• Ensure linelevel amounts are rounded to two decimal places before aggregation.

7. Example XML Snippet

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">    <cbc:ID>INV-20230045</cbc:ID>    <cbc:IssueDate>2023-07-15</cbc:IssueDate>    <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>    <cbc:DocumentCurrencyCode>AUD</cbc:DocumentCurrencyCode>    <cac:AccountingSupplierParty>        <cac:Party>            <cbc:EndpointID schemeID="GLN">0081234567890</cbc:EndpointID>            <cac:PartyLegalEntity>                <cbc:CompanyID schemeID="ABN">51 824 753 556</cbc:CompanyID>            </cac:PartyLegalEntity>        </cac:Party>    </cac:AccountingSupplierParty>    <cac:AccountingCustomerParty>        <cac:Party>            <cbc:EndpointID schemeID="GLN">0080987654321</cbc:EndpointID>            <cac:PartyLegalEntity>                <cbc:CompanyID schemeID="ABN">45 123 456 789</cbc:CompanyID>            </cac:PartyLegalEntity>        </cac:Party>    </cac:AccountingCustomerParty>    <cac:TaxTotal>        <cbc:TaxAmount currencyID="AUD">110.00</cbc:TaxAmount>    </cac:TaxTotal>    <cac:LegalMonetaryTotal>        <cbc:PayableAmount currencyID="AUD">1210.00</cbc:PayableAmount>    </cac:LegalMonetaryTotal>    <cac:InvoiceLine>        <cbc:ID>1</cbc:ID>        <cbc:InvoicedQuantity unitCode="EA">10</cbc:InvoicedQuantity>        <cbc:LineExtensionAmount currencyID="AUD">1000.00</cbc:LineExtensionAmount>        <cac:Item>            <cbc:Description>Consulting Services</cbc:Description>        </cac:Item>        <cac:Price>            <cbc:PriceAmount currencyID="AUD">100.00</cbc:PriceAmount>        </cac:Price>    </cac:InvoiceLine></Invoice>

8. Testing and Certification

Before going live, organisations should:

• Validate XML against the official UBL2.1 XSD and the additional UBL-Local-Invoice-au-v1.0-wd01 schema extensions.
• Run test transactions with at least one trading partner to confirm endtoend interoperability.
• Document any custom mapping rules and retain them for audit purposes.

9. Maintenance and Updates

The UBL community releases periodic updates. Subscribers must monitor the official UBL website for revisions to the Australian profile. When a new version is published, perform a gap analysis against existing implementations and schedule migration activities.

10. Conclusion

Adhering to the guidelines set out in UBL-Local-Invoice-au-v1.0-wd01 enables Australian businesses to exchange invoices in a format that is globally recognized yet locally compliant. By implementing the mandatory elements, respecting the validation rules and testing thoroughly, companies can achieve seamless electronic invoicing, reduce processing costs, and meet regulatory obligations.