/ THE SHORT ANSWER
- 01Maintain separate submission, matching and payment states.
- 02Reconcile credits and partial receipts at line level.
- 03Assign one owner to each unresolved exception.
/ dotSuper point of view
Invoice connectivity creates value when finance can distinguish document delivery from the right to pay.
Start with the decision your status actually represents
Give each gate its own status, owner and evidence.
Start by confirming your Singapore entity's applicable requirements, then reconcile every submitted document back to its accounting record.
A successful transmission should never, by itself, release money or close a purchasing dispute.
IRAS describes a phased GST InvoiceNow requirement, with different treatment for registration circumstances and existing businesses.
Its current page also identifies exclusions.
Avoid assigning a deadline using company size alone, or treating another group's implementation date as your own.
[1]
IMDA presents InvoiceNow as the national electronic invoicing network.
That connectivity addresses document exchange.
The additional commercial gates proposed here are dotSuper's operating design for a manufacturer receiving materials, equipment or contracted services.
[2]
Make one invoice visible in three different queues
Link the supplier document number, purchase order, receiving records and network references to it.
Users should reach the same record from any queue without relying on filenames or email subject lines.
The transmission queue answers whether the required data reached the intended system and what response returned.
The matching queue answers whether price, quantity and contractual conditions agree.
Treasury's queue answers whether an authorised person may release the approved amount.
Keep status timestamps and event history.
A credit arriving tomorrow must not erase the explanation for today's hold.
Separate a document amendment from a reviewer changing an internal reason code, because those events have different accounting consequences.
Choose owners before choosing dashboard colours.
An integration failure belongs to a technical operator, a short receipt to stores or procurement, and a blocked beneficiary to treasury.
Finance needs an escalation path when an exception crosses these boundaries.
Use a release table that staff can challenge
The following table is a proposed control design, not a statement of IRAS requirements.
Apply it to a few real document types with your accountant before configuring automatic transitions.
Partial approval should be explicit.
Where contracts and accounting policy permit it, approve an undisputed portion while preserving the disputed balance.
Do not mark the entire document paid merely because one payment instruction was created.
Give reviewers a way to reject a suggested match and explain the reason.
That explanation is more useful for improving matching rules than a silent manual correction that disappears into the ledger.
| Gate | Evidence needed | Owner |
|---|---|---|
| Identity | Supplier entity matches the order | Vendor master steward |
| Transmission | Recorded acknowledgement or actionable error | Integration operator |
| Receipt | Accepted quantity or service confirmation | Stores or service owner |
| Commercial match | Agreed price and approved variances | Accounts payable |
| Payment | Approved amount and verified beneficiary | Treasury |
Worked hypothetical: a short delivery passes transmission
The supplier sends an invoice for S$6,000, and the invoice transmission succeeds.
Stores accepts 460 fittings and records 40 missing from the delivery.
The accepted goods value is 460 multiplied by S$12, or S$5,520.
The disputed quantity represents 40 multiplied by S$12, or S$480.
These figures explain the commercial mismatch; they do not determine the appropriate GST or correction treatment.
Accounts payable links the receiving evidence and asks procurement whether the supplier will complete delivery or issue an adjustment.
Treasury sees only the amount approved under the company's payment policy.
Nobody changes the transmission status to conceal the disagreement.
If the remaining fittings arrive, stores adds another receipt against the same order line.
If they will never arrive, finance follows the appropriate adjustment process.
Either path leaves a readable chain from the original invoice to the final settlement.
Design for retries, duplicates and interrupted handovers
A timeout may leave the sender unsure whether processing occurred.
Reconcile the existing record using available references before permitting another submission, and make uncertainty visible instead of labelling it simply failed.
Likewise, do not accept matching totals as proof that two documents are identical.
Supplier number, currency, issue date and line details provide additional context.
A legitimate recurring invoice can resemble last month's document without being a duplicate.
Shift changes create another risk.
An operator may fix a mapping problem while finance still sees an old error.
Refresh the shared event history and require handover notes for unresolved batches so both teams act on the same state.
More controls also create work.
Keep routine, well-evidenced records moving automatically where policy permits.
Reserve scarce reviewer attention for changed beneficiary details, missing receipts and material variances rather than asking someone to reconfirm every unchanged field.
Judge success by an explainable month-end close
Record where staff had to search outside the finance system.
Those searches identify missing relationships more reliably than a vendor's feature checklist.
Track unresolved transmission records separately from unmatched commercial value.
A falling technical error rate can coexist with growing receipt disputes.
Combining the two into a single success percentage would hide the team's next useful improvement.
Before expanding, ask a colleague unfamiliar with the invoice to explain its final payment using only the linked evidence.
If that requires a phone call to the original operator, improve the record before adding more automated actions.
Make the next implementation task concrete: one owner, one document family and one missing evidence link.
A controlled invoice journey is ready to scale when another person can reconstruct it during absence, dispute or month-end pressure.
What this page cannot conclude
- 01The IRAS rollout is phased and entity-specific; confirm the applicable phase and exclusions directly.
- 02Hypothetical amounts exclude tax and are not estimates of implementation savings.
- 03This workflow does not determine GST treatment or replace tax advice.
- 04This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Sources
- 01GST InvoiceNow RequirementInland Revenue Authority of Singapore · accessed Sep 15, 2026
- 02InvoiceNowInfocomm Media Development Authority · accessed Sep 15, 2026
This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 15, 2026). Singapore InvoiceNow Needs Three Separate Approval Gates. dotSuper. https://dotsuper.net/feeds/applied-systems/singapore-invoicenow-payment-gates