Cash Forecasting: Build Weekly Cash Plans from FreeAgent Exports in Model Reef

🧭 Overview

This guide shows you how cash forecasting works when you combine FreeAgent exports with a driver-based model in Model Reef. It’s built for founders, finance managers, and advisors who need a weekly cash forecast they can trust-without rebuilding spreadsheets every time an invoice lands late or expenses shift. You’ll set up a repeatable workflow that turns FreeAgent actuals into an ongoing plan: what cash is coming in, what’s going out, and when. The outcome is a weekly view you can use for decisions, scenario planning, and stakeholder updates-aligned to the broader FreeAgent cash flow forecasting approach.

🤝 How Model Reef + FreeAgent Fit Together

FreeAgent remains the operational system where transactions are recorded and reconciled. It’s your “what happened” layer: invoices, bills, bank activity, and historical reporting. Model Reef becomes the “what happens next” layer: a planning environment where you forecast cash, test timing shifts, and turn raw actuals into a weekly cash forecasting rhythm that stays stable as your business scales.
The hand-off is clean: you export a consistent set of FreeAgent reports (or refresh connected datasets), import them into Model Reef, and map them once so updates don’t break. From there, Model Reef structures receivables, payables, recurring costs, and cash reserves into a weekly schedule—so your forecast cash flow reflects both actual performance and forward-looking drivers. If you want to standardise this across clients, teams, or business units, start from Templates. This pairing is best when you need weekly visibility, scenario agility, and fewer spreadsheet rebuilds.

Responsibilities & Hand-Offs (required)

Category	FreeAgent	Model Reef
Source-of-truth system	Stores reconciled accounting actuals.	Stores the planning model built from actuals + drivers.
Primary job-to-be-done	Record, reconcile, and report historicals.	Convert actuals into forward-looking decisions and scenarios.
Data captured / managed	Invoices, bills, bank transactions, journals.	Drivers, timing rules, scenarios, and forecast structure.
Data exported / shared	Financial reports and transaction summaries.	Forecast outputs, scenario comparisons, and weekly cash plans.
What gets modeled in Model Reef	Not designed for modelling logic.	Receipts timing, payments timing, and cash runway impacts.
Refresh cadence	Updates continuously as users post transactions.	Refreshes on a weekly cadence (or more often when needed).
Ownership	Owned by accounting/ops owners of the ledger.	Owned by finance lead who maintains assumptions and logic.
Outputs produced	Historical financial reports.	Weekly cash forecast, stress tests, and decision-ready views.
Common failure point	Inconsistent coding makes exports messy.	Poor mapping causes mismatched categories over time.
Best-practice guardrail	Lock a consistent chart-of-accounts structure.	Map once, then refresh with a controlled import process.

✅ Before You Begin

Before you begin your cash forecasting workflow, align these prerequisites so your numbers stay trustworthy week after week:

Access/permissions: you need permission to export the relevant FreeAgent reports and confirm the reporting period is consistent.
Data needed: at minimum, cash/bank balances, outstanding invoices, outstanding bills, and key expense lines (by category).
Mapping decisions: decide how you’ll group lines for forecasting (e.g., core operating costs vs discretionary, and one-off items vs recurring).
Refresh cadence decision: choose a weekly refresh day/time, and decide what triggers an “off-cycle” refresh (e.g., payroll runs, large customer collections).
Ownership decision: confirm who maintains assumptions, and who signs off the weekly numbers.
Scenario boundaries: agree which levers you’ll vary (collections timing, payment terms, payroll timing, and spend controls) so you can build a reliable cashflow forecast view.

If you want to reduce manual export work over time, review Integrations so you can choose the cleanest refresh path for your team. You’re ready if you can export consistent FreeAgent actuals, define categories once, and commit to a weekly review rhythm.

Step-by-Step Instructions

Step 1: Define the workflow and success criteria.

Start by defining what “done” looks like for your weekly cash forecasting process. For most teams, success is a repeatable weekly pack that answers: (1) current cash position, (2) expected cash receipts by week, (3) expected cash payments by week, and (4) runway under best/base/worst cases. Decide who the output is for: founder decision-making, board reporting, advisory check-ins, or day-to-day cash control. Then define the minimum level of detail. Too much granularity makes maintenance painful; too little hides risk. A strong baseline is: collections, payroll, tax, rent, core operating costs, discretionary spend, and financing movements. Finally, agree how you’ll measure accuracy—e.g., variance between last week’s cash forecast and what actually landed this week-so you can improve the model each cycle.

Step 2: Extract/connect the data cleanly.

Export a consistent set of FreeAgent reports for the same time window each cycle. The goal is to make refreshes predictable-so you can forecast cash flow without rework. Use sanity checks before importing: confirm bank balances match your expected closing cash, and verify your receivables/payables totals reconcile to what the business believes is outstanding. Next, bring the exports into Model Reef and keep the file structure consistent so your refresh cadence doesn’t drift. If your team prefers fewer manual steps, align your process with Deep Integrations so you can streamline how actuals arrive and how often they refresh. This is where many teams lose time: inconsistent export formats and ad-hoc naming conventions. Standardise early, and your cash forecasting workflow becomes an operational habit rather than a monthly fire drill.

Step 3: Map and reconcile (lock the source of truth).

Mapping is the “lock-in” step that makes cash forecasting stable. In Model Reef, define your cash accounts, then map revenue and expense categories into forecasting groupings that match how decisions are made. For example: instead of dozens of expense lines, roll them into a small set of controllable buckets (payroll, marketing, software, contractors, overhead). Reconcile totals so you can trust the structure before you add forecasting logic: your imported actuals should match your expected baseline view for the historical period. Then add timing assumptions—when invoices are expected to collect, when bills are expected to be paid-so your cashflow forecast reflects reality, not accounting recognition. If something looks off, fix the mapping now, not later. Clean foundations are what let you forecast cash weekly with confidence.

