Lock the reporting period
Confirm that Program and Finance are describing the same dates, award scope, and version of the budget. A clean reconciliation cannot start while teams are using different cutoffs.
Build a budget-to-narrative bridge
Map material expense categories and program activities to the claims made in the narrative. The goal is not to rewrite accounting records; it is to make contradictions visible before approval.
Surface variance early
Flag unspent balances, overspend, timing differences, reclassifications, and budget modifications early enough for the explanation and approvals to remain consistent.
Resolve ownership of open questions
Every mismatch needs a named owner, next action, due date, and evidence source. A comment without responsibility often survives until the final submission meeting.
Record the accepted explanation
Keep the approved variance explanation beside the reviewed financial file and the relevant narrative section. This gives the final reviewer one version to verify.
Freeze the submitted version
Connect the final financial report, narrative reference, approver, and submission version. If a funder asks a follow-up question, the team can reproduce exactly what was sent.