Six service lines that take ledger and operational files through to a monthly pack, a rolling cash view and a signed metric register.
Guide
Each block below is a service you can buy on its own or as part of a reporting build. The word counts describe the work, the artefacts you receive, and the duration we usually quote. Fees sit in a later panel as Singapore-dollar ranges. They are indicative bands for scoping, not a quote. Licensed advisory, tax filing and bookkeeping are outside every line.
Service
The pack is the monthly document the board and the operating team use to close the period. Page order is frozen so a reader can compare months without hunting. Typical contents are a one-page operating summary, P&L versus budget and versus prior year, cash movement, cohort or channel contribution, a short working-capital note, and variance commentary. Every figure has a source in the ledger or in a signed operational extract. We write commentary to the variance. We do not add colour for its own sake.
Build includes the template, the data map, the first three live months under a parallel run, and a short operating manual. After go-live a retainer can operate the calendar. The pack is issued as PDF. A dashboard, if used, shows the same numbers and is refreshed after the pack is signed.
Typical duration: 6–8 weeks for a single-entity pack, longer where multi-entity consolidation is in scope.
Service
The rolling cash view covers thirteen weeks from the last actual bank date. Inflows are built from invoiced receivables, expected collections and known receipts. Outflows include payroll, supplier runs, tax, rent, and debt service. The sheet is refreshed on a stated weekday. Actuals overwrite the first column after each bank file lands. The rest of the horizon is a forecast that uses driver rates, not a copied P&L.
We reconcile opening cash to the bank and explain unpresented items. We do not treat the cash view as a promise of liquidity. It is a scenario on documented collection and payment assumptions. When those assumptions change, the change log records the date and the reason.
Typical duration: 4–6 weeks as a stand-alone model, or inside the reporting build.
Service
Contribution is only useful if the cost map is signed. We list which costs are treated as direct to a product, cohort or channel, which costs are allocated, and which costs stay in a central bucket. The same map is used in the pack and in the forecast so a channel page cannot drift from the P&L. Where data allows, we separate volume, price, mix and discounting.
Payback windows and contribution per order or per contract are calculated from those definitions. They are measurement tools. They are not a claim about future returns. If a channel lacks a reliable cost feed, we say so in the register and we do not invent a number to fill the cell.
Typical duration: 3–5 weeks once revenue and cost extracts are stable.
Service
The annual budget is loaded as a driver-based plan, not as a pasted P&L. Monthly flash compares actuals with that plan and with the prior year. Variance commentary must answer what moved, whether it is timing or run-rate, and what decision it informs. We separate volume, rate and mix where the source files support those splits. Where they do not, the commentary says the split is unavailable.
Re-forecasts during the year copy the driver sheet. We keep a change log so a reader can see which version of the budget a pack was written against. Board packs always name the budget version in the footer of the summary page.
Typical duration: 4–7 weeks depending on the number of cost centres.
Service
This line walks from list price or standard contract value down to contribution. Discount, freight, returns, payment terms and direct fulfilment sit as discrete steps. The walk is rebuilt each period from transactional files rather than from a remembered percentage. Margin by SKU family, contract type or customer segment is produced only when the grain exists in the source.
The output supports pricing conversations inside the business. It is analysis of realised price and cost. It is not a recommendation to raise or cut prices, and it is not tax or legal advice on how a price should be structured.
Typical duration: 3–6 weeks after transactional extracts are mapped.
Service
Reporting fails when keys do not match. This line documents extracts from the ledger, billing, payroll, inventory and channel tools. Each extract has an owner, a file name pattern, a refresh time and a join key. Reconciliation rules state how revenue in the operational file is tied to the ledger, and what happens to unmatched rows. Exception lists are part of the monthly close, not a side note.
We work with the systems already in place. We do not require a warehouse rebuild before a pack can be issued. If a warehouse or a BI tool already exists, we document how our maps sit on top of it. Cut-off rules are written so a late file has a known treatment.
Typical duration: 3–6 weeks, often overlapping the pack build.
| Included | Not included |
|---|---|
| Management reporting packs and commentary | Statutory audit |
| Rolling cash views and driver-based forecasts | Tax filing and tax advice |
| Metric definitions and reconciliation maps | Bookkeeping and ledger posting |
| Dashboard views that match the pack | Licensed financial, investment or legal advice |
| Training the client team on the operating manual | Bonus schemes linked to unpublished performance claims |
We work with the systems already in place. Accounting ledger exports, spreadsheet models, BI dashboards and warehouse tables are all acceptable sources. The constraint is that each source has an owner and a documented mapping. If a dashboard tool is already licensed, we publish pack-matching views there rather than introducing a second screen. If the close still lives in spreadsheets, we keep the model in a controlled workbook until a warehouse extract is stable enough to take over. Tool choice is recorded in the statement of work so a later reviewer can see why a figure is produced where it is.
Every engagement is a written statement of work with a fixed scope and a fixed fee in Singapore dollars. Work outside that scope is quoted before it starts. Indicative bands for a single operating company in Singapore are as follows. A diagnostic review typically sits in the S$4,000–S$8,000 band. A reporting build of pack, cash view and definitions typically sits in the S$14,000–S$32,000 band depending on entity count and the number of source systems. A forecast and scenario model typically sits in the S$8,000–S$18,000 band. A monthly retainer typically sits in the S$2,800–S$6,500 band. These ranges are for scoping conversations. They are not a quote and they do not vary with operating results.
Next step
Send the current pack, name the systems, and say which close calendar you want to hold. We return a 30-minute call and a written summary of the gaps discussed.
Request a briefing