Step 4: Build the model logic + outputs.

Now translate your mapped actuals into a weekly plan. Create receipt schedules driven by collections assumptions (e.g., % collected in-week, 7 days, 14 days) and payment schedules driven by terms and payroll cycles. This is where Model Reef adds leverage: instead of a static spreadsheet, you build driver rules that update as the underlying actuals refresh. Your weekly output should show: opening cash, receipts, payments, net movement, and closing cash-plus key risk flags (e.g., lowest weekly balance, weeks below a minimum cash threshold). This structure makes it easy to run “what-if” changes: tighten costs, delay a hire, or shift payment timing to protect runway. The result is a decision-ready cash forecast you can share internally without worrying about broken links or stale tabs.

Step 5: Operationalise: cadence + governance.

Turn your cash forecasting workflow into a routine. Schedule a weekly cycle: refresh FreeAgent actuals, run checks, review variances, then publish outputs. Define governance so the model stays trusted: who updates assumptions, who approves changes, and how exceptions are handled (one-off payments, unusual collections, tax events). Track a few KPIs to keep the process healthy: forecast accuracy by week, number of manual overrides, and time spent on refresh. Over time, refine the model by upgrading “unknowns” into drivers-e.g., split collections by customer type, or payroll by team. This is also where you formalise scenario management: name scenarios consistently, document the differences, and keep a baseline intact. With this cadence, forecast cash flow becomes a weekly management tool-not just a reactive spreadsheet exercise.

🧠 Tips, Edge Cases & Gotchas

If your cash forecast swings week-to-week, check timing assumptions first (collections days, payment terms, payroll dates) before you change the underlying drivers.
Don’t let one-off transactions pollute your baseline: isolate unusual costs (equipment, legal, tax catch-ups) so your cash forecasting view stays comparable.
Watch for timing mismatches between accounting recognition and cash movemen-especially if you invoice monthly but collect mid-month. This is a common cause of “false confidence” in a cashflow forecast.
If categories change in FreeAgent over time, your mapping can silently drift. Build a quick checklist to confirm new accounts get mapped before each refresh.
Permissions matter: if exports are owned by one person, the workflow breaks when they’re away. Assign a backup and document the refresh steps.
If you work across tools, it can help to compare approaches-e.g., Cash flow forecasting for FreshBooks – templates vs Model Reef live models to pressure-test what’s truly repeatable vs what’s spreadsheet habit.

📌 Example

A boutique agency runs weekly cash forecasting to manage payroll risk. They export FreeAgent bank balances, outstanding invoices, and bills each Friday. In Model Reef, they map invoices into expected receipts based on historical collection patterns (70% within 7 days, 25% within 14 days, 5% later), and map payroll + recurring costs into weekly payment schedules. They then run a scenario where a top client pays two weeks late and a contractor cost increases by 10%. The output shows the lowest weekly cash balance would dip below their minimum threshold in week 4, so they adjust the plan: pause discretionary spend and negotiate staggered contractor payments. The next week, they refresh actuals, validate variance, and repeat—keeping the model live and decision-ready. If you want to see what the workflow looks like end-to-end, use See it in action.

❓ FAQs

A cash forecast typically focuses on timing-what cash enters and leaves the bank and when. A cashflow forecast is often used more broadly and may blend operational assumptions with accounting-style categories, depending on the business. In practice, what matters is that your forecast reflects real collection and payment timing, not just recognised revenue and expenses. If you need weekly control, prioritise a timing-based approach that helps you forecast cash flow with fewer surprises. You’re on the right track if your model explains “why” the cash moves, not just “that” it moves.

Weekly is the default for most SMEs, because cash risk changes quickly and weekly cycles align with payroll, collections, and supplier payments. More frequent refreshes make sense during high-growth periods, tight runway windows, or when large receivables are uncertain. The key is consistency: refresh on the same day, run the same checks, and record variances so the model improves over time. If you’re building the habit, start weekly and add an “off-cycle” refresh rule for major events. You’ll gain confidence fast once the workflow is repeatable.

Yes, but you should treat the first cycle as a stabilisation pass. If coding is inconsistent or bills/invoices aren’t up to date, your forecast timing will be distorted. Start by forecasting the “known knowns” (payroll, rent, tax, committed payments) and use conservative assumptions for receipts until the data improves. Over time, you’ll get better outputs as your FreeAgent hygiene improves and your mapping becomes consistent. The goal isn’t perfection on day one—it’s a process that gets more accurate with each refresh.

Keep it simple: opening cash, receipts, payments, closing cash, minimum cash level, and the key assumptions that drive variance. Then review the top 3 timing risks: delayed collections, unplanned spend, and upcoming payroll/tax events. This creates a decision loop where you can intervene early—before cash becomes a crisis. If your weekly review ends in action (tighten spend, chase debtors, adjust payment timing), your forecasting process is working. Start small, keep the structure consistent, and expand detail only when the team actually uses it.

🚀 Next Steps

You now have a practical workflow for cash forecasting that turns FreeAgent exports into a repeatable weekly management cadence. The next step is to standardise your model structure (so refreshes stay clean), document your assumptions (so stakeholders trust the logic), and run at least one downside scenario each cycle (so you’re never surprised by timing shifts). If you want to scale this across multiple clients or entities, build a reusable baseline in Model Reef and treat it as your single planning layer-while FreeAgent remains your accounting source of truth. Keep momentum by upgrading one manual assumption into a driver each week, and you’ll quickly move from reactive spreadsheet updates to proactive decision-making.