Quick answer
Two different things get called a prepayment, and Xero handles them differently. Money paid before a document exists (a deposit, an advance) is recorded with Xero’s prepayment transaction type from the bank reconciliation screen, then allocated when the bill or invoice arrives. A prepaid expense (an annual cost consumed monthly) is recorded by parking the bill in a prepayments asset account and releasing it to expense with a repeating manual journal. Naming which case you have is most of the job.
Case one: payment before the document
A supplier wants a deposit before starting work, or a customer pays ahead of invoicing. When the money moves through the bank feed, code the statement line as a prepayment against the contact rather than forcing it onto a not-yet-existing document or dumping it in an expense account. The prepayment sits on the contact’s account as available credit, visible in their activity, and the reconciliation is clean. When the bill or invoice arrives, allocate the prepayment against it; the document shows part-settled and only the balance changes hands. Two refinements: if terms attach conditions to the deposit, note them in the reference; and if the deal collapses before any document exists, the prepayment refunds directly, keeping the round trip on the contact’s history.
Xero also has an overpayment type for the neighbouring case where a document existed but the payer sent too much. Prepayment is before the document; overpayment is beyond it. Picking the right one matters mainly for tax, since overpayments never carry tax while prepayments can.
Case two: prepaid expenses spread over time
The annual insurance premium, the yearly software licence, the trade body subscription: one bill, twelve months of benefit. Recording the whole cost in the payment month makes that month look terrible and the other eleven artificially good, which defeats monthly reporting. The pattern:
- Record the bill normally, but code the line to a prepayments current asset account instead of the expense account.
- Set up a repeating journal dated the last day of each month: debit the expense account, credit prepayments, one month’s share.
- Give the repeating journal an end date at the final month so it stops itself.
- At each month end, reconcile the prepayments account balance to a simple schedule of what remains unreleased per contract.
Materiality sets the threshold: spreading a small subscription is effort without insight, and most firms set a floor below which annual costs just expense on payment. Above the floor, the schedule-plus-repeating-journal pattern keeps the balance sheet honest about value not yet consumed.
Keeping the two cases apart
The failure pattern is treating case one with case two’s tools or vice versa. A supplier deposit coded into the prepayments asset account (instead of the prepayment transaction type) reconciles the bank but detaches the amount from the supplier, so when their bill arrives it shows fully payable and the deposit is forgotten until someone audits the asset account. In the other direction, an annual premium recorded as a contact prepayment leaves the whole cost waiting to allocate against the bill, doing nothing to spread it. Deposit or advance: contact-linked prepayment transaction. Cost benefiting future months: asset account plus release journals.
Common mistakes
- Supplier deposits coded straight to expense, overstating costs now and understating them when the real bill arrives.
- The prepayments asset account growing all year because release journals were never set up; the balance should shrink to its schedule every month.
- Release journals without end dates, quietly expensing a thirteenth and fourteenth month.
- Deposits for cancelled deals left sitting as contact credits nobody reviews.
- Tax coded inconsistently between the prepayment and the eventual document, unbalancing the return for the period.
Software that helps
- Xero’s prepayment and overpayment types plus repeating journals cover both cases without add-ons.
- ExpenseFlow helps at the capture step: annual invoices are extracted with the full document image alongside, coded with the right tax treatment, and posted to Xero through approval, and that review moment is where the spread-or-expense decision gets made deliberately rather than by default.
- Workpaper templates for the prepayments schedule keep the month-end reconciliation to minutes; our month-end checklist includes the step.
Related guides
The mirror-image adjustment is recording accruals in Xero; the journal mechanics are in journal entries; the review rhythm is in end of month. Concept: prepayment.
From ExpenseFlow
Expense coding on autopilot
ExpenseFlow reads every receipt, assigns the right tax treatment and account code, and syncs to Xero or QuickBooks Online once you approve.