T+4
Working-day cut-off for the monthly pack. Source files are frozen on T+2 so reviewers have a full day before issue.
Management reporting that closes on time and survives questions
Beautyandhealthco builds the monthly reporting pack, the rolling cash view and the unit-economics model for Singapore-based operating companies. The work is written so a board pack can be defended from the source ledger.
- Rolling 13-week cash view
- Close pack by T+4 working days
- Driver-based forecast, one model
Operating board
Process facts we hold to
13 weeks
The cash model covers thirteen weeks from the last actual bank date. Receipts, payroll, tax and supplier runs sit on the same sheet.
Monthly
One pack per period, same page order every month. Variance commentary answers the same three questions so the board can compare periods.
4 views
Profit and loss, cash, cohort and channel. Each view uses the same revenue and cost definitions so the four pages reconcile.
1 model
Driver-based forecast lives in a single workbook. Scenarios copy the driver sheet rather than forking a second model.
Quarterly
Assumptions are reopened every quarter. The change log records what moved, why it moved, and which pack version first used the new base.
Remit
What we do
Beautyandhealthco takes raw accounting data and operational exports and turns them into a reporting set that management can act on. Ledgers, bank files, billing systems and channel reports arrive in different shapes. We map them, apply cut-off rules, and publish the same pack on a stated calendar.
The work covers the monthly close pack, the rolling cash view and the unit-economics model. We reconcile those three products to one another so a margin figure in the pack matches the cash implication in the forecast. Definitions are written down before the first model is built.
We operate as an analytics and reporting firm. We do not replace your accountant, file tax, or issue investment recommendations. The output is a documented reporting operation that an owner-manager, finance lead or board can run every month.
Service set
Capabilities
Method
Framework rail
-
Data intake and mapping
We list every source file, owner and refresh time. Field maps sit in a register so a later analyst can repeat the extract without reconstructing it from memory.
-
Reconciliation and cut-off rules
Revenue, cash and balance-sheet movements are tied to the ledger. Cut-off is written as a rule, including what happens when a file arrives late in the close window.
-
Metric definitions signed off
Each board metric has a definition, a source and a named owner on the client side. Build does not start until that register is signed.
-
Build and parallel run
The pack, cash view and model are built against the signed definitions. A parallel run compares the new pack with the existing close before switchover.
-
Monthly operation and review
After go-live the calendar runs. Each issue is reviewed, exceptions are logged, and quarterly re-baselining reopens the assumption set.
Scope and definitions are written down before anything is built.
Deliverables
Reporting output
Three formats carry the same numbers. The board pack is a paginated PDF with commentary. The live dashboard holds the current period and the trailing twelve months for operators who need a screen during the month. The model workbook holds drivers, scenarios and the 13-week cash sheet.
| Deliverable | Format | Cadence | Owner |
|---|---|---|---|
| Board pack | Monthly, T+4 | Reporting lead | |
| Live dashboard | Screen in the client BI tool | Refresh after close | Reporting lead |
| Model workbook | Spreadsheet | Monthly update, quarterly re-base | Modelling lead |
| Cash view | Sheet inside the model | Weekly on the stated day | Modelling lead |
| Definitions register | Controlled table | On change | Client decision-maker |
Coverage
Sectors
Retail and F&B groups
Store contribution, labour hours and inventory days are usually the first three views we stand up.
E-commerce and D2C
Channel contribution, returns and paid-acquisition payback sit on the same definition set as the P&L.
B2B services
Utilisation, DSO and delivery margin are built before any growth dashboard is added.
Light manufacturing and distribution
Gross margin by SKU family, inventory days and supplier payment runs drive both pack and cash view.
Healthcare and wellness operators
Appointment yield, practitioner utilisation and consumable cost are mapped to the ledger before the pack is frozen.
Property and facilities services
Contract margin, mobilisation cash and retention balances are tracked on a site or contract grain.
Worked examples
Illustrative engagement patterns
Multi-outlet group, late pack
The monthly pack reached the board after the second week of the following month. Outlet files arrived on different days. Cash was managed from a separate spreadsheet that did not tie to the P&L.
A T+4 calendar was written, with a T+2 freeze on source files. Outlet contribution was mapped to the same revenue definition as the group P&L. A 13-week cash view was added to the model workbook.
Weekly cash position became available every Monday from the same workbook. Outlet contribution was visible per location. The board pack issued on a stated working-day and carried a reconciliation note to the ledger.
Direct-to-consumer brand, mixed channels
Marketplace, own-site and wholesale numbers lived in three exports. Contribution was discussed in meetings without a cost map. Paid media sat outside the finance pack.
A channel cost map was signed, listing what is treated as direct, what is allocated, and what is excluded. The pack gained a channel page that reconciled to net revenue on the P&L.
Contribution margin became visible per channel. Returns and discounting appeared as discrete lines. The forecast used the same channel drivers as the pack.
B2B services firm, utilisation off-ledger
Time records sat in a delivery tool. Invoicing sat in the ledger. Utilisation and delivery margin were calculated by hand at month-end and often changed after the pack was sent.
A mapping from time records to invoice codes was documented. Delivery margin used signed cost rates. DSO was added to the pack with an ageing bridge.
Utilisation and delivery margin were available on the close calendar. Unbilled time had a stated cut-off. Cash collections could be compared with invoiced revenue on the same page.
Questions
Asked before a briefing
How quickly can the first pack be produced?
A reporting build is scoped at six to eight weeks including a parallel run. A diagnostic review in three weeks produces a gap list and a calendar, not a live pack. Timing depends on data access and a signed definitions register.
Do you replace our accountant?
No. We work from ledger exports and operational files. Statutory accounts, tax filing and bookkeeping stay with your existing accountant. We document the mapping so both sides can see where a figure originated.
What data access do you need?
Read access to the accounting ledger export, bank statements or bank-feed files, and the operational systems that feed revenue and cost. We prefer client-owned systems. Access is listed in the statement of work.
How are fees structured?
Fixed scope and a fixed fee, written in a statement of work. Indicative bands are published on the capabilities page in Singapore dollars. Work outside the signed scope is quoted before it starts.