8 Marina View, #28-01 Asia Square Tower 1, Singapore 018960

Monday–Friday, 9:00 AM – 6:00 PM

About the editorial desk

The total is the only thing that should look live.

Meridian Ledger is an editorial resource for Singapore group finance teams working through cloud bookkeeping, consolidation and intercompany close. It is written by people who have closed group books, not by a marketing team repurposing vendor pages.

Published for
Group finance teams
Singapore
Written by
Finance practitioners
No bylines yet
Reviewed against
Vendor documentation
Before publishing
Reader corrections
Welcome
Published as received
Paid placements
None
Disclosed where they would exist

Why this site exists

The question "which cloud accounting platform handles multiple entities" gets answered badly. Roundups written for freelancers put FreshBooks next to NetSuite OneWorld as if they were alternatives, and a group controller reading that wastes a week.

We write for the reader who already has a ledger and an accountant, and who needs to know what changes when a second, third and fourth entity arrive.

That is a narrower audience than most accounting sites target, and it is the one we are built for. The honest answer to the platform question usually depends on intercompany volume, entity count and how much of the close is currently manual — so that is the ground every guide on this site starts from.

The editorial desk

Who writes and reviews the pages

The desk is small on purpose. Every practitioner note below describes how a piece of guidance on this site gets written, checked and published — or which part of the practice we are honest about still being thin.

Background

Who writes the guidance

The editorial desk is made up of finance professionals with Singapore group accounting experience, plus contributors who have implemented multi-entity systems locally. They have run month-end closes across entities, worked eliminations by hand, and seen how the software behaves when the group grows from two entities to four.

We do not publish author names on every page yet, and we note that as a limitation rather than dressing it up. What you can rely on is that the writing is done by people who have had to explain a group figure to a board, not by a copy team repurposing vendor pages.

Corrections

How corrections are handled

Corrections are welcome from any source and published regardless of who sends them. We do not remove a correction once it has been made, and where a page has been reviewed against new information the update is noted on the page itself.

If you spot something that does not match the documentation or your own experience with these platforms, sending it on is more useful than quietly disagreeing with the page. Send it to the editorial desk at [email protected].

Review

Who reviews before publishing

Substantive pages are checked for factual accuracy against vendor documentation before they go live, and, where relevant, against published Singapore advisory material on intercompany treatment, GST registration and e-invoicing readiness.

Reviewers are not named, and none of them are compensated by the platforms discussed. The check is about whether a claim survives contact with the documentation — not about whether the platform comes out looking good.

Practitioner input

Where a contributor has an interest

Where we cite a firm with an implementation interest — RSM Stone Forest's guidance on Sage Intacct or on intercompany capability, for example — we say what that interest is next to the citation.

Practitioner content is often better than vendor content and it is still not neutral. Reading it with the interest in view is more useful than pretending the interest is not there.

The practice workroom at midday — a ledger shelf, a statement tray and one person in profile at the desk
The practice workroom at midday — where the desk actually sits, and where most of the guidance on this site was written.

How we handle conflicts of interest

Two positions this site holds, and one place you would see a conflict disclosed if it ever existed.

Position we hold
What it means for the reader
Where to check

No payment for placement

We do not take payment to be included in comparisons, and no platform has paid to sit higher in a list on this site.

If a platform's position on a page ever reflected a commercial arrangement, that arrangement would be disclosed on the page itself and on this page — in the same place a reader would look for it.

On every comparison page

No affiliate links

No link out of a comparison earns the desk a commission. Nothing on this site is a paid introduction.

If that ever changes — for example if a vendor-funded summary were added — the paid relationship would be printed on the same block of copy the reader is reading, not in a footnote.

Same place as the row above

Practitioner citations carry their interest

When we lean on a firm's guidance — RSM Stone Forest on Sage Intacct, for instance — we name the interest next to the citation.

Practitioner content on multi-entity software is often more honest than vendor marketing. It is still not neutral, and the interest sitting behind it is part of what you are reading.

Beside each citation

Coverage

What we cover, and what we don't

The site is deliberately not an everything-to-everyone accounting page. Both lists below are short because both lists are honest.

Inside the scope

Group-level work

Chart of accounts design across entities, intercompany reconciliation and eliminations, multi-currency handling, month-end close sequencing, GST reporting per registration, and InvoiceNow-aligned e-invoicing flows.

Platform comparison across Xero, QuickBooks Online, MYOB, FreshBooks, AccountsIQ, Sage Intacct, NetSuite OneWorld and Oracle Fusion Cloud ERP — plus workflow tools such as Datamolino and Airbase, where they materially change how a close runs.

Outside the scope

Needs a practitioner

Corporate tax filing, audit, transfer pricing and employment matters are not covered here. Each of those needs a Singapore practitioner with your structure in front of them, and pretending the site can substitute for that would waste your time.

Where a question sits at the edge — an intercompany pricing policy that also has a tax consequence, for instance — we note who should be in the room rather than answering it for you.

Updates

Platforms change their multi-entity positioning and Singapore compliance requirements change too. Substantial pages are reviewed periodically; where a page has been reviewed, the date is noted on it.

Nothing is posted from this field — it just sizes itself to your answer, the way a worksheet column would.

Updates and review

How updates work

An editorial resource that never moves is not really an editorial resource. The pages on this site are reviewed periodically and updated when something material shifts — a vendor changes how its multi-entity tiers are sold, a Singapore reporting requirement moves, or a practitioner note turns out to be wrong.

Where a page has been reviewed, the date is noted on it so a reader can see how recent the position is. Where it has not been reviewed since a change we know about, we say so on the page rather than quietly leaving a stale answer standing.

Send a correction

Corrections are welcome from any source and published regardless of who sends them. If a page on this site disagrees with the vendor documentation or your own books, we would rather hear it than not.

Contact the editorial desk

Reach the desk

Corrections, notes from your own close, or a specific question about a platform's multi-entity behaviour — all of it comes to the same inbox. There is no separate sales desk on this site.

Address
8 Marina View, #28-01 Asia Square Tower 1, Singapore 018960
Desk hours
Monday–Friday, 9:00 AM – 6:00 PM