Ready for GST InvoiceNow before your date arrives.

The GST InvoiceNow requirement changes what an invoice is. Under the phased IRAS rollout, invoice data is transmitted in structured form over the nationwide InvoiceNow network, which is built on the international Peppol standard — not printed, attached or retyped. From April 2026 the requirement applies to newly incorporated companies that register voluntarily for GST, IRAS is notifying existing GST-registered businesses of their own implementation dates, and the requirement extends in stages to all GST-registered businesses. The date that matters is yours: IRAS publishes an implementation date calculator, and transitional support is available for early adopters. Why connector-only projects fail The transmission pathway is the visible part of the work, and it is rarely where compliance fails. A readiness position depends on the layers underneath: whether GST configuration produces the right posting outcome for every transaction type you actually run, whether customer and supplier master data carries the identifiers a structured invoice requires, whether the invoice document itself is complete without manual editing, and whether somebody owns the exceptions when a transmission is rejected. A connector on top of unreliable data automates the production of wrong submissions. What the programme covers GST configuration and posting-flow review: every tax posting group, calculation and rounding rule checked against the outcomes it produces, so the numbers being transmitted are the numbers you can defend. Customer, supplier and invoice-data readiness: identifier completeness, registration data and the invoice fields a structured transmission requires, measured across your live master data rather than asserted. InvoiceNow integration and transmission pathway: Business Central's e-document capability connected to a Peppol-ready access point, with the transmission route documented rather than assumed. Exception, cancellation and correction handling: rejected documents, credit notes, corrections and cancellations designed as owned workflows with named responsibility — because compliance fails at the exception path, not the happy path. Test cases, reconciliation and audit evidence: invoice scenarios executed end to end with traceable outcomes, reconciliation between what the ledger says and what was transmitted, and the evidence trail an auditor will ask for. What you leave with A documented map of tax and invoice data gaps, an approved integration and exception-handling design, tested invoice scenarios with traceable outcomes, and named operational ownership for ongoing compliance. Readiness is a position you can show, not a project that happened.