Common GST Data Errors Automation Can Detect

Two supplier invoices enter the accounting system with different filenames:

INV-1048.pdf
June materials final.pdf

The supplier, invoice number, date and amount are identical. A person reviewing a busy purchase ledger may not notice. A duplicate check should.

That is the useful role of automation in GST work. It does not decide whether a transaction qualifies for zero-rating or whether an expense has a sufficient business purpose. It compares records, applies known rules and puts suspicious items in front of someone who can inspect the evidence.

For Singapore SMEs, these checks should happen continuously—not for the first time on the evening the GST return is due.

Why GST errors are often data errors first

A GST return is assembled from sales, purchases, credit notes, import records and adjustments. If the underlying data is duplicated, incomplete, miscoded or posted in the wrong period, the return inherits the problem.

IRAS says incorrect input-tax claims are the most common mistakes found among the roughly 3,000 GST-registered businesses selected for audit each year. Its current conditions for claiming input tax require, among other things, valid supporting documents and a business purpose.

Automation cannot prove every condition. It can find transactions that do not look as though they meet them.

Here are the checks worth building.

1. Duplicate supplier invoices and input-tax claims

A duplicate may enter through two inboxes, an invoice portal and an email, or a reissued document with a new filename. If both records are posted, the business may overstate purchases and claim the same input tax twice.

A useful duplicate check compares several fields:

supplier identifier;
invoice number;
invoice date;
amount before GST;
GST amount;
total amount; and
purchase-order or payment reference.

Exact matches are easy. Near-duplicates need more care. An invoice number may appear as INV1048 in one record and INV-1048 in another. Optical character recognition may confuse a zero with the letter O. A supplier may issue a corrected invoice for the same amount.

The automation should therefore assign a confidence level and hold likely duplicates for review. It should not automatically delete one record. One document may be a legitimate credit note, corrected invoice or staged billing.

IRAS permits input tax to be claimed using a consistent posting or processing-date approach in qualifying circumstances, but businesses must maintain controls that prevent double claims. The current rules and examples are set out in IRAS guidance on claiming input tax in the correct accounting period.

2. Missing details on tax invoices

Input-tax claims on local purchases generally need to be supported by valid tax invoices addressed to the business or by simplified tax invoices.

An extraction tool can check whether the document appears to contain:

the supplier’s name and address;
the supplier’s GST registration number;
an invoice number and date;
the words “tax invoice,” where required;
a description of the goods or services;
the amounts before and after GST;
the GST amount or an acceptable GST-inclusive statement; and
customer details where required.

The requirements differ according to the document and amount. For example, a simplified tax invoice may be used when the total including GST does not exceed S$1,000 and requires fewer particulars. The IRAS invoicing guidance should be the source for the current requirements.

A field being present does not make it correct. “GST Reg No” followed by a malformed value should still be flagged. So should an invoice issued to an employee personally when the claim depends on proving the employee acted for the business.

The right workflow is to quarantine the claim and request a valid document from the supplier before filing.

3. Invalid or unexpected supplier GST registration details

An invoice can display a GST registration number even when the supplier is not registered, the number has expired, or the number belongs to a different entity.

Automation can:

validate the number’s format;
compare the stated supplier name with the approved supplier record;
identify a new or changed GST number;
check the supplier’s status against the official GST register; and
flag GST charged before the supplier’s effective registration date or after cancellation.

Do not quietly “correct” the supplier record based on one invoice. A change in legal entity or GST number may be legitimate, but it deserves verification.

IRAS specifically tells businesses to check supplier registration status when validating input-tax claims. Its GST-registered business search is the authoritative lookup.

4. GST amounts that do not recalculate

For a standard-rated local supply, the system can recalculate GST from the taxable value and compare it with the posted amount. It can then flag:

arithmetic differences beyond an agreed rounding tolerance;
a 9% tax code with no GST amount;
GST applied twice;
GST calculated on a total that already includes GST;
line totals that do not add to the invoice total; and
a document total that differs from the ledger entry.

Singapore’s prevailing GST rate is 9%, but the presence of another rate is not automatically an error. Older documents, credit notes linked to earlier supplies, zero-rated transactions and special cases need context.

Build date and transaction-type rules around the check. Do not replace a non-9% rate merely because it is unusual.

IRAS explains the current rate and exceptions in its guidance on when to charge GST.

5. Suspicious zero-rating

“Customer is overseas” is not, by itself, a complete zero-rating rule.

For exported goods, the business needs to meet the relevant conditions and retain evidence of export. Services must qualify as international services under the applicable rules. A foreign billing address alone does not settle the treatment.

Automation can flag:

zero-rated sales without export or transport documentation;
services coded at 0% when delivery records indicate the customer or beneficiary was in Singapore;
local delivery addresses paired with a zero-rated code;
recurring customers whose tax treatment changed unexpectedly; and
free-text reasons such as “overseas client” without a supporting category.

This is a review queue, not a tax engine. The person reviewing it needs to determine the supply, contractual parties, place of performance and documentary support.

IRAS lists unsupported zero-rating among the common errors when completing GST returns.

6. Disallowed or non-business input-tax claims

An expense can contain GST and still be ineligible for an input-tax claim.

