TOEIC Link Invoice Dispute and Payment Hold Vocabulary: The Receive-Match-Query-Release Cluster for Part 4 and Part 7

In TOEIC Link, an invoice is a claim for money that has to survive a check before it is paid. A supplier submits an invoice, an accounts payable clerk matches it against the purchase order and the receiving record, and only a clean three-way match gets approved for payment. When something does not line up — a wrong price, a quantity that never arrived, a duplicate bill — the clerk puts the invoice on hold and raises a query with the vendor. ETS tests whether you can tell which point of that check a message describes. A recorded message tells a manager that a payment is held pending a corrected invoice, not that the company refuses to pay (Part 4). An email thread shows a price discrepancy, a credit note, and a decision to release the invoice for payment once the correction lands, and a question asks whether the invoice was paid, disputed, or still on hold (Part 7). Because every bill moves through the same gate — receive, match, query, release — ETS can set the stages against each other and leave exactly one answer standing. Miss a term like three-way match, discrepancy, on hold, credit note, or remittance and a payment-status question can slip past in one move.

This article organizes the cluster by the way a bill moves through accounts payable — receive, match, query, release — because that sequence is exactly how ETS threads the messages together. Because an invoice can only be checked against the order that authorized it, pair this first with the purchase order and vendor confirmation cluster — the PO is the document the invoice has to match before a cent moves. And because a hold is often triggered by goods that never fully arrived, contrast this with the shipping delay and backorder notice cluster, where a short shipment becomes the quantity mismatch that stalls the bill.

Why invoice dispute and payment hold vocabulary is overweighted

Reason 1 — an invoice has a status at every step. Received, matched, queried, on hold, approved, paid — a bill is in exactly one state, and each earlier state is a plausible distractor for the current one. When a question asks whether the supplier has been paid, only the released-and-remitted status answers it — exactly what a linked set needs.

Reason 2 — a hold is not a refusal. A payment held pending a corrected invoice is still going to be paid; a disputed charge that is written off is not. ETS loves the gap between "we are not paying yet" and "we are not paying." The question "Will the vendor be paid?" has exactly one answer, and it lives in whether the hold was cleared or the charge was reversed.

Reason 3 — the AP terms are fixed conventions. Three-way match, discrepancy, on hold, credit note, remittance advice mean the same thing across every finance team. 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 way a bill moves through accounts payable

Stage 1 — receive the invoice

Verbs and collocations: submit an invoice, receive a bill, log the invoice, enter it into the system, acknowledge receipt.

Nouns: invoice, bill, invoice number, due date, payment terms.

A bill enters the system when a vendor submits an invoice and a clerk logs it against a purchase order number, noting the due date and payment terms (net 30, net 60). A Part 4 voicemail confirms an invoice was received but not yet entered because the referenced PO is missing; a Part 7 question asking why a supplier has not been paid may point to an invoice that never reached the system, not to a refusal. The trap offers a later stage — approval — to the reader who assumed the bill was already in the queue.

Stage 2 — match against the order

Verbs and collocations: match against the purchase order, check the receiving record, run a three-way match, verify the price, confirm the quantity.

Nouns: three-way match, purchase order, receiving record, line item, unit price.

The clerk then runs a three-way match — invoice, purchase order, and receiving record must agree on price and quantity. A Part 4 notice says a match failed on one line because the unit price is higher than the order; a Part 7 thread showing a quantity that exceeds what was received asks why the bill cannot be approved yet. Because an invoice can only be authorized against the spend it was booked to, this stage connects directly to the corporate card and purchase approval cluster, where the same charge starts as an approval limit the finance team set.

Stage 3 — query and hold

Verbs and collocations: raise a query, flag a discrepancy, put the invoice on hold, dispute a charge, request a correction.

Nouns: discrepancy, query, hold, dispute, corrected invoice.

When the match fails, the clerk raises a query with the vendor and puts the invoice on hold while the discrepancy is resolved. A Part 4 message reports that a payment is held pending a corrected invoice; a Part 7 thread pairing a price dispute with a request for a corrected invoice asks what is stopping the payment — the discrepancy, not a cash problem. The reader who separates a query (a question that pauses payment) from a dispute (a rejection of the charge) catches which one the message describes.

Stage 4 — correct, approve, and release

Verbs and collocations: issue a credit note, resubmit the invoice, approve for payment, release the payment, remit funds.

Nouns: credit note, approval, payment run, remittance advice, cleared payment.

Finally the vendor issues a credit note or resubmits a corrected invoice, the clerk approves it for payment, and it goes into the next payment run with a remittance advice sent to the supplier. A cleared query ends in a released payment; an unresolved one keeps the hold. A Part 7 thread pairing a credit note with a confirmation asks whether the invoice was paid in full or the disputed amount was deducted — and the distinction is the trap.

The paraphrase traps ETS builds on this cluster

On hold vs. refused. A held invoice is waiting on a fix; a refused one is being sent back for good. A question asking whether the vendor will be paid rewards the reader who checks whether the hold was cleared.

Query vs. dispute. A query pauses payment to ask a question; a dispute rejects the charge as wrong. ETS offers "the company will not pay" to the reader who saw "query" and assumed the worst.

Overdue vs. queried. A payment can be late because it was queried, not because it was forgotten. A question asking why a supplier has not been paid rewards the reader who keeps a hold apart from simple lateness.

How to drill this cluster

Practice by moving one invoice through AP in a single sitting. Take a single bill — invoice #2214 against PO #880 — and narrate it: the vendor submits it net 30; the clerk runs a three-way match and finds the unit price is higher than the order; the invoice goes on hold and a query goes out; the vendor issues a credit note for the difference and resubmits; the corrected invoice clears the match, is approved, and goes into Friday's payment run with a remittance advice. When you can say which stage a sentence belongs to and whether an invoice was paid, held, or disputed, the Part 7 linked set stops being a reading exercise and becomes a matching exercise.

Studied together, the receive-match-query-release loop covers the "paying the supplier" threads ETS writes — the back half of the order-to-payment story that begins the moment a purchase order is raised.

The one-sentence version

An invoice moves through accounts payable in a fixed order — the vendor submits a bill, the clerk matches it against the purchase order and receiving record, a mismatch puts it on hold with a query, and a credit note or correction clears the way to approve and release the payment — and TOEIC Link tests whether you can tell which point of that check a message describes and whether the invoice was paid, held, or disputed.