If you invoice across Malaysia, Singapore, and Indonesia, you're managing three separate compliance regimes with overlapping but incompatible rules. Malaysia mandates MyInvois (LHDN submission). Singapore has no single e-invoice mandate yet—but the Infocomm Media Development Authority (IMDA) and Accounting and Corporate Regulatory Authority (ACRA) are moving toward structured e-invoicing. Indonesia's e-Faktur is real-time, mandatory, and will reject invoices that fail validation in milliseconds. The problem: an invoice that passes Malaysian validation may fail Singapore's structural expectations and trip Indonesia's tax ID checks. This post maps the actual validation rules, submission formats, and audit trails across all three—and tests which invoicing platforms handle the divergence without manual intervention. Malaysia's MyInvois: LHDN submission and real-time validation MyInvois went mandatory for businesses with turnover exceeding RM3 million (approximately USD 650K) in June 2023. The system validates invoices in real-time against LHDN's (Inland Revenue Board) database before acceptance. Key validation rules: Buyer Tax ID format. MyInvois accepts only valid Malaysian tax IDs (BRN for businesses, NRIC for individuals). The system cross-checks against LHDN's registry. Invalid or unregistered IDs trigger immediate rejection. Seller registration. Your business must be registered in the MyInvois portal with a valid eServicesTax account and digital certificate (MyID or other MDCA-approved certificate). Structured XML format. Invoices must be submitted in MyInvois XML schema (UBL 2.1 wrapper). Free-text or PDF-only invoices don't pass. GST/Service Tax codes. Malaysia's Service Tax (0%, 6%, or exempted) and GST are encoded in line-item tax type codes. Mismatched codes fail validation. Allowances and charges. Discounts and surcharges must be linked to specific line items and carry tax impact codes. Blanket discounts fail. Currency. MYR invoices are standard. Foreign currency invoices are allowed but require explicit exchange rate notation and FX disclosure. Submission is not optional: MyInvois invoices must be submitted within 48 hours of invoice date. Non-compliance can trigger penalties. Singapore's e-billing landscape: Mandatory adoption without a single standard Singapore has no single e-invoice mandate comparable to MyInvois. However, ACRA and IMDA are actively promoting structured e-invoicing, and major procurement bodies (PSA, JTC, government agencies) now require e-invoices from suppliers. Key structural expectations: UBL 2.1 adoption. Singapore's recommended format is UBL 2.1 (the same XML standard Malaysia uses), but adoption is voluntary for most B2B transactions. Government procurement mandates it. GST validation. Singapore's GST is 8% (as of 2024). The invoice must encode GST treatment correctly (taxable, exempt, zero-rated, or out-of-scope). Unlike Malaysia, there's no single mandatory real-time validation gateway—yet. Tax ID format. Singapore uses the UEN (Unique Entity Number), a nine-digit code. Unlike MyInvois, there's no mandatory real-time cross-check against ACRA's database for ordinary B2B invoices, but government contracts often require prior registration and verification. No universal submission requirement. Invoices are typically exchanged peer-to-peer or via bank-integrated platforms (DBS, OCBC, UOB all support e-invoicing portals). ACRA does not operate a centralized repository. Archival and audit. Invoices must be kept for five years and be capable of being produced in structured format if ACRA requests them during audit. The format requirement is retrospective, not submission-based. Singapore's approach is standards-based but enforcement-light. The real risk is that your largest Singapore clients may demand UBL compliance as a contract requirement, even if ACRA doesn't. Indonesia's e-Faktur: Real-time validation and instant rejection Indonesia's e-Faktur (electronic tax invoice) is mandatory for businesses with turnover above IDR 4.8 billion (approximately USD 310K). Unlike MyInvois's 48-hour grace period, e-Faktur validation is synchronous: invoices are validated and numbered in real-time by DJP (Directorate General of Taxes). Key validation rules: Tax ID (NPWP) verification. Both seller and buyer NPWP codes must exist in DJP's database. A buyer with an invalid or unregistered NPWP causes immediate rejection. There's no workaround. Transaction type codes. e-Faktur requires explicit transaction classification (domestic sale, export, service, etc.). Incorrect or missing codes trigger rejection. PPN (VAT) rates and treatment. Indonesia's standard PPN is 11% (increased from 10% in 2022). Reduced rates (0%, 5%) apply to specific goods and services, and the system validates rate eligibility against commodity codes. Mismatched rates fail. Serial number sequence. e-Faktur invoices are numbered sequentially by DJP, not by your accounting system. Gaps or duplicates are flagged and may trigger