GST compliance is not governed by one global timetable. Start by identifying the country, legal entity, GST registration, accounting period and transaction types in scope. Then separate enacted obligations from announced commencement dates and policy recommendations. Singapore’s InvoiceNow rollout has published phased dates; India’s October 2026 GST Council changes are recommendations until implemented through the relevant legal instruments.
For a large group, preparation is an enterprise program rather than a tax-team task. It involves entity mapping, threshold calculations, invoice data, ERP integration, network connectivity, controls, testing, evidence and ongoing change management.
As an Amazon Associate I earn from qualifying purchases.
What “large business” means for GST preparation
Do not use “large” as an informal substitute for a legal threshold. A group may be large globally but fall into different GST phases because each jurisdiction applies its own tests to particular registrations, supplies, turnover measures or transaction categories.
Create an inventory for every affected entity and registration containing:
#1 Best Overall
- Country and tax authority
- Legal entity name and GST registration number
- Branches, fixed establishments and shared-service arrangements
- Accounting periods and the period used to calculate a threshold
- Standard-rated, zero-rated, exempt, reverse-charge, import and export transactions
- ERP, billing, procurement and tax-engine systems that create or receive invoices
- Whether the obligation is enacted, announced for a future date, or only recommended by a policy body
This perimeter prevents a common error: applying the deadline of one registration or country to every company in the group.
Build a jurisdiction-by-jurisdiction obligation register
Maintain one obligation record per entity and requirement. At minimum, record the threshold, measurement period, commencement date, required transmission or filing, exceptions, accountable owner and the official page or notification last checked.
Use a status field that distinguishes:
- In force: an enacted rule or active tax-authority requirement applies now.
- Announced: the authority has published a future phase or commencement date.
- Recommended: a council or policy body has proposed a change, but an implementing notification, regulation or statute is still required.
- Under verification: the business has identified a possible impact but has not confirmed the legal scope.
Assign a tax owner to interpret the rule, an IT owner to deliver the system change, a finance owner to reconcile books and returns, and business-process owners to approve operational changes. Keep a dated copy or link to each authority update so later decisions can be traced to the rule that was in effect at the time.
Singapore: preparing for GST InvoiceNow
Singapore’s Inland Revenue Authority of Singapore (IRAS) states: “All GST-registered businesses must submit invoice data to IRAS using InvoiceNow-Ready Solutions.” The obligation is being introduced in phases, and the phase depends on the registration’s annual supplies rather than a general description such as “large company.”
Singapore’s published phases
IRAS’s February 2026 announcement describes this schedule:
| Business category | GST InvoiceNow commencement |
|---|---|
| New compulsory GST registrants and existing businesses with annual supplies at or below S$200,000 | 1 April 2028 |
| Existing businesses with annual supplies at or below S$1 million | 1 April 2029 |
| Existing businesses with annual supplies at or below S$4 million | 1 April 2030 |
| Existing businesses with annual supplies above S$4 million | 1 April 2031 |
The schedule is Singapore-specific. The government intends to extend the requirement to all GST-registered businesses by April 2031. IRAS gives larger businesses more time because their enterprise systems and software-refresh cycles are typically more complex.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
How IRAS measures the phase threshold
The relevant measure is the total value of standard-rated, zero-rated and exempt supplies in accounting periods ending in calendar year 2025. Use the definition and accounting-period treatment in IRAS guidance when calculating the amount for each GST registration. Do not replace that calculation with group revenue, worldwide turnover, net sales or an internal “large account” classification.
Entities excluded from the stated Singapore scope
IRAS excludes overseas entities registered under the Overseas Vendor Registration regimes and businesses that are liable to register wholly because of reverse charge. Confirm the facts for each registration before treating an entity as excluded; an exclusion for one registration does not automatically apply to other registrations in the group.
Choose the Singapore connection route
IRAS describes two practical paths. The right choice depends on the existing finance architecture, number of entities, invoice volume, data quality and ability to change the ERP.
| Route | What it involves | Best questions to answer |
|---|---|---|
| Off-the-shelf finance solution | Use an accounting or finance product on IMDA’s accredited InvoiceNow-ready solutions list. | Is the product currently accredited, can it support every affected registration, and does it transmit the required GST invoice data without manual re-entry? |
| In-house enterprise system | Connect the existing ERP or finance system through an IMDA-accredited Access Point Provider, obtain a Peppol ID and activate GST InvoiceNow submission. | Can the architecture support the network connection, entity-level identifiers, error handling, monitoring and reconciliation? |
IRAS does not endorse a particular vendor or publish a product ranking. Check the current accreditation and support status directly before signing a contract.
Steps for an in-house ERP or finance platform
- Assess the current invoice flow. Document where invoices are created, approved, amended, cancelled, stored and posted to the general ledger. Include shared-service centres and acquisitions.
- Select an IMDA-accredited Access Point Provider. Confirm supported message formats, environments, service monitoring, incident handling, security responsibilities and integration interfaces.
- Register in the SG Peppol Directory. Use the business’s Unique Entity Number (UEN) to obtain a Peppol ID. Ensure that the identifier is mapped to the correct legal entity and GST registration relationships.
- Connect and configure the solution. Map supplier and customer master data, tax codes, invoice fields, document types, credit notes, debit notes and required references. Define how rejected or malformed messages return to the finance team.
- Activate GST InvoiceNow submission. Complete the authority and provider onboarding steps, then enable the submission path for the relevant registration rather than switching on every entity indiscriminately.
- Test and reconcile. Compare transmitted records with the originating invoice, accounting entry and GST return data. Retest corrections, cancellations, duplicate messages, late changes and connectivity failures.
IRAS says onboarding may take as little as three months and that most businesses complete setup within a year, depending on readiness and configuration. Treat these as indicative ranges, not a service-level guarantee. A group with multiple ERPs, shared ledgers or poor master data should plan for the longer end of the range.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Singapore support and budgeting
IRAS announced a grant of up to S$5,000 for larger early adopters. The announcement said further details would follow, so do not include the amount as guaranteed funding. Confirm eligibility, qualifying costs, application timing and payment conditions under the current program rules before relying on it in a business case.
India: treating the October 2026 GST Council changes correctly
A Government of India Press Information Bureau explainer on the October 2026 GST Council recommendations describes a proposed e-invoicing extension for domestic supplies received from unregistered persons where reverse-charge tax is payable and for imports of services. The described turnover threshold is aggregate annual turnover of ₹5 crore or more.
The wording matters: these are Council recommendations. The explainer does not itself establish an effective date or prove that an implementing notification has taken effect. Do not tell an operating team that the recommendation is already law until the applicable statute, notification, circular or tax-authority implementation page confirms it.
India verification workflow
- Identify every Indian GST registration and calculate aggregate annual turnover using the definition in the applicable rule.
- Separate domestic reverse-charge purchases from ordinary purchases and identify imports of services, including recurring intercompany or platform arrangements.
- Check the Central Tax notification, circular and other implementing instruments applicable to the relevant period.
- Confirm the effective date, covered document types, exemptions, reporting fields, cancellation rules and any transition treatment.
- Update the invoice, procurement, accounts-payable and tax-reporting systems only after the legal trigger and technical specification are confirmed.
- Record the date and document used for the conclusion, then schedule a recheck because recommendations can be amended or implemented in stages.
The notification index reviewed for this issue lists Central Tax notifications through 2025, so it cannot resolve whether later 2026 recommendations have been implemented. That uncertainty is a reason to verify, not a reason to assume either immediate compliance or no action.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Map the enterprise data and control flow
GST changes often fail at the interfaces between tax policy and operational systems. Draw the complete flow for each entity:
- Customer, supplier and legal-entity master data
- Product, service and tax-code determination
- Purchase order, sales order and invoice creation
- Approval, amendment, credit-note and cancellation controls
- ERP, billing platform, tax engine and data warehouse interfaces
- Transmission to the tax network or authority
- Rejection queues, retries, manual overrides and escalation
- Reconciliation to the general ledger, GST return and management reports
Document the owner, source field, transformation rule and evidence produced at each hand-off. This exposes problems such as a branch using a different tax code, a shared service centre issuing invoices under the wrong UEN, or an acquisition operating on an unconnected billing platform.
Test before the legal start date
Testing should represent the transactions the business actually handles, not only a clean domestic sale. Build a case matrix covering:
Rank #4
- Standard-rated, zero-rated and exempt supplies
- Purchases subject to reverse charge
- Imports of goods and services
- Intercompany transactions and shared-service charges
- Credit notes, debit notes, cancellations and corrected invoices
- Multiple currencies, tax-inclusive pricing and rounding
- Missing master data, duplicate documents and rejected submissions
- System outages, provider downtime and delayed acknowledgements
For every test, retain the source transaction, generated document, transmitted payload or record, response, correction and reconciliation result. IRAS publishes the transmission requirement but not a complete enterprise test script; the matrix above is prudent implementation practice, not a quoted statutory checklist.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallGovernance for a large-group rollout
Assign decision rights
Create a steering group with tax, finance, IT, procurement, security, internal audit and business-process representation. Tax should own legal interpretation; IT should own architecture and release management; finance should own ledger and return reconciliation; process owners should approve changes that affect sales, purchasing and customer service.
Control configuration changes
Require documented approval for tax-code changes, field mappings, routing rules, master-data changes and provider configuration. Separate development, test and production access. Record who approved a change, when it was deployed, which entities it affects and how the result was validated.
Preserve evidence
Keep an auditable record of threshold calculations, authority notices, design decisions, test outcomes, approvals, transmitted records, exceptions and reconciliations. The appropriate retention period depends on local law and the entity’s record policy; obtain jurisdiction-specific advice rather than adopting an unsupported universal number.
Monitor after go-live
Track submission success rate, rejected documents, ageing of unresolved exceptions, duplicate or missing transmissions, reconciliation breaks and manual overrides. Review these measures by entity and transaction type so a group-wide average does not hide a failing branch.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsCommon failure modes and fixes
Using group revenue for a registration-level threshold
Symptom: the business assigns a Singapore phase from consolidated revenue. Fix: recalculate using the IRAS definition of total standard-rated, zero-rated and exempt supplies for accounting periods ending in calendar year 2025.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Assuming a recommendation is already enforceable
Symptom: an India project announces a mandatory date based only on a Council explainer. Fix: obtain the implementing notification or other legal instrument and record its effective date before changing production controls.
Connecting one entity and overlooking the group
Symptom: a shared ERP transmits invoices for the parent but not subsidiaries or branches. Fix: maintain an entity-to-identifier matrix and test each registration, issuing location and document type.
Testing only successful invoices
Symptom: the first rejection, cancellation or provider outage becomes a production incident. Fix: test negative cases, retries, manual recovery and reconciliation before activation.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Budgeting on unconfirmed support
Symptom: the business reduces its project budget on the assumption that the Singapore grant will cover a particular cost. Fix: treat the announced ceiling as conditional until current eligibility and application rules are published and checked.
A practical preparation timetable
First 30 days: establish scope
- Name the accountable executive and workstream leads.
- Complete the entity, registration, system and transaction inventory.
- Classify each obligation as in force, announced, recommended or under verification.
- Calculate Singapore’s 2025 supply measure for each potentially affected registration.
- Identify Indian transactions that could fall within the proposed reverse-charge and imported-services scope.
Days 31–90: design the solution
- Choose the off-the-shelf or in-house Singapore route after checking current accreditation and integration fit.
- For an in-house route, engage an accredited Access Point Provider and begin Peppol Directory registration planning using the UEN.
- Confirm Indian legal instruments, effective dates and technical specifications before committing to a production release.
- Approve the target data model, control design, exception workflow and reconciliation method.
- Build the transaction test matrix and agree evidence standards.
After design approval: build, test and activate
- Configure tax logic, master data, interfaces, identifiers and user permissions.
- Run representative and failure-case testing for every entity and transaction class.
- Reconcile test transmissions to source records and tax returns.
- Train sales, purchasing, accounts payable, accounts receivable, tax and support teams.
- Activate in controlled waves, monitor exceptions daily and retain the go-live decision evidence.
Schedule the work backward from the legal commencement date with contingency for procurement, security review, data remediation, provider onboarding and software release windows. IRAS’s indicative three-month-to-one-year range is a useful planning signal, not a promise that every enterprise can complete onboarding in three months.
Quick Recap
Decision checklist for the board or audit committee
- Have all affected countries, legal entities and GST registrations been identified?
- Does every threshold calculation show its measurement period and source definition?
- Are future dates separated from recommendations that still require legal implementation?
- Can the business trace an invoice from source transaction through transmission, ledger posting and GST return?
- Are provider, Peppol ID, UEN and entity mappings owned and tested?
- Have rejection, correction, cancellation, outage and reconciliation scenarios been exercised?
- Are tax, finance, IT and process owners named for every unresolved decision?
- Is any grant, reimbursement or timing assumption dependent on rules that have not yet been published?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
