EDGE financial framework: build a 13-week cash-flow control

An EDGE financial framework project should help management decide, not only improve the appearance of reports. A practical starting point is a 13-week cash-flow control connected to sales, collections, purchasing, payroll, tax and financing. The same project can then align financial models, KPI reporting and the strategic roadmap around one set of assumptions.

Reconcile the opening position

Begin with bank balances, restricted cash, undrawn facilities, overdue receivables, committed purchases, payroll, tax and debt payments. Reconcile the first forecast week to the accounting records and bank statements. Identify entities and currencies explicitly. An unexplained opening balance makes every later cash conclusion unreliable.

Build a receipts schedule by customer and invoice rather than applying one collection percentage to revenue. Use agreed payment terms, actual collection history and known disputes. For payments, separate contracted dates, management choices and uncertain estimates. This gives the forecast a clear audit trail and allows owners to update their inputs.

Fit the official financial-management scope

The official activity page supports initiatives covering performance tracking, financial reporting and growth planning. Its listed deliverables include a business plan, financial-management gap analysis, financial models, KPI tracking system, strategic recommendations and roadmap. The proposal should show how each output will be used and accepted.

The page excludes business valuations solely for setting a transaction price, regulatory compliance work and post-deal purchase price allocation among other items. Separate those needs from the supported advisory scope. Record the full company-funded cost and obtain current written clarification where a workstream sits near a stated boundary.

Design the 13-week decision rhythm

Assign a weekly cutoff, preparer, reviewers and owners for sales, collections, purchasing and payroll inputs. Compare actual cash with the prior forecast and classify timing, amount and missing-item variances. A forecast that is overwritten each week cannot reveal bias. Retain each approved version and the actions taken.

Set thresholds for decisions such as delaying discretionary spend, accelerating collection, drawing a facility or seeking board approval. Show the earliest week in which headroom falls below the agreed minimum. Do not use the forecast to promise solvency. It is a management model whose assumptions require continuing review.

Connect KPIs to cash and strategy

Choose measures that explain the forecast: order intake, gross margin, delivery backlog, invoice accuracy, days sales outstanding, inventory turns and supplier terms. Name the source system and owner for each. Avoid dashboards with dozens of measures that do not change a decision. A KPI should have a target, variance explanation and response.

Build base, downside and action cases for the strategic model. Keep volume, price, headcount, capital expenditure and financing assumptions visible. Reconcile the near-term 13-week forecast to the annual plan and explain differences. This stops the board from seeing one cash story in operations and another in the business plan.

Accept the framework through live use

Require at least two complete forecast cycles using current data before final acceptance. Test late invoices, a disputed receivable, foreign currency, tax payments and an unexpected purchase. Confirm that staff can update the model without breaking formulas and that access to banking and payroll data is restricted appropriately.

Link the finished model to the EDGE project cash-flow guide and the consultancy completion file. Use the business support cornerstone to compare the project with self-funded finance improvement.

Use a controlled implementation file

Keep one dated file that links the decision, approved scope, source evidence, responsible owner, milestones, costs and final acceptance. A status label should distinguish proposed, approved, completed, claimed and paid items. This prevents an application acknowledgement or a vendor invoice from being mistaken for a completed outcome.

Review the file when ownership, scope, eligibility or timing changes. Preserve the earlier version and the reason for the change. Where a formal adviser, auditor or authority is required, record that dependency rather than replacing it with an internal assumption. Management remains responsible for accurate declarations and the commercial decision.

Stage the decision before commitment

Use four review points: fit, application or authority engagement, implementation and closeout. At the fit review, confirm the applicant, activity and business need. At the application review, freeze the requested scope and preserve the submission. During implementation, compare actual work with the approved terms. At closeout, reconcile deliverables, cost, payment, evidence and continuing obligations.

Name the person who may approve each review point and the evidence that person must see. Procurement should not treat a draft application as approval to contract. The project team should not treat a vendor completion notice as company acceptance. Finance should not treat claim submission as payment. These distinctions protect both operating quality and the integrity of any support request.

Plan for changes and exceptions

Maintain an exception log for delayed milestones, substituted staff, changed suppliers, cost movements, technical limitations and missing evidence. State the effect on scope, business benefit, eligibility and timing. Where authority approval is needed, submit the change through the official route before relying on it. Silence or a portal upload should not be read as consent.

For a material defect, pause the affected acceptance or claim item, preserve the original evidence and assign corrective action. Do not rewrite a baseline after seeing the result, backdate a document or move a cost between categories to improve the appearance of compliance. A transparent exception with a resolution is stronger than a clean file that cannot explain the actual project.

Close the project with independent readback

Have a person who did not prepare the final pack compare the approved terms, latest deliverables, invoices, full-payment evidence and operating result. Recalculate totals and test several source records. Confirm that public, employee or customer claims remain accurate. Record unresolved items separately, with owners and dates, instead of hiding them in a completion statement.

After submission, retain the acknowledgement and reconcile any questions, adjustments and final receipt to the project ledger. Continue conditions that survive closeout, including record retention, asset use, reporting or outcome commitments. The project is finished only when management can explain what was approved, what was delivered, what was paid and what must still be maintained.

Practical review checklist

• Opening cash reconciled
• Receipts and payments have owners
• Forecast versions preserved
• KPIs drive decisions
• Two live cycles accepted

A credible financial framework gives management one reconciled view of cash, performance and strategic choices. The 13-week control is the proving ground: if owners can explain variances and act on them, the wider framework is becoming operational.