TOMS in Xero — what works, what doesn't, and where the workarounds break

The Tour Operators Margin Scheme is the second-most awkward UK VAT regime to handle in cloud accounting software, after partial exemption. It's also unusual in that — unlike partial exemption — the affected businesses are easy to identify and almost always know they're affected. They're tour operators. They've heard of TOMS. What they may not know is how thoroughly their accounting platform fails to support it.

This post walks through what TOMS actually requires, how Xero (the most common cloud platform among tour operators) handles it in practice, and where the workarounds break. Most of what's said here applies equally to QuickBooks Online, Sage Business Cloud, and FreeAgent.

What TOMS is, briefly

The Tour Operators Margin Scheme is a special VAT regime for businesses that buy in and resell travel facilities as a principal or undisclosed agent. Instead of accounting for VAT on the full selling price of a travel package, the operator accounts for VAT on the margin — the difference between the selling price and the bought-in cost.

The headline rule is simple: VAT is calculated on the margin, not the full sale. The operating reality is anything but simple, because TOMS introduces several mechanics that the standard VAT model doesn't have.

• Provisional output VAT during the year, with a year-end recalculation
• Booking date vs departure date distinctions that cloud ledgers don't natively support
• Zero-rating for non-UK destinations (a post-Brexit change that took effect 1 January 2021)
• Multiple supply types within a single package, some inside TOMS and some outside
• No input VAT recovery on bought-in margin scheme costs — VAT effectively absorbed into the cost of sales

Post-Brexit: the rule change most operators are still adjusting to

Before 1 January 2021, TOMS applied to all travel margin scheme supplies regardless of where the holiday was enjoyed. The post-transition rules treat margin on holidays enjoyed outside the UK as zero-rated, while UK holidays remain subject to TOMS VAT at the standard rate.

This sounds like a simplification — and for operators selling exclusively non-UK holidays, it largely is. But for operators selling a mix, the calculation becomes split: UK margin attracts VAT, non-UK margin doesn't. Allocating costs and selling prices between UK and non-UK supplies adds another layer of working that the ledger doesn't natively handle.

HMRC published Revenue and Customs Brief 5 (2024) clarifying that TOMS applies on a B2B wholesale basis at the operator's option — they can choose whether to apply the margin scheme to wholesale supplies or treat them under standard VAT rules. The choice has knock-on effects for how the books are kept.

