Skip to content

Core Concepts

This is the architecture layer: how commercial billing data is validated by tax authorities in real time, and how documents are signed and routed. If you are looking for the plain-English meaning of consolidated e-invoice, pool or validation, start at Concepts instead — this page assumes them.

The E-Invoice Validation & Clearance Lifecycle

Tax compliance submission follows a structured 5-step lifecycle. Each step represents an automated cryptographic transformation and validation milestone.

StepMilestoneBusiness PurposeApplet Used
1Commercial Invoice GenerationSales order billing or POS checkout creates commercial invoice in ERPSales Invoice Applet
2Data Transformation & SignData formatted into LHDN’s schema and digitally signed by BigLedger as your intermediary — no certificate of yours is involvedMY E-Invoice Admin Applet
3Tax Authority API SubmissionReal-time REST API transmission to tax gateway (e.g., LHDN)MY E-Invoice Admin Applet
4QR Code & UUID ClearanceTax authority validates schema, issues unique UUID and clearance QR stampGovernment Tax API
5Recipient DispatchValidated e-invoice, with its QR code, e-mailed to the buyer and viewable by themMY E-Invoice Portal Applet

PEPPOL Global Network Routing

While government tax APIs handle local country tax compliance, the PEPPOL (Pan-European Public Procurement On-Line) network provides standard international B2B electronic document delivery:

  • PEPPOL Participant ID: Unique global business identifier (e.g., scheme ID + registration number) used for routing.
  • Access Point (AP): BigLedger acts as a certified PEPPOL Access Point, automatically converting commercial invoices into UBL XML standards for instant cross-border delivery.

What to Read Next

  • Concepts — the plain-English layer underneath this one: consolidated e-invoices, pools and queues, validation and clearance.
  • Configuration — Set up tax registrations, intermediary authorisation and classification codes.
  • MyInvois Setup — the same ground as a step-by-step guide, if you are the one doing it.
  • Use Cases — Review reference architectures for commercial B2B billing, consolidated retail POS, and foreign self-billing.