Skip to main content
Clever Ops

Case studyReal job

How we connected Cloudbeds, BriteBiz and Stripe to Xero

We built software that posts an accommodation and events venue's money into Xero.

  • CloudbedsRoom bookings
  • BriteBizEvents
  • StripeEvent card payments
into
  • XeroThe books

Transcript

This is a made-up stay going through software we built for an accommodation and events venue. The deposit, the checkout invoice and the payout are posted into Xero by the system, not keyed in by hand.

This job came in through the form on our website. The venue takes room bookings in Cloudbeds, runs its events in BriteBiz and takes event card payments through Stripe. The books are in Xero. Their trouble was getting that money into Xero in a shape the bookkeeper could use without rebuilding it by hand.

I got back to them the same day, and on the first call I told them I couldn't say what we could build until I'd seen what each system's API would actually give us. So we started with a paid discovery: read-only access to each system, live tests of each API, and a kickoff with the owners and their bookkeeper.

Here's what we found. Room money reached the bank as one bulk payout, with the card fees already taken out. It didn't split rooms from extras, or either of those from deposits for stays that hadn't happened yet. So the bookkeeper was pulling each payout apart by hand in a spreadsheet.

Events had their own version of it. BriteBiz's Xero connector recorded each payment at its full amount. The bank got less, because the card fees came off first. So the two didn't match without someone fixing it by hand.

Here's how it works now. Each payment channel has its own clearing account in Xero. Guest money goes in at the full amount. When a payout lands, the system moves the net to the bank and posts the fees, so each payout should net back to zero in that account.

Deposits are recorded as they come in and held against the booking. At checkout, the system raises one invoice for the stay and applies the deposit. On the event side, BriteBiz's own connector still does the invoicing, and we pick the fees up from Stripe.

Anything the system can't prove, it holds instead of guessing. Each Sunday evening the bookkeeper gets an email listing the open items, each with a reference, an amount and the next step, and no guest names. A person still matches the bank feed in Xero and finishes event invoices in BriteBiz.

Now the detail. Cloudbeds' Accounting API gives each reservation's posted transactions, with a service date and a transaction code. That's enough to tell a deposit from a room charge. When we built this, the card fees weren't in that data, so payouts and fees come from Cloudbeds' reports, through its Data Insights API.

For events, Stripe had what we needed. It breaks each charge's fee into its own fee, BriteBiz's fee and the GST on the fee, and a payout can be traced back to its charges. That let us settle events at the account level, without matching each booking to an invoice.

Xero's Custom Connection lets our system post receipts, invoices and transfers without anyone logging in. Xero's API doesn't reconcile bank statement lines, and Xero says so in its docs. So we post the transfer to the bank, and the match to the bank feed happens in Xero.

Two rules hold it together. A payout only posts when each payment in it ties to a receipt or refund we've already posted. And each write to Xero carries a key in our ledger, so a job that runs twice finds the first write instead of making another.

A big part of the job was agreeing how each kind of money should post before anything touched their books. The client signed that off line by line. Then it ran alongside the bookkeeper, emailing what it would have posted. We switched it on after the bookkeeper asked us to.

It's been live since October, posting guest receipts, checkout invoices, refunds, fees and payout transfers into Xero, and the Sunday list still goes out. The event side is still bedding in. We didn't measure the bookkeeping hours beforehand, so there's no before and after to show you.

If you're running Cloudbeds, BriteBiz or Stripe and the money isn't landing in Xero the way your bookkeeper needs, get in touch.

Guest payments, card fees and payouts run through one clearing account per payment channel, and each stay gets one invoice at checkout. BriteBiz still raises the event invoices. Anything the system can't tie back to its source is held and listed for the bookkeeper each Sunday.

How and why they came

The enquiry came through the form on our website. The venue takes room bookings in Cloudbeds, runs events in BriteBiz and takes event card payments through Stripe. The books are in Xero, and the money wasn't reaching Xero in a form the bookkeeper could use without rebuilding it by hand.

On our first call I said what we could build depended on what each system's API would give us. So we started with a paid discovery.

The paid discovery

  • Read-only access to each system
  • Live API tests
  • A kickoff with the owners and their bookkeeper
  • A written design for how the money should flow

The problem

Rooms

Cloudbeds

Room money reached the bank as one bulk payout, net of card fees, with no split between rooms, extras and deposits for stays still to come. Nothing connected the room bookings to Xero, so the bookkeeper split each payout by hand in a spreadsheet.

Events

BriteBizStripe

Events had a different gap. BriteBiz's Xero integration recorded each payment at its full amount, but two card fees came off before the money reached the bank. So the Xero entries and the bank deposits didn't match without manual work.

What we built

  1. 1
    Xero

    Clearing accounts

    One in Xero for each payment channel. The bookkeeper created the accounts and we mapped to them.

  2. 2
    CloudbedsXero

    Rooms

    Each guest payment from Cloudbeds posts into the Cloudbeds clearing account at its full amount, and deposits are held against their booking. At checkout the system raises one invoice for the stay and applies the deposit. Refunds post too.

  3. 3
    CloudbedsXero

    Payouts

    The system moves the net amount from clearing to the bank with a transfer and posts the fees, so each payout should net back to zero. A control report on the Cloudbeds clearing account is stored each day.

  4. 4
    BriteBizStripeXero

    Events

    BriteBiz's connector keeps raising the invoices and recording prepayments. The system picks the card fees up from Stripe and posts them through a Stripe clearing account.

