Walkthrough Testing: Definition and How It Works

Walkthrough testing traces one transaction end to end through AP process controls to confirm each step is followed as designed, before broader testing begins.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Walkthrough Testing: Definition and How It Works

Walkthrough testing is a control test that traces one transaction end to end through a process, such as purchase order to payment, to confirm each step happens the way the documentation says it does. Auditors use it to understand how a process actually works before deciding what to test at scale.

In an AP or contract compliance context, a walkthrough answers a narrower question than most people expect from an audit: not "how much did we lose," but "does the control that should have caught this actually exist, and does anyone follow it." That distinction shapes when a walkthrough belongs in an engagement, and what it hands off to the testing that follows.

1. What does walkthrough testing actually involve?

Walkthrough testing follows a single transaction through every step of a process, from the purchase order through receipt, invoice entry, approval, and payment. The tester interviews each person who touches the transaction and inspects the document each step produces: the PO, the receiving report, the approval sign-off, the payment record. The goal is to confirm the control exists and is followed, not to search for a dollar error.

This differs from an audit sample, which tests many transactions to estimate an error rate. A walkthrough tests one, in depth, to map the process itself.

2. Why do auditors use a walkthrough before a full test?

A walkthrough scopes the work that follows. It tells the tester where a control point actually sits, who owns it, and what evidence it produces, so a later full-population test knows exactly what to pull and compare. Skipping it risks testing against a process description that no longer matches what employees actually do, which wastes the deeper testing effort.

A walkthrough surfaces gaps a written procedure hides. A step marked as required on paper may be skipped in practice, or performed by someone other than the documented owner.

3. What is the difference between walkthrough testing and three-way matching?

Three-way matching is a standing control: every invoice is checked against its purchase order and receiving report before payment. Walkthrough testing is a one-time diagnostic step: it confirms that three-way matching, and every other control around it, is actually happening as designed. One runs continuously on every transaction; the other runs once, on one transaction, to verify the system.

A walkthrough can reveal that three-way matching exists on paper but is bypassed for certain vendors or invoice types, a gap ongoing matching alone would not surface.

4. What does a walkthrough miss that full testing catches?

A walkthrough confirms a control exists on the transaction it traces. It cannot say whether that control holds across every vendor, contract clause, or invoice type in the business, because it tests one path, not the population. Findings such as a missed rate schedule, an expired surcharge, or a gap in rebate tracking surface only when the full set of invoices is compared against contract terms.

That comparison work is where categories such as a rate card mismatch or a missed credit memo get identified and quantified, a separate step from confirming the process design.

Margin drift, the gap between what a vendor contract says and what the invoice actually charges, is what that comparison step is built to find. A walkthrough does not measure it; it only checks whether the control meant to catch it is in place.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What is walkthrough testing in an AP audit?

Walkthrough testing traces a single transaction end to end through a process, from purchase order to payment, to confirm each control step actually happens the way the process documentation says it does. It is a test of the process design, not a search for errors across every invoice.

Is walkthrough testing the same as a full invoice audit?

No. A full audit tests a population of transactions to find and quantify errors. Walkthrough testing tests one or a handful of transactions to confirm the control steps exist and are followed. It answers whether the process works, not how much money it lost.

How many transactions does a walkthrough use?

Typically one transaction per process variant, enough to observe every control point once. This is a design choice about coverage, not a claim about how many transactions companies test in practice.

Who performs a walkthrough?

Internal audit, an external auditor, or a diagnostic team maps the transaction by interviewing the people who touch it: the AP clerk, procurement, the approver, and reviewing the documents each step produces.

Does walkthrough testing find dollar leakage?

Not directly. It identifies where a control is missing, weak, or bypassed. Quantifying leakage requires testing a broader set of invoices against the contract, which is a separate step.

When is walkthrough testing used instead of full testing?

Early in an engagement, when the goal is to understand how a process actually runs before deciding where to test the full transaction population. It scopes the deeper work rather than replacing it.

What does a walkthrough actually document?

For each control point: who performed it, what evidence was produced, such as a PO, a receipt, or an approval, and whether that evidence matches the contract terms in place at the time.

Can walkthrough testing replace three-way matching?

No. Three-way matching is an ongoing control that checks every invoice against the PO and receipt. A walkthrough is a one-time test that confirms three-way matching, or any other control, is actually operating as designed.

1. What does walkthrough testing actually involve?

Walkthrough testing follows a single transaction through every step of a process, from the purchase order through receipt, invoice entry, approval, and payment. The tester interviews each person who touches the transaction and inspects the document each step produces: the PO, the receiving report, the approval sign-off, the payment record. The goal is to confirm the control exists and is followed, not to search for a dollar error. This differs from an audit sample, which tests many transactions to estimate an error rate. A walkthrough tests one, in depth, to map the process itself.

2. Why do auditors use a walkthrough before a full test?

A walkthrough scopes the work that follows. It tells the tester where a control point actually sits, who owns it, and what evidence it produces, so a later full-population test knows exactly what to pull and compare. Skipping it risks testing against a process description that no longer matches what employees actually do, which wastes the deeper testing effort. A walkthrough surfaces gaps a written procedure hides. A step marked as required on paper may be skipped in practice, or performed by someone other than the documented owner.

3. What is the difference between walkthrough testing and three-way matching?

Three-way matching is a standing control: every invoice is checked against its purchase order and receiving report before payment. Walkthrough testing is a one-time diagnostic step: it confirms that three-way matching, and every other control around it, is actually happening as designed. One runs continuously on every transaction; the other runs once, on one transaction, to verify the system. A walkthrough can reveal that [three-way matching](/glossary/freight-and-3pl-audit) exists on paper but is bypassed for certain vendors or invoice types, a gap ongoing matching alone would not surface.

4. What does a walkthrough miss that full testing catches?

A walkthrough confirms a control exists on the transaction it traces. It cannot say whether that control holds across every vendor, contract clause, or invoice type in the business, because it tests one path, not the population. Findings such as a missed rate schedule, an expired surcharge, or a gap in rebate tracking surface only when the full set of invoices is compared against contract terms. That comparison work is where categories such as a [rate card mismatch](/glossary/rate-card) or a [missed credit memo](/glossary/missed-credit-memo) get identified and quantified, a separate step from confirming the process design. Margin drift, the gap between what a vendor contract says and what the invoice actually charges, is what that comparison step is built to find. A walkthrough does not measure it; it only checks whether the control meant to catch it is in place. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What is walkthrough testing in an AP audit?

Walkthrough testing traces a single transaction end to end through a process, from purchase order to payment, to confirm each control step actually happens the way the process documentation says it does. It is a test of the process design, not a search for errors across every invoice.

Is walkthrough testing the same as a full invoice audit?

No. A full audit tests a population of transactions to find and quantify errors. Walkthrough testing tests one or a handful of transactions to confirm the control steps exist and are followed. It answers whether the process works, not how much money it lost.

How many transactions does a walkthrough use?

Typically one transaction per process variant, enough to observe every control point once. This is a design choice about coverage, not a claim about how many transactions companies test in practice.

Who performs a walkthrough?

Internal audit, an external auditor, or a diagnostic team maps the transaction by interviewing the people who touch it: the AP clerk, procurement, the approver, and reviewing the documents each step produces.

Does walkthrough testing find dollar leakage?

Not directly. It identifies where a control is missing, weak, or bypassed. Quantifying leakage requires testing a broader set of invoices against the contract, which is a separate step.

Margin Drift Resources