GST handling
Whether Singapore GST is part of the data model or bolted on. Wrong here means a year of amendments, because IRAS-facing output has to be right the first time.
LedgerLane · Published evaluation method
Know what your books are signing you up for.
Every platform in our accounting software directory is read against the same four criteria — GST handling, InvoiceNow participation, bank reconciliation and remote collaboration with an accountant. This page shows how we apply them, where the information comes from, and what would make us change an entry.
Evaluation sheet
LedgerLane Pte. Ltd. · Method note
- GST handling (weighted)
- Reviewed in entry
- InvoiceNow readiness (weighted)
- List check + vendor claim
- Bank reconciliation (weighted)
- Behaviour + reader reports
- Accountant collaboration (weighted)
- Access + handoff
- Feature count
- Not scored
- Price
- Not scored
Where a platform's own claim and a public list disagree, the entry follows the list.
Fit, not ranking
Why this page exists
Read the method, then judge the entry
This page exists so you can judge our directory entries rather than take them on trust. It sets out what we look at, where the information comes from, how often entries are revisited, and how we handle the fact that software vendors have a commercial interest in what we write.
We publish the method because an evaluation criteria page that stays vague is not really a criteria page. If you disagree with a weighting, this is where to see what we did — and every entry in the directory is written to this standard, not a looser one.
Criteria weightings
What we weight, and why
Four criteria carry the most weight for Singapore readers because a wrong choice in any of them is expensive to undo. The two lines at the bottom of the list are deliberately outside the scoring.
InvoiceNow participation
Whether the platform appears on IMDA's InvoiceNow-ready list, and whether it handles both sending and receiving structured invoices rather than one half of the exchange.
Bank reconciliation
How bank feeds and statement imports behave with real transactions, and how quick it is to correct a wrong match once one happens.
Accountant collaboration
How cleanly a bookkeeping firm can be brought in — access levels, handoff, and whether the workflow assumes an in-house finance team.
Not scored
Feature counts
A longer feature list is not evidence of a better fit. In our experience the platforms with the longest lists are the ones small businesses abandon — the count rewards vendors who ship breadth, not the ones who get a handful of GST-registered workflows right.
Not scored
Price
Pricing varies with user count, add-ons and negotiation, so a published figure is a poor proxy for what a Singapore business actually pays. Where pricing is genuinely distinctive, we mention it in the entry text and leave it out of the weighting.
How we test GST handling
IRAS-facing workflow, tested on the recording side
We look at whether the platform's Singapore edition treats GST as a first-class part of the data model or as a configuration exercise the user has to build. Practically, that means checking how tax codes attach to revenue lines, how credit notes and amendments behave in the ledger, and whether the tax invoice output contains the elements IRAS requires.
We do not assess whether a particular supply is standard-rated, zero-rated or exempt, because that is an accounting determination rather than a software feature. Our interest is narrower and more useful: whether the software makes the right answer easy to record and easy to audit later.
Where a vendor's local GST support is claimed but not documented in detail, we say so in the entry rather than treating the claim as verified. That is a small editorial habit, and it matters when a reader is deciding where to spend money.
InvoiceNow readiness
Stated by the vendor is not the same as listed by IMDA
We distinguish between a vendor stating readiness and a product actually appearing on IMDA's InvoiceNow-ready list. Both can be true, and the list is the stronger evidence. The distinction is deliberate — we would rather it read slightly pedantically than be wrong.
How the entry records it
Stated by the vendor
A vendor's own product page or help centre says the platform supports InvoiceNow. We repeat that claim and attribute it, without treating it as verification. Where the vendor documents nothing further, the entry says so.
We also note whether the claim covers sending and receiving, or only one half of the exchange. A platform that sends structured invoices well but handles inbound documents poorly is only half ready, and the entry says that.
Stronger evidence
Listed on IMDA's InvoiceNow-ready list
The product appears on IMDA's published InvoiceNow-ready list of accredited solutions. Where that is the case, the entry says so directly and the readiness claim moves from attribution to evidence.
We re-check the list rather than assume it stayed stable — accreditation changes, and an entry that quotes a list from last year is not evidence, it is a stale page.
Reconciliation and day-to-day friction
An hour or a weekend — usually decided here
Reconciliation is where we rely most on how the workflow behaves with real data. Bank feed quality varies by bank, statement import formats vary by bank, and the number of accounts a business holds changes everything.
We favour platforms where correcting a wrong match is quick and where the unmatched queue has an obvious owner. Those two things decide whether a month-end is an hour or a weekend, which is the part the feature list rarely explains.
We are explicit that behaviour depends on your bank. Where readers report friction with a specific feed, we note it as a report rather than as a finding, because we have not reproduced it on every account type.
- Undo a wrong match without re-importing the feed
- An unmatched queue with an obvious owner
- Statement imports that survive a bank's own format
- Multiple accounts handled without a second file
Sources and updates
Where the information comes from, and how entries get revisited
Nothing in a directory entry is written from a press release, and no entry is left to rot quietly. The two halves below are the sourcing rule and the update rule as they apply across the site.
Sourcing
What we read and what we replace
- Vendor documentation, Singapore edition The primary source for what a platform claims to do, product page and help centre combined.
- IMDA and IRAS published guidance Where InvoiceNow accreditation or IRAS-facing requirements need a public reference rather than a vendor's word.
- Hands-on use where we have access Trying the GST recording, reconciliation and accountant handoff inside the product itself.
- Accountant communities Practitioners encounter edge cases the documentation does not describe; that is often where a caveat comes from.
We do not cite press releases as evidence for a compliance claim, and we do not treat a vendor's comparison chart as a source about a competitor. Where something is reported to us rather than observed directly, the entry indicates that.
Update cadence
Revisited when something changes
- Vendor changes its Singapore feature set A GST workflow change, a new reconciliation behaviour, or a move in InvoiceNow participation.
- Official guidance changes The IMDA InvoiceNow-ready list and IRAS guidance get rechecked rather than assumed stable.
- A reader tells us something is out of date Reader corrections are the single most useful input we get, and they are acted on.
There is no fixed calendar, because software does not change on a schedule. Entries are not versioned publicly, but material changes are reflected in the text rather than left as a footnote saying the page was updated. If an entry is wrong, the fix is published in the entry rather than in a quiet edit.
Conflicts of interest
Why we do not sell implementation
No vendor pays for placement, and none reviews an entry before it is published. There are no affiliate links in the directory. We also do not run an implementation practice, so there is no revenue from helping businesses migrate onto any of the platforms we cover.
That is a deliberate structural choice rather than a moral one: the moment we sold implementation, our advice about which platforms are hard to implement would become unreliable.
Disclosure commitment
If any of this changes, the change appears here first.
The disclosure would appear on this page and on the affected entries before it takes effect — not after.
Paid placement
None
Affiliate links
None
Implementation services
Not offered
Boundaries
What we deliberately do not do
- No numbered ranking
- The input that decides the ranking is your business, not ours. Two firms with the same turnover and the same bank can land on different platforms because one bills a handful of larger customers and the other issues many small invoices.
- No accountant referrals
- We are not positioned to assess the quality of an accountant's work, and the referral would be worth more to us than to you. Other sites do that work; we describe software.
- No false support tests
- We do not open support tickets under false pretences to see how fast a vendor answers, and we do not quote satisfaction scores we have not verified.
- No unverified scores
- Satisfaction percentages and survey rankings get quoted everywhere without provenance. We leave them out rather than repeat them.
What we do is describe how a platform behaves in the Singapore market and who it tends to suit. You bring the rest.
Reader correspondence
The corrections that shaped these entries
Corrections arrive from business owners, bookkeepers and accountants who use these platforms daily. They are quoted here as they were sent, with permission, to show what the report-and-fix loop actually looks like in practice.
"You flagged that the GST support was 'stated by the vendor'. Their help centre now documents the tax code behaviour for Singapore. Worth checking whether the entry should say so."
Common questions
Answers about the evaluation method
If a reader or a reviewer still has a question about how an entry was produced, the fastest way to get an answer is to write to us. The corrections inbox is read every working day.
Corrections inbox
Email [email protected] or call +65 6203 0861, Monday to Friday, 9:00 AM to 6:00 PM.
Do you accept payment for a directory entry?
No. There is no paid placement, no sponsored position and no affiliate arrangement in the directory. Vendors receive no advance copy of an entry, and they cannot see a draft before it is published.
Can a vendor ask for an entry to be changed?
A vendor can point out a factual error and we will check it, which is the same courtesy we extend to any reader. That is a correction process, not an editorial veto, and the resulting change is visible in the entry text rather than tucked into a footnote.
Why do you not score platforms numerically?
Because a number implies a shared context that does not exist. A platform scoring well for a GST-registered agency would score badly for a microbusiness that bills occasionally. We describe fit instead, and explain the criteria so you can weight them yourself.
Do you cover platforms that only serve larger firms?
Only where the Singapore edition genuinely reaches small businesses with six to fifty staff, or home-based operators. Where a platform's local presence is aimed upward, the entry says so instead of pretending the fit exists.
Where to go next
Judge an entry against the method it was written to
Every software directory entry follows the criteria on this page — the GST handling, the InvoiceNow evidence trail, the reconciliation behaviour, and the sourcing note that says where a claim came from. If an entry you read does not hold up against any of it, that is a correction worth sending.