How do you track budgets, invoices and actual spend?
Track budget and actual spend by linking the approved budget to the financial records for the same grant, period and cost categories. Define what “actual” means under Finance’s reporting basis, keep invoices and payment status distinct, reconcile the totals and explain the differences. A submitted or approved invoice does not by itself establish that cash was paid or that the amount belongs in the period’s reported expense.
By Sopact Academy · Reviewed September 12, 2026. This lesson combines cited public guidance with practical workflow recommendations. Figures and teaching scenarios are illustrative unless explicitly identified as a published case.
Follow one reported amount back to its source
Bring: the approved budget, a financial report and a small set of supporting records. Use the matching-period rules from How Do You Compute Grantee Variance?.
Leave with: a budget-versus-actual view with a defined basis, source references and unresolved differences. Finance remains responsible for accounting treatment and approval; the examples here are fictional monitoring exercises.
What does actual spend mean?
Actual spend is the amount recorded as spent for the defined reporting purpose and period. The report must state its basis: a cash-payment view and an expense view may include different amounts at the same date. Ask Finance which records and rules govern the report instead of treating “actual” as a self-explanatory label.
| Term | What it describes | What it does not establish alone |
|---|---|---|
| Budget | The approved plan for a defined scope and period | That the planned amount has been spent |
| Commitment | An obligation or planned purchase tracked under the organization’s rules | That an invoice has been received or paid |
| Invoice | A supplier’s bill with a date, amount and supporting details | Payment, correct coding or the accounting period |
| Approved invoice | An invoice that has passed the relevant approval process | That settlement is complete |
| Payment | A recorded cash settlement | That the whole payment is the expense for this reporting period |
| Reported actual | The amount included under the approved reporting basis | Completeness unless it has been reconciled to the relevant records |
Confirm which approval, invoice and settlement statuses Finance uses, and which authoritative source establishes each one. Approval alone does not establish payment.
1. Attach the approved budget and its dimensions
Identify the grant or award, program, legal entity, funding source, currency, fiscal period and budget version. Use only the dimensions that matter to the reporting task, with agreed definitions.
For a multi-year grant, keep both the total authorized budget and the relevant period plan visible. A fiscal year may differ from the grant year. Do not spread a total evenly across months unless that is the approved plan.
Stable identifiers reduce ambiguous matching, but matching tags alone do not prove the amounts are correct. A budget line needs a clear relationship to the records included in its actual total.
2. Preserve revisions and approvals
Keep the original approved budget and each authorized revision, including the effective date and reason. Label a proposed revision as proposed until the required approval is complete.
When comparing a prior report, use the target version appropriate to that comparison. If you also show a restated comparison under a new budget, label it separately. Do not erase a historical shortfall by silently replacing the original plan.
A practical revision record answers four questions: what changed, who requested it, who approved it and when it applies. Keep the supporting explanation accessible to the authorized reviewer.
3. Collect supporting records with enough context
An invoice submission should identify the supplier, invoice number, invoice date, amount, currency and the relevant program or cost category, alongside the file. Capture the service period where it is needed to interpret the charge.
Some actuals come from records other than invoices, such as payroll summaries, approved allocations or other Finance records. Do not assume a complete invoice folder equals complete program spending. Collect the supporting level of detail Finance requires while limiting access to sensitive information.
For compensation costs, agree the period, cost categories and allocation basis with Finance. A total salary budget cannot be checked against a partial set of contractor invoices. Keep the report’s scope clear rather than expanding into individual payroll detail unnecessarily.
How do you track compensation budget spend?
Start with the approved compensation budget and the payroll or allocation report for the same period. Confirm whether both include the same salary, employer benefit and other cost categories. Keep the cash payment date separate from the period Finance assigns the cost to.
- Identify the compensation lines and grant or program codes in the approved budget.
- Obtain the relevant Finance-approved actuals, using the minimum employee-level detail needed for the review.
- Apply the approved allocation basis for shared roles. Retain its source and effective period.
- Reconcile the allocated total to the source, then compare it with the matching budget and explain exceptions.
Fictional example: Finance confirms $15,000 in eligible compensation costs for a shared role this month and an approved 30% allocation to the grant. The grant share is $4,500. Against a $5,000 monthly compensation budget, that is $500 below plan, or −10% using actual minus budget. The remaining $10,500 belongs outside this grant’s allocation. Do not charge the entire $15,000 to every program using the role.
The 30% is an exercise assumption, not a universal allocation rule. If the report excludes benefits while the budget includes them, or the allocation lacks approval, resolve that mismatch before interpreting the variance. A lower cost alone does not establish a saving: a vacancy, timing difference or delayed activity may need explanation.
4. Obtain status from the authoritative source
Identify where invoice approval, payment and posted financial amounts are maintained. If those records come from another system, document the authorized export or integration, field mapping, refresh schedule and error handling.
Show when data was last refreshed. A successful connection last week does not make today’s view current. Preserve rejected or unmatched records in a visible exception list and identify who resolves them.
In a Sopact setup, partner-submitted files and reporting context can be connected for review. Any link to an accounting platform must be scoped and verified for that implementation. Do not promise automatic two-way synchronization or a live reconciled balance without testing the actual connection and controls.
5. Reconcile before presenting one total
Compare the reported total with the Finance-approved source for the same scope and date. Trace differences to unmatched records, duplicates, timing, credits, allocations or another documented cause. A summary marked “no flags” is not proof that reconciliation happened.
Worked example · fictional
Three amounts, three different meanings
The period budget is $30,000. Finance’s approved expense report shows $27,000. Recorded cash payments total $25,000. A further $2,000 invoice is approved but unpaid.
For this exercise, Finance confirms that the $2,000 invoice is included in the $27,000 expense figure and that the remaining $25,000 has been paid. Under that stated assumption, the difference between the expense and cash views is explained.
Budget versus reported expense is $27,000 − $30,000 = −$3,000, or −10%. The cash view is separately $25,000. Do not add the unpaid invoice to the expense figure again.
The explicit assumption matters. In a real report, an approved unpaid invoice is not enough to infer its accounting treatment. Ask Finance and verify the source. Other adjustments could also explain a difference between expense and payment totals.
For a shared cost, use the approved allocation rather than charging the full amount to every grant. Check that the amounts assigned across funding sources reconcile to the relevant total. Do not add amounts in different currencies without an agreed conversion basis.
6. Review exceptions with context
Useful checks include duplicate invoice identifiers, missing required fields, unmatched budget lines, an unexpected period, unexplained differences and stale source data. Each check needs a clear rule and an owner.
A budget line with no activity may be expected if the work starts later. Spending ahead of an even monthly pace may be planned. Compare with the actual delivery and financial schedule before labeling either a problem.
AI can help read supporting files and prepare an exception summary in a configured workflow. Review its extraction and interpretation. A likely duplicate needs investigation; two similar amounts are not enough to establish that the same bill was paid twice.
Watch the explainer · 6 minutes 7 seconds
Help readers understand the evidence in a report
This Sopact video explains why sources, definitions and audience context matter even when the numbers are clean. Apply that lesson when explaining the reporting basis, source and period behind a financial total.
▶ Play video: why clean reporting data still gets ignored
Watch on YouTube if playback is unavailable · Browse the video library
7. Resolve the issue without overwriting the source
For a genuine difference, identify the specific record, explain the question and assign it to the appropriate owner. Keep corrections as a traceable change with the reason and approval where required.
A program officer may clarify which activity an invoice supports; Finance may determine its accounting treatment. Keep those responsibilities clear. Do not ask an assistant to change payment status merely to make the reporting view match.
If a partner needs to provide a missing file, request that item rather than the full reporting package. Use a focused request identifying the missing record and preserve an unresolved status until the evidence is checked.
8. Close the period with a reviewable snapshot
Record the reporting date, budget version, source refresh date, reconciliation owner and unresolved items. Preserve the reviewed snapshot so the next update does not silently change what the prior report showed.
Show the appropriate breakdown by grant, program, entity or funding source, without counting the same record twice. Include the basis and scope where a reader can see them. A concise explanation is more useful than an unexplained single number labeled “actual.”
Connect the financial view to delivery and outcome evidence where it supports a decision. Do not infer cost effectiveness from spending alone; the result and its measurement need to be clear too.
A usable review instruction
Using the supplied approved budget and Finance report for [period], identify the definition and basis of actuals, then map each included amount to its grant and budget category. Keep invoices, approval status and payments separate. List unmatched records, possible duplicates, timing differences and missing source information. Do not infer accounting treatment or change records. Reproduce the budget-versus-actual calculation only where the scope and period match, and identify the questions Finance must resolve.
Use this in an authorized workspace with the relevant documents. It is a review aid, not an instruction to post entries, approve an invoice or make a payment.
Exercise: trace the $27,000
Use the fictional reconciliation above. List the source records needed to substantiate the $27,000 expense figure and its relationship to the $25,000 cash total. Then add a duplicate upload and an invoice from another period.
Test whether your view counts either item incorrectly. Record how the reviewer identifies the issue and how Finance’s confirmed correction is reflected without losing the original submission.
Pass condition: another authorized reviewer can reconstruct the total, its basis and the unresolved questions. The view does not confuse invoice receipt, approval, expense and payment.
Frequently asked questions
What is actual spend?
It is the amount recorded as spent for the defined reporting purpose and period. State the approved basis and source, because a cash-payment view and an expense view may differ.
Is an approved invoice the same as a payment?
No. Approval and settlement are different stages. Use the authoritative payment record to establish whether cash has been paid.
How do you compare budget with actual spending?
Use the approved budget version and actuals for the same scope, period, currency and categories. Reconcile the total, then calculate and explain the difference.
How should multi-year budgets be tracked?
Keep the overall authorization and relevant period plans distinct, with version history and effective dates. Do not assume even monthly spending unless that is the approved schedule.
How should an accounting-system connection be checked?
A connection must be scoped and verified for the specific implementation. Confirm the available integration or export, mappings, permissions, refresh timing and error handling before relying on synchronized status.
Can invoices alone show complete program spending?
Not necessarily. Relevant records may include payroll, allocations or other Finance-approved entries. Use the source set required for the report’s basis and scope.
Does a clean exception list mean the numbers are reconciled?
No. Reconciliation requires a checked comparison with the relevant authoritative records. Record the reviewer, date, source and explanation for any differences.
Carry the financial context into the next report
The related lesson compares grantee reports over time. Keep the budget version, reporting basis and period snapshot so future comparisons do not mix different definitions.
For the final narrative, use the impact report writing ebook and example reports. Continue through the course overview.