Accounting integration FAQ for onboarding properties

Your accounting integration is getting an upgrade.

 

A more reliable data source, a clearer audit trail, and a setup that matches exactly what you see in Mews.

 

Mews is migrating accounting integrations from the old connection to a new, validated flow based on Mews ledger data. The switch happens automatically on the date confirmed in your migration email. You don’t need to do anything that day, but a few optional preparation steps can make the transition smoother. This document answers the questions we hear most often.

 

In this article, you can learn about:

• What precisely changes

• What doesn't change

• The essentials

• Preparing for the switch

• During and after the switch

• Troubleshooting and support

What precisely changes

• Source of data: Order items → ledger entries (revenue, tax and payment ledger movements, as well as deposit, guest and city ledger movements).

• Granularity: Unchanged. Optional new mapping codes let you split outstanding balances into deposit, guest and city ledger balances, though most integrations currently post everything to a single balance by default.

• Reconciliation: Your postings now tie to the Ledger Activity Report and trial balance in Mews, with outstanding balances split into deposit, guest and city ledger balances.

 

What doesn't change

Your connection, your accounting system and your delivery schedule are unaffected.

The essentials

Why is this change happening? Mews has rebuilt its financial reporting around ledger data: immutable, accounting-compliant entries that accurately reflect your property's financial activity. Your accounting integration via Omniboost is being updated to use Mews ledger reports as its source, instead of the old connection. The result is a more reliable data source, a clearer audit trail, and a setup that is consistent with what you see in Mews.

 

Is this change mandatory? Yes. The old connection is being decommissioned, so all affected properties will be migrated automatically. You will get a direct message from Mews with your switch date and the next steps.

 

Which properties are affected? Every property connecting Mews to accounting software via Omniboost on an accrual (consumed) accounting flow will eventually be affected. The rollout happens in phases, starting with integrations like Xero or QuickBooks, so not all properties move across at the same time. If you have received a migration email, your property is affected. Properties on cash-basis accounting are not affected at this stage.

 

When is the switch happening? Your switch date is confirmed in the migration email Mews sends roughly a month ahead. The migration then goes live automatically on that date, so you do not need to do anything that day.

Preparing for the switch

What do I need to do before the switch? Preparation is optional but recommended, to minimise possible discrepancies. Once you receive your migration email, read the steps in How to prepare to switch your accounting integration to ledger data in Mews Operations. In short:

• Adjust your business day and editable history window settings in Mews Operations to reduce late data corrections.

• Log in to the Omniboost Base platform and update your ledger account mapping codes if you would like more detailed postings in your accounting system.

• Run the old and new reporting sets in parallel for a few days to understand the differences before the switch.

Nothing needs to happen on the day itself: the switch is fully automatic.

 

Which settings may need updating in Omniboost? By default, your existing guest ledger account code is used for all ledger movement postings across deposit, guest and city ledgers. If you would prefer more detailed postings, update the mapping codes in the Omniboost Base platform before your migration date. Omniboost will contact you directly with instructions to access or create your Base profile. If you already have one, log in at app.omniboost.io/login > Integration Settings, and update the ledger account codes.

 

Haven't heard from Omniboost? Email [email protected] with subject “Base access needed for Mews Ledger migration”, and include your property name, user name and user email address.

During and after the switch

Is there any downtime or data loss? No. The migration happens in the background and your accounting system keeps receiving data throughout:

• Up to the switch date: your system receives order item data as usual.

• During the editable history window: ledger entries accumulate in the background, sent as a backfill once the window closes.

• End of the window: you receive the final batch of order item data plus the ledger backfill.

• After the transition: your system receives only ledger entries going forward.

Why does my data look slightly different afterwards? Some differences are expected: ledger entries follow accounting principles and behave differently from order items. The main scenarios:

• Late check-in: order items post on the scheduled date; ledger entries post when the guest actually checks in.

• Changes in the history window: order items show only the latest value; ledger entries keep the original and add a correction.

• Cancellations in the window: order items remove revenue; ledger entries keep the original and add a reversal.

• Products on a future reservation: order items post on consumption; ledger entries post when the reservation checks in.

Shortening your editable history window and aligning your business day settings before the switch reduces these differences.

Troubleshooting and support

I'm seeing duplicated revenue entries. What should I do? Duplicated revenue isn't expected for every reservation: it's an edge case tied to particular scenarios, such as a guest checking in after the business day has already completed, or products consumed against a future stay. It happens because an item was already posted to your accounting system via the old order-item route before the switch, and is then posted again as a ledger entry once it's included in the post-switch backfill.

Once your editable history window closes after the switch, check for it:

1. Open the Ledger Activity Report in Mews and filter by accounted date from your switch date onwards.

2. Add the Consumption date column and filter by consumption date earlier than your switch date.

3. Review the results: these are the duplicated entries.

4. Remove the duplicates from your accounting system. This is a one-off action.

Note: If you have products linked to future reservations, similar duplicates may appear in later months when those reservations check in, so use the same filter to catch them for the first month or two.

 

Will the granularity of the data I receive change? No. Your accounting system keeps receiving data at the same granularity it does today: transaction-level or aggregated, whichever you already use. The only change is that you can now provide additional mapping codes to split outstanding balances into deposit, guest and city ledger, for a more detailed breakdown than before.

 

What happens if I miss the deadline or don't update my settings? Your integration keeps working automatically: you don't need to do anything for the migration to complete. If you don't update your mapping codes beforehand, transactions may be grouped into broader ledger accounts instead of being split across the new ledgers. You can still update the codes with Omniboost later if you'd like more detail.

 

Who do I contact for support? If you have questions about this migration, reach out to the Mews support team through the Support portal or in-app chat. We can advise you directly, or liaise with Omniboost on your behalf if needed.