Automation can scan supplier, account and description data for categories that deserve review, such as:

private or personal purchases;
family expenses;
motor-car purchase and running costs;
certain medical or insurance expenses;
entertainment without a recorded business purpose; and
costs allocated to exempt or non-business activities.

Keyword detection is only a first pass. “Insurance” covers many arrangements, and a restaurant receipt may represent either a valid business meeting or a private dinner. The system should ask for evidence or route the item to a reviewer, not reject it from a word alone.

The applicable conditions and examples of disallowed claims are maintained in the IRAS input-tax guidance.

7. Claims posted in the wrong accounting period

Timing errors happen when invoices arrive late, dates are extracted incorrectly or staff backdate entries to fit a reporting period.

Checks can compare:

invoice or import-permit date;
posting or processing date;
GST accounting period;
effective GST registration date;
credit-note date; and
whether the same source document appeared in an earlier return.

The system also needs to know which permissible claiming approach the business uses. Mixing invoice-date and posting-date methods transaction by transaction can create inconsistent results.

If a date is ambiguous—03/04/26, for example—do not guess silently. Use the supplier’s locale, document layout and other evidence, then ask for confirmation when confidence is low.

8. Input tax on supplier balances unpaid after 12 months

A business can generally claim input tax before paying its supplier if the other conditions are met. But where payment has not been made within 12 months from the due date, IRAS requires the input tax to be repaid through the GST return. It may be reclaimed later when payment is made, subject to the rules.

This is well suited to an automated ageing check. The system can identify:

invoices approaching 12 months from the due date;
unpaid or partly paid balances;
claimed GST associated with those balances;
payments that were posted but not allocated; and
later payments that may allow a reclaim.

The check depends on accurate due dates and payment allocation. If every old invoice is left with the default “due immediately,” the alert will be precise but unhelpful.

IRAS provides worked examples in its guidance on claiming input tax in the correct accounting period.

9. Credit notes and adjustments without a source transaction

A credit note should not float in the ledger without context. It needs to be linked to the original sale or purchase so the system can adjust the correct value, tax amount and period.

Flag:

credit notes with no original invoice reference;
credits larger than the original transaction;
repeated credits against one invoice;
a GST code that differs from the original supply without explanation; and
manual journals posted directly to GST control accounts.

Manual journals are not inherently wrong. They are simply high-value review items because they can bypass the normal invoice-level checks.

10. GST return totals that do not reconcile

The final control compares the draft return with the ledgers and source records.

Useful reconciliations include:

sales ledger to reported supplies;
purchase ledger to taxable purchases;
output-tax control account to output tax due;
input-tax control account to input tax claimed;
import permits to import entries;
credit notes to their adjustments; and
current-period opening balances to the prior period’s closing position.

The goal is not merely to make the return total equal the ledger. A balancing journal can force agreement while hiding the original error. The reconciliation should preserve a trail from return box to transaction and source document.

A workable exception report

A long spreadsheet of every transaction is not a control. It is another inbox.

A useful GST exception report should show:

Priority	Exception	Evidence shown	Next action
High	Possible duplicate input-tax claim	Both invoices and prior claim reference	Hold and review
High	Supplier GST number invalid	Invoice and official lookup result	Request corrected invoice
High	Zero-rated sale lacks support	Invoice, delivery data and missing-document list	Tax review
Medium	GST amount differs from calculation	Line values and tolerance	Verify source
Medium	Invoice approaching 12-month unpaid point	Due date, balance and GST claimed	Review adjustment
Low	New tax-code pattern	Similar historical transactions	Confirm coding

Assign every exception an owner and a due date. Record the reviewer’s decision and retain the evidence. If the same exception is repeatedly approved, improve the underlying rule or master data instead of training the team to click “ignore.”

What automation still cannot decide

Automation is strong at comparison and consistency. It is weak where the answer depends on facts not present in the accounting record.

Keep human review for:

whether a service qualifies as an international service;
whether an expense has a sufficient business purpose;
whether input tax relates to taxable, exempt or non-business activities;
the treatment of unusual contracts, reimbursements or mixed supplies;
whether evidence is substantively reliable; and
how to correct an error already included in a filed return.

If an error is found after filing, do not erase the source entry to make the ledger look clean. Preserve the audit trail and follow IRAS’s correction process. Its Voluntary Disclosure Programme explains when self-initiated disclosures may qualify for reduced penalties.

Start with three checks

An SME does not need to implement all ten checks at once. Start with:

duplicate supplier invoices;
missing or invalid tax-invoice details; and
GST amounts that do not recalculate.

These use data most accounting systems already hold, are easy for a reviewer to understand and can be tested without letting the automation alter a filed return.

Run the checks in shadow mode for one GST cycle. Measure how many genuine exceptions they find, how many false alerts they create and how long review takes. Our guide to choosing what to automate first gives a practical scoring method, and the automation savings calculator can help you test whether the recurring effort justifies a build.

The target is not a “fully automated GST return.” It is a return prepared from cleaner data, with fewer surprises and a visible trail of what was checked.

If your GST preparation still depends on a last-minute spreadsheet, book a 30-minute discovery call. We can map the data flow and identify which checks can be automated safely before the next filing cycle.