August 14, 2026
I grew up running charter boats in St. Maarten — deckhand, then first mate, then captain in my family's company — and at some point I ran the same search you probably just ran: accounting software for tour operators. What comes back is depressing. The top result is a Capterra directory page titled "Best Tour Operator Software — 2016 Reviews." Under it sit dead links, an old DMOZ listing, and forum threads from 2010. Nobody has actually written the answer for a small operator who takes cards on the dock, sells across a couple of currencies, and has to remit tourism tax to a government that expects it on time.
So here's the answer. I built Junglebee, which now runs more than $4 million in bookings a year for operators across the Caribbean, and I've watched this exact mess up close. There are three problems generic accounting software was never built for: reconciling the payouts you get from booking platforms, handling more than one currency, and staying tax-compliant across the places you actually sell. Let's take them one at a time.
QuickBooks, Xero, and Wave are all built on the same quiet assumption: you send a customer an invoice, the customer pays it, and a deposit lands in your bank that matches the invoice. Clean. One in, one out.
That is not how we get paid. Our money arrives in lumps — from Viator, from a card processor, from cash handed over on the dock — often in different currencies, with fees and taxes already skimmed off before it reaches us. The software isn't broken. The assumption underneath it just doesn't match a tour business. If you want the wider view of every tool that touches your money, I wrote separately about what "back office" actually means for a tour operator. This piece is about the three parts that hurt the most.
Reconciliation just means checking that the money you think you earned matches the money that actually landed in the bank. For most businesses that's boring and quick. For us it's where the real accounting work lives — and where the errors hide.
When a platform pays you, it rarely pays you per booking. One deposit can bundle a dozen bookings together, deduct different fees on each, and handle the tax differently inside the same lump sum. According to Hostfully, which builds tools for exactly this problem, that bundling is the whole issue: the deposit is a net number, and the detail that produced it is buried underneath.
So when you look at your bank feed, you don't see "twelve tours, minus commission, minus tax." You see one figure. If that figure is $40 short of what you expected, good luck finding out why after the fact.
Here's the trap I watched operators fall into for years. They'd leave reconciliation until the quarter ended, or worse, until tax time. By then the small discrepancies — a fee that changed, a refund you forgot, a currency conversion that moved — have piled on top of each other, and there's no way to trace which payout caused which gap.
It gets worse: as Hostfully notes, some platforms can reverse a payout months after the fact when a guest disputes a charge. If your books closed in March and the reversal hits in June, you're reopening old accounts to figure out what happened. Reconcile little and often, and each payout is still fresh enough to check. Reconcile once a year, and you're doing archaeology.
A real example makes this concrete. Viator settles supplier payouts on a monthly cycle — it pays within about 21 business days after the end of the travel month. A tour a guest takes in May is typically paid out by late June. There's a faster weekly PayPal option if you'd rather not wait, but the standard rhythm is monthly and delayed.
And before any of it reaches you, Viator takes a flat 20% supplier commission off the top. (Don't confuse that with its unrelated 8% affiliate/referral rate — different thing entirely.) So the deposit you're reconciling in late June is already a month old, already net of a 20% cut, and already bundled across every May booking. If you want the full breakdown of that cut, I've covered what Viator's commission actually costs you elsewhere. For accounting purposes, the point is simpler: the number in your bank is not the number your guests paid, and you have to be able to bridge the two.
If you sell to guests from three countries, you're a multi-currency business whether you meant to be one or not. Currency reconciliation is treated as one of the core categories of payment reconciliation for travel platforms, alongside matching transactions and vendors — because currency swings, timing differences between the sale and the settlement, and different financial rules country to country all put dents in your revenue numbers, as the reconciliation specialists at Blue Copa lay out.
Here's what the three tools most operators actually consider will and won't do about it.
QuickBooks Online does multi-currency well, but not on the cheapest plan. According to Intuit's own documentation, the entry-level Simple Start plan doesn't include it — you have to be on Essentials or higher. As of 2026 that's roughly $75/month for three users on Essentials, versus about $38/month for Simple Start.
Two things to know before you flip the switch. First, QuickBooks pulls exchange rates automatically from a third-party financial data provider, refreshing every few hours, and you can override the rate manually on any single transaction. Second — and this catches people — once you turn multi-currency on for a company file, you cannot turn it off. Decide before you enable it, not after.
Xero is stricter about this than QuickBooks. Multi-currency lives only on its top-tier Established plan in the US. If you're on Early or Growing, you can't transact in a foreign currency at all — you have to upgrade to do it. And as of March 2026 that Established plan ran about $90/month, against $25 for Early and $55 for Growing.
So with Xero the question isn't "which add-on do I need," it's "am I willing to jump to the top plan." For an operator taking euros or Eastern Caribbean dollars, that jump isn't optional.
A lot of very small operators default to Wave because it's free, and for a single-currency shop that's a fair call. But Wave has no true multi-currency support. It operates in one business currency per company, and it can't produce consolidated multi-currency reports or automated foreign-exchange revaluation — that's the plain comparison, and it's confirmed against Xero in Plutio's tool breakdown.
If every sale and every payout is in your home currency, Wave is genuinely fine. The moment a guest pays in one currency and you settle in another, you're doing the FX math by hand in a spreadsheet — which brings me to the cost nobody puts on the books.
Here's the money leak I wish someone had shown me earlier. The real cost of moving money across currencies isn't just the wire fee you can see. It's the bank margin baked quietly into the exchange rate, plus the timing of when the conversion happens. Float Financial estimates those unaddressed FX costs can quietly eat 1-2% of revenue for small businesses transacting internationally — and that they're usually buried in the books as generic "bank fees" instead of tracked as their own line.
On a business doing a few hundred thousand a year, 1-2% is real money you never decided to spend. You can't manage what you can't see. Give it its own line in your chart of accounts and watch it.
This is the part mainland software ignores completely, because it was never written for our region. Tourism tax isn't one rule — it's a different rule on every island. Here's how it actually works in a few of the places we serve, and why it matters to how you tag and remit.
Sint Maarten is home for me, so I'll start here. The Dutch side levies a 5% room tax (the logeergastenbelasting) on non-resident guests of hotels and guesthouses. On top of that sits a 5% turnover tax — the BBO, belasting op bedrijfsomzetten — on the delivery of goods and virtually all services rendered within its territory, whether the business doing the rendering is resident or not.
That second one is the catch for a tour or charter operator. "Virtually all services rendered" includes the tour you just sold. So local sales carry BBO, and your books need to tag it as tax collected, not revenue kept.
The Bahamas runs a standard VAT rate of 10% — cut from 12% on January 1, 2022, after being raised from 7.5% to 12% back in 2018. For tour and excursion operators, VAT has been part of the price charged to passengers since VAT first arrived in January 2015. You've had to build it into the ticket for a decade.
Worth noting for perspective: cruise-line private islands only became VAT-liable in March 2024, as The Tribune reported. Small operators were carrying this compliance load nine years before the big cruise brands were. If you sell in the Bahamas, VAT isn't a surprise line — it's baked into what the guest pays, and your accounting has to separate it back out.
Jamaica charges a reduced General Consumption Tax of roughly 10% to hotels and tour operators licensed as approved tourism undertakings, versus the 15% standard GCT rate. That's a real break — if you're properly licensed.
Put this one on your watch list, though. As of early 2026 the Jamaican government has proposed raising the tourism GCT rate from 10% to the full 15% by April 2027, phased in over two years, according to the Jamaica Gleaner. The Jamaica Hotel and Tourist Association is actively fighting it, partly because many tour contracts are locked in years ahead and a mid-contract tax hike eats straight into a margin that was already priced. Whatever lands, your rate could change — so don't hard-code 10% and forget it.
Bonaire went the other direction and simplified. It scrapped its old per-night room tax and car-rental tax and replaced them with a flat Visitor Entry Tax: USD 75 per non-resident visitor aged 13 and up, USD 10 for children under 13, paid once per visit and valid for a month.
That's easier to reason about than a nightly tax, and it's the direction a few Caribbean destinations are drifting — one simple fee. But simpler for the traveler doesn't mean invisible for you. It's still a charge your booking and accounting stack has to track and reconcile against what actually landed in the bank.
Four countries, four different rules — but one principle ties them together. Tag the tax at the moment of sale, per jurisdiction, before the money nets out into a payout.
Because once you wait for the deposit, the tax is already tangled into a single net number, often in a foreign currency, and pulling it back apart is guesswork. This is the whole reason I keep arguing why local payout settlement keeps Caribbean operators tax compliant: when your sale is recorded and settled in the country it happened in, the tax stays attached to it instead of getting lost on the way through a mainland bank.
If any of your card processing or marketplace payouts run through US systems, you'll meet the Form 1099-K. It confuses a lot of operators, and 2025 made it more confusing, so let's be precise.
Under the One Big Beautiful Bill Act, signed July 4, 2025, the 1099-K reporting threshold for third-party settlement organizations — payment apps and marketplaces — was reinstated to more than $20,000 in gross payments AND more than 200 transactions per year. That reverses the much lower $600 threshold that had been phasing in.
One critical point the IRS makes plainly: this threshold only governs when a form gets issued, not whether the underlying income is taxable. You owe tax on your earnings whether or not a 1099-K shows up in the mail. The form is paperwork; the tax obligation is separate and always there.
Here's where operators genuinely get tripped up. Payments processed through a credit, debit, or other payment card have no minimum threshold at all for 1099-K purposes. A form is required for any card-processed amount — even a single cent. That's a completely separate rule from the $20,000 / 200-transaction marketplace threshold.
Why does this matter to us specifically? Because operators mix the two streams in one bank account. Your card-processor payouts (Stripe, JB Pay, whatever you use) fall under the no-minimum card rule, while your OTA marketplace payouts fall under the $20,000/200 rule — and if they all pour into the same account undifferentiated, you can't tell which form covers what at tax time. Keeping those payout streams cleanly separated is half the reason I care so much about how credit-card processing and payment gateways for Caribbean tour operators are set up in the first place.
Enough theory. Here's the routine I'd run if I were back on the operator side of the desk. It's three habits, and none of them need fancy software.
Before money lands, know where it came from: OTA marketplace, card processor, or cash and local sales. Give each its own category in your books. This is the single habit that makes everything downstream easier — the 1099-K sorting, the tax separation, the FX tracking. When a $2,000 deposit arrives, you already know whether it's a Viator settlement or a card-processor batch, and you're not reverse-engineering it three months later.
Open your books once a week and match that week's payouts against your bookings. Weekly, the numbers are still fresh enough that a $40 gap is traceable. Quarterly, the gaps have compounded into a mess, and remember those payouts a platform can reverse months later — you want to catch a reversal in the week it happens, not rediscover it at year-end. Fifteen minutes a week beats a lost weekend every quarter.
That 1-2% of revenue leaking into FX costs, and every dollar of tourism tax you collect on behalf of a government — give each its own line, separate from the catch-all "bank fees" bucket. Tax you've collected isn't yours; it's a liability you're holding until you remit it, and it should never sit blended into revenue. FX loss isn't a fixed cost of doing business; it's a number you can shrink once you can finally see it.
Strip away the feature lists and it comes down to three questions:
One last, non-salesy point, because it's the whole reason I built what I built: the less your money has to travel, the less there is to reconcile. When a booking and payment setup pays out to your local bank in your local currency — which is exactly why we made JB Pay settle on-island — the deposit you're matching is already in the right currency and the right country. The FX guesswork shrinks, and the tax stays attached to the sale where it belongs. No accounting tool can fix a payout that arrives foreign, netted, and a month late; the fix starts upstream, at how you get paid.
Do I need multi-currency accounting if I only sell in one currency?
No. If every sale and every payout is in your home currency, a single-currency tool like Wave is genuinely enough. The moment a guest pays in euros and you settle in dollars — or an OTA pays you in a different currency than you sell in — you need it, and that means QuickBooks Essentials or higher, or Xero's Established plan.
Can QuickBooks or Xero auto-match OTA payouts to bookings?
Not out of the box. They import the bank deposit as one lump sum. Matching that lump back to the individual bookings, fees, and taxes inside it is still manual work unless you add a connector or line it up in a spreadsheet first. That matching is the core reconciliation job — no mainstream accounting tool does it for you automatically.
What's the simplest way to track tourism tax across multiple countries?
Tag it at the point of sale, per jurisdiction, before the payout nets it out. A booking system that sells and settles locally makes this far easier than trying to reverse-engineer a mixed, foreign-currency deposit weeks after the fact. And keep the tax you collect in its own liability line, never blended into revenue.
Is Wave good enough for a small tour operator?
If you sell in one currency and keep your OTA and card-processor payouts organized, Wave's free tier can absolutely do the job. If you sell across borders, its single-currency limit becomes a real wall — no consolidated multi-currency reporting, no automated FX revaluation. That's the point where QuickBooks or Xero starts earning its monthly fee.
