Financial Audit Manual

If you touch public funds, procurement, or compliance in Pakistan, this manual is the rulebook your auditors follow, so knowing it means fewer surprises. Students of accounting and civil-service aspirants get a plain-language map of professional standards. Even curious readers will find a surprisingly practical philosophy: trust nothing, verify everything, write it down.

1. 1Audit Planning

   Audit starts before you open a single ledger

   Picture an audit party arriving at a government office with no plan: they flounder, miss the risky transactions, and waste weeks. The manual insists the opposite. Before fieldwork begins, the auditor studies the entity, its accounts, its budget, and prior audit records, then drafts a plan setting out the areas to be examined, the audit approach, and the time each task will take. The department head approves that plan. Only then does the team move, and the difference is a focused examination instead of a blind one.

   The idea

   Planning converts an audit from a fishing trip into an investigation with a target. By studying the entity and its history first, the auditor decides where the money is most likely to leak and aims the effort there. What surprises newcomers is how much of audit quality is decided before anyone touches a voucher: a written, approved plan disciplines the team, allocates scarce hours to the riskiest areas, and gives supervisors a benchmark to judge whether the work stayed on course.

   Try this: Before your next review, write a one-page plan naming the areas you will examine and the time each deserves, and get a senior to sign off.

2. 2Vouching

   Vouching: trace every payment back to its paper trail

   A voucher sits in a file: a payment made, a signature at the bottom. The auditor picks it up and asks the only question that matters, does the recorded transaction actually happen and is it properly supported? Vouching means examining vouchers, invoices, contracts and receipts to confirm entries in the books are backed by authentic evidence. The manual treats this as the backbone of a detailed audit, because a single unsupported payment can hide everything from a genuine error to a deliberate fraud.

   The idea

   Vouching is the audit's truth serum. Books can say anything; vouchers either prove the story or expose the gap. The discipline lies in direction: start from the entry and work back to the supporting document, checking date, amount, payee and authority. What surprises people is how often this simple tracing catches trouble, because fraudsters rarely forge every layer of paper, and an auditor who insists on the original document, not a photocopy or a promise, breaks most schemes quickly.

   Try this: Pick five payments from your own records this week and trace each to its original invoice and approval; note what is missing.

3. 3Vouching

   Follow the money forward: the cast of vouching

   Vouching has a twin. Tracing runs the other way: the auditor starts from the source documents, the cash book, the bills, the receipts, and follows them forward into the ledger to confirm nothing was dropped, altered or posted twice. Where vouching asks whether an entry is genuine, tracing asks whether the records capture everything that happened. The manual pairs the two because each covers the other's blind spot, and together they close the loop on completeness and accuracy.

   The idea

   The two directions of testing exist because fraud hides differently in each. A fake entry needs a fake voucher, which vouching catches; a real transaction kept off the books leaves no entry at all, which only tracing catches. Run both and the auditor covers existence and completeness at once. What surprises people is that omission, not fabrication, is often the bigger risk in government books, since unrecorded receipts and payments never appear in any summary an official might volunteer.

   Try this: Take one week of receipts and check each one reached your ledger, at the right amount, exactly once.

4. 4Verification of Assets and Liabilities

   Verification: proving the assets on the books exist

   The ledger says the office owns furniture, vehicles, equipment. The auditor walks the storerooms and compounds to see whether those assets are physically there, in usable condition, and genuinely the property of the entity. Verification, as the manual defines it, is confirming the existence, ownership and valuation of assets and liabilities, often by physical inspection. A balance that cannot be walked up to and counted is a claim, not a fact, and the audit report treats it accordingly.

   The idea

   Verification grounds accounting in reality. Entries can be duplicated, misvalued, or describe property that was sold, stolen or never existed; physical inspection and examination of title documents cut through all of it. The surprise for newcomers is that existence is only one of three questions, ownership and valuation matter just as much, since an asset can be real, yet belong to someone else, or sit on the books at a value no buyer would pay. Sound balances answer all three.

   Try this: List the equipment your office claims to own, then physically locate each item and note anything you cannot find.

