# Prepaid Account Reconciliation Template and Schedule

- Author: PreciseBankFlow (https://precisebankflow.com)
- Published: 2026-10-17
- Category: Account reconciliations
- Canonical: https://precisebankflow.com/blog/prepaid-account-reconciliation-template

> A prepaid account reconciliation template with an amortization schedule, invoice support, the rollforward and what to do when the balance won't tie.
A prepaid account reconciliation template compares the prepaid expense balance in the general ledger with a schedule listing every amount paid in advance, how much has been expensed and how much remains. The schedule is built from vendor invoices, rolled forward each month, and the template shows the unexpensed total agreeing with the ledger account.

## Columns of a prepaid account reconciliation template

A prepaid schedule needs one row per prepaid item and enough columns to recompute its balance without opening another file: vendor, invoice number, description, total paid, service start and end dates, monthly amount, months expensed, amount expensed to date and remaining balance. The total of the last column is the figure that must equal the ledger.

A sensible column order is:

1. **Vendor** and **invoice number**, so anyone can pull the document.
2. **Description** of what was bought, such as "general liability insurance policy" or "annual software subscription".
3. **Payment date** and **amount paid**.
4. **Service start** and **service end** dates. These drive everything else.
5. **Months in term** and **monthly expense**, computed from the dates and the amount.
6. **Expensed to date**, the cumulative amount moved to expense through the period end.
7. **Remaining balance**, amount paid less expensed to date.
8. **Expense account** the monthly amount is charged to.

Above the rows sits a short balance block: the schedule total, the ledger balance and the difference. Below it sits the sign-off. Keep the formulas visible in the monthly-expense and expensed-to-date columns. A typed number in either column is the first thing a reviewer will question.

Some teams add a column for the expected renewal date. It costs nothing and it warns the team when a policy or contract will produce a new invoice, so the next prepaid line is not missed.

## Building the prepaid amortization schedule from the vendor invoice

An amortization schedule spreads one advance payment evenly over the months it covers. Take the amount from the invoice, count the months between the service start and end dates, and divide. Each month the schedule moves one share from the prepaid asset to expense, and the remaining balance falls by the same amount.

Read the invoice, not the payment. The payment date tells you when cash left, but the service period on the invoice tells you which months benefit. An insurance policy paid on December 20 for a term starting January 1 has nothing to expense in December, even though the cash is gone.

Here is a worked example with three illustrative items for a company with a calendar year, reconciled at the end of April.

| Item (example) | Paid | Term | Monthly | Months expensed to Apr 30 | Expensed to date | Remaining |
| --- | --- | --- | --- | --- | --- | --- |
| Liability insurance | 14,400.00 | Jan 1 to Dec 31 | 1,200.00 | 4 | 4,800.00 | 9,600.00 |
| Software subscription | 6,000.00 | Mar 1 to Feb 28 next year | 500.00 | 2 | 1,000.00 | 5,000.00 |
| Trade show booth deposit | 3,000.00 | Event in September | 0.00 | 0 | 0.00 | 3,000.00 |
| **Total** | **23,400.00** | | | | **5,800.00** | **17,600.00** |

The trade show deposit shows a useful edge case. It is not spread over months at all. The whole amount moves to expense when the event happens, so the schedule holds it at full value until September.

Partial months need a rule. Two common rules are to start amortization in the first full month of service, or in the month service starts if it starts on or before the 15th. Pick one rule, write it at the top of the schedule and apply it every time. Day-based proration is more precise and rarely worth the effort on small items.

## The prepaid rollforward: opening balance, additions, amortization, closing balance

A prepaid rollforward explains the month's movement in four lines: the opening balance from last month, plus new prepaid payments, less the amount expensed this month, equals the closing balance. When the closing figure agrees with both the schedule total and the ledger, the month is reconciled and the schedule itself is proven arithmetically.

Using the example above, the April rollforward looks like this:

| Rollforward line (example) | Amount |
| --- | --- |
| Opening balance per ledger, March 31 | 16,300.00 |
| Add: April debits to the prepaid account per ledger | 3,400.00 |
| Less: April amortization (1,200.00 + 500.00) | (1,700.00) |
| Closing ledger balance, April 30 | 18,000.00 |
| Schedule remaining balance | 17,600.00 |
| Difference | 400.00 |

The difference of 400.00 is deliberate in this example. The ledger shows 3,400.00 of April additions, while the schedule only picked up the 3,000.00 trade show deposit. The missing 400.00 is an annual parking permit paid in April and posted to the prepaid account, but never added to the schedule. Adding the line closes the gap, or, under the threshold rule discussed further down, the payment is reclassified to expense.

The rollforward is the part a reviewer checks first, because it ties three independent things: last month's signed-off balance, this month's payments from the ledger, and the schedule's arithmetic. A schedule that is correct on its own can still hide an unrecorded addition. The rollforward will not.

## What invoice support should each prepaid line carry?

Each prepaid line needs the vendor invoice or contract that shows the amount and the service period, and proof that the payment was made. For insurance, that means the policy declarations page. For subscriptions, the order form or renewal notice. For deposits, the agreement that says when the service will be delivered.

Store the support where the next reviewer can find it, linked by invoice number. A short checklist for each new line:

- **Invoice or contract** with the vendor's name, amount and dates.
- **Service period** clearly stated. If the invoice says "annual" without dates, add the start date from the contract or an email.
- **Payment evidence**, such as the bank statement line or the card charge.
- **Approval**, if your process requires one for advance payments over a certain size.

Payments made by company card are the ones most often missed. An annual subscription charged to a card lands in the card account with the merchant name only. Unless someone recognises it during the card reconciliation, it is coded straight to expense and the prepaid schedule never sees it. The process for working through those charges is set out in [how to reconcile credit card statements in Excel](/blog/how-to-reconcile-credit-card-statements-in-excel). Bank debits for prepaids are easier to catch, and [PreciseBankFlow](/get-started) lists each statement line with its amount and date so the large advance payments stand out when you match them.

Marketplace sellers face a version of this. Advertising or subscription fees taken out of a payout are paid before the benefit arrives, yet they appear as deductions inside the settlement, not as separate invoices. Splitting those deductions out is part of the [Amazon settlement reconciliation for sellers](/blog/amazon-settlement-reconciliation).

## Why won't the prepaid balance tie to the amortization schedule?

A prepaid balance that will not tie usually comes from one of four things: a payment missing from the schedule, an amortization entry skipped or doubled, a finished item still on the ledger, or an expense coded to the prepaid account by mistake. Each leaves a recognisable trace.

Work through the checks in this order:

1. **Compare additions.** Filter the prepaid ledger account for the month's debits. Every debit should match a new row on the schedule. The parking permit in the example was found this way.
2. **Compare amortization.** The month's credits to the prepaid account should equal the schedule's monthly total. A missing entry leaves the ledger higher than the schedule by exactly one month's charge. A duplicated entry leaves it lower by the same amount.
3. **Look for finished items.** When an item's term ends, the schedule shows zero, but if the final month's entry was skipped, the ledger keeps a stub.
4. **Look for wrong postings.** A credit to the prepaid account that is not amortization may be a refund, a cancellation or a misposted payment.

When the difference equals one item's monthly amount, start with step 2. When it equals an odd amount near a recent payment, start with step 1. If the ledger account has a subsidiary list in your system, the schedule acts as that list, and the same logic as a [control account reconciliation to the subsidiary ledger](/blog/control-account-reconciliation) applies: entries posted to the account without a matching schedule line break the tie.

Cancellations deserve a note. When a contract is cancelled mid-term and the vendor refunds part of the payment, remove the remaining balance from the schedule, record the refund against it, and expense any difference. Leaving the line to run its normal course overstates expense later.

## Prepaid payments too small to capitalize

Small advance payments are often expensed immediately rather than placed on a prepaid schedule. A written threshold, such as a set dollar amount per invoice, keeps the schedule focused on items that matter and saves monthly entries that would not change anyone's view of the results. Below the threshold, the payment goes straight to expense.

The threshold is a policy choice, not a rule from outside. Set it with the person who signs the financial statements, write it down, and apply it consistently. A company with large monthly results might choose a higher figure than a small one. Some teams also skip the schedule for any term of one month or less, since the expense lands in the right period anyway.

There are times not to use the shortcut:

- **Year end.** A large payment in December for next year's service belongs on the balance sheet, even if the company usually expenses small items as they come.
- **Grant or contract reporting.** If costs must be reported in the period they benefit, the threshold may not apply.
- **Many small items for one purpose.** Ten subscriptions each under the threshold can add up to a material amount.

Deferred revenue is the mirror image of a prepaid expense. The same schedule, rollforward and threshold logic applies from the seller's side, as shown in the [deferred revenue reconciliation template in Excel](/blog/deferred-revenue-reconciliation-template-excel).