TOEIC Link Purchase Order and Vendor Invoice Vocabulary: The Order-Receive-Match-Pay Cluster for Part 4 and Part 7
In TOEIC Link, a purchase order is never just a form — it is a commitment, a receiving record, an invoice, a three-way match, and a released payment, and ETS can test every stage. A recorded warehouse briefing says a delivery cannot be accepted without a matching purchase order number (Part 4). A purchase order sits beside a vendor invoice, and a question asks what was ordered, what actually arrived, or why the invoice is on hold (Part 7 double passage). Because procurement always runs the same loop — raise the order, receive the goods, match the invoice, resolve any discrepancy, release payment — ETS can set what was ordered against what was billed and leave exactly one answer standing. Miss a term like purchase order, goods receipt, three-way match, discrepancy, or release for payment and a linked pair of documents can slip in one move.
This article organizes the cluster by the procure-to-pay cycle — order, receive, match, resolve, pay — because that cycle is exactly how ETS threads the documents together. Because a purchase order authorizes the spend before it happens, pair this first with the petty cash and cash reimbursement cluster — a purchase order routes the large, planned purchase, while petty cash covers the small one paid on the spot. And because goods received have to be counted against what the order promised, contrast this with the inventory audit and stock count cluster whenever the question turns from a single delivery to what the shelves actually hold.
Why purchase order and vendor invoice vocabulary is overweighted
Reason 1 — an order quantity plus an invoiced quantity is a ready-made linked set. The purchase order states what was ordered; the invoice states what was billed. When a question asks why payment is delayed or which figure is wrong, the two numbers force one conclusion, exactly what a linked set needs. ETS asks the reader to match the invoice to the order, and only one reading survives.
Reason 2 — procurement runs on a fixed cycle. Because every purchase follows the same order — raise, receive, match, resolve, pay — ETS can ask "What must happen before the invoice is paid?" or "Why was the shipment refused?" with exactly one correct answer. The reader matches the cycle against the paperwork.
Reason 3 — the terms are fixed procurement conventions. Purchase order, goods receipt note, three-way match, invoice discrepancy, and release for payment mean the same thing across every company. That rigidity makes the cluster perfectly testable — and perfectly learnable. The collocation, not the isolated word, is the unit of memory.
The cluster, organized by the procure-to-pay cycle
Stage 1 — raising the purchase order
Verbs and collocations: raise a purchase order, issue a PO, place an order, authorize the spend, quote a unit price.
Nouns: purchase order, PO number, line item, unit price, requisition.
A department raises a requisition, which is approved and turned into a purchase order carrying a unique PO number, itemized by line item at an agreed unit price. A Part 4 briefing says no goods are ordered without an approved PO; a Part 7 question about whether an order is valid points to a missing PO number, not to the vendor's willingness to ship. The PO is the authorization — everything downstream is checked against it.
Stage 2 — receiving the goods against the order
Verbs and collocations: receive against the PO, inspect on arrival, sign for delivery, log a goods receipt, short-ship.
Nouns: goods receipt note, delivery, packing slip, quantity received, shortage.
Goods are received against the purchase order and logged on a goods receipt note, with the quantity received checked against the packing slip. A Part 4 message tells staff to inspect on arrival and record any shortage; a Part 7 question about why fewer units were entered points to a short shipment, not a data-entry error. The trap offers a full order that was only partly delivered.
Stage 3 — matching the invoice
Verbs and collocations: match the invoice, run a three-way match, verify against the PO, cross-check the receipt, reconcile the amounts.
Nouns: vendor invoice, three-way match, invoice total, billed quantity, supporting documents.
The vendor invoice is verified by a three-way match — purchase order, goods receipt, and invoice must agree on quantity and price. A Part 7 pairing gives a PO beside an invoice; a question about which invoice can proceed points to the one where all three documents agree. Read carefully — an invoice that bills for more than was received cannot pass the match, and ETS plants an over-billed line among clean ones to test whether you check the receipt, not just the total.
Stage 4 — resolving a discrepancy
Verbs and collocations: flag a discrepancy, put on hold, dispute the charge, request a credit note, adjust the invoice.
Nouns: invoice discrepancy, price variance, hold, credit note, disputed amount.
When the numbers disagree, the invoice is flagged for a discrepancy and put on hold while the buyer disputes the charge and requests a credit note for the disputed amount. A Part 4 voicemail says a payment is held pending a corrected invoice; a Part 7 question about why a vendor was contacted points to a price variance, not a late delivery. The trap offers a plausible reason for the hold that the documents do not actually support.
Stage 5 — releasing payment
Verbs and collocations: release for payment, approve the invoice, remit payment, settle the account, process within terms.
Nouns: payment approval, remittance, payment terms, due date, remittance advice.
Once the match clears, the invoice is released for payment and remitted within the agreed payment terms, with a remittance advice sent to the vendor. A Part 7 question about when a supplier will be paid points to the due date set by the terms, not to the invoice date. Note that approval, not receipt of the invoice, starts the clock — ETS uses this to test whether you know a held invoice is not yet due.
The paraphrase traps ETS repeats
- Ordered vs. received. The PO says one quantity; the goods receipt says another. A question about a shortage points to the receipt, not the order — ETS rewards the reader who checks what actually arrived.
- Billed vs. matched. The invoice total looks correct in isolation but fails the three-way match. The trap is the clean-looking total; the answer is the line that does not reconcile.
- On hold vs. overdue. A held invoice is not late — it is disputed. ETS offers "the vendor was not paid on time" when the real reason is an unresolved discrepancy.
- Requisition vs. purchase order. A requisition requests; a PO authorizes. A question about what is missing before goods can be ordered points to an approved PO, not the internal request.
How to drill this cluster
Study the five stages as one chain, not twenty separate words. When you read purchase order, expect goods receipt, three-way match, discrepancy, and release for payment to follow, because ETS threads them in that order. Practice by taking any PO-and-invoice pair and asking the three questions ETS always asks: what was ordered, what arrived, and what may be paid. The moment you can answer those from the documents alone, the linked-set questions in Part 7 stop being traps and start being arithmetic.
A purchase order and a vendor invoice are the two ends of the same transaction, and ETS tests the space between them — the receipt, the match, the hold. Learn the procure-to-pay cycle as a fixed sequence, and the cluster resolves to exactly one defensible answer every time.