If you invoice across Malaysia, Indonesia, Singapore, or Thailand, you're running on borrowed time. Real-time tax reporting systems—MyInvois, e-Faktur, GST Portal, Revenue Code—are live. Your invoicing platform might silently fail submission, or your accountant might catch rejected batches in April. The cost of discovery then: hours of remedial invoicing, audit flags, and penalties nobody budgets for. This checklist audits your invoices against what these platforms actually require, tested against real submission APIs. You'll see which fields kill acceptance, which platforms hide failures, and exactly what to fix before Q2 2025 closes the window. Why invoicing platforms fail silently on tax compliance Most invoicing tools generate valid-looking invoices. They have the right fields, the math checks out, and your accountant's month-end reconciliation balances. Then MyInvois rejects the batch. e-Faktur times out. GST Portal flags duplicates. SST calculations sit in a rejection queue. The gap: compliance submission is not the same as invoice generation. A platform can format a perfect invoice document and still fail to submit it to tax authorities in the required structure. Worse, some platforms fail silently—they show a green checkmark in your UI but never actually reach the API. Real-time tax platforms don't forgive: MyInvois (Malaysia): Rejects invoices with missing or invalid company UMNo, customer IDNO/Passport, or incorrectly formatted tax ID structure. Batch fails entirely if one invoice is malformed. e-Faktur (Indonesia): Requires NPWP in exact format, matching registered business entity. Timestamps must align with system clock. Amount rounding follows Indonesian tax rules, not IEEE. GST Portal (Singapore): Duplication by invoice number + customer + amount triggers 48-hour quarantine. Relief Claims must arrive within 5 calendar days of issue. Platform date fields and tax date fields must not diverge. Revenue Code (Thailand): VAT calculations must use precise tax rate per transaction type. Withholding tax on services triggers separate submission. Mismatched issuer and payee registration breaks batch submission. If your invoicing platform doesn't validate these rules before sending, you won't know until tax authorities reject it—or until your accountant flags it in their audit queue. The checklist: field-by-field validation Run this audit on 10 recent invoices from each jurisdiction where you operate. For each field, check yes/no. If you have more than 2 no answers per invoice, stop and escalate to your platform vendor or accountant. Malaysia (MyInvois) Supplier UMNo: Is it 12 digits? Does it match the entity registered with SSM? Open MyInvois Portal, search your company—does it show this UMNo as primary? Customer IDNO or Passport: If a local company, is the IDNO exactly 12 digits with no spaces or dashes? If an individual or foreign entity, is the passport or alternative ID present and formatted without leading zeros? Invoice date and document date: Are they the same? MyInvois rejects invoices where document date is after invoice date. Amount in words: Is it present? MyInvois requires the amount in Malay words for invoices over RM 1,000. SST rate: For taxable supplies, is the rate 0% (exempt), 6%, or 10%? Check against the service type—not all services are 6%. Digital services, for instance, may be zero-rated. Does your invoice show the exemption reason if it's zero-rated? Grand total: Does it equal subtotal + SST (if applicable)? Manually calculate; do not trust the platform's math without verification. Issue date timezone: Is it before today at your tax authority's clock time? MyInvois uses server time; if you're in Kuala Lumpur and issue at 11:59 PM local but submit at 12:02 AM UTC, the document date may fail. Customer address: Is it complete (street, city, postcode, state)? MyInvois requires this for GST relief claims; partial addresses trigger silent rejections on cross-border invoices. Indonesia (e-Faktur) NPWP format: Is it exactly 15 digits with the pattern XX.XXX.XXX.X-XXX.XXX? Leading zeros must be present. Does it match the business entity registered with Direktorat Jenderal Pajak? Customer NPWP or NIB: If B2B, is the customer's NPWP in the same 15-digit format? If foreign customer, is their country code and tax ID present? Invoice series and number: Is the series registered in e-Faktur first? Unregistered series fail immediately. Is the number sequential within that series? Tanggal Faktur (invoice date): Is it within 30 days of issuance? Backdated invoices older than 30 days will not be accepted by e-Faktur unless a correction (Note of Amendment/Koreksi) is filed. Tax rate: For each line item, is the rate 0%, 5%, 10%, or 15%? Is the calculation precise to the rupiah (no rounding within the line; rounding only on totals)? e-Faktur rejects rounding errors—it does not use banker's rounding. Currency: Is it IDR only, or if a foreign currency is present, is there a conversion rate and an IDR equiv