TOEIC Link Invoice Dispute and Payment Discrepancy Vocabulary: The Cluster for Part 3, Part 4, and Part 7

A TOEIC Link company is always sending or receiving an invoice, and the numbers rarely match on the first try. An accounts-payable clerk calls a supplier because the invoice charges for ten units when only eight arrived (Part 3). A recorded reminder states that an outstanding balance is overdue and lists the late fee that now applies (Part 4). An invoice sits beside an email that disputes one line item and requests a corrected statement (Part 7 double passage). Because a billing problem follows a fixed arc — issue the invoice, spot the discrepancy, dispute it, correct it — ETS can link two documents with exactly one defensible answer. Miss a term like outstanding balance, discrepancy, or credit note and you can lose a linked pair at once.

This article organizes the cluster by the billing-to-resolution timeline — the invoice, the discrepancy, the dispute, and the correction — because that sequence is precisely how ETS threads the pieces together. If your general business base is thin, build it first with the TOEIC Link vocabulary essentials guide; this cluster layers on top. A billing dispute often starts from a delivery that did not match the order, so pair this with the customer complaint and service recovery cluster if the resolution side is where you slip.

Why invoice vocabulary is overweighted

Reason 1 — a billing problem produces naturally linked documents. An invoice plus a dispute email is a ready-made double passage. The amount charged in one and the amount contested in the other cross-reference each other — exactly what a linked set needs to force a single conclusion.

Reason 2 — numbers create arithmetic-flavored questions. An invoice has line items, quantities, unit prices, a subtotal, tax, and a total, so ETS can ask "What is the corrected amount?" or "Why does the customer dispute the invoice?" with one correct answer. The reader has to combine a figure from each document.

Reason 3 — the terms are fixed accounting conventions. Invoice, outstanding balance, and credit note mean the same thing at every company. That rigidity makes the cluster perfectly testable — and perfectly learnable. The collocation is the unit of memory.

The cluster, organized by the billing timeline

Stage 1 — issuing the invoice

Verbs and collocations: issue an invoice, bill a client, charge for services, itemize the charges, apply sales tax.

Nouns: invoice, bill, statement, line item, subtotal, unit price, quantity, sales tax.

Watch invoice / bill / statement — a stem may name one while the passage uses another. All three point to the document that starts the timeline. Line item / charge / entry cluster tightly, and a Part 7 question often turns on which single line item is contested.

Stage 2 — spotting the discrepancy

Verbs and collocations: notice a discrepancy, overcharge a customer, double-bill, omit a discount, exceed the quoted price.

Nouns: discrepancy, error, overcharge, discount, quote, estimate.

Discrepancy / error / mistake are interchangeable here, and a stem naming a discrepancy maps to whichever passage carries the mismatched figure. Overcharged / billed twice / incorrectly charged often anchor a "why is the customer contacting accounting?" question, and the answer is the specific number that does not match.

Stage 3 — disputing the amount

Verbs and collocations: dispute a charge, query an invoice, request a corrected statement, withhold payment, contest the total.

Nouns: dispute, query, outstanding balance, amount due, payment terms, due date.

Outstanding balance (still owed) / amount due / balance remaining are close synonyms, and a stem naming the balance maps to whichever passage carries it. Payment terms — net 30, due upon receipt — often set up a "when must the customer pay?" question that a late-fee reminder in Part 4 then reinforces.

Stage 4 — correcting the invoice

Verbs and collocations: issue a credit note, revise the invoice, adjust the total, waive the late fee, reconcile the account.

Nouns: credit note, revised invoice, adjustment, refund, reconciliation.

This is where the linked pair usually resolves. A credit note (reduces what is owed) is not a refund (money returned) — a "how will the supplier fix the overcharge?" question rewards the reader who catches which correction was named. ETS builds a distractor from the correction the passage did not offer.

Paraphrase traps ETS builds on this cluster

• Correction substitution. The supplier issues a credit note; a distractor says the customer received a refund. The correct answer names the mechanism actually used.
• Balance vs. dispute. The invoice shows a total, but the customer disputes only one line item. A "what does the customer contest?" question targets the single item, not the whole balance.
• Due date vs. issue date. A reminder names a due date while the invoice shows an issue date. A "when is payment required?" question rewards the reader who separates the two.

How to drill this cluster

Do not memorize the words as a flat list. Memorize them as a timeline: invoice → discrepancy → dispute → correction. When a Part 7 double passage puts an invoice beside a dispute email, your eye should already know that the pivot is a single mismatched figure and that the correction — credit note, revised invoice, or refund — is what the question will turn on. Practice by taking any invoice scenario, naming the exact discrepancy, and predicting the correction ETS would offer versus the one it would use as a distractor.

Layer this on top of the vocabulary essentials, and when a billing dispute grows out of a service problem, cross it with the customer complaint and service recovery cluster so the complaint and its billing correction read as one connected set.