Blog · 18 September 2026 · 9 min read

Match donor report headings to the grant agreement

Choose donor report columns from the signed grant agreement, map local records clearly, and avoid changing the meaning of approved budget lines.

A donor report can contain correct figures and still be difficult to approve if its column headings do not match the signed grant agreement. A heading such as “Project costs” may make sense in your cashbook, but it is not enough if the agreement separates training, travel, supplies and staff costs.

Before entering transactions, build the report around the donor’s own terms. This gives each amount a clear place and makes it easier to compare the report with the approved budget. The task is not to create impressive accounting language. It is to preserve the meaning of the agreement while showing what was spent during the reporting period.

Start with the signed agreement and its annexes

Use the final signed grant agreement as your main source. The approved budget may be in the agreement itself, in an annex or in a later amendment. Check which document is legally part of the grant and whether any revised budget has replaced the original one.

Do not copy headings from an old report simply because they look familiar. That report may relate to another donor, an earlier grant or a budget that was later amended. Likewise, do not assume that your organisation’s normal bookkeeping headings are suitable for the donor report.

Write down the exact budget line names and codes in the order used by the agreement. If the budget says “B2 Community facilitator travel”, keep that wording and code. Do not shorten it to “Transport” unless the donor’s template requires a shorter heading.

Also note the reporting currency, grant period and reporting frequency. The agreement may distinguish between direct project costs, administration costs and equipment. It may also place a limit on moving money between budget lines. These details affect how the report should be arranged.

Your source list might contain the following items:

• Signed grant agreement and approved budget annex
• Any signed amendment or approved revised budget
• Donor reporting template and written guidance
• Approved chart of budget line codes, if supplied
• Clarification emails that form part of the donor’s written instructions

Separate transaction columns from budget headings

A common source of confusion is treating every heading as the same kind of information. Transaction columns describe an individual payment. Budget headings show where that payment belongs under the agreement.

For a transaction list, useful columns may include date, voucher number, payee, description, donor budget code, amount in local currency and amount in reporting currency. These headings help someone trace a reported cost back to the bank statement, cash record or receipt.

The donor budget lines should usually appear in a dedicated column called something like “Agreement budget line” or “Donor budget code”. Avoid creating separate columns for food, fuel, stationery and every other expense unless the donor template is designed that way.

For example, a transaction row could read: 12 April, PV-018, Sunrise Guesthouse, venue for community meeting, B3 Meeting costs, 20,000 local currency units. The description says what was bought, while B3 shows where the agreement allows it to be reported.

A practical transaction schedule could use these headings:

• Transaction date
• Payment or voucher reference
• Payee or supplier
• Purpose of expenditure
• Donor budget code
• Donor budget line
• Amount in local currency
• Exchange rate, where required
• Amount in grant currency
• Evidence or explanation note

Build a clear mapping from local records

Your cashbook may use different names from the agreement. A church project might record “Ministry travel”, while the donor budget says “B2 Field monitoring transport”. A community organisation might use “Refreshments”, while the approved line is “C1 Participant meeting costs”.

Create a small mapping table before preparing the report. Put the local cashbook category in one column and the matching donor budget line in another. Add a short rule describing what is included. This is an internal working document, not a way to change the approved budget.

For example, “Motorbike fuel for field visits” might map to B2 Field monitoring transport. “Tea and lunch for registered workshop participants” might map to C1 Participant meeting costs. “Printer paper for the main office” might map to D1 Office supplies, but only if the agreement allows general office supplies.

Do not map a cost only because a budget line has money remaining. The purpose shown by the receipt, payment request and activity record must fit the wording and purpose of that line. A printer bought for the office should not be placed under “Training materials” simply because it was used to print training handouts.

Some descriptions are too vague to map safely. A receipt marked only “transport” does not show whether the journey was for training, monitoring, purchasing or administration. Look for the related travel request, activity report or payment voucher. If the purpose still cannot be established, mark it for clarification rather than choosing a convenient line.

Keep one donor line for each transaction row where possible. If one supplier receipt includes items for two approved lines, split the amount into two rows and use the same receipt reference on both. Add a note explaining the split.

Use summary columns that preserve the budget meaning

