A · Correct
Corrections to anything on the site
Name the page and quote the sentence. Whether it is a rate, an integration detail or a workflow step, the page and the exact wording are what let us check it in one read.
Contact the editorial team
Reach the desk
Contact the LedgerLane Editorial Team
One inbox for corrections, topic suggestions and questions about cloud accounting in Singapore. This page explains what to send and what happens after you do.
- Editorial inbox
- [email protected]
- Phone
- +65 6844 4118
- Working hours
- Monday to Friday, 9:00 AM – 6:00 PM
- Postal address
- 1 Raffles Place, #20-61 One Raffles Place, Singapore 048616
Editorial inbox · routing
Priority
Corrections & factual updates · first read
Routing
Questions about a platform decision, topic ideas for the guide
Deadline
Time-sensitive note goes on line one — we answer honestly about timing
What to send us
Four things arrive in the inbox that actually move the guide forward.
The pages are written for Singapore SMBs who run their own books, so the useful messages are the ones that touch that reality: a number that has changed, a workflow a platform now does differently, or a local gap nothing else covers.
B · Decide
Questions about a platform decision you are stuck on
Describe the choice and what you have already tried. We will point you at the comparison row or the workflow page that addresses it, which is usually faster than a general answer.
C · Suggest
Topic suggestions, especially Singapore-specific gaps
Where a local angle — a bank feed route, an IRAS workflow, a UEN handling case — is not covered anywhere useful, that is the suggestion we want most.
D · Update
Factual updates when something has changed
A bank feed, an integration or a compliance detail that has moved. Send the change and the date you noticed it; that is enough to start the verification.
A better correction
What makes a correction actionable
Name the page and quote the sentence. State what is wrong and, if you have one, the source that contradicts it. We verify before we change anything, so the source saves a round trip.
Sources that move fastest
- IRAS or ACRA — the primary pages for GST and company filings.
- A bank's own integration documentation — DBS, OCBC or UOB feed notes.
- A vendor's Singapore-specific material — regional release notes or pricing pages.
We do not change copy on a stranger's word. Every rewrite is checked against a primary source before it publishes, which is why a citation in your first message is worth more than a follow-up thread.
Reply timing & who reads
What happens after you send the message
How quickly to expect a reply
Corrections get read first, usually within a few working days.
General questions take longer — particularly through GST filing periods when the inbox fills up faster than it usually does. If your query is time-sensitive, say so in the first line and we will tell you honestly whether we can help in time.
Expected read window
- Day 1–3 Corrections read
- Day 3–5 Verification
- After Change published
Who reads the messages
The editors who wrote the page, not a support queue.
Messages go to the editorial team, and they are read by the people who write the pages. That is why a specific correction gets a specific response rather than a template — and why the reply you get names the sentence it is talking about.
It also means volume is handled by a small group, so replies are not instant. If your message needs a decision we cannot make — a rate filing, an audit trail, a platform commitment — we will say so instead of guessing.
Expanding beyond the guide
If your question needs a qualified accountant — a tax position, a filing, a review of your books — that is the honest answer, and we will point you toward the right page on this site rather than stretch the reply.
What we cannot help with
We are not an accounting firm. We will not file for you, review your books, or advise on your tax position.
Questions that depend on your own circumstances need a qualified accountant. What we can do is point you toward the page on this site that covers the workflow — and be clear when a question sits outside that.
Reporting a technical problem
A page nobody can read is not much use to anybody.
If a page will not load, a link goes nowhere, or something looks broken, tell us the page and roughly when it happened. Browser and device details help. These reports get passed on quickly.
Include if you can
- The page URL or the link to the section you were on
- Roughly what time you saw it, and which time zone you are in
- The browser and device you were using, plus a screenshot if easy
Before you write
Check these three pages first
They answer a lot of the questions that would otherwise take a round trip. If they do not, the inbox is still the right place.
- How we review and update The verification method behind every comparison, which answers most questions about why a platform was described a certain way.
- Privacy policy What happens to your data when you use the form on this page, and how long it is kept.
- Compare cloud accounting software The platform comparison answers most of the which one should I pick questions directly, without a message.
Send your message
One form. It posts to the editorial inbox.
Tell us what page you are writing about and what you found. A source or a link in the first message saves a round trip. If your query is time-sensitive, note that in the first line.
Where to continue
The guide is what we are here for. The inbox is how it stays accurate.
Whether you came to flag one sentence or to ask which platform suits a two-person Singapore shop with GST registration around the corner, this page is the right door. If a correction lands, the whole guide gets better for the next reader.