Delivery knows the same day.
Finance hears about it through the margin report.
A project slips by four weeks. Progress sits in time recording, actual cost in the ERP, the estimate to complete in a spreadsheet. They come together at the close — and by then the quarter is gone.
Which projects are losing margin right now — and when does that become cash?
Progress
It arises where the work happens and reaches finance with the period report.
Estimate to complete
The number that decides between intervening and letting it run lives in a spreadsheet in many organisations.
Billing
A milestone that slips changes billing before it shows up at the close.
Margin losses in project business build up across several periods. A monthly report shows them once the buffer is gone.
From the transaction to the decision.
Four steps, and the same cross-functional capabilities across every one of them.
- Cases
- Controls
- Authorities
- Evidence
What comes together.
Every module is a standalone entry point. This chain shows what comes together once several of them run on the same finance data model.
Project Finance PSA
In active development
Keeps progress, actual cost and completion on one project object and computes estimate to complete and estimate at completion.
Margin & Profitability Profitability
In active development
Works the change through to contribution per project, customer and segment — with the project that caused it attached.
Planning & CFO Intelligence FP&A · EPM
In active development
Carries the margin change into the earnings expectation for the period and the year, and names the cause of the variance.
Working Capital AR · AP
Pilot / validation
Sets when delivered work becomes an invoice and from there a receivable — the expected payment date moves.
Treasury & Liquidity TMS
Pilot / validation
Carries the shifted receipts into cash forecast and headroom. Four weeks on three milestones is a funding question.
The chain of financial effects.
Who decides, and what stays of it.
Intervene, renegotiate, redirect or replan. The expected effect stays on the decision, so the actual one sits next to it later instead of being estimated again.
The boundary we do not move.
Time and activity recording
Progress and effort arise where the work happens. FinanceOS reads them.
ERP and accounting
Actual cost and billing stay in the posting system.
Write-back
Where write-back is in scope, it is defined per path and per system and not assumed.
What we can evidence here — and what we cannot.
What is not marked, we do not claim. The full state per capability is on the module pages and under what we can evidence today.
Three questions from the first conversation.
We already have project controlling. What changes?
The reach. Project controlling shows the project. This chain shows what the project change does to portfolio margin, earnings expectation, billing and liquidity — on the same numbers.
Where does the completion estimate come from?
From your own recording. FinanceOS does not invent progress and proposes no pattern from too little history; the assumption stays visibly yours.
Is this a replacement for our ERP?
No. Actual cost and billing stay in the posting system. FinanceOS connects progress, margin, forecast and cash across the systems.
Thirty minutes on one of your own projects.
Bring this case as it looks in your organisation. We work through it on your example and say where a common finance layer holds and where it does not.