5. 5Cash and Bank

   The cash book and bank reconciliation never lie for long

   Cash is the most liquid, most tempting asset a government office holds, so the manual gives it special treatment. The auditor examines the cash book, checks receipts against counterfoils, and then performs the decisive test: reconciling the book balance with the bank statement balance, explaining every difference. A reconciliation that cannot explain a gap is a red flag; one that reconciles cleanly, with outstanding items verified, is strong evidence the cash records can be trusted.

   The idea

   Bank reconciliation works because it forces two independently kept records to agree. The office writes one story, the bank writes another, and any unexplained difference between them is either a timing item or trouble. Auditors love the test because concealment is hard: to fake cash you must fake both sides and every intervening document. What surprises people is how small and boring the exercise is, and how disproportionately many fraud cases begin with a reconciliation someone stopped doing.

   Try this: Reconcile one of your own accounts this month and investigate every difference you cannot explain in one line.

6. 6Payroll Audit

   Payroll: the audit of people as well as numbers

   Every month the payroll runs, and every month it can quietly leak. The manual directs the auditor to check that sanctioned posts exist, that the people drawing salaries are real and entitled, that increments and allowances follow the rules, and that recoveries and deductions are actually made. Ghost employees, unauthorised allowances and unpaid recoveries are the classic failures, and each is caught by comparing the payroll against establishment records, sanction orders and attendance evidence rather than trusting the pay list itself.

   The idea

   Payroll fraud thrives on distance: the payer rarely sees the paid. The audit's answer is to reconnect the payment to a verifiable person and a valid sanction, post, appointment, increment, deduction, each checked against its authorising record. What surprises people is that the expensive failures are rarely arithmetic; they are entitlement failures, payments made to people or posts that should not exist, which no amount of adding and cross-adding will reveal without the sanction file.

   Try this: Compare your organisation's payroll headcount against its sanctioned posts and list every person who lacks a matching sanction.

7. 7Procurement Audit

   Procurement: where public money most often goes astray

   Contracts are where scrutiny pressure is highest, so the manual sends the auditor straight into the procurement file. Was the purchase need genuine? Were competitive quotations or tenders obtained as the rules require? Was the lowest evaluated bidder selected, and did the contract terms match the tender? Splitting purchases to dodge thresholds, accepting late bids, tailoring specifications to a favoured supplier, each pattern has a paper footprint, and the auditor's job is to read the file until the pattern shows.

   The idea

   Procurement audit matters because it is the point where discretion meets money. Competition is the public sector's main defence against overpayment, so every departure from competitive process is a question, not automatically a wrong, but always a question requiring justification. What surprises people is that the audit rarely needs accounting skill, it needs file discipline: reading the record in sequence, from demand to sanction to tender to contract, where manipulated deals almost always leave a step done out of order.

   Try this: Pull one recent purchase file at work and check the bids were invited, evaluated and awarded in the order the rules require.

8. 8Internal Control

   Internal controls: judge the system, not just the transactions

   Checking every transaction forever is impossible, so the manual builds the audit on a prior question: how good is the system itself? The auditor evaluates internal controls, the segregation of duties, the authorisations, the checks and balances an office uses to keep itself honest. Strong controls let the auditor test samples with confidence; weak ones mean no sample is safe, and the examination must widen. The control evaluation thus decides the shape and depth of everything that follows.

   The idea

   This is the idea that modernised auditing: reliability comes from systems, not spot checks. If duties are separated and payments need two signatures, errors and fraud need conspiracy to survive, which is rare; if one person controls a transaction from start to finish, no amount of vouching gives comfort. What surprises people is how directly the control verdict drives audit work, weak controls do not just get criticised, they multiply the testing the auditor must do, which is exactly the incentive offices need.

   Try this: Map who initiates, approves and records payments in your office; flag any transaction type one person controls alone.

