InvoiceNow for SMEs: A Practical Setup Guide
InvoiceNow is not simply a different way to email a PDF. It sends structured invoice data between finance systems—and, for businesses covered by the GST InvoiceNow Requirement, to IRAS as well.
InvoiceNow lets businesses send and receive invoices as structured data directly between finance systems.
That is different from generating a PDF and attaching it to an email. A PDF still leaves the recipient—or their software—to interpret and re-enter its contents. An InvoiceNow transaction arrives in a standardised digital format that the receiving system can process.
For Singapore SMEs, there are now two related questions:
- How do we send and receive invoices through the InvoiceNow network?
- When must we transmit invoice data to IRAS under the GST InvoiceNow Requirement?
The answers overlap, but they are not identical.
This guide explains the distinction, the current implementation timetable, and a practical setup process for an SME using an off-the-shelf accounting or finance system.
The regulatory details in this article reflect IRAS and IMDA guidance available on 10 August 2026. Check the current IRAS GST InvoiceNow page before making implementation decisions.
What is InvoiceNow?
InvoiceNow is Singapore's nationwide e-invoicing network. It is based on the international Peppol standard.
Instead of two businesses needing the same accounting software, each business connects through an accredited access point. The sender's system creates a structured invoice, the network routes it using the recipient's Peppol identity, and the recipient's system receives the data.
In practical terms, that can reduce:
- Manual invoice entry
- Mistyped supplier and invoice data
- Missing PDF attachments
- Time spent routing invoices
- Duplicate processing
- Uncertainty over delivery
InvoiceNow does not automatically guarantee that an invoice is correct, approved, or paid. It improves the transport and structure of invoice data. Your billing, approval, reconciliation, and collection controls still matter.
IMDA's InvoiceNow overview and onboarding guidance explains the network and lists the routes available to businesses.
InvoiceNow versus the GST InvoiceNow Requirement
This distinction deserves its own section.
InvoiceNow
InvoiceNow is the network businesses use to exchange structured invoices with one another.
A business can adopt InvoiceNow to improve invoicing even if it is not yet required to transmit data to IRAS.
GST InvoiceNow Requirement
The GST InvoiceNow Requirement requires covered GST-registered businesses to use InvoiceNow-Ready Solutions to transmit in-scope invoice data to IRAS.
When the GST submission feature is enabled, IRAS receives invoice data through the InvoiceNow network. This includes relevant invoices exchanged through InvoiceNow and, where required, invoice data recorded in the accounting system even when the customer or supplier is not on the InvoiceNow network.
That last point matters. “Our customers do not use InvoiceNow” does not necessarily remove a covered business's obligation to transmit invoice data to IRAS.
IRAS remains the authoritative source for scope, exclusions, transmission deadlines, and implementation dates. Your software provider helps transmit the data; it does not take over your GST responsibilities.
Who must comply, and when?
IRAS is implementing the GST InvoiceNow Requirement in phases.
As of 10 August 2026, the published timetable is:
| Implementation date | Businesses covered |
|---|---|
| 1 November 2025 | Newly incorporated companies applying for voluntary GST registration within six months of incorporation |
| 1 April 2026 | All businesses applying for voluntary GST registration, regardless of incorporation date or business structure |
| 1 April 2028 | New compulsory GST registrants; existing GST-registered businesses with total annual supplies of SGD 200,000 or less |
| 1 April 2029 | Existing GST-registered businesses with total annual supplies of SGD 1 million or less |
| 1 April 2030 | Existing GST-registered businesses with total annual supplies of SGD 4 million or less |
| 1 April 2031 | Existing GST-registered businesses with total annual supplies above SGD 4 million |
The thresholds and applicable date should be confirmed against the current IRAS timetable and your own facts.
Do not wait for the deadline to discover that your accounting product, customer records, or invoice process cannot supply required data cleanly. The software connection may be quick; correcting years of improvised billing fields is not.
Step 1: Confirm your implementation date and scope
Start by documenting:
- Whether the business is GST registered
- Whether registration was voluntary or compulsory
- GST registration application date
- Incorporation date, where relevant
- Total annual supplies used for the applicable phase
- Current accounting or finance system
- Invoice sources outside that system
Some SMEs create invoices in several places: the accounting platform, a point-of-sale system, an ecommerce platform, spreadsheets, and project-management software. Map all of them before choosing a solution.
Also identify:
- Sales invoices and tax invoices
- Supplier invoices
- Credit and debit notes
- Simplified tax invoices or receipts
- Point-of-sale transactions
- Petty-cash purchases
- Transactions handled outside the main ledger
IRAS specifies which transaction data must be transmitted, which data may be aggregated, and which transactions are excluded. Do not build the scope from assumptions or from a software sales demonstration.
Step 2: Check whether your system is InvoiceNow-Ready
For an SME using off-the-shelf software, the normal route is an IMDA-accredited InvoiceNow-Ready Solution Provider, commonly shortened to IRSP.
Ask the provider:
- Is our exact product and plan InvoiceNow-Ready in Singapore?
- Can it both send and receive InvoiceNow documents?
- Does it support the GST InvoiceNow submission feature?
- Which document types are covered?
- How are non-InvoiceNow transactions transmitted to IRAS?
- How do we see successful and failed submissions?
- How are corrections, credit notes, and rejected documents handled?
- What implementation, transaction, or support fees apply?
- Who provides the access-point service?
- How do we export our data and audit history?
“Peppol compatible” is not a complete answer. Confirm that the solution supports Singapore's current InvoiceNow and GST submission requirements for your workflow.
Businesses with custom enterprise systems may need to work directly with an IMDA-accredited Access Point Provider. That is a larger integration project and should be planned separately from the SME setup described here.
Step 3: Register the business and obtain a Peppol ID
Your provider or access-point partner registers the business in the SG Peppol Directory using its UEN and obtains the business's Peppol ID.
The Peppol ID is the network address used to route e-invoices. Treat registration as a controlled business change:
- Confirm the legal entity and UEN
- Identify the authorised person approving registration
- Record which provider performed it
- Confirm when the directory listing becomes active
- Test that trading partners can find the business
- Document how to update or transfer the registration later
Do not register the wrong entity because several related companies share a finance team. Each legal entity's invoicing and GST position must remain clear.
Step 4: Clean customer, supplier, and invoice data
Structured exchange exposes inconsistent data quickly.
Review:
- Legal business names
- UENs and GST registration numbers
- Billing addresses
- Customer and supplier Peppol IDs
- Tax codes and GST treatment
- Currency
- Payment terms
- Invoice numbering
- Product or service descriptions
- Purchase-order references
- Credit-note links to original invoices
Decide where each field is mastered. If a customer name is maintained in the CRM but overridden in accounting, which version controls the invoice?
Avoid filling required fields with placeholders merely to make a transmission pass. That turns a technical success into a data-quality failure.
Step 5: Map the invoice workflow
Document the current path from commercial event to accounting record.
For sales:
Order or work completed
→ invoice prepared
→ review and approval
→ invoice issued
→ customer receives it
→ payment recorded
→ bank reconciliation
For purchases:
Supplier invoice received
→ supplier and document validated
→ purchase matched or coded
→ approval
→ payment
→ bank reconciliation
Then mark what changes under InvoiceNow.
Questions to resolve include:
- Does the invoice still require approval before transmission?
- What happens when the recipient cannot be found?
- Does the customer also receive a readable copy?
- Where do incoming invoices wait for review?
- How are duplicate invoices detected?
- Who handles failed transmissions?
- How are attachments and supporting documents exchanged?
- What is the fallback if the network or provider is unavailable?
InvoiceNow should reduce re-entry, not bypass approvals.
Step 6: Configure GST InvoiceNow submission
If the business is covered by the GST InvoiceNow Requirement—or is onboarding early—ask the provider to enable the GST submission feature.
IRAS states that covered businesses must transmit data for specified supplies and purchases reported in GST returns. Current guidance includes standard-rated, zero-rated, and exempt supplies, plus standard-rated and zero-rated purchases, subject to the detailed rules and exclusions.
The scope can include:
- Sales invoices and tax invoices
- Simplified tax invoices and serially numbered receipts
- Supplier invoices
- Debit notes
- Credit notes
- Permitted aggregated transaction data
Some items are excluded, and different transaction types can have different treatment. Use the IRAS e-Tax Guide with your tax adviser or accountant when mapping anything unusual.
IRAS also states that supporting documents do not need to be transmitted as part of invoice data submission, but businesses must retain the records required to support their GST declarations.
Step 7: Test the complete cycle
Do not stop after one successful outbound invoice.
Test:
- Standard-rated sales invoice
- Zero-rated or exempt invoice, if applicable
- Incoming supplier invoice
- Credit note
- Invoice to a customer not on InvoiceNow
- Required aggregated data, if used
- Failed or rejected transaction
- Correction after an error
- Duplicate document
- GST submission and acknowledgement
For each test, confirm:
- The correct legal entity sent or received it
- All required fields arrived accurately
- Tax treatment remained correct
- The accounting entry is correct
- The document status is visible
- Failure or rejection creates an alert
- Resubmission does not create a duplicate
- The provider records a usable audit trail
- GST data transmission receives the expected acknowledgement
Keep screenshots, transaction references, and test results. “It worked during the demo” is not implementation evidence.
Step 8: Run a controlled rollout
Start with a small group of customers and suppliers whose processes you understand.
A sensible rollout might include:
- One cooperative customer already on InvoiceNow
- One customer not on the network
- One regular local supplier
- One credit-note scenario
- One employee from finance and one backup
Run the old monitoring process alongside the new workflow briefly—not duplicate invoicing, but parallel checking. Confirm that every intended document appears once, reaches the right destination, and produces the right accounting and submission status.
Expand only after exceptions are understood.
Step 9: Assign operational ownership
InvoiceNow is infrastructure, not a set-and-forget switch.
Assign owners for:
| Responsibility | Suggested owner |
|---|---|
| Customer and supplier master data | Finance operations |
| Invoice approval | Existing authorised approver |
| Failed transmissions | Named finance administrator |
| GST coding and reporting | Accountant or tax owner |
| Provider access and permissions | System administrator |
| Reconciliation and completeness review | Finance manager |
| Incident escalation | Director or designated senior owner |
Create a short runbook covering:
- Daily or weekly exception checks
- Failed-document handling
- Correction and credit-note process
- New trading-partner onboarding
- User access changes
- Provider support contacts
- Month-end completeness checks
- GST return reconciliation
If only one employee understands the setup, the process is not ready.
Controls SMEs should not skip
Verify bank-detail changes separately
Structured invoices reduce manual entry but do not remove payment fraud. Treat bank-account changes as high risk and verify them through a trusted channel.
Restrict who can change master data
Not every invoicing user should be able to change tax codes, supplier bank information, customer identities, or Peppol settings.
Reconcile documents to the ledger
Check that transmitted and received documents agree with accounting records and GST reporting. A successful network transmission does not prove the accounting treatment is correct.
Monitor acknowledgements and failures
Define what counts as delivered or submitted successfully. Failed documents must enter a visible work queue with an owner and deadline.
Preserve supporting records
Keep contracts, purchase orders, delivery records, and other documents needed to support the underlying transaction and GST position.
Review provider access
Understand what data the provider handles, where administrative access sits, how users are removed, and what happens when the service is changed.
Common implementation mistakes
Treating InvoiceNow as a PDF delivery tool
The value comes from structured data moving between systems. If staff still recreate every invoice manually on both sides, investigate the workflow.
Assuming every business must comply immediately
The GST requirement is phased. Confirm the applicable date rather than repeating an outdated headline.
Assuming non-network customers are outside GST submission
For a covered business, relevant invoice data recorded in the InvoiceNow-Ready system may still need to be transmitted to IRAS.
Activating before cleaning master data
Incorrect UENs, tax codes, and entity records become harder to ignore once systems exchange data automatically.
Testing only happy paths
Credit notes, duplicates, rejected documents, corrections, and unavailable recipients are where operations fail.
Giving the project to software alone
The provider connects the system. Your team still owns invoice accuracy, GST treatment, approvals, reconciliation, and record retention.
A practical SME checklist
Before going live, confirm:
- Applicable GST InvoiceNow implementation date documented
- All invoice sources mapped
- IMDA-accredited provider confirmed
- Peppol ID registered to the correct entity
- Customer and supplier master data reviewed
- Tax codes and document types mapped
- Sales and purchase workflows documented
- GST submission feature configured where applicable
- Outbound, inbound, credit-note, and failure scenarios tested
- Acknowledgements and audit trail verified
- Finance owners and backups trained
- Permissions reviewed
- Month-end completeness check documented
- Supporting-record retention confirmed
- Provider support and fallback process recorded
The bottom line
InvoiceNow is a data and process change, not merely another invoice format.
For most SMEs, the technical route is straightforward: select an accredited InvoiceNow-Ready provider, register the business and Peppol ID, activate the required features, and test.
The harder work is making sure customer records, GST coding, approvals, corrections, and exception handling remain accurate when invoice data moves faster.
If you are also trying to improve the collection process after invoices are issued, read our guide to automating invoicing and payments for a Singapore small business.
Use the Calcudesk automation ROI calculator to identify where manual invoice handling is consuming time. If your InvoiceNow rollout touches several systems or approval paths, book a 30-minute discovery call and we will map the workflow and controls before recommending automation.