# Invoice approval automation for Singapore SMEs: matching, exceptions and audit trails

> Design a Singapore invoice approval workflow with duplicate checks, PO matching, exception queues and retrievable GST records. InvoiceNow is a separate duty.

Source: https://www.fyadvisers.com/blog/invoice-approval-workflow-automation-singapore/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

Invoice approval automation should move a checked invoice to the right reviewer. It should not turn every attachment into an approved bill. Start with supplier identity, a duplicate check and the purchase evidence. Keep disputed amounts and mismatched documents in an exception queue, where a person can see them, rather than inside an email chain.

This guide covers the path from receipt to an approval decision. Creating the supplier and changing bank details sit in the [supplier onboarding](/blog/supplier-onboarding-bank-detail-change-workflow/) guide. Chasing payment sits in the [overdue reminder](/blog/overdue-invoice-reminder-workflow-singapore/) guide. The purchase that should have existed first is the [purchase order workflow](/blog/purchase-order-approval-workflow-singapore/).

## States worth building

Give the invoice one status, stored on a business record, not only inside a running flow.

| State | Meaning | Who may move it |
|---|---|---|
| Received | A file and a message reference exist. Nothing is trusted yet | Intake |
| Validated | Required fields are present and the file opens | Intake or a reviewer |
| Matched | PO and, where used, receipt evidence agree within the written tolerance | Matching rules, then a person if outside tolerance |
| Pending approval | The current document version is with a named approver | The workflow, after the match result is visible |
| Rejected | A reason is stored. The same version cannot be posted | The approver |
| Ready to post | Approval is recorded and coding is complete | Finance |
| Posted | The accounting document exists and its id is stored | The accounting write, confirmed |

Approval of the invoice is not payment authorisation. A second control, often a payment run with its own approver, should be required before money moves. Do not let a successful approval action create a payment instruction by default.

## Fields to capture, and what extraction is allowed to mean

Capture at least: supplier id in your system, supplier’s invoice number, issue date, currency, tax fields you actually use, purchase-order reference, line and header totals, and a pointer to the source file and the message it arrived on. OCR or an AI extraction is a proposal. A person or a deterministic check confirms it before the status becomes validated. A wrong total that is then approved is an approved wrong total.

Duplicate detection needs a key the business agrees. A practical key is supplier id plus supplier invoice number, with a normalised amount and issue date as a second look for the same PDF forwarded twice. The acceptance case is the same invoice arriving by email and by a supplier portal. The second copy should land as a duplicate of the first record, not as a second bill.

## Two-way and three-way match

These are implementation patterns, not a legal rule.

- **Two-way:** invoice lines against the purchase order. Use it when receipt is not a separate event you trust, and say so.
- **Three-way:** invoice against the order and against what was received. Use it when goods or staged services are receipted.

Tolerances are a business decision: quantity, price and tax, written down, with a named role allowed to accept a variance. Split deliveries should hold the unreceived quantity instead of approving the whole supplier total. A credit note against an already approved invoice needs its own link to that invoice and must not silently reduce a different bill. When the approved file is replaced, the new version goes back through approval. The old decision stays visible and does not apply to the new file.

Microsoft’s [sequential approval](https://learn.microsoft.com/en-us/power-automate/set-up-sequential-approvals) tutorial shows a staged “start and wait” approval, including more than one approver. Any dollar figure in that tutorial is Microsoft’s example. It is not a Singapore authority threshold. Set bands by legal entity, amount and cost centre in your own matrix. Record the decision maker, the time, the document version and, on rejection, the reason.

## InvoiceNow is not the approval workflow

IRAS describes InvoiceNow as Singapore’s nationwide e-invoicing network. On the [GST InvoiceNow Requirement](https://www.iras.gov.sg/taxes/goods-services-tax-(gst)/gst-invoicenow-requirement) page, checked on 8 November 2026, GST-registered businesses must submit invoice data to IRAS using InvoiceNow-Ready Solutions, in phases. An approval flow that reads a PDF is not that solution. Transmitting data, approving it internally and keeping records are three different jobs.

The page’s published phases are:

| Implementation date | Who the page says it applies to |
|---|---|
| 1 November 2025 | Companies registering for GST voluntarily within six months of incorporation |
| 1 April 2026 | Businesses applying for voluntary GST registration on or after that date, regardless of incorporation date or structure |
| 1 April 2028 | New compulsory registrants from that date, and existing GST-registered businesses with total annual supplies of S$200,000 or less |
| 1 April 2029 | Existing GST-registered businesses with total annual supplies of S$1,000,000 or less |
| 1 April 2030 | Existing businesses with total annual supplies of S$4,000,000 or less |
| 1 April 2031 | Existing businesses above S$4,000,000 |

IRAS defines total annual supplies, for this schedule, as the total of standard-rated, zero-rated and exempt supplies (Box 4 of the GST return) in the prescribed accounting periods ending in calendar year 2025. The same page says IRAS has notified GST-registered businesses that were registered before 2026 of their mandatory implementation date from mid-2026, and that a business which has not received a notification will be told later. Use the notification or IRAS’s calculator for a specific entity. This article does not say that every SME is already mandated.

The page also excludes some overseas entities and businesses liable to register wholly under the reverse charge regime. Businesses remain responsible for GST returns and for keeping records. IRAS’s [record-keeping page](https://www.iras.gov.sg/taxes/goods-services-tax-(gst)/basics-of-gst/invoicing-price-display-and-record-keeping/keeping-records) says GST records, including tax invoices, receipts and credit notes, must be kept for at least five years from the end of the accounting period. That is a GST rule, not a reason to retain every failed automation payload for five years, and not a reason to delete other records on the fifth anniversary. How to separate those copies is covered in [data retention for automation](/blog/workflow-automation-data-retention-audit-logs/).

## Acceptance tests and what to ask a supplier

Witness these three cases:

1. The same supplier invoice arrives by email and by a portal.
2. An approver rejects a bill, the draft is revised, and the old rejection remains attached to the old version.
3. A credit note refers to an invoice that is already approved.

Ask where matching tolerances are stored and who can change them, whether approvers can open the file without mailbox rights, and whether the approval evidence exports after the platform’s run history expires. [System integration](/services/system-integration/) matters here because the accounting write can succeed while the workflow’s acknowledgement fails. That case needs a business key, not a blind replay.

Illustrative scenario, not a client engagement: a wholesaler receives an invoice for a purchase order that was only partly delivered. The workflow matches the received quantity, holds the rest, and asks the buyer to resolve the mismatch. It does not create a payment. The buyer’s decision is stored against the invoice version they actually saw.

This is an operational design guide. It is not tax advice, and FYAdvisers is not a law firm or a tax agent. To sketch the states against one real bill, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### Can approvers see the source document without access to the whole mailbox?

They should. Store the file in a restricted library and show that copy on the approval record. A design that requires every approver to open the shared inbox will spread personal data and make the audit trail depend on who still has mailbox access.

### Who sets matching tolerances?

The business does, in writing, by supplier or by category if the risk differs. A percentage copied from a demo is not a control. Zero tolerance with an explicit exception path is easier to explain than a silent rounding rule.

### Can we export the approval evidence?

Yes, that should be an acceptance test. Export the supplier, invoice number, document version, approver, decision time, rejection reason and the link to the posted bill. Platform run history is not a substitute; Microsoft documents a 30-day run retention for cloud flows.

### Does invoice approval meet the GST InvoiceNow Requirement?

No. IRAS requires phased transmission of invoice data through InvoiceNow-Ready Solutions. Internal approval, network transmission and keeping GST records are separate duties. Check the IRAS page for the date that applies to the business.
