NGO Audit Afghanistan: A Compliance Checklist for Finance Teams

An NGO audit in Afghanistan tests more than arithmetic. It tests whether an organisation can show, with documents, that money was received, spent as agreed, and reported honestly — in an operating environment where banking, access, and record-keeping are all harder than usual. Finance teams that prepare continuously, rather than in the weeks before an auditor arrives, find the process far less disruptive.

This checklist is general guidance for finance teams. It describes no specific NGO, donor, project, or past engagement, and it is not legal or tax advice. Where a donor agreement or local requirement sets a stricter rule, that rule governs.

1. Start from the agreement, not from the ledger

Before touching a transaction, confirm what was actually agreed:

• The grant or contract, including its budget lines, reporting periods, and any conditions on eligible costs.
• Which costs are eligible, which need prior approval, and which are excluded.
• The reporting format and deadlines the donor expects, and who signs off internally before submission.
• Any requirements on procurement thresholds, asset ownership, or separate bank accounts.

Most audit findings trace back to a mismatch between what a team assumed the agreement allowed and what it actually says. Keep a short, agreed summary of these terms where the finance team can reach it, and update it whenever an amendment is signed.

2. Keep records that an outsider can follow

An auditor should be able to trace any reported figure back to its source without asking the finance team to reconstruct it. For each material transaction, the file should show:

• What was bought or paid for, and why it was needed for the program.
• Who approved it, who recorded it, and who verified receipt or delivery.
• The supporting document: invoice, receipt, contract, attendance record, or delivery note, as appropriate.
• How it was coded, and to which budget line and reporting period.

Where original paper is the only record, scan and back it up on a regular schedule, and keep the filing system consistent across field offices so a reviewer in Kabul sees the same structure as a reviewer in a province.

3. Separate duties, even in a small team

Segregation of duties is the control auditors test first, and the one small teams find hardest. No single person should control a payment from start to finish. At minimum, separate:

• Authorisation (who approves the spend) from recording (who enters it in the books).
• Custody of cash or bank access from reconciliation of the bank account.
• Procurement decisions from receipt and verification of goods or services.

Where staffing makes full separation impossible, add a compensating check: a second review of bank reconciliations, a manager sign-off on payroll changes, or a periodic independent sample of transactions. Document the arrangement — an auditor can accept a well-designed compensating control, but not an undocumented gap.

4. Reconcile early and often

• Reconcile bank accounts monthly, and clear old reconciling items rather than carrying them forward unexplained.
• Reconcile spending against budget monthly, and investigate variances while the explanation is still fresh.
• Reconcile advances to staff and partners: advances outstanding, advances settled, and advances overdue, with follow-up dates.
• Reconcile payroll to staff lists and contracts, including joiners, leavers, and salary changes.

A reconciliation done late is still useful, but one done monthly turns an audit into a confirmation exercise instead of an investigation.

5. Procurement: show competition and justification

Procurement is where auditors look for value for money and for favouritism. For each significant purchase, keep:

• The need and specification, agreed before suppliers are approached.
• Evidence of competition proportionate to the value — quotations, tender records, or a documented reason for a single-source choice.
• The selection decision and who made it.
• The contract or order, delivery evidence, and payment record.

Single-source purchases are not automatically a problem, but they are automatically a question. A short written justification, made at the time, answers it.

6. Cash, assets, and field spending

Where banking is limited and field spending is in cash, controls matter more, not less:

• Set cash advance limits and settlement deadlines, and enforce them consistently.
• Require original receipts for field expenditure, with a clear explanation where a receipt genuinely cannot be obtained.
• Maintain an asset register — what was bought, where it is, who holds it, and its condition — and verify a sample physically each year.
• Record distributions (cash, goods, or services) with beneficiary or recipient evidence that can be checked without identifying vulnerable people unnecessarily.

7. Donor reporting: agree the numbers before they leave the building

Before a financial report is submitted:

• Agree it to the ledger, not to a separate spreadsheet that nobody reconciles.
• Check that expenditure is in the right period and the right budget line.
• Confirm that any ineligible or questioned item is disclosed or excluded, with a note explaining why.
• Keep a copy of exactly what was submitted, and who approved it.

If a donor later queries a figure, the team should be able to reproduce it from the books, not from memory.

8. Prepare for the auditor, not just for the audit

• Agree the audit scope, timetable, and document list with the auditor in advance.
• Nominate one coordinator who gathers documents and tracks requests, so field staff are not pulled in several directions.
• Prepare a schedule of key judgements: provisions, accruals, exchange-rate treatment, and any area where the team had to interpret a rule.
• Disclose known problems early. An issue the team found and fixed reads very differently from one the auditor discovers.

9. Close the loop: the management letter is the real deliverable

The audit opinion matters, but the management letter — the auditor’s list of control weaknesses and recommendations — is where improvement happens. For each point:

• Agree or challenge it on evidence, promptly.
• Assign an owner and a deadline.
• Track completion, and report it to senior management or the board.

An organisation that clears its management-letter points year after year builds a record that donors notice. One that lets the same points recur invites a harder audit next time.

Common mistakes

• Reporting from spreadsheets that never reconcile to the ledger. One set of books, agreed to every report.
• Approvals after the fact. An approval dated after payment is not a control; it is a signature.
• Advances that never settle. Old, unsettled advances are the fastest route to a qualified finding.
• Procurement files with no decision record. Quotations without a selection note prove shopping, not judgement.
• Treating the audit as an annual event. Controls tested once a year are controls that fail quietly for eleven months.

Questions a finance team should ask any audit or assurance provider

1. What will you test, and how will you choose the sample — by value, by risk, or both?
2. How will you handle field verification where access is limited?
3. What will you need from us, by when, and in what format?
4. How will you raise issues during the audit, so we can respond before the report is finalised?
5. What will the management letter cover, and how will you help us prioritise the actions?
6. How do you keep your work independent of the program team whose spending you are checking?

Listen for specifics: a sampling approach, a field plan, a timetable, and a follow-up process — not just a promise of a clean opinion.

Frequently asked questions

How far in advance should we start preparing for an NGO audit?

Preparation should be continuous — monthly reconciliations, filed supporting documents, and settled advances. A team that does those three things well can usually assemble an audit file in days, not weeks.

What is the difference between an audit and a financial verification?

An audit gives an opinion on financial statements or a project’s accounts. Financial verification checks specific facts — that funds were used as agreed, that reported results or assets exist, or that controls operated as described. The two often complement each other, and a donor may commission either or both.

What if our records are incomplete for an earlier period?

Say so early, reconstruct what can be reconstructed from bank records and other evidence, and document the gap and its cause. Auditors treat an honest, documented gap far better than a gap discovered in testing.

Talk to Blue Presto

Blue Presto Consultant Services is a Kabul-based firm helping organisations in Afghanistan prepare for audits, verify the use of funds, and strengthen financial controls. Learn more about our financial verification and fiduciary assurance services, read how organisations choose an assurance partner in our article on audit firms in Afghanistan, see our financial and taxation services for tax compliance support, or contact us to discuss audit readiness. Credible Evidence. Confident Decisions.