Prepaid Income for Wedding Venues in Xero: How to Automate Deferred Revenue by Event Date
- Simon Hancott
- 11 minutes ago
- 5 min read
If you run a wedding venue, you already know the pattern. A couple books their date, sometimes two years out, and pays a deposit. More payments follow over the following months. The final balance often lands just weeks before the big day.
Every one of those payments hits your bank account long before the wedding actually happens. And every one of those payments is, in accounting terms, prepaid income, money you've received for a service you haven't delivered yet.
The accounting principle is simple: that money isn't your revenue yet. It's a liability on your balance sheet, an obligation to deliver a wedding, until the date the wedding actually takes place. Only then is it earned.
The practice, as one operator running multiple wedding venue companies through Xero described it, is considerably harder: "We currently raise the invoices when payment is made, and then record that on a spreadsheet, and then release that... by the event date, which is the wedding date. But that is all handled by spreadsheets."
This post explains how to stop doing that, and have Xero recognise the revenue automatically, on the date of the wedding, without a spreadsheet in sight.
Why Wedding and Events Businesses Have This Problem More Than Most
For most businesses, the gap between cash received and revenue earned is small, a few weeks at most. For wedding venues, it can be twelve months, eighteen months, sometimes longer. A venue might receive a deposit in January for a wedding the following September. By the time the wedding happens, that payment has been sitting on the balance sheet as prepaid income for the best part of a year.
Multiply that across every booking, every deposit instalment, every balance payment, across however many wedding dates you have booked at any given time, and the spreadsheet becomes a permanent, ever-growing tracking exercise. One payment per booking is manageable. Three or four payments per booking, across dozens of bookings, each needing to be released on a different date, is not.
The operator on the call described exactly this: payments coming in via "three separate payments through for one company, and then... another four or five through the other company", all relating to a single wedding date, all needing to be tracked until that date arrives, all currently done "bit by bit by bit" through bank reconciliation, "probably... daily."
The Multi-Company Structure Makes It Harder Still
Many wedding and events businesses don't operate as a single company. A venue might be one company. Catering might be a second. A marquee or events arm might be a third. Each with its own Xero organisation, its own invoices, its own prepaid income to track, but all tied to the same underlying event dates.
This means the spreadsheet isn't just tracking prepaid income for one business. It's tracking it across multiple Xero organisations, with the same wedding date appearing in two or three different places, each needing to be released independently, each one a chance for something to be missed or mismatched.
The Fix: Let the Invoice Carry the Date
The single change that makes this entire process automatable is remarkably simple: put the event date in the invoice description.
When a deposit invoice is raised in Xero for a wedding booking, instead of a generic description like "Deposit - Smith Wedding," the description becomes "Smith Wedding - 12 July 2027." That's it. That single date is everything Spread needs to know.
From that point, the process works like this:
The revenue is backed out of the invoice month immediately. As soon as the deposit invoice is raised, whenever that is, however far in advance, the revenue is moved off the P&L and onto the balance sheet as deferred income.
The revenue is recognised in the month of the wedding. On the date specified in the invoice description, the full amount moves from the balance sheet onto the P&L. No spreadsheet, no manual journal, no one needing to remember.
This happens for every payment, automatically. Whether a booking involves one payment or five, each invoice carries its own description and is recognised independently, or all recognised together on the wedding date, whichever matches how the booking actually works.
The process is described by Spread's own product team in simple terms: "We back out the revenue from the invoice month... and then the rest of the subsequent journals to realise the revenue were posted based on what the date was. That's it. That's as simple as that."
What This Looks Like Across Multiple Venues or Companies
For businesses operating multiple wedding venue companies through separate Xero organisations, Spread connects to each one independently. Every organisation appears in a single dashboard, so whether you're managing one venue or eight different companies across a wider estate, the prepaid income process works the same way in each, visible from one place.
Each organisation gets its own balance sheet reconciliation, a report showing every booking, the invoice number, the couple's name, the wedding date, the amount deferred, and the month it will be (or has been) recognised. One line per invoice. The whole prepaid income position, for every venue, visible at a glance.
What About Bookings Already on the Spreadsheet?
This is the question every business asks when they first look at this, what happens to everything currently sitting on the existing prepaid income spreadsheet?
The answer is straightforward: nothing needs to be unpicked. Pick a start date, typically the beginning of a new month or financial period. Everything currently on the spreadsheet stays there and runs down to zero on its existing schedule, exactly as it would have done anyway. Every new booking from the start date forward goes through the automated process from day one.
For anything on the existing spreadsheet that hasn't yet been released, it can also be imported into Xero as a manual journal in one batch, "a couple of hours usually," as Spread's team describe it, bringing the balance sheet up to date in one go, with the new automated process taking over from that point.
Annual and Multi-Year Memberships - The Same Principle Applies
The same approach applies beyond weddings. Venues with annual memberships, moorings, clubs, season passes, face an identical prepaid income problem: payment received upfront, revenue earned across the year ahead.
For businesses with large volumes of annual payments against a specific revenue category, there's a bulk option: select every transaction for that category in one go and apply a single date range across all of them in one click. One operator described exactly this pattern for football season tickets — sold in one month, the season running through to a fixed end date, the whole batch processed in under a minute once set up.
Whether it's a wedding date, a mooring renewal, or a season ticket expiry, if the date is known at the point of sale, it can be built into the invoice and the rest follows automatically.
Getting Started
Spread connects to each Xero organisation in under two minutes. For a multi-company estate, each company connects separately but sits in the same dashboard.
The recommended starting point: pick one company, often the one with the simplest prepaid income pattern, and run it for a single month-end first. Once the process is proven on one, extending it to the rest of the estate is largely a configuration exercise rather than a new project.
There's a free trial, with no long-term contract. Cancel any time.
Start your free trial at spread.finance
Further reading:
This post is based on a real conversation with an operator managing prepaid income for wedding venue businesses across multiple Xero organisations. Details have been adjusted to protect confidentiality, but the substance of the conversation is unchanged.
Comments