How do I test a hotel PMS connection to Xero before going live?
Use a small set of controlled transactions to check what reaches Xero, what needs manual handling and whether your accountant can trace every amount.
Before going live, agree the connector’s posting method and mapping with your accountant, then test an invoice, advance payment, balance payment, credit note, refund and repeat transmission. Compare source references, dates, account codes, tax treatment and balances in both systems. Accept the connection only when every test has evidence, failures are visible and someone owns each manual exception. A successful connection message alone is insufficient.
Agree what the connection must transfer
Write a one-page specification before your hotel PMS Xero integration test. Use fictitious guest details in a supplier-approved test setup. Confirm that it cannot email real guests, charge real cards or post into your live accounts.
- Posting method: individual invoices and linked payments, or summary journals with guest balances maintained in the PMS. Specify direction and the system responsible for corrections.
- Mapping: list your actual Xero account codes for accommodation, extras, advance receipts and payment clearing, plus the applicable tax codes and inclusive/exclusive treatment. Have your accountant approve them.
- Timing: agree the export trigger, expected arrival window, invoice and payment dates, accounting period, time zone and historical cut-off.
For invoice posting, inspect each document and outstanding balance. For journal posting, inspect the batch, account totals and balancing entries. Do not expect an individual Xero guest invoice from a summary-journal configuration.
Run this six-scenario test matrix
Record the expected result before running each case. Save the PMS reference, Xero record or batch ID, export time, actual result and reviewer. Mark each case pass, fail or an explicitly accepted manual step.
| Test | Transaction to run | Evidence required to pass |
|---|---|---|
| Invoice | Create accommodation plus a separately coded extra. | Correct customer/reference, GBP amount, net/VAT/gross totals, accounts, tax treatment and posting date; one invoice or the agreed journal contribution. |
| Advance payment | Take £60 for a future stay before the final invoice exists; later complete the invoicing workflow. | The receipt reaches the approved advance-payment route and is applied once. No stranded payment or duplicated revenue/VAT when the final bill is posted. |
| Balance payment | Apply the remaining £180 against a £240 bill after the £60 advance. | Exactly £240 paid overall; correct payment date and bank/clearing account; zero guest balance after allocation. |
| Credit note | Reduce the paid bill by £24 using the agreed correction process, without yet refunding cash. | Traceable correction for the same customer; £24 credit available; correct revenue/VAT adjustment; no invented cash movement. |
| Refund | Return the £24 credit through the approved payment route. | One cash refund and one matching accounting entry; credit settled. Identify any manual Xero step and retain its reference. |
| Duplicate transmission | Ask the supplier to replay the same successful invoice/payment or journal batch, then test recovery from an interrupted export. | No extra invoice, payment or journal; unchanged totals. Show how completed records are recognised before retrying. |
These are acceptance criteria, not a statement that every connector automates every step. An unsupported required workflow needs an agreed workaround or a different configuration.
Check the numbers with one booking
Illustrative example: a VAT-registered hotel issues a £240 accommodation invoice before receiving a £60 advance and £180 balance. Assume standard VAT accounting, all events in one VAT period, a short stay wholly subject to 20% VAT, no fees and no other charges. The invoice is £200 net plus £40 VAT.
| Stage | Document total after credits | Net cash received | Guest position |
|---|---|---|---|
| £240 invoice; £60 received | £240 | £60 | £180 still due |
| £180 balance received | £240 | £240 | Nothing due |
| £24 credit issued | £216 | £240 | £24 to refund |
| £24 refund recorded | £216 | £216 | Nothing due or refundable |
The credit reduces net sales by £20 and VAT by £4. Final totals are £180 net + £36 VAT = £216. A bank payout can occur later; this example checks guest receipts and accounting records, not settlement timing.
Also run the matrix’s advance-before-invoice case across month-end. HMRC’s hotel deposit guidance requires VAT on most advance deposits in the period received. Confirm tax points and revenue timing with your accountant; the export date alone does not determine either.
Test failures before signing off
In the test setup, ask the supplier to demonstrate a missing account mapping, rejected tax code and interrupted connection. Check where the error appears, who receives it and how the affected record is recovered without repeating successful postings.
- Compare record counts and totals by account, tax code and payment method for one complete export cycle.
- Test a correction after export and a transaction dated in a locked period; agree who authorises the remedy.
- Have the accountant approve the mapping and exceptions, the supplier approve recovery, and the manager assign daily checks and the cut-over date.
Delay activation if money is missing, duplicated or unexplained. If launch fails, pause the connector, preserve records and resolve what already posted before restarting; avoid overlapping manual imports.
What to verify with RoomRaccoon
Xero appears in RoomRaccoon’s UK directory of hotel software integrations. Its published Xero connection documentation describes invoice-based and journal-based options. Confirm the method, schedule and package or upgrade requirements for your property.
For invoice-based syncing, that documentation lists linked invoices as a prerequisite for payments, excludes overpayments and negative-payment refunds from export, and requires VAT rates to be configured in Xero. It also limits accommodation revenue mapping to one ledger, with an exception for differing VAT rates. Ask the team to confirm these limits against your test matrix, including credit-note handling and corrections after export.
If you also use integrated hotel payments, demonstrate the payment and accounting workflows together. Collecting or refunding money and posting it into Xero are separate checks.
Bring your own acceptance test. Share your chart of accounts, payment methods and a fictitious £240 booking with a £60 advance and £24 refund. Ask which steps transfer automatically and who completes the rest.
Discuss your Xero integration requirementsQuestions before you go live
Does a successful export prove the figures are correct?
No. It proves a transfer was accepted. Compare accounts, dates, tax amounts and balances with your expected result, including any later correction.
Does Xero itself support refunds?
Yes. Xero’s payment-processing guidance describes credit notes and associated refund payments. A connector’s inability to send a negative payment is a separate limitation.
What if there is no separate test environment?
Agree a supervised validation process with the supplier and accountant before posting anything. Document how test entries will be identified and corrected, and prevent guest communications or real card charges.
Sources and verification
Checked on 10 November 2026. Product scope and configuration can change. Confirm the current connector limits with RoomRaccoon and the accounting treatment with your accountant. Support documentation may require sign-in.












