TOEIC Link Software License Renewal and Subscription Billing Vocabulary: The Plan-Renewal-Charge-Change Cluster for Part 4 and Part 7
In TOEIC Link, a software subscription is a cycle — a customer is on a plan, the license comes up for renewal, a charge is billed, and the customer can change the arrangement — and ETS tests whether you know which step a passage names. A plan the customer subscribed to is one thing, the renewal that comes due is another, and the charge the company billed is a third — and a question can turn on whether the license auto-renews or expires. A recorded message tells callers their subscription will renew automatically unless they cancel (Part 4). A billing email states a license is due for renewal, shows the amount charged to the card on file, and explains how to upgrade, downgrade, or cancel, and a question asks why the email was sent, what the customer was charged, or how to change the plan (Part 7). Because a subscription always moves the same way — plan, renewal, charge, change — ETS can set the steps against each other and leave exactly one answer standing. Miss a term like renew, expire, auto-renewal, upgrade, or prorate and a billing question can slip past in one move.
This article organizes the cluster by the way a subscription moves through a billing cycle — plan, renewal, charge, change — because that sequence is exactly how ETS threads a subscription notice together. Because a software license is a contract that comes up for renewal on a schedule, pair this first with the contract renewal and service agreement cluster — a subscription renewal is a service agreement renewing on its own terms. And because every renewal produces a bill with payment terms, contrast this with the invoice and payment terms cluster, where the same skill — separating what was charged from what is still due — is what a question turns on.
Why subscription billing vocabulary is overweighted
Reason 1 — a billing event has several plausible descriptions. A renewal charge, an upgrade fee, a prorated adjustment, and a late payment all appear on a subscription notice, and each is a plausible distractor for the others. When a question asks why a customer was charged, only the stated reason answers it — exactly what a linked set needs.
Reason 2 — a subscription reads in a fixed direction. Because a subscription always runs the same way — plan, renewal, charge, change — ETS can ask "Why was the email sent?" or "What should the customer do to avoid the charge?" with exactly one correct answer. The reader matches the direction against the notice.
Reason 3 — the terms are fixed conventions. Renew, expire, auto-renewal, upgrade, and prorate mean the same thing across every software vendor. 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 subscription moves through a billing cycle
Stage 1 — the plan
Verbs and collocations: subscribe to a plan, sign up for a tier, activate a license, be on a monthly plan, hold a subscription.
Nouns: plan, subscription, license, tier, seat.
The cycle begins with the plan the customer is on — the subscription they signed up for or the license they activated, priced per seat or per tier. A Part 4 message confirms a customer is on the annual plan; a Part 7 question asking what level of service the customer has points to the plan line, not the renewal notice. The trap offers a different tier to the reader who confused the current plan with an available upgrade.
Stage 2 — the renewal
Verbs and collocations: come up for renewal, renew automatically, expire on a date, lapse, be due for renewal.
Nouns: renewal, renewal date, expiration, auto-renewal, term.
The subscription then comes up for renewal — the license is due for renewal, it will renew automatically on the renewal date, or it will expire if not renewed. A Part 7 notice stating a license will auto-renew unless the customer cancels asks what happens if no action is taken; the reader who knows auto-renewal means the charge proceeds by default, while expire means access ends, avoids reversing the two. This is where ETS most often sets renew (continue) against expire (end) — one word decides which.
Stage 3 — the charge
Verbs and collocations: bill the customer, charge the card on file, process the payment, apply a discount, prorate the amount.
Nouns: charge, invoice, billing statement, amount due, billing cycle.
Then the company bills the customer — it charges the card on file, processes the payment for the new billing cycle, and may prorate the amount for a mid-cycle change. A Part 4 message states the card on file will be charged on the renewal date; a Part 7 question asking how much the customer will pay points to the amount due, and the trap offers last cycle's figure to the reader who missed a price change. What was charged this cycle, not the standard rate, is what this stage tests.
Stage 4 — the change
Verbs and collocations: upgrade the plan, downgrade to a lower tier, cancel the subscription, add seats, switch billing to annual.
Nouns: upgrade, downgrade, cancellation, plan change, refund.
Finally the customer can make a change — upgrade to a higher tier, downgrade to a cheaper one, add seats, or cancel the subscription, sometimes with a prorated refund. A Part 7 email explaining how to cancel before the renewal date to avoid the charge asks what the customer should do; the reader who knows downgrade (a lower tier, still active) differs from cancel (service ends) avoids the swap. This is the subtlest part of the cluster — plan changes look alike, and a single word decides whether the customer pays more, pays less, or stops paying.
How the four stages become one question
A single Part 7 double passage can run all four. A billing notice confirms a customer is on the annual plan (Stage 1), states the license is due for renewal and will auto-renew on a given date (Stage 2), shows the amount that will be charged to the card on file (Stage 3), and explains how to upgrade, downgrade, or cancel before that date (Stage 4). The question — "What must the customer do to avoid being charged?" — is answerable only if you tracked the subscription from plan through renewal to the change options. A reader who stopped at the charge picks the amount as the answer; a reader who followed the sequence picks "cancel before the renewal date." That is the entire design: four stages, one defensible answer.
The paraphrase traps to rehearse
- Renew vs. expire. A subscription that renews continues; one that expires ends. A notice saying a license will auto-renew is the opposite of one saying it will expire — and a question often offers "the service will end" to the reader who misread the auto-renewal.
- Upgrade vs. downgrade. An upgrade moves to a higher, pricier tier; a downgrade moves to a lower, cheaper one. A customer who downgrades is still subscribed, just paying less — the trap swaps the direction.
- Cancel vs. downgrade. Canceling ends the subscription; downgrading keeps it at a lower level. A message about canceling before renewal is not the same as switching to a smaller plan, and ETS pairs these to test whether the reader knows access continues in one case and stops in the other.
- Charge vs. refund. A charge takes money; a refund or credit returns it. A prorated refund for a mid-cycle downgrade is money back, not a new bill — and the trap offers a charge to the reader who saw only the plan change.
How to study this cluster
Read a subscription notice as a four-step cycle, not a list of words. Ask of any passage: What plan is it? When does it renew? What is being charged? What can the customer change? Those four questions map onto plan, renewal, charge, and change — and a TOEIC Link question always lands on one of them. Learn the collocations in pairs — subscribe to a plan, renew automatically, charge the card on file, cancel the subscription — because ETS tests the phrase, not the isolated word. Then rehearse the traps above until renew ≠ expire and cancel ≠ downgrade are automatic. When the four stages are second nature, a subscription-billing question stops being a vocabulary test and becomes a matter of finding which step the question points to — which is exactly how the cluster is built to be solved.