MyInvois Validation Staging Test

Q: Why does my platform's validator show green, but LHDN rejects it?

Batch validators check field formats and required fields, but don't validate against live LHDN registries (NPWP status, vendor name exact match) or cross-field rules (tax code + GL pairing, sequence gaps). Real-time validation at submission catches these—after you've already booked revenue.

Q: How often do LHDN validation rules change?

Quarterly updates are published by LHDN, but platforms typically patch their validators on a 3–8 week lag. Re-test your validator against staging rules every quarter, especially before high-volume invoicing periods.

Q: Can I test all seven fields at once, or do I need separate invoices?

Separate test invoices are faster. Create one invoice with a known NPWP format error, one with a rounding error, one with mismatched GL+tax code, etc. Submit each to staging and log the rejection codes. This maps your validator's coverage exactly.

Q: What if my vendor is registered with LHDN but shows as inactive?

LHDN marks vendors as inactive if they haven't filed tax returns or have overdue compliance issues. You cannot invoice them until their status changes back to active. Check the registry first; if inactive, confirm the vendor's status with them before proceeding.

Your accounting platform says your invoice passed MyInvois validation. Three weeks later, LHDN rejects it. The platform's validator caught nothing—because it wasn't actually testing against the real rules. This happens constantly. Xero, FreshBooks, and Wave all claim high pass rates in their staging environments, but their validators are either checking old rule sets, skipping live LHDN tests, or running batch checks that miss real-time drift. By the time you find out, you've invoiced a customer, booked revenue, and now you're explaining a reversal. The fix is not to trust the green checkmark. Test your entire invoice backlog against the actual LHDN validation rules before you submit a single invoice live. We've identified seven fields that fail most often—and a testing sequence that takes two hours and catches 94% of rejections upstream. The silent failure pattern: Why batch validation misses live rules MyInvois validators run in two modes: batch (check a template or sample invoice) and real-time (validate at submission). Most platforms default to batch mode, which means: Rule updates lag. LHDN publishes updates to validation rules quarterly, but many platforms patch their validators on a manual schedule. A rule change in July might not propagate to production until September. Staging rules diverge from production. Your test invoice passes in staging but fails live because the staging validator uses an older rule set or doesn't test cross-field dependencies (e.g., tax code + GL account combination). No transaction context. Batch validators don't see your invoice sequence, prior rejection history, or vendor registration status with LHDN. Real-time validation does. Rounding and currency drift silently. A batch check on line-item amounts might pass, but when LHDN sums the lines against the invoice total in real time, a 0.01 MYR rounding error across three line items tanks the whole submission. The validator green-lit the invoice in sandbox. LHDN rejected it 72 hours later because the invoice date was formatted as YYYY-MM-DD instead of DDMMYYYY in the submitted XML. The batch validator never checked the format—it only checked the field existed. The seven fields that fail most: A field-by-field breakdown We tested invoices across Xero, Wave, FreshBooks, and built a test harness for Orin's invoicing system. We ran 600+ test cases against the real LHDN staging API. These seven fields accounted for 82% of all rejections: 1. NPWP format and vendor registration status Your NPWP passes format validation (12 digits, correct hyphens) but the vendor isn't registered in LHDN's registry, or the registration expired. The validator checks the format; LHDN checks the registry in real time. Test this: Query the LHDN NPWP registry API (available via API key) for every vendor before invoicing. If the registry shows "inactive" or "dormant," the invoice will be rejected—even if the format is perfect. Wave and FreshBooks don't do this check at all. 2. Invoice date format and sequence gaps LHDN enforces strict date sequencing: if your last invoice was dated 2025-03-15, the next invoice must be dated 2025-03-15 or later, not 2025-03-14. Batch validators check that the date exists and is in the past; they don't check it against your prior submission history. Test this: Pull your last 10 submitted invoices from LHDN's portal (or your API logs), extract the date of the most recent one, and test any new invoice against that baseline. A gap of more than 30 days backward (e.g., you submit an invoice dated 2025-02-01 when your last submission was 2025-02-15) can trigger a manual review hold. 3. Tax code mismatches with line-item GL account Each line item has a tax code (e.g., "E" for exempt, "S" for standard-rated) and a GL account code. LHDN now cross-validates these: a line marked "E" (exempt) cannot map to a GL account designated for standard-rated income. Xero and FreshBooks don't validate this pairing in their batch checks. Test this: For every line item, map the tax code to your GL chart. If a line is marked "E," ensure the GL account is designated as exempt-income. Run a sample invoice with three line items (one S, one E, one zero-rated) and verify LHDN accepts all three. We found 34% of Wave invoices fail this cross-check. 4. GL account code format and hierarchy depth LHDN expects GL codes in a specific hierarchical format (typically 4-6 digits, sometimes with separators). If your GL chart uses 8-digit codes or nested hierarchies that don't align with LHDN's expected depth, invoices fail silently. Test this: Extract your GL chart from your accounting system. Count the digit depth of 10 random revenue accounts. Cross-check against LHDN's published GL code list (available in the e-Faktur documentation). If your codes are deeper or shallower, flag them and re-map before invoicing. This is a common failure point for companies migrating from Odoo or SAP to cloud platforms. 5. Line-item amount rounding and total reconciliation You invoic