A summary report normally compares approved amounts with spending. Copy the donor’s budget lines down the rows, then choose columns that show the required period and totals without changing what the agreement measures.

A useful structure is: approved budget, expenditure this period, cumulative expenditure, and balance remaining. If the donor asks for a forecast or commitments, add those as separate columns. Do not put unpaid purchase orders into an expenditure column unless the agreement specifically uses accrual accounting.

Suppose the approved amount for B2 Field monitoring transport is 6,000 in the grant currency. Earlier reports showed cumulative expenditure of 1,500. This quarter’s eligible transactions total 900. The new cumulative expenditure is 2,400, and the balance remaining is 3,600.

Label those figures precisely. “Previous expenditure”, “Current period expenditure”, “Cumulative expenditure” and “Remaining budget” are clearer than headings such as “Old”, “New”, “Total” and “Balance”. State whether the balance is calculated as approved budget less cumulative expenditure.

Keep approved budget and actual expenditure separate. Do not quietly edit the approved budget column to match how the project spent the money. If a budget revision has been formally approved, label the column “Revised approved budget” and keep evidence of the approval.

Be careful with “variance”. It can mean either money remaining or the difference between planned and actual spending for a period. If the donor uses the word, follow its definition. Otherwise, “Remaining approved budget” is often less ambiguous.

A summary table might use these headings:

• Donor budget code
• Approved budget line
• Original approved budget, if required
• Revised approved budget, if formally approved
• Expenditure in this reporting period
• Cumulative expenditure to date
• Remaining approved budget
• Explanation or forecast, if required

Name currency and exchange columns precisely

If the grant currency differs from the currency used for purchases, the heading should identify both. “Amount” is not enough. Use wording such as “Amount in local currency” and “Amount in grant currency”. Name the currencies in the report, for example “Amount in ETB” and “Amount in GBP”.

Follow the exchange method stated in the agreement or donor guidance. The required method might use the rate received when funds entered the project bank account, a transaction-date rate or another documented approach. The column heading and report note should make the chosen method visible.

For example, a supplier payment of 30,000 local currency units might be converted using an approved rate of 60 local units to one grant currency unit. The reported grant-currency amount would be 500. The calculation is 30,000 divided by 60.

State clearly how the exchange rate is written. A heading such as “Local currency units per 1 grant currency unit” removes doubt. Without that explanation, a reviewer may not know whether to multiply or divide.

Rounding can create small differences between transaction totals and summary totals. Use the number of decimal places required by the donor and apply the same rule throughout the report. Do not hide a rounding difference inside an unrelated budget line. Show it separately or explain it in a note if the donor’s template permits that.

Test the headings before completing the report

Enter a few different transactions before filling the whole report. Choose examples such as a bank payment, a cash purchase, a refund and a cost involving foreign currency. Check whether each item can be described, traced and placed under an approved budget line without forcing information into the wrong column.

Ask someone who knows the project but did not design the spreadsheet to read the headings. They should be able to tell which amount was approved, what was spent this period, what has been spent since the grant began and what remains.

Check the headings against the donor template one final time. Some donors require exact wording or a fixed order. Do not rename protected template columns merely to make them look neater. If the template conflicts with the agreement, ask the donor for written clarification rather than deciding silently.

Once the structure is confirmed, protect formula cells and keep a clean master copy. Record the reporting period near the top, including full start and end dates. A heading such as “Quarter 2” is not sufficient if the donor’s quarter dates differ from the calendar year.

Before submission, perform these checks:

• Every summary row matches an approved budget line or an authorised addition
• Every transaction has a donor budget code
• The reporting period is stated with exact dates
• Each amount column identifies its currency
• Cumulative expenditure includes accepted earlier periods only once
• Approved budget figures agree with the latest signed documents
• Refunds, corrections and transfers are clearly labelled rather than hidden in net totals

Questions

Good column headings act as a bridge between the signed agreement, the transaction evidence and the reported totals. Start with the donor’s exact budget terms, separate transaction details from summary figures, label currencies clearly and test the structure before entering every receipt. Honest Record can automate matching and checks, but the agreement should still determine what each report heading means.

More guides

• Add budget versus actual without confusion
• What donors check in a small NGO financial report
• Using AI for bookkeeping safely
• Preparing grant records for a donor audit