ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

Hong Kong — voluntary e-invoicing and Peppol-friendly hub

Hong Kong is one of the few major Asia-Pacific trade hubs with no e-invoicing obligation. There is no VAT, no GST, no mandated format and no clearance platform: invoicing stays contractual and paper-or-digital at the parties' discretion. The only binding framework is fiscal — the Inland Revenue Department requires 7-year record retention (s.51C of the Inland Revenue Ordinance).

Regulatory timeline

  • 2000 — Electronic Transactions Ordinance (Cap. 553). Hong Kong recognises the legal effect of electronic documents, contracts and signatures, laying the groundwork for voluntary dematerialised invoicing.
  • Always — No VAT/GST. Hong Kong has never introduced value-added tax or GST; a 2006 public consultation on a GST was dropped. The absence of a transactional tax removes any incentive for a clearance model.
  • Standing — Inland Revenue Ordinance, s.51C. Obligation to keep business records (invoices included) for at least 7 years, with a fine up to HK$100,000 for non-compliance. This is the only real constraint bearing on invoices.
  • 1 June 2025 — Fully electronic government payments. For tenders invited from this date, the administration pays suppliers solely by bank transfer or the Faster Payment System (FPS), dropping cheques. This dematerialises payment, not an e-invoicing mandate.
  • 2026 — Voluntary status quo. No B2B or B2G mandate announced. Hong Kong keeps a market-led approach; Peppol uptake is driven by commercial access points and players such as GS1 Hong Kong, with no national Peppol Authority (to confirm should an official designation occur).

Technical schema

Hong Kong mandates no technical schema. An invoice may be a PDF, a proprietary EDI message, a UBL file or any other medium agreed between the parties. The only data really expected on the tax side is whatever lets assessable profit be determined and the business be identified.

  • Entity identifier : the 8-digit Business Registration Number (BRN) usually appears on the invoice; the Companies Registry CRN identifies the legal entity.
  • Currency : HKD by default, free multi-currency (USD, CNY, EUR…) — Hong Kong is an open financial centre.
  • Tax : no VAT/GST line. Invoices carry no VAT-type TaxScheme; excise duties (tobacco, alcohol, fuels) are handled separately at import.
  • If Peppol is used voluntarily : profile urn:cen.eu:en16931:2017 via Peppol BIS Billing 3.0, EndpointID under the GLN scheme (0088) or another agreed identifier — there is no official Peppol "HK" scheme dedicated to the BRN (to confirm).

Example of a voluntary UBL invoice with no tax (typical HK case) :

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017</cbc:CustomizationID>
  <cbc:ID>INV-HK-2026-0042</cbc:ID>
  <cbc:IssueDate>2026-06-20</cbc:IssueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>HKD</cbc:DocumentCurrencyCode>
  <cac:AccountingSupplierParty><cac:Party>
    <cac:PartyLegalEntity>
      <cbc:RegistrationName>Ediverse Demo Ltd</cbc:RegistrationName>
      <cbc:CompanyID>12345678</cbc:CompanyID><!-- 8-digit BRN -->
    </cac:PartyLegalEntity>
  </cac:Party></cac:AccountingSupplierParty>
  <cac:TaxTotal><cbc:TaxAmount currencyID="HKD">0.00</cbc:TaxAmount></cac:TaxTotal>
  <cac:LegalMonetaryTotal>
    <cbc:PayableAmount currencyID="HKD">10000.00</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>
</Invoice>

Submission flow

There is no clearance flow. The invoice travels directly from issuer to buyer, without passing through a state platform and without real-time tax reporting. Two patterns coexist :

  • Direct channel (majority case) : PDF by email, proprietary EDI or a private platform. The buyer receives, books, pays; each side archives for 7 years for the IRD.
  • Voluntary Peppol channel (4-corner) : issuer → outbound access point → SMP/SML resolution → inbound access point → buyer, over AS4. No tax "fifth corner" on the Hong Kong side — the IRD is not in the loop.
┌──────────────┐     invoice (PDF / UBL / EDI)      ┌──────────────┐
│ Issuer HK    │ ─────────────────────────────────> │ Buyer HK     │
│ (ERP)        │   email · platform · Peppol AS4    │ (ERP)        │
└──────┬───────┘                                    └──────┬───────┘
       │ 7-year retention (IRO s.51C)                      │ 7-year retention
       ▼                                                   ▼
   [ accounting records — auditable by the IRD on request ]

   No clearance platform · No real-time reporting · No VAT

For B2G, a supplier may submit via the Government e-Procurement System and be paid electronically (bank transfer / FPS since June 2025), but on market terms, not under a mandatory invoice format.

Validation

Common pitfalls

  1. Assuming a mandate is imminent. Unlike Singapore (InvoiceNow) or Malaysia (MyInvois), Hong Kong has announced no obligation timetable. Over-scoping a "clearance" project for HK is wasted effort; the real risk is the opposite — underestimating plain 7-year retention.
  2. Adding a VAT/GST line. Hong Kong has no value-added tax. An ERP set to insert a 0% VAT TaxScheme or a default rate produces invoices that break with local practice and confuse buyers.
  3. Confusing BRN and CRN. The Business Registration Number (8 digits, IRD) and the Company Registration Number (Companies Registry) are distinct. Mapping one for the other in an exchange identifier breaks reconciliation on the partner side.
  4. Assuming a national Peppol scheme for HK. There is no Peppol Authority and no official scheme dedicated to the BRN: interoperability runs through commercial access points and agreed identifiers (often GLN 0088). Check case by case (to confirm).
  5. Neglecting archive integrity and accessibility. Section 51C requires "sufficient" records for 7 years, legible and reliable. A lost PDF or a proprietary format that becomes unreadable risks a fine of up to HK$100,000.
  • PEPPOL — network reachable voluntarily via access points.
  • UBL 2.1 — XML syntax used by Peppol players.
  • EN 16931 — semantic model of the European invoice, reused by Peppol BIS.
  • EDIFACT — proprietary EDI still common in Hong Kong trade.
  • Singapore — neighbour with a Peppol mandate (InvoiceNow), a direct contrast.
  • Japan — another Asia-Pacific Peppol hub.
  • Official sources : ird.gov.hk, gov.hk, cr.gov.hk.