Which finance figures a weekly operations review needs
Finance reporting for a weekly operations review should be short and provisional: committed and billed cost for active jobs, overdue receivables that affect delivery, payables at risk, and any exception with a known cost. It should come from the same records finance uses for the monthly close, so the weekly view and the month-end figures tell one story. Companies that want this usually need to plan their operations and finance systems together, starting with the operating rhythm.
Operations reviews in most enterprises run on activity: orders shipped, jobs completed, issues outstanding. Finance joins once a month with a P&L describing what already happened. The leaders in the room make weekly decisions about overtime, subcontractors and priorities with no cost signal until it is too late to adjust.
Weekly decisions, monthly books
The two departments work at different speeds for good reasons. Finance closes monthly because accruals, bank reconciliation and accountant review take time, and figures published before that work are incomplete. Operations meets weekly because the work changes weekly. Neither rhythm is wrong, so the weekly report has to be honest about what it is.
Label weekly finance figures as provisional and show how they will be confirmed. A job's committed cost is known as soon as operations places the order; its billed cost appears when the supplier invoice arrives; its final cost settles at month-end. Showing all three stops leaders from treating an early number as final, and stops finance from refusing to share anything until the close.
Cash deserves a line of its own. Operations leaders committing to large orders should know whether the company is in a tight cash week, and finance usually knows well ahead when big customer receipts or tax payments fall due. A one-line cash note in the weekly review prevents commitments finance would have asked to delay.
A finance segment for the weekly agenda
Keep the finance segment to a fixed set of items operations leaders can act on this week. Anything that cannot change a decision belongs in the monthly review instead.
- Active jobs where committed cost is running ahead of plan, with the reason from operations
- Customer balances overdue enough that delivery should pause or continue only with approval
- Supplier bills awaiting operations approval, so payment runs are not held up
- New exceptions from the week with an estimated cost
- Upcoming large payments that affect what operations can commit next week
- Decisions from last week's review and whether they held
Signs both systems need to change together
Finance prepares the numbers and operations prepares the explanations. Circulate both a day ahead so the meeting is spent deciding rather than reading.
Sometimes meeting discipline is enough. If operations already tracks jobs consistently and finance can report by job, the review just needs an agenda. A joint programme for both department systems becomes worthwhile when neither side can produce its half without manual work: operations tracks jobs in spreadsheets that use different names from the ledger, and finance cannot report cost by job at all. Another sign is a weekly meeting that already exists but depends on someone spending the day before it building the finance pack by hand from exports. That effort costs the business every week, and the pack usually stops appearing the moment that person goes on leave.
In that situation, improving one side alone disappoints. A new operations tracker without job-coded finance data produces activity reports with no cost. A finance upgrade without consistent job references from operations produces cost reports nobody can map back to the work.
The order to introduce both systems
Start with the operating rhythm. Agree the weekly review, its attendees and its agenda, and run it for a while with whatever figures exist. That exposes which numbers leaders actually use. Next, settle the job or site reference both teams will carry, and have finance code bills and costs to it. Then bring operations onto consistent work and exception tracking under the same reference. Connecting the two views comes last, once both sides produce clean data independently.
This order keeps the programme grounded in decisions people make every week. Each phase also delivers something on its own: a better meeting, then job-level costs, then live operational status.
Supporting the weekly review with Fasttrade
Fasttrade's BukuOP is built around work tracking, exceptions and operating rhythm, and BukuCloud around bills, invoicing and financial reports. For companies planning both, we start with the weekly review itself and the shared job reference, and we scope any data exchange between operations and finance with you once those foundations are agreed.
Frequently asked questions
Can finance give accurate figures every week?
Not final ones, and it should not pretend to. Committed cost, bills received and payments made are all known during the month and are accurate as far as they go. Accruals, adjustments and accountant review happen at close. Label weekly figures as provisional, show where each number comes from, and reconcile the weekly view to the month-end report so leaders learn how far to rely on it.
Who should present finance figures in an operations review?
Someone from finance who knows the operations side well enough to answer questions, often a management accountant or finance business partner. They present numbers and flag concerns, while operations leaders explain causes and commit to actions. If finance only sends a spreadsheet and does not attend, questions go unanswered and the figures are easily dismissed.
What is the minimum needed to start job-level finance reporting?
A job or site reference that operations assigns before work begins and that finance records against every related bill, cost and invoice. Without that shared reference, job reporting depends on someone matching items by hand. With it, even a simple accounting setup can report cost by job, and more detailed tracking can come later.
Next step
Explore BukuCloud or tell Fasttrade what your team needs.
These articles explain enterprise process design. Product availability and detailed scope are confirmed in conversation.