
Connecting Booking, POS and Accounting: An Integration Guide for Vancouver Island Tourism and Hospitality Operators
Pick one source of truth per record: booking owns reservations, POS owns sales, accounting owns the books. Use native connectors first and APIs or automation second. Map revenue centres, PST and MRDT, tips and refunds to your chart of accounts, then test charge-to-room, voids and offline queuing before peak season.
Turning on a connector is the easy part. The hard part is deciding which system owns what, getting BC's taxes right, and keeping the setup working when you add a menu, an outlet or a rate. This guide is for the owner-run inn, the café with rooms upstairs, and the tour operator with a gift shop, not the hotel chain.
Why this matters on the Island
Tourism is a big part of the Island economy. Destination BC's Vancouver Island regional profile counts 2,730 tourism businesses and $4.1 billion in visitor spending in the region in 2024, about 18% of BC's total. Accommodation (29%) and food and beverage (28%) made up the largest shares of that spending, which is exactly where booking, POS and accounting meet.
What disconnection costs you
When the three systems don't talk, the costs show up as work and errors rather than a line on an invoice:
- Someone re-keys daily sales or room revenue into the books.
- The night audit doesn't match because a room charge, a void or a refund landed in one system and not another.
- Tax gets coded wrong, and you find out at filing time.
- Month-end turns into a hunt. We wrote about that in month-end cannot go down, and about how the spreadsheet in the middle quietly becomes the system.
Step 1: Decide which system owns each record
Before connecting anything, write down which system is the source of truth for each kind of record:
- Reservations and guests: your booking engine or PMS.
- Item-level sales, tips and payments at the counter: your POS.
- The general ledger, tax liabilities and reporting: your accounting package.
Data should flow out from its owner, not back and forth. Two systems that can both edit the same record are how you get sync loops and duplicates.
Step 2: Choose the connection type
There are three common options, each with trade-offs.
Native connector
Built by one of the vendors. It's usually the cheapest and fastest to turn on. The catch is you get the mapping they designed, which may not match how you split revenue or handle deposits.
Automation platform
A general-purpose tool that moves data between apps on triggers. It's flexible and quick to set up, but logic tends to spread across many small automations, and it's easy to lose track of who owns them.
Custom API layer
A small piece of software that sits between your systems. It's the most work up front, but it handles your exceptions on purpose and puts the rules in one place. It makes sense when the connectors can't model how you actually operate.
Start with native connectors. Move up only when they genuinely can't do the job.
Step 3: Map the money
This is where most setups go wrong. For each flow into the books, decide where it lands:
- Revenue centres: rooms, food, beverage, retail, tours. Keep them separate if you report on them separately.
- Payment types: card, cash, gift cards, direct billing, deposits.
- Tips: usually a liability that gets paid out, not revenue.
- Refunds, voids and cancellations: they need to reverse cleanly, not just disappear.
- Deposits: money taken before the stay isn't earned until the stay happens.
PST and MRDT
In BC, short-term accommodation carries the 8% PST, and in participating areas, the Municipal and Regional District Tax (MRDT) of up to 3% applies on top, according to the BC government's PST accommodation guidance. The province's small business guide notes that MRDT has its own tax return, so it needs its own account, not a lump with PST.
Under the Designated Accommodation Area Tax Regulation, the City of Victoria, the City of Nanaimo and the City of Campbell River are each at 3%. Victoria's and Campbell River's current rates are set to expire on January 1 and March 1, 2027, so check whether they have been renewed before you rely on them.
For Tofino, Ucluelet and anywhere else, confirm the rate for your property on the official BC MRDT map or with your accountant before you set up the mapping.
Step 4: Test like it's August
Test before peak season, not during it. At minimum:
- Charge-to-room from every outlet: café, bar, shop, tours.
- Cancellations, voids and partial refunds: they should reverse in every system.
- Line-level reconciliation: a day of POS sales should match what lands in the books, by revenue centre and tax.
- Network drops: pull the connection and see what happens. Does the POS queue transactions and send them later, or lose them? Connectivity on parts of the west coast can be patchy, so it's worth knowing before a busy Saturday finds out for you.
Step 5: Keep it working after go-live
Integrations don't stay finished. Mappings break when you add a menu item, open a second outlet, launch a new rate or change a tax setting. Two habits help:
- Re-check mappings whenever something changes, not just at month-end.
- Name one owner for sync errors. If an error email goes to a shared inbox nobody reads, it's not being handled.
Whether that owner is on staff or a partner, someone has to have the job.
Frequently asked questions
Do I need custom integration if my systems have a native connector?
Often not. Use the connector, check its mapping against how you actually report, and test it. Consider custom work only when it can't handle your revenue split, deposits or multi-outlet setup.
What about MRDT?
MRDT applies on top of PST to short-term accommodation in participating areas and is filed on its own return. Rates vary by area, so check the official map and keep it in its own account.
Who should own the integration?
One named person or partner who watches errors and re-checks mappings when you change menus, outlets or rates. Ownership matters more than the tool.
Can this run on a seasonal budget?
Yes. Do the design and testing in the shoulder season, go live before peak, and keep post-launch work to scheduled check-ins rather than emergencies.
Running three systems as three islands?
Send us your stack and a recent night-audit headache, and we'll map where the data should flow before next season. If you're still deciding custom vs off-the-shelf software, start with what off-the-shelf can't see. Get in touch.
