To record prepaid expenses, code a payment that covers future months, such as a twelve-month insurance premium, to a prepaid expenses asset account instead of an expense. Then post a monthly journal entry that moves one month's share into the expense account. Each month carries its own cost, and the asset shows what is still unused.
Which payments should be recorded as prepaid expenses?
A payment is a prepaid expense when it buys a service the business will use over several future months, paid before those months arrive. Annual insurance premiums are the classic case. Annual software plans, rent paid in advance, maintenance contracts and trade show deposits for a show months away fit too.
Two tests separate a prepayment from an ordinary expense:
- Does the benefit run past the current month? A $7,200 premium that covers March through February does. A single month's phone bill does not.
- Is the amount large enough to matter? Spreading a $40 annual domain renewal over twelve months adds work with no useful effect on any report.
Prepayments are different from purchases of equipment. A laptop or a vehicle is a long-lived asset that is depreciated, which is a separate process. A prepayment is a service bought in advance that is simply used up month by month.
Prepaid treatment also assumes the books use accrual accounting, or at least that the client wants monthly figures that compare fairly. A cash-basis client who only needs a tax-year total may be fine expensing the premium when paid. Confirm the approach with the client's CPA before setting up schedules for every renewal.
Posting the prepaid payment from a single bank statement line
The prepaid payment itself is one line on the bank statement, and it is coded to an asset, not to expense. Debit "Prepaid expenses" (or a sub-account such as "Prepaid insurance") and credit checking for the full amount, dated the day the payment posted.
Suppose the statement shows "ACH DEBIT HARBORLINE INS PREMIUM 7,200.00" on March 1. The entry is:
- Debit prepaid insurance 7,200.00.
- Credit checking 7,200.00.
At this point no expense has been recorded. The profit and loss for March is untouched until the first monthly release is posted.
When the client pays the premium in installments, each installment can still be a prepayment if it covers more than the month it is paid in. A quarterly installment covering three months gets the same treatment: post it to the asset, then release a third of it each month.
Keep the invoice or policy declaration page with the payment. It shows the coverage period, which decides how many months the cost is spread over and when the release starts.
If the payment came from a card rather than the bank account, the treatment is identical. Only the credit side changes, to the card liability account.
A monthly release schedule for prepaid insurance
A release schedule spreads the prepayment evenly across the months it covers. The schedule is the source for each month's journal entry and the check on the remaining balance. For the example policy, $7,200 over twelve months is $600 a month, starting in March, the first month of coverage.
The figures below are an example for a fictional client.
| Month | Release to insurance expense | Prepaid balance after release |
|---|---|---|
| March | 600.00 | 6,600.00 |
| April | 600.00 | 6,000.00 |
| May | 600.00 | 5,400.00 |
| June | 600.00 | 4,800.00 |
| July | 600.00 | 4,200.00 |
| August | 600.00 | 3,600.00 |
| September | 600.00 | 3,000.00 |
| October | 600.00 | 2,400.00 |
| November | 600.00 | 1,800.00 |
| December | 600.00 | 1,200.00 |
| January | 600.00 | 600.00 |
| February | 600.00 | 0.00 |
Each month's entry is the same: debit insurance expense 600.00 and credit prepaid insurance 600.00.
The release is a journal entry, not a bank transaction. No line on any bank statement corresponds to it, so it will never arrive through a bank feed or a converted statement. That is exactly why releases get forgotten.
Coverage that starts mid-month
A policy that starts on March 15 covers half of March. Two common approaches work: start the release in April and run it through the following March, or release a half month in March and a half month at the end. Pick one convention per client and record it on the schedule.
Amounts that do not divide evenly
An annual software plan of $1,000 does not split into equal cents. Release $83.33 for eleven months and $83.37 in the last, so the balance reaches exactly zero.
Prepaid balances after cancellations, refunds and card rewards
A prepaid balance changes partway through when the client cancels, the vendor refunds part of the charge, or the original payment is reversed. In each case, adjust the asset first, then put any difference into the expense account. The schedule then needs a fresh line from the change onward.
Cancellation with a partial refund. The example client cancels the policy at the end of July with $4,200 still in prepaid insurance. The insurer refunds $3,950 and keeps $250 as a cancellation charge. Record the refund deposit as a debit to checking of 3,950.00 and a credit to prepaid insurance of 3,950.00. Then move the remaining 250.00 from prepaid insurance to insurance expense. The balance is zero, and the cancellation cost sits in July.
A reversed payment. Sometimes the original debit bounces or the bank reverses it, and the vendor collects again later. Reverse the prepaid entry against the reversal line, so the asset does not hold a payment that never went through. The guide to reversed transactions on bank statements covers how to pair the original and reversal lines.
Card rewards on a large premium. A premium paid on a rewards card can earn cash back. The reward does not reduce the prepaid balance on the schedule; treat it according to the client's policy for rewards. The post on recording cash back rewards explains the usual choices.
Mid-term price changes. An insurer may add a charge after an audit or a coverage change. Post the new amount to prepaid if it covers the rest of the term, and spread it over the months left.
When is a prepaid amount too small to spread?
A prepaid amount is too small to spread when spreading it would not change any decision the client or CPA makes from the reports. Many practices set a written threshold per client, such as any prepayment under a set amount being expensed when paid. Below the threshold, the extra schedules cost more time than they are worth.
Setting the threshold:
- Agree it with the CPA. The tax and reporting effect depends on the client, so the figure belongs in the client's file, not in the bookkeeper's head.
- Apply it consistently. Spreading one $300 renewal and expensing another invites questions at review time.
- Look at the total, not the item. A client with forty small annual renewals that together reach a large amount may justify spreading the largest few.
- Watch year end. A large prepayment made in December that covers next year distorts both years if it is expensed. That is the case most worth getting right, even for clients who are otherwise relaxed about monthly accuracy.
When a client is on cash-basis books and only uses the reports for tax, the answer may be to expense almost everything. Record that decision too, so the next bookkeeper does not set up schedules nobody needs.
Reconciling the prepaid expenses account at month end
Reconciling the prepaid expenses account means proving that its balance equals the unused part of every open prepayment. List each schedule's remaining balance and compare the total with the account balance in the books. A difference means a missed release, a release posted twice, or a payment coded straight to expense.
An example month-end reconciliation for the fictional client at June 30:
| Prepayment | Paid | Schedule balance at June 30 |
|---|---|---|
| Insurance, March to February | 7,200.00 on March 1 | 4,800.00 |
| Software plan, January to December | 1,200.00 on January 1 | 600.00 |
| Total per schedules | 5,400.00 | |
| Prepaid expenses per books | 5,400.00 |
When the totals disagree, check the most recent month first. The usual cause is a release that did not post, or a new prepayment that was coded to expense because the bank line looked like any other bill. Searching the bank lines for vendors with annual billing, such as insurers and software companies, finds the second case quickly.
Recurring entries for the monthly prepaid release
A recurring journal entry makes the monthly release automatic, so it cannot be forgotten. Most accounting systems can save the release as an entry that posts each month for a set number of months. Set it up the day you code the prepayment, and set its end date to the last month of coverage.
A recurring entry still needs checking. Cancellations, mid-term charges and renewals at a new price all break the pattern, and the scheduled entry will keep posting the old amount unless someone changes it. The month-end reconciliation catches these.
The bank side and the release side are separate tasks. A statement converter handles the payment line: in AutoBankConvert, a client rule can send the insurer's annual debit to the prepaid insurance account each time it appears, so the renewal is not coded as a plain expense next year. The monthly release stays in the accounting system. The guide to bookkeeping automation software looks at which tools cover which parts of that work.