TOEIC Link Corporate Card and Purchase Approval Vocabulary: The Request-Approve-Charge-Reconcile Cluster for Part 4 and Part 7

In a TOEIC Link office, buying something on the company's money is a controlled process, and ETS tests whether you can trace a purchase from the first request all the way to a reconciled statement. A voicemail from a finance clerk reminds an employee that the purchase still needs approval before the corporate card can be used, and that the receipt must be kept (Part 4). An email confirms that the requisition was approved, the charge went through, and asks the employee to submit the receipt so the expense can be reconciled by month-end (Part 7). Because every company purchase follows the same arc — a requisition is raised and approved, the card is charged, the receipt is submitted, and the statement is reconciled — ETS can set the steps against each other and leave exactly one answer standing. Miss a term like approve, authorize, charge, submit, or reconcile and a "what does the employee still need to do?" question can slip past in a single move.

This article organizes the cluster by the way a company purchase moves from a submitted request to a reconciled charge — the requisition is raised and approved, the card is charged, the receipt is submitted, and the statement is reconciled — because that arc is exactly how ETS threads the terms together. Because most corporate-card spending happens on the road, pair this first with the business travel booking and itinerary cluster — the same approve-then-charge vocabulary decides whether a trip's flights and hotels can be booked. And because catering and event spending is one of the most tested purchase types, contrast this with the catering and event food order cluster, where a quote, an approval, and a receipt reappear on a different kind of order.

Why corporate card and purchase approval vocabulary is overweighted

Reason 1 — a purchase has a status on a timeline. Requested, approved, charged, submitted, or reconciled — a purchase sits in exactly one state, and each state is a plausible distractor for the others. When a question asks whether the employee can buy the equipment, only the current status settles it: "the requisition is submitted" does not mean it is approved, and "the card was charged" does not mean the expense is reconciled. Part 4 messages are built to test that gap.

Reason 2 — approved and pending are opposite states, and so are authorized and declined. What the employee can do depends on the wording: an approved purchase can proceed, a pending one cannot, an authorized charge goes through, and a declined one bounces. ETS loves the gap. The question "Why couldn't the employee pay?" has exactly one answer, and it turns on whether the card was declined or the purchase was never approved.

Reason 3 — the finance terms are fixed conventions. Requisition, approve, authorize, charge, receipt, reconcile, reimburse mean the same thing across every purchase and every finance notice. 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 company purchase moves from a submitted request to a reconciled charge

Stage 1 — the requisition is raised and approved

Verbs and collocations: raise a requisition, request approval, approve the purchase, sign off, set a spending limit.

Nouns: requisition, purchase request, approval, spending limit, budget code.

The arc starts when an employee raises a requisition: they request approval for the spend, a manager signs off, and the amount is checked against a spending limit and a budget code. A Part 4 message saying "get the purchase approved before you order" answers a "what must the employee do first?" question; a Part 7 approval form listing the budget code points to this first step. The trap offers a charging or receipt detail to a reader asked only whether the purchase was cleared.

Stage 2 — the card is charged

Verbs and collocations: charge the card, authorize a payment, place the order, pay the vendor, decline a transaction.

Nouns: corporate card, charge, transaction, authorization, vendor, invoice.

Once approved, the corporate card is charged: the employee places the order, the payment is authorized, and the vendor is paid against an invoice. A Part 4 message noting "the card was declined, so the order didn't go through" answers a "what went wrong?" question; a Part 7 statement line showing an authorized transaction points to charging, not to the earlier approval. The reader who separates "authorized" from "declined" knows whether the purchase actually happened.

Stage 3 — the receipt is submitted

Verbs and collocations: submit a receipt, itemize the expense, attach documentation, code the expense, meet the deadline.

Nouns: receipt, expense report, documentation, category, deadline.

With the card charged, the employee submits the receipt: they itemize the expense, attach documentation, and code each line to the right category before the month-end deadline. A Part 4 message stressing "finance needs the itemized receipt by Friday" answers a "what is the employee missing?" question; a Part 7 reminder that an expense report is incomplete without receipts points to this stage. The detail that recurs — no receipt, no reimbursement — is a favorite ETS trap.

Stage 4 — the statement is reconciled

Verbs and collocations: reconcile the statement, match the charges, reimburse the expense, dispute a charge, reject a claim.

Nouns: statement, reconciliation, reimbursement, discrepancy, refund.

The loop closes when the statement is reconciled: finance matches the charges to the receipts, reimburses any personal outlay, and flags a discrepancy to be disputed. A Part 4 message announcing "your expenses are reconciled and the reimbursement is on its way" answers a "what has been resolved?" question; a Part 7 notice that a claim was rejected for a missing receipt points to this final step. The trap offers a charging or submission detail to a reader asked whether the money was actually returned.

How ETS builds the traps

The four stages give ETS a clean grid of distractors. A "requested" purchase is offered when the answer is "approved"; an "authorized" charge is offered when the answer is "declined"; a "submitted" receipt is offered when the answer is "reconciled." Every wrong option is a real step in the cycle — just the wrong one for the question asked. Knowing the definitions is not enough; the test rewards you for knowing the order and, above all, the approved-versus-pending and authorized-versus-declined splits.

Listening (Part 4) tends to test the next action — what the employee must still do before a purchase clears or an expense is paid. Reading (Part 7) tends to test the status — where in the finance cycle a particular purchase sits, based on a requisition, a statement, or a reimbursement notice. Train both angles on the same vocabulary and the cluster stops leaking points.

Study routine for this cluster

1. Draw the arc. Write the four stages — request, charge, submit, reconcile — and file each verb and noun under its stage. A word you cannot place is a word you cannot yet use.
2. Drill the status splits. For each practice item, ask two questions: approved or pending? authorized or declined? The wording, not the amount, decides.
3. Read statements for status. Practice with expense reports and reconciliation notices, and for each one name the current stage of the purchase. This mirrors exactly what Part 7 asks.
4. Transfer the loop. Review this cluster alongside the business travel booking and itinerary cluster and the catering and event food order cluster, and notice that the same approve-charge-reconcile vocabulary governs every company purchase — learn it once, apply it everywhere.

Own the request-approve-charge-reconcile arc and the corporate card cluster becomes one of the most predictable point sources on the test — a tight finance loop ETS reuses precisely because every purchase is controlled the same way.