Learn / Costing
7 costing reports every F&B CFO should run weekly
Most F&B CFOs see costing data once a month at close. That's three weeks too late to act on operational issues. Here are the 7 reports you should be looking at every Monday — and what each one tells you about the past week.
Most F&B CFOs see costing data once a month, during close. By that time, any operational issue has been running for 2–3 weeks. Variance has accumulated. The cause is hazy. The fix is delayed.
The CFOs who get ahead of margin compression do something different: they look at the same data weekly, scan for outliers, and act fast on signals.
This article lists the 7 reports worth looking at every Monday, what each one tells you, and where in AION you’d find them.
Report 1 — Weekly variance summary by job
What it shows: Every job order completed last week with its variance breakdown (material usage, labour efficiency, overhead).
What to look for: Outliers. Sort by total variance descending. The top 3–5 jobs usually account for 60–70% of total variance for the week.
Action: For each outlier, drill into the job-level detail. Compare to the rolling 8-week average for the same SKU. Is it a one-off (operator change, equipment hiccup) or a trend?
Where in AION: Manufacturing → Variance Report → filter by completion date in past 7 days. Source endpoint: /manufacturing/variances/discrete-jobs/:jobId.
Report 2 — Material usage trend by raw material
What it shows: Variance per raw material aggregated across all jobs that used it, weekly, for the past 12 weeks. Trend line per material.
What to look for: Materials whose variance is consistently increasing. Flat = healthy. Trending up = recipe drift, supplier issue, or process discipline gap.
Action: For materials with increasing variance, audit the recipe vs actual consumption. Possibly recipe needs updating; possibly supplier changed something; possibly measurement is drifting.
Where in AION: Manufacturing → Variance Trend → group by material, last 12 weeks.
Report 3 — WIP balance by warehouse / line
What it shows: Current WIP balance broken down by production warehouse or sub-inventory. Compared to last week, last month, year-to-date trend.
What to look for: WIP balance growing faster than revenue. WIP-to-revenue ratio creeping past 10% of monthly revenue. Single line or warehouse holding disproportionate WIP.
Action: If WIP is growing, dig into why. Slower cycle times? More QA holds? More jobs in flight? Reduce WIP through prioritisation and clearing the backlog.
Where in AION: Manufacturing → WIP Balance → group by warehouse. Source: get-wip-valuation.use-case.ts.
Report 4 — Item cost trend, top 20 SKUs by volume
What it shows: Average cost month-over-month for your 20 highest-volume SKUs. 6-month trend line per SKU.
What to look for: SKUs where cost is rising faster than your pricing power. SKUs where cost is rising and you haven’t moved sell price. SKUs where cost is falling — opportunity for margin expansion or competitive pricing.
Action: For SKUs with rising cost and stable sell price, the margin call is overdue. For SKUs with falling cost, decide whether to pass to customers or capture margin.
Where in AION: Inventory → Item Cost History → top 20 by 90-day volume.
Report 5 — Inventory valuation reconciliation
What it shows: Inventory subledger total vs GL inventory account balance. Should match exactly. If they don’t, the gap is unposted activity or a reconciliation issue.
What to look for: Any non-zero variance. Even small drifts compound over months.
Action: Investigate. Common causes: in-transit inventory not yet received in the system, costing close not finished for the period, missing journal for a costing adjustment.
Where in AION: Inventory → Reports → Valuation. Cross-check against GL → Trial Balance → Inventory accounts.
Report 6 — Overhead absorption variance
What it shows: Absorbed overhead vs incurred overhead, by resource (bottling line, blending line, packing crew, QA). Weekly.
What to look for: Under-absorption (resource ran fewer hours than budgeted; fixed overhead spread less). Over-absorption (rare but indicates higher utilisation than planned). Resources where absorption is consistently off — your absorption rate is wrong.
Action: Under-absorption suggests utilisation problem (downtime, line speed below plan). Reset the absorption rate annually based on actual run-rate.
Where in AION: Manufacturing → Resource Utilisation → Overhead Variance.
Report 7 — Top variance contributors, year-to-date
What it shows: Cumulative variance dollar value, by category (material usage, labour efficiency, overhead) and by SKU. YTD ranking.
What to look for: Where the SAR is actually going. If material usage variance is SAR 800K YTD and labour efficiency is SAR 50K, you know where to focus. If one SKU accounts for 30% of total variance, you know which SKU to fix first.
Action: Use this to allocate management attention. The biggest variance categories get the most senior eyes.
Where in AION: Manufacturing → Variance Summary → YTD pivot.
How to set up the weekly cadence
If you’re starting from zero, here’s a 4-week implementation:
Week 1: Identify the 7 reports above as saved queries in AION. If a report doesn’t exist yet, build it. Define thresholds (what’s a yellow vs red flag for each).
Week 2: Run the reports manually on Monday morning. Time how long it takes. Note which thresholds are useful vs noisy.
Week 3: Set up a Monday-morning calendar block for the analyst plus the CFO. 30-45 minutes. Walk through each report together. Capture follow-up actions.
Week 4: Tune the thresholds based on what was useful vs noise. By now you should be looking at the right outliers, not chasing every minor variance.
After a month of this rhythm, the CFO is acting on operational issues 2–3 weeks earlier than the previous monthly cadence. Margin compression that used to be invisible is now visible. The variance accounts go from “background noise on the financials” to “leading indicators we monitor.”
What this doesn’t replace
Weekly reports are operational. They don’t replace:
- Monthly close. Books still need to close monthly for legal and tax reporting.
- Board reporting. Boards look at financial summaries, not job-level variance.
- Annual budgeting. Standards still need to be reset annually based on engineering and procurement reality.
The weekly reports are for the CFO and the production director, not for the board.
Where to go next
If you’re not yet capturing the underlying data — material issue transactions, labour bookings, completion postings — start with the Period close in 2 days article which covers what AION captures from the operational layer. If you’re set on the data side and want to understand the costing capabilities feeding these reports, the pillar guide on food manufacturing costing is the comprehensive overview.
For the specific outlier you’ll spot first — material usage variance — go to Material usage variance — spotting recipe drift.
See this in the Oasis Fresh demo
Log into the Oasis Fresh (Saudi) BG as cfo.saudi
Common questions
Why weekly cadence and not monthly?
Monthly reporting is for the board. Weekly reporting is for management. A material usage variance spike on the second week of the month is a 2-week-old problem if you only look monthly — by the time you act, 8 more days of the same issue have happened. Weekly cadence catches issues when they're still small and the cause is fresh.
What if our ERP can't produce these reports?
Then you don't have an accounting system, you have a bookkeeping system. The reports below all come from data the ERP already captures during normal operations — receipts, issues, completions, scrap. If the reports aren't available, the data is being thrown away or never structured in the first place. That's a deeper fix than reporting.
How long should running these reports take?
30-45 minutes for all 7, if you have an analyst doing it once a week and the ERP has them as standard reports. The first time you set up the cadence it takes longer — building the saved queries, agreeing on thresholds. After that it's a Monday-morning routine.