Build a Complete Recurring-Payment Inventory

Create one register for monthly, four-weekly, quarterly, and annual commitments across cards, accounts, and app stores.

Illustrated overview of Build a Complete Recurring-Payment Inventory
Original WHERE.YOU illustration for this guide.

What the register must explain

A complete inventory records cadence, annual cost, billing owner, renewal terms, and the next review action.

A list of merchant names is not enough. The inventory should explain what each commitment costs, who controls it, and what event ends or renews it.

Collect from every billing channel

Review bank accounts, cards, digital wallets, app stores, telecom bundles, and payroll deductions. Use 13 months where possible to expose annual charges.

Use fields that support a decision

Use fields that support a decision table
FieldPurpose
Merchant and serviceSeparates processor from benefit
Amount and cadenceCalculates annual commitment
Billing ownerShows who can make changes
Renewal and notice datesPrevents missed decisions
Last use and next actionTurns inventory into review

Keep the inventory actionable

Use a longer transaction window to catch charges that appear only once a year with How to Find Forgotten Subscriptions.

Turn mixed billing frequencies into comparable annual totals through How to Find Annual Subscription Renewals.

Populate the owner, cadence, amount, and next-action fields in the recurring-payment inventory tool.

Recurring-payment inventory at a glance

A recurring-payment inventory connects each charge with its cadence, annual cost, billing owner, renewal terms, and next review action.

Fields to put on the worksheet
RecordMerchant, service purpose, and payment account
RecordAmount, cadence, annualized cost, and next date
RecordOwner, cancellation route, notice deadline, and decision

Use the completed worksheet to decide

Mark the charge keep, change, negotiate, cancel, or investigate. An inventory without an owner and review date becomes another forgotten list.

Track status without deleting the trail

Use separate statuses for active, under review, cancellation requested, and closed. A cancellation request is not closed until confirmation arrives and the expected final billing date passes. Keep the old amount, effective date, and evidence when a plan changes. This history makes price increases and charges that return after cancellation much easier to spot.

Reconcile the inventory

Compare the next statement with the register. Add new charges, close cancelled items only after confirmation, and investigate amount changes. Keep inactive records so a returning charge is visible.

Design the inventory around actions

Each row should identify the commitment, billing owner, payment account, current amount, cadence, annualized cost, next expected date, notice deadline, purpose, recent use, status, and evidence link. Add an action owner and review date so the register does not become a passive list.

Design the inventory around actions table
StatusMeaningRequired evidence
ActiveAccepted commitment currently billingCurrent terms and next date
InvestigateCharge or purpose is not confirmedReceipt, account, or merchant record
Change requestedDowngrade or negotiation is pendingReference and promised effective date
Cancellation requestedStop request submitted but not verifiedConfirmation and expected final charge
ClosedAgreement ended and later billing checkedEffective date and clean statement

Reconcile the register as a control account

At each review, compare expected charges with the statement. A missing expected charge may signal a changed date or payment failure; an unexpected charge may be a new commitment, a price change, or a cancelled service that returned. Preserve old rows so changes remain visible.

Summarize the inventory by annual commitment, next thirty-day cash requirement, amount under review, and renewals before their notice deadlines. Those four views support different decisions.