Audit and Control Foundations and Responsibilities · Lesson 4

Transaction maps and evidence handoffs

5 min read

Lesson objectives

  • Map an order-to-pay flow, identify decisions and handoffs, and locate a missing three-way-match control point.
Reading tools

A process map is a testable hypothesis about how one request moves from initiation to a financial consequence, not a decorative diagram. Start with one tracking unit such as a purchase-request identifier, then place steps in order and name the custodian of each record at every handoff. A department requests goods; an authorized person approves; purchasing sends an order; stores records quantity and condition received; accounts payable receives the invoice; finance matches and pays; accounting posts the obligation and cash movement. At each arrow, record the identifier linking both sides and the time of transfer. If order identifiers differ across the purchasing and invoice systems, ask for the mapping table before declaring the transaction missing. Put emergency purchases on a visible exception branch instead of hiding them in the normal flow.

Three-way matching compares the purchase order, receipt evidence, and supplier invoice before paying a transaction to which the organization's policy applies. It is more than gathering three images: each record proves a different proposition. The order states what was authorized and at what price and quantity. The receipt records what arrived according to inspection. The invoice asks for payment. In a hypothetical case, an order is for 10 units at 80 each, eight arrive, and the supplier invoices 10 for 800. If the organization's criterion is to pay only for goods received, the amount currently supportable is 8 times 80, or 640, before any assumed tax or fees. The difference of 160 needs explanation, not another signature that conceals it. A contract may allow an advance payment; that requires a separate documented path and criterion. Do not turn the exercise's rule into universal law.

Suppose stores recorded eight units in a file accounts payable cannot see. Mark the gap at the receipt-to-match handoff, not only at payment. A possible control pauses payment if invoiced quantity exceeds linked receipt quantity, with separate review of exceptions. It fails if an accounts clerk can edit the receipt and release the payment; permissions are part of the decision point. Ask management when the systems synchronize. A receipt that reached the other system after payment might explain an apparent exception, but cannot prove a prepayment check occurred. Preserve the reason for an override and the identity of its approver for later testing.

To test the map, trace one ordinary transaction and one real exception. Start from the request number and follow identifiers, dates, quantity and amount through each record to payment. If the link disappears, specify what proposition remains unproved: receipt, authorization, or prevention of overpayment. Paper evidence or another system may exist and should be checked. Then work backward from a recorded payment to a request and receipt. Forward tracing alone might omit payments created outside the purchasing system. The two directions address different risks: completeness of the selected payment population and validity of transaction details. Neither direction permits a conclusion beyond the records actually tested.

Make the map show three breaks that require different repairs. A record break means a necessary item is absent or inaccessible; mandatory capture or integration may address it. An authority break means a payment or override decision maker is unclear or exceeds a limit; a permission matrix and restricted access may address it. A timing break means records exist but were created after payment, so they cannot evidence a preventive check. In the ten-unit case, if the receipt for eight units was posted the day after an 800 payment, do not say the three-way match preceded payment. Ask what supported releasing 800 at that moment, and distinguish a later explanation of the difference from a control that operated in time. This distinction leads to a targeted procedure rather than a vague recommendation to collect more documents.

Lesson summary

Map each transaction step, ID, record and decision point; an isolated document does not prove order, receipt and payment are linked.