GST reporting that starts from matched books
The GST work is rarely complicated. It is just late — because it waits on a ledger nobody has reconciled yet. Reconcilia Cloud moves the review into the reconciliation step.
- 01 DBS current account · export invoice settled 4,180.00
- 02 UOB operating · supplier payment, GST 9% −1,962.00
- 03 OCBC · intercompany transfer, out of scope −8,000.00
- A1 Sales · zero-rated export, treatment tagged 4,180.00
- A2 Purchase · standard-rated, GST input claimed −1,962.00
- A3 Intercompany · flagged out of scope −8,000.00
Treatment is set on the entry — standard-rated, zero-rated, exempt, out of scope — while the reviewer still has the amount and the counterparty in front of them.
Where GST treatment gets attached
Treatment is set at the transaction level — standard-rated, zero-rated, exempt, or out of scope. During matching, a reviewer sees the treatment alongside the amount and the counterparty, which is when it is easiest to catch a miscoding.
Catching it inside the reconciliation means the correction is a matched entry with an audit trail, not an adjustment discovered during filing week.
- 01 Tag treatment while the feed line is matched
- 02 Review flagged codings before the period locks
- 03 Export the period position with the trail attached
The tour is the review step itself — no separate module, no second pass over a report.
A correction belongs in the ledger it came from. When the treatment sits on the entry, the audit trail is the entry too.
GST review as part of the close
The review step sits after matching and before the period is locked. Entries with tax treatment that looks inconsistent with the counterparty or the transaction type surface for a second look.
This is a short review when the coding is disciplined and a useful one when it is not. Either way it happens while the context is fresh, rather than a month later from a report.
A number you can defend
Output is a GST position by period, traceable from the summary figure back to individual matched entries. That traceability is the practical difference between a number you can defend and a number you hope is right.
The output is designed to support your filing preparation. It is not a filing service, and it does not replace your obligations to IRAS.
- 01 Summary figure on the period return top
- 02 Treatment grouping by rate and category group
- 03 Individual matched entries carrying that treatment line
- 04 Reconciliation audit trail on the entry lock
The trail ends at a matched entry, not at a note in a spreadsheet.
What IRAS compliance means here, precisely
The platform keeps GST calculation and reporting aligned with the reconciled ledger and preserves the treatment history per entry. That is the whole of the claim.
Keeps GST calculation and reporting aligned with the reconciled ledger, and preserves treatment history per entry so a later question has an answer.
It does not give tax advice, and it does not assess whether a specific transaction is correctly treated under your particular GST situation.
Where treatment is unclear, the answer comes from your tax adviser or from IRAS guidance. The platform's job is to make sure the position you file reflects a ledger you have actually reconciled.
Common GST reconciliation problems
These recur in Singapore books every quarter. Each is easy to fix once the exception categories are visible, and expensive to find during filing.
- 01 Zero-rated export coded as standard-rated because the customer address was not checked categor-y
- 02 A bank charge treated as if it carried GST when it does not bank-fee
- 03 An out-of-scope intercompany transfer mixed in with trading income interco
- 04 A credit note applied in a later period than the original invoice credit-note
The exception view lists the pattern, the entry, and the treatment that produced it — so the fix is a matched entry, not a footnote.
Bad debt relief and credit notes
Credit notes and bad debt relief adjustments need the same discipline as ordinary entries: a clear link back to the original transaction, and treatment recorded consistently.
When those items are matched and coded inside the reconciliation, the supporting documentation sits with the entry rather than in a folder someone has to remember. That matters most when a credit note lands a period after the invoice it corrects: the reconciliation holds the link, so the adjustment does not silently disappear into a later return.
GST rate changes and historical periods
Historical periods keep the treatment that applied when they were posted. A later rate change does not retroactively rewrite a locked period, which matters when you are asked about a return filed two years ago.
The rate applied at posting, the treatment recorded on each entry, and the entry detail that supported the return. Locking a period freezes the position rather than the presentation of it.
Adjustments in the current period, new credit notes, and new matched entries. The past is frozen, the present is not.
Who this matters most for
Two situations where the reconciliation-first GST posture pays off fastest — and where the habits get set.
An SME that just crossed the threshold
Filing quarterly for the first time is where the habits are set. Coding treatment inside the reconciliation from the start means quarter four is not the quarter anything falls over.
Most useful before your first quarterly return, not after it.
A finance manager holding a spreadsheet return
Someone who inherited a return assembled in spreadsheets, and wants to stop rebuilding it every quarter. The reconciliation replaces the rebuild, and the trail is the return's own.
Most useful across the first two quarters after switching.
GST and IRAS compliance questions
Does Reconcilia Cloud file my GST return with IRAS?
No. The platform produces a GST position by period traceable to your matched entries, which supports your filing preparation. Filing itself stays with you or with the adviser who files on your behalf, and the obligations to IRAS are unchanged.
Which GST treatments can be tagged on a transaction?
Standard-rated, zero-rated, exempt, and out of scope. The tag sits on the entry alongside the amount and the counterparty, so the reviewer sees the coding question and the transaction context in the same row during matching.
What happens to treatment history when the GST rate changes?
Locked periods keep the rate, the treatment, and the entry detail that applied when they were posted. A later rate change does not retroactively rewrite an already-locked period, so a return filed two years ago still answers against the position you filed.
Can I reconcile only the GST-relevant entries and skip the rest?
You can, but the GST position is only as defensible as the ledger underneath it. Out-of-scope moves, bank charges, and credit notes are exactly where the treatment question hides; reconciling only the standard-rated lines tends to leave the harder categorisations unreviewed.
Does the platform tell me how to treat a specific transaction?
No. Where treatment is unclear, the answer comes from your tax adviser or from IRAS guidance. The platform's job is to keep the ledger and the treatment history in one place so the position you file reflects a ledger you have actually reconciled.
Bring the GST review into the reconciliation
If you want to see how treatment tagging sits on a matched entry, the workflow page walks through the sequence. If you would rather check the plan tiers against your quarterly volume, pricing carries the GST features per tier.
Reconcilia Cloud
71 Robinson Road, #14-01, Singapore 068895
Monday to Friday, 9:00 AM – 6:00 PM (SGT)