🧭 Overview
If your team relies on MYOB for clean actuals but still struggles to produce a confident forecast, this guide is your bridge. We’ll show how to turn transaction history into a repeatable financial forecasting workflow by exporting MYOB actuals, mapping them into Model Reef, and building a driver-based forecast that updates without spreadsheet chaos. It’s built for finance leaders, accountants, and operators who need a plan that’s explainable, scenario-ready, and board-presentable. If you want the bigger picture on planning workflows, start with MYOB budgeting and forecasting.
🔗 How Model Reef + MYOB Fit Together
MYOB is your source of truth for accounting: it captures transactions, produces statutory reports, and keeps your chart of accounts consistent. But forecasting in accounting often breaks down when you try to “plan inside the ledger” – because forecasting needs drivers, assumptions, scenarios, and governance around change. That’s where Model Reef fits: it layers a planning model over your MYOB actuals so you can build forecasts that are measurable, explainable, and easy to iterate as conditions change. Practically, MYOB exports provide the actuals baseline, while Model Reef converts those figures into a model that supports assumptions, versions, and scenario comparisons. If you want a deeper breakdown of responsibilities and outputs, see the Model Reef vs MYOB comparison. This pairing is best when you want MYOB to stay clean and compliant, while Model Reef handles planning complexity.
✅ Before You Begin
Before you build a repeatable financial forecasting workflow, confirm a few fundamentals:
- Access: MYOB user permissions to export P&L, balance sheet, and relevant detail (tracking categories/classes if used).
- Data scope: decide entities, departments, and the time range (typically 12–24 months actuals, plus a 12–18 month forecast horizon).
- Export format: align on a consistent MYOB export structure (account codes, names, periods, and any dimensions).
- Mapping decisions: confirm how accounts roll up into planning lines (COGS, opex buckets, payroll groupings).
- Refresh cadence: choose whether forecasting refresh happens monthly (post-close) or mid-month (flash updates).
- Ownership: assign who owns the export, who owns model logic, and who signs off on scenarios.
- Tooling decision: determine whether you’ll run a manual export/import, or move toward productised connectors via Integrations.
You’re ready if you can export consistent actuals, you have a forecast owner, and you’ve agreed what “forecast-ready” looks like for stakeholders.
Step-by-Step Instructions
Step 1: Define the workflow and success criteria.
Start by defining what “done” means for financial forecasting in your business. Who is the forecast for (CEO, board, department heads), and what decisions does it support (hiring, pricing, cash runway, inventory buys)? Set the horizon (e.g., 12 months rolling), the granularity (monthly vs weekly), and the outputs you’ll publish (P&L, cash view, driver summary). Then pick the forecast “spine”: what top-level drivers explain performance (volume, price, headcount, utilisation, churn)? This is where many financial forecasting methods fail – teams begin with a spreadsheet layout instead of a decision-driven model. Finally, define success metrics: forecast accuracy bands, cycle time to update, and whether scenario comparisons are mandatory each refresh.
Step 2: Extract/connect the data cleanly.
Export MYOB actuals in a way that stays consistent every cycle: same report, same filters, same time buckets. Validate totals against your MYOB financial statements to avoid silent mismatches. Then decide the hand-off approach: (1) a controlled export/import workflow, or (2) automated refresh via Deep Integrations if you need higher cadence or reduced manual handling. Either way, establish a “data contract”: one file naming convention, one folder location, one owner. Clean up the obvious friction early – account naming inconsistencies, missing months, and dimension changes – because these are the fastest way to break financial forecasting models over time. The goal of this step isn’t perfection; it’s repeatability and trust, so the forecast conversation stays on drivers rather than spreadsheets.
Step 3: Map and reconcile (lock the source of truth).
Now reconcile structure, not just totals. Create a stable mapping from MYOB accounts into planning lines (e.g., “Marketing spend” vs “SaaS tools”), and document any rules (capitalise vs expense, reclasses, one-off exclusions). In Model Reef, treat mapping like product design: if leaders can’t understand it, they won’t trust it. This is also where forecasting in accounting typically hits its ceiling – the ledger view is excellent for reporting history, but planning needs a driver-aligned view that remains consistent when the chart of accounts changes. Build a small set of standard rollups and lock them. If you need departmental forecasting, confirm allocation logic and prevent “double counting” by clearly defining what belongs to each cost bucket.
Step 4: Build the model logic + outputs.
With clean structure, build the planning logic around drivers, not line-item guessing. Choose the right financial forecasting methods for each section: top-down for broad costs that scale with revenue, bottom-up for headcount and unit economics, and rule-based for recurring expenses. This becomes your operational financial forecasting models library – consistent drivers, assumptions, and scenarios that can be reused across cycles. Design outputs for action: a baseline forecast, an upside/downside scenario, and a short variance narrative. Keep reporting stable (same charts, same KPI definitions) so stakeholders can compare month-to-month without relearning the pack. The goal is a model that leaders can challenge (“what changes if churn rises?”) without breaking the build.
Step 5: Operationalise: cadence + governance.
Finally, turn forecasting into a system. Set a cadence (monthly close + mid-month flash, or monthly only), define review stages, and implement version naming that everyone understands (Baseline, Reforecast 1, Board Case). Add governance: who can edit drivers, who approves assumptions, and when scenarios are locked. This is the difference between “we built a model once” and an always-on financial forecasting workflow. Make the process visible: publish an update checklist, log major assumption changes, and keep a changelog of driver edits. If you want a quick walkthrough of how this looks end-to-end, See it in action. The outcome is a forecast that’s faster to refresh and easier to defend.
🧪 Example
A services firm closes books in MYOB monthly but needs a forecast weekly because project demand changes fast. They export MYOB actuals each close, map costs into stable planning buckets, and build a driver model based on billable headcount, utilisation, and average rate. Mid-month, they update utilisation assumptions and run downside scenarios for pipeline risk. The finance lead publishes a two-page forecast pack: baseline, downside, and a short driver narrative. After two cycles, update time drops from two days to two hours, and stakeholders stop debating “what the spreadsheet means.” For teams who also want the cash impact view alongside the P&L, the rolling cash workflow in the MYOB cash flow forecast guide is the natural next layer.
🚀 Next Steps
You now have a practical how to workflow for turning MYOB history into repeatable financial forecasting – without turning your ledger into a planning tool or your spreadsheet into a single point of failure. The next step is to pick your first driver set, run one baseline forecast, and schedule your first recurring refresh meeting. When you’re ready to see a complete workflow in motion, See it in action.
Back