ROLLER to Xero Revenue Recognition
Gift cards, memberships, future-dated bookings and refunds are classified before they reach Xero, so revenue lands when it is earned and outstanding balances sit where they belong as liabilities.
Money taken is not always revenue earned. A venue that sells a gift card in November has taken the cash but owes a visit. A twelve-month membership sold on one day is earned across the next twelve. A booking for March is paid for in January. Post all of it as revenue on the day the money arrives and the accounts overstate the months the selling happened in and understate the ones the guests actually turn up in.
Without this integration, the correction is manual. Someone in finance works back through the ROLLER takings, pulling out the gift-card sales, splitting membership payments across their term, holding future-dated bookings back and remembering to release each one when the visit happens. Balances that were never redeemed accumulate somewhere nobody is watching, and the liability side of the balance sheet is only as accurate as the last time that person had a quiet afternoon.
With the integration running, IntelliPaaS classifies each ROLLER transaction before it reaches Xero. Gift-card sales post as a liability and move to revenue on redemption. Memberships are deferred across the term they cover. Future-dated bookings wait for the visit date. Refunds reverse against the account the original transaction went to, and balances still unredeemed are reported separately rather than quietly counted as income.
Watch the agent run, end to end
Why deploy this use case
A gift-card sale posts to Xero as money owed rather than money earned, and moves to revenue only when the card is redeemed.
A membership payment is deferred across the period it covers instead of landing as a single spike in the month it was sold.
Revenue for a booking taken months ahead is recognised on the visit date, so the month the guests actually come is the month that shows the income.
A refund is posted against the account the original transaction went to, rather than netted off whatever the current period happens to be.
Gift-card value still outstanding is reported separately, so the liability does not sit unnoticed inside general revenue.
Each ROLLER transaction type is mapped once and treated the same way on every run, rather than depending on who is doing the month-end.
More ROLLER automations
Questions teams ask
How does the ROLLER to Xero Revenue Recognition integration work?
The pack is a prebuilt IntelliPaaS workflow between ROLLER and Xero. Every transaction recorded in ROLLER is classified before it is posted - gift-card sales and unredeemed balances as liabilities, memberships and future-dated bookings as deferred revenue, redemptions and completed visits as earned revenue, refunds as reversals - and each posts to the Xero account you have mapped for it.
How is this different from the ROLLER to Xero Invoice Automation pack?
Invoice Automation creates a Xero invoice for each confirmed ROLLER booking, which is the pack you want if the need is billing documents. This one governs when revenue is recognised: it separates gift cards, memberships, future-dated bookings, refunds and unused balances so earned revenue and outstanding liability post to different accounts rather than landing together as takings. Many venues run both.
Does the ROLLER to Xero sync happen in real time?
Transactions are picked up as they happen in ROLLER, so postings reach Xero within moments rather than waiting for an overnight batch. Deferred amounts are a deliberate exception - they are released to revenue when their classification calls for it, on the schedule you set. A run can also be started by hand.
What's included in the ROLLER Xero Revenue Recognition Integration Pack?
The pack covers classification and posting of gift-card sales and redemptions, membership payments deferred across their term, future-dated bookings held until the visit, refund reversals, and separate reporting of balances that remain unredeemed. The mapping of each ROLLER transaction type to its Xero account is included and editable. The full flow is set out on this page.
Do I need a developer to set up the ROLLER Xero integration?
No developer is needed. The trigger, the agent logic and the actions arrive preconfigured, and the setup is connecting your ROLLER and Xero accounts and confirming where each transaction type posts. Everything is adjusted from the IntelliPaaS dashboard, with no infrastructure to provision. Most teams are live the same day.
How much does the ROLLER Xero integration cost?
The ROLLER to Xero Revenue Recognition Integration Pack is priced per month, and the current rate is shown on this page. Full plan details and what each tier includes are on the IntelliPaaS pricing page.
Can I customise how each transaction type is classified?
Yes. Every mapping between a ROLLER transaction type and its Xero account is editable, and you can layer your own conditions, filters and transformations on top inside the Integration Pack. Venues commonly adjust the deferral schedule used for memberships and the rule that releases gift-card balances left unredeemed.