The same flow in Xero's Demo Company

  • The deposit, received into the Cloudbeds clearing account.

    Xero Demo Company. Sample data.

  • One invoice for the stay, with the deposit applied.

    Xero Demo Company. Sample data.

  • The clearing account after the payout, back to zero.

    Xero Demo Company. Sample data.

  • The same stay run twice. The second run posts nothing new.

    Replay against Xero's Demo Company. Sample data.

What a person still does

The bookkeeper works through the Sunday list and matches bank lines in Xero. After an event, someone creates the final invoice in BriteBiz, and its connector sends it to Xero.

The technical detail

What each system allowed

Cloudbeds

  • The Accounting API returns posted transactions, searchable by reservation, each with a service date and an internal transaction code that identifies its type.12
  • That was enough to tell a deposit from a room charge.
  • Cloudbeds can consume deposits automatically at check-in or checkout, or leave that to be done by hand.3
  • Here it's set to manual, so the middleware applies each deposit to the checkout invoice in Xero.
  • Cloudbeds Payments bundles a day or more of transactions into one payout and takes the processing fees out first.4
  • When we built this, the card fees weren't in the accounting transactions, so payout and fee detail comes from Cloudbeds' reports through the Data Insights API.5

BriteBiz

  • For bookings without an invoice, its Xero integration records payments as prepayments. When the invoice is created in BriteBiz and sent to Xero, the prepayments are applied to it.1
  • We left that in place.

Stripe

  • Here, event card payments came through BritePay and settled in Stripe.
  • Stripe's balance transaction breaks each fee into parts, including Stripe's fee, an application fee earned by a connected platform, and tax.1
  • On this job that's Stripe's fee, BriteBiz's fee and the GST on the fee.
  • For automatic payouts, Stripe lists the transactions each payout includes.2
  • So events reconcile at the account level, without joining each booking to its Xero invoice.

Xero

  • A Custom Connection uses the client credentials grant to reach one Xero organisation, for back-end, machine-to-machine integrations.1
  • Through the Accounting API the system creates receive and spend money transactions, sales invoices and bank transfers.234
  • Xero doesn't support reconciling bank statement lines through the Accounting API.5
  • So the middleware posts the transfer to the bank, and the match to the bank feed is made in Xero.

Vendor links checked 15 November 2026.

Design decisions

  • No payout without proof

    A payout posts only when each payment in it ties to a receipt or refund already posted. Until then it's held.

  • One invoice per stay

    We'd planned to post night by night. The bookkeepers asked for one invoice per stay at checkout, so that's how it posts.

  • Checking repeat writes

    Each write to Xero has a key and a hash of the request in a posting ledger, so a job that runs again finds the earlier write.

The hard parts

  • Agreeing the treatment first

    We set out how each kind of money would post as an online sign-off sheet. The bookkeepers reviewed it, we worked through it on calls, and the client signed it before anything went live.

  • Running in parallel

    Before go-live the system read live data, wrote nothing to Xero and emailed the bookkeeper what it would have posted. We switched it on after the bookkeeper asked us to.

  • Switching over

    The bookkeeper had already recorded deposits taken before the switch-over. We kept those entries, set a start date, and loaded the earlier deposits as a reviewed list so each one is applied once.

How exceptions reach a person

Each Sunday at 6 pm Sydney time an email lists the open items. Each has fixed wording for its kind, a reference, an amount and a next step, and no guest names. The bookkeeper's copy has the items that are theirs to record. Our copy adds the items we investigate first and the system's own checks. An item stays on the list until it's resolved.

The Sunday list, rendered from sample data.

Where it stands

Live since

October 2026

Posting into Xero

  • Guest receipts
  • Checkout invoices
  • Refunds
  • Payout transfers
  • Fee entries
  • The Sunday list goes to the bookkeeper and to us.
  • The accommodation payouts so far have posted with the check passed.
  • In progressThe event side is still bedding in.

We didn't measure bookkeeping time before it went in, so there's no before and after figure on this page.

Questions

Does Cloudbeds give enough detail to split a payout in Xero?

On this job, from two sources: the Accounting API for each reservation's transactions, and Cloudbeds' reports through the Data Insights API for payouts and fees.

We already use BriteBiz's Xero integration. Does it have to go?

Not on this job. BriteBiz kept raising the event invoices. We added the fee side from Stripe through a clearing account.

Will the payouts match the bank feed on their own?

Not through the API. Xero's documentation says bank statement lines can't be reconciled through the Accounting API, so the match is made inside Xero.

What happens when something doesn't line up?

It's held and goes on the Sunday list with a reference, an amount and a next step.

Who decides how things are coded?

Your bookkeeper or accountant has the final say. On this job the bookkeeper set up the accounts and reviewed how each kind of money would post, and the client signed it off before go-live. We don't give accounting advice.

Got Cloudbeds, BriteBiz or Stripe going into Xero?

Book Free Assessment

Product names and logos belong to their owners and are shown to identify the systems connected.