9. 9Audit Sampling

   Sampling: opinion from a part, honestly taken

   No auditor can read every voucher in a large department, so the manual legitimises the sample, with conditions. The items chosen must represent the whole, selected without the auditor's bias steering the result, and the conclusions drawn must stay within what a sample can support. Done properly, examining a slice tells the auditor something defensible about the loaf; done carelessly, it tells them only what they already assumed, dressed up as findings.

   The idea

   Sampling is where audit becomes statistics, and honesty becomes method. The danger is not smallness but selection: pick the convenient files, the round numbers, the items you already distrust, and the sample proves nothing. Random or systematic selection, with the population defined first, is what lets a conclusion travel from the items tested to the whole. What surprises people is that a small, unbiased sample beats a large, hand-picked one every time, because bias, not size, is what destroys the inference.

   Try this: Next time you review a file stack, define the whole population first, then pick every tenth item rather than the ones that look interesting.

10. 10Working Papers and Documentation

    Working papers: the audit that cannot show its work did not happen

    An auditor's findings are only as strong as the file behind them. The manual requires working papers, records of the procedures performed, the evidence examined, and the conclusions reached, assembled as the audit proceeds. When a departmental officer contests a finding months later, the working paper is what lets the auditor answer with specifics instead of memory. An undocumented audit, however diligent, is indefensible, and the manual treats documentation as part of the audit itself, not an afterthought.

    The idea

    Working papers are the audit's memory and its evidence of care. They serve three masters at once: they let a reviewer check the work, they let a successor build on it next year, and they let the auditor defend a finding against challenge long after fieldwork ends. What surprises people is the discipline this imposes in real time, knowing every step must be written down forces auditors to perform steps worth writing down, which quietly raises the quality of the examination itself.

    Try this: After your next review task, write a half-page note of what you checked, what you found, and what you concluded, and file it.

11. 11Audit Reporting

    Findings must say what should have been, what was, and why it matters

    Fieldwork ends and the real test begins: turning files into a report an official cannot shrug off. The manual sets the standard for audit findings, each one stating the criteria, the condition actually found, and the effect, written clearly enough for the reader to understand the lapse without visiting the office. Vague findings, irregularities alleged without amounts or authority, get challenged and die. Precise ones, grounded in the cited record, survive scrutiny and force a response.

    The idea

    A finding is an argument, and the manual teaches its structure: here is the rule, here is what the record shows, here is what it cost or risked. Leave out any leg and the objection writes itself, the rule did not apply, the facts are wrong, the matter is trivial. What surprises people is how much accountability depends on writing quality rather than detection, a perfectly discovered irregularity, badly worded, gets settled away, while a plainly written one follows the officer to the response sheet.

    Try this: Rewrite one complaint at work as a proper finding: the rule breached, the observed fact, and the consequence, in three sentences.

12. 12General Principles

    Audit's purpose is accountability, not ambush

    Behind every procedure sits a single aim: the manual opens by framing audit as an examination of accounts and records to establish how far the department's financial transactions are in accordance with the authority, rules and intentions behind them. The auditor is the public's standing check on the executive, comparing spending against sanction, rules and purpose. That framing explains the manual's tone throughout, sceptical of every entry, but aimed at conformity with authority rather than at personalities.

    The idea

    Defining audit as conformity with authority gives the whole craft its compass. Every test in the manual, vouching, verification, reconciliation, procurement review, reduces to one question: was this money spent by the right person, for the right purpose, under the right rule? What surprises people is that this makes the auditor's job almost judicial, the standard is external, written, and applies to the auditor's own work too, which is why the manual holds its procedures to documentation and review standards as strict as those it imposes on the audited.

    Try this: For one expense you approve this week, name the rule and sanction that authorise it before signing; if you cannot, ask.

Government accountants, auditors, and departmental officers who face audit in Pakistan will use this constantly. Accounting students and civil-service aspirants get a clear, authoritative map of how public financial accountability actually works.

FAQ