TOEIC Link — Purchase Order, Goods Receipt, and Three-Way Match Vocabulary Cluster

Accounts payable is one of the most reliably testable settings in business English because it runs on a simple rule with dense vocabulary: a supplier is not paid until three documents agree. The purchase order says what was ordered, the goods receipt says what arrived, and the invoice says what is being billed. When the three line up, payment is released; when they disagree, the invoice is held and someone has to reconcile the difference. TOEIC Link builds inference questions on exactly that structure — a passage rarely tests whether you can read a bill, and instead tests whether you can spot which of the three documents does not match and what that mismatch triggers.

This guide walks the procure-to-pay cycle from requisition to payment as a connected sequence, isolates the matching and exception vocabulary the test leans on, and closes with a drill protocol. It builds on general procurement terminology and pairs with the supplier negotiation and price agreement vocabulary cluster, since the price on an invoice is only correct if it matches the agreed rate, and with the orientation in what TOEIC Link measures.

The procure-to-pay cycle as a document trail

The organizing fact is that procurement leaves a paper trail, and each document is created at a different stage by a different party. The passage reasons about whether the trail is complete and consistent, so the reader who can place each document in the sequence has the passage half solved.

It begins with a requisition (or purchase requisition) — an internal request to buy something, raised by a department and sent for approval. Once approved, the buyer issues a purchase order (PO) to the supplier: a formal commitment stating the item, quantity, agreed unit price, and delivery terms, identified by a PO number that everything downstream will reference. The supplier then fulfills the order and ships the goods.

When the goods arrive, the receiving team records a goods receipt (or goods received note, GRN) confirming what physically came in — the quantity actually delivered, which may differ from what the PO ordered. Separately, the supplier sends an invoice billing for the goods, referencing the same PO number. The invoice sits in accounts payable until it is matched, then it is approved for payment and settled on its due date according to the payment terms.

The three-way match — where the inference questions live

The heart of this cluster is the three-way match, the check that decides whether an invoice gets paid, and it is where TOEIC Link concentrates its harder questions. The match compares three numbers across three documents.

The purchase order supplies the ordered quantity and the agreed price. The goods receipt supplies the received quantity. The invoice supplies the billed quantity and the billed price. For payment to release automatically, three things must agree: the invoiced quantity must not exceed the received quantity, the received quantity should reconcile with the ordered quantity, and the invoiced price must match the PO price. A passage may lay out all three figures and ask which one is wrong — the classic setup is an invoice billing for ten units when the goods receipt records only eight, inviting the reader to infer that the invoice is held pending the missing two.

The vocabulary of disagreement is precise. A discrepancy is any mismatch between documents; a price variance is specifically an invoice price above the PO price; a quantity variance is a billed quantity above the received quantity. A short shipment (or partial delivery) means fewer goods arrived than ordered, so the goods receipt is smaller than the PO — which is why an invoice for the full order would then fail the match. The mirror case is an over-shipment, where more arrives than ordered. A passage often turns on the direction of the variance, because it decides who owes an explanation: the supplier who over-billed, or the receiver who logged a short delivery.

The exception and correction vocabulary — where the holds live

When the match fails, the invoice does not simply disappear; it enters an exception process, and the cluster supplies the terms the test uses to describe it. The central term is the hold.

An unmatched invoice is placed on hold (or blocked for payment) until the discrepancy is resolved, so a passage may hinge on whether an invoice will be paid on its due date or delayed by a hold. Resolution takes a few standard forms. If the supplier over-billed, they issue a credit note (or credit memo) reducing the amount owed; if they under-billed, a debit note or a supplementary invoice. A pricing error may be fixed by amending the PO through a change order so the documents agree. A genuine short shipment is closed either by the supplier delivering the backorder (the outstanding balance) or by closing the PO short and paying only for what arrived.

Approval carries its own vocabulary. Small mismatches within a set tolerance (an allowed margin, e.g. a few percent) may auto-approve without human review, while anything outside tolerance is escalated to a manager. A passage may state that a variance was "within tolerance" and expect the reader to infer that payment proceeded despite the mismatch — the exception that avoids the hold. The judgment of an invoice, like the judgment of a payroll run, lives in these holds and tolerances, not in any single figure on the bill.

Payment-terms and settlement vocabulary

Once an invoice clears the match, the surrounding vocabulary governs when and how it is paid, and passages test it directly. The payment terms set the clock: net 30 means payment is due thirty days from the invoice date, while 2/10 net 30 offers a 2% early-payment discount if paid within ten days. A passage may test whether taking the discount is worthwhile, or simply whether a payment fell inside the discount window. Timing intersects with the deadline habit from the payroll and timesheet approval vocabulary cluster: both run on cutoffs where an action before or after a date changes the outcome.

Settlement vocabulary rounds out the cluster. Payment is remitted by bank transfer, ACH, or check, accompanied by a remittance advice that lists which invoices the payment covers. An overdue invoice is past due or in arrears and may accrue a late fee. A statement from the supplier lists all open invoices, and reconciling it against the buyer's records is a statement reconciliation — a passage may present a statement showing an invoice the buyer has no record of, inviting the inference that it was never received or was billed against the wrong PO.

Drill protocol — reading accounts-payable passages under time pressure

Practice this cluster with a fixed routine so the matching logic becomes reflex rather than recall.

First, on any invoice or procurement passage, identify the three documents and their numbers before reading the questions: the PO quantity and price, the received quantity, and the invoiced quantity and price. Almost every question depends on which pair disagrees, so laying out the three figures first turns the passage into a simple comparison.

Second, when a passage mentions a delay in payment, look for the cause in the match, not the calendar. A held invoice is usually blocked by a discrepancy — a short shipment, a price variance, or a missing approval — rather than by the due date alone. Naming the variance tells you what has to happen before payment resumes.

Third, treat "credit note," "change order," and "backorder" as the three standard fixes and match each to its cause: a credit note fixes an over-billing, a change order fixes a price mismatch, and a backorder fixes a short shipment. Practising this on a handful of passages makes the exception logic automatic. Combine it with the price-agreement habit from the supplier negotiation and price agreement vocabulary cluster, and accounts-payable passages become a dependable source of points rather than a tangle of numbers.