How Xero handles TOMS in practice (spoiler: it doesn't)

The standard practitioner approach to TOMS in Xero, documented by ICAEW and TOMS specialists, looks roughly like this:

1. Set up custom tax rates: T3 (or similar) for margin scheme supplies, separate codes for in-house and out-of-scope supplies, a different code for supplies outside TOMS but within the same business
2. Record sales using the appropriate tax codes — but only as gross amounts, since the margin VAT calculation can't be done at point of sale
3. At the end of each VAT period, run a transactions-by-tax-rate report
4. In a spreadsheet, calculate provisional output VAT using a percentage based on prior year's actual (or projected, for new businesses)
5. Post a manual journal to recognise the provisional output VAT in Box 1 of the return
6. Submit the return through Xero's standard MTD interface
7. At year-end, recalculate the actual margin for the full financial year
8. Compare to the provisional figures and post an adjustment journal in the next VAT period

Each step works individually. The cumulative effect is a workflow held together by spreadsheets and discipline.

From Rebecca Bishop's ICAEW article on TOMS in Xero, on the most fundamental problem:

"I need to record both the booking date and the departure date in Xero, but there is only one date field?"

"Now this is probably the trickiest problem and there is no one answer. My first recommendation would be to have a separate CRM system to keep track of bookings, either a standalone software or one that integrates with Xero."

In other words: the recommended workflow involves a separate system entirely, because the ledger can't track the two dates that TOMS calculations actually require.

The booking date vs departure date problem

TOMS accounts for VAT on the date of departure, not the date of booking. In an active tour operator business, these can be six to eighteen months apart. A booking taken in March for a departure in October sits in the books as a sale in March (when the cash arrives) but doesn't generate output VAT until October.

Xero (and QBO, and Sage, and FreeAgent) all treat the transaction date as the single date that matters. There's no native concept of "this sale was made today but VAT becomes due in October". The standard workarounds are:

• Track bookings outside the ledger in a CRM or booking system, generate a monthly summary by departure date, post a journal to Xero reflecting the departures
• Park sales on a deferred income account when booked, release them to revenue on departure — works but requires careful balance sheet management
• Use prepayment/deposit handling in Xero to track unearned revenue, then trigger the margin VAT calculation on departure — clunky

None of these are wrong. All of them require additional process discipline and create reconciliation work.

Provisional output VAT during the year

TOMS requires provisional output VAT calculations during the year, based on either prior-year actual margin percentages or projected percentages for new businesses. The provisional figure is applied as a flat percentage to total margin scheme departures during the period.

Worked example: total departures for the quarter are £200,000, provisional margin is 30%, output VAT is calculated as £200,000 × 30% × 1/6 = £10,000. (The 1/6 is the VAT fraction at the standard rate of 20%.)

This calculation happens entirely outside Xero. The result is posted as a manual journal to Box 1 of the VAT return. The ledger has no way to validate that the calculation is correct, or that the percentage being used reflects the latest information.

The year-end calculation

At financial year-end, the operator recalculates the actual margin for the full year. Total departures × actual margin percentage × 1/6 = actual output VAT due. The difference between this figure and the provisional output VAT posted during the year is the annual adjustment.

This produces the same audit trail problem as partial exemption's annual adjustment. The year-end calculation rests on the spreadsheet workings from each quarter, plus the year-end reconciliation. Any transaction movement during the year — and tour operator books move a lot, with cancellations, amendments, late add-ons, currency adjustments, supplier renegotiations — invalidates the working papers.

Where the workarounds break

In real tour operator practice, the workflow breaks at predictable points:

1. Cancellations and refunds. A booking taken in March for an October departure gets cancelled in August. The deferred income reverses, but the spreadsheet that supported the Q2 provisional calculation still includes the original booking. By the time the cancellation flows through, the spreadsheet is wrong.
2. Currency-denominated supplier costs. A holiday is sold in GBP but bought in EUR. The cost of sale (and therefore the margin) changes when the EUR invoice is settled at a different rate than the GBP sale. The margin recalculates after the fact, but the spreadsheet has already been used for the return.
3. Late-arriving supplier invoices. Supplier invoices for autumn departures often arrive in December or January. They affect the margin calculation for departures that have already been counted in the quarterly provisional figures. The annual adjustment captures this — but only if the practitioner is disciplined about when supplier costs are dated.
4. In-house vs bought-in supplies. TOMS only applies to bought-in margin scheme supplies. Anything provided in-house (own coaches, own hotels, own tour leaders) is taxed under standard VAT rules. Operators with a mix of in-house and bought-in supplies have to maintain two parallel calculations, with allocation rules between them.
5. B2B wholesale. Following Brief 5 (2024), operators selling wholesale to other tour operators can choose to apply TOMS or not. The choice has consequences across the year. The accounting treatment differs depending on the choice.

Each of these is manageable in isolation. Together, they explain why TOMS is the area where tour operator practitioners spend the most time defending their workings to HMRC.

What good looks like

The same principles apply as for partial exemption. A connected calculation engine that:

• Tracks booking date and departure date as separate concepts
• Pulls supplier costs against bookings on a per-departure basis
• Applies the provisional margin percentage automatically at quarter-end
• Generates the annual adjustment as a working paper attached to the journal
• Handles cancellations, currency adjustments, and late invoices by recalculating live rather than re-doing the spreadsheet
• Distinguishes UK and non-UK destinations cleanly post-Brexit
• Distinguishes in-house and bought-in supplies cleanly
• Supports the B2B wholesale election

This is hard. It's why the workarounds exist. But it's not impossible, and the tools that handle it are starting to mature.

What this means for your business

If you're a tour operator currently using Xero, QBO, Sage, or FreeAgent for TOMS:

1. Document your provisional percentage. Whatever percentage you're using, write down where it came from, when it was last reviewed, and what evidence supports it. HMRC will ask.
2. Reconcile bookings to departures monthly. Don't wait for quarter-end. The reconciliation gets harder the longer you leave it.
3. Lock VAT periods after submission. Use Xero's lock date feature (or the equivalent in your platform) to prevent transactions from being backdated into a submitted period.
4. Treat the year-end adjustment as a proper working paper, not a single journal. Attach the calculation to the journal, save it somewhere durable, and make sure your handover notes explain how to find it.

If you'd rather not handle TOMS in spreadsheets at all — particularly if you have a mix of UK and non-UK destinations, currency-denominated costs, and seasonal cancellations — there are now connected alternatives that handle the calculation alongside the ledger.