Switching your accounting integration to ledger data means you change the data source from operational order items to accounting ledger entries in Mews Operations. You do this as a general manager or finance team member to ensure accurate financial reporting and easier reconciliation. You prepare for this change before your scheduled switch date and complete it during the transition period in your accounting workflows.

 

Why this change is happening?

Mews has rebuilt its ledger reporting on GAAP/IFRS-compliant accounting principles, including double-entry accounting, in-built balance reconciliation, and immutable data. This means what you see in your Mews ledgers now accurately reflects accounting reality.

 

As part of this, Mews is gradually sunsetting the previous reporting based on Order items (operational data). Switching your integration to the new ledger data source ensures that what the system sends to your accounting system matches exactly what you see in Mews ledgers. This gives you a single, reliable source of truth and cleaner reconciliation.

 

If you are using Omniboost, we communicate the date when your integration switches automatically.

 

This article helps you prepare, understand key differences, and reconcile your data after the switch.

 

In this article, you can learn about:

• Pre-requisites

• Understanding the 4 key differences

• How the switchover works when using Omniboost

• Post-switch reconciliation checklist

 

Pre-requisites

Prepare your property settings and reporting to reduce discrepancies. This integration switch applies to properties using accrual accounting flows.

1. Adjust your settings

2. Run both reporting sets in parallel

3. Update your integration if you use Omniboost

Adjust your settings

Adjusting your settings reduces corrections made to past operational data, which can cause discrepancies between old and new reporting.

• Define your business day to match your property operations

• Shorten your editable history window for both accounting and operations to the minimum possible to support daily operations

Learn more in our help article How to configure your business day in Mews Operations to include late charges in reports and ledgers. This guidance applies to both the business day and editable history window settings above.

Run both reporting sets in parallel

Running both reporting sets in parallel helps you become familiar with the differences between old and new reporting, which makes it easier to reconcile any discrepancies after the switch.

• Run the Trial Balance and Ledger Activity Report

• Run the Accounting Ledger report

• Compare totals for a few days to identify differences

Learn more in our help article How to reconcile accounting reports with ledger reporting in Mews Operations.

Note: This step helps you identify and resolve discrepancies before the switch.

If you use Omniboost

Omniboost contacts you directly before your migration date with instructions to access or create your Base platform profile. Your Base profile allows you to review and update your ledger mapping codes, view your integration logs, and rerun data independently.

If you already have a Base platform profile

Log in at app.omniboost.io/login, go to Integration Settings, and update the ledger account codes for the new ledgers before your migration date.

If you do not yet have a Base profile

You receive an invitation from Omniboost to create your account ahead of the migration. Follow the instructions in that email to set up your profile and configure your ledger mapping.

If you do not receive an invitation, contact [email protected] using the following format:

• Subject: Base access needed for Mews Ledger migration
• Include:
  • Property name
  • User name
  • User email address

 

Understanding the 4 key differences

Ledger entries follow accounting principles, so they behave differently from order items. Most of these differences come from data changes made within the editable history window but after the end of business day. You can reduce these differences by adjusting your settings as above and limiting late changes in daily operations.

1. Late check-in after business day end

• Order items post revenue on the scheduled check-in date

• Ledger entries post revenue when the guest actually checks in

For example, a reservation with a scheduled check-in date of one day posts revenue on that day in order items, but posts later in the ledger if the guest checks in later.

 

2. Changes within the editable history window

• Order items show only the latest value

• Ledger entries keep the original value and add a correction

For example, if you change a price, the ledger shows both the original and corrected entries.

3. Cancellations within the editable history window

• Order items remove revenue

• Ledger entries keep the original entry and add a reversal

For example, a cancelled stay shows no revenue in order items but shows a posting and reversal in the ledger.

4. Products linked to a future reservation

• Order items post revenue on the consumption date

• Ledger entries post revenue when the reservation checks in

For example, a product consumed today but linked to a future stay posts later in the ledger.

 

How the switchover works when using Omniboost

During the switch, both data sources temporarily overlap due to the editable history window.

1. Before the switch date

2. During the editable history window period

3. At the end of the editable history window

4. After the transition completes

Before the switch date

• Your accounting system receives order item data as usual, with editable history window delay

During the editable history window period, from the switch day to the end of the editable history window

Note: Do not change your editable history window or business day configuration during this period. Changes to these settings affect how data flows and can create reconciliation discrepancies.

 

Your system records ledger entries for this period, but does not send them to accounting yet. The system accumulates these entries and sends them after the editable history window ends as a backfill.

 

Order item data from dates before the switch day continues to flow due to the editable history window delay.

 

Note: This behavior ensures that all data from before and during the editable history window is included and reported correctly once the period ends.

At the end of the editable history window

• You receive the final batch of order item data

• You receive a backfill of ledger entries for the period between switch day and editable history window period.

Note: This is the key moment to validate and reconcile your data.

After the transition completes

• Your accounting system receives only ledger entries

 

Post-switch reconciliation checklist

After the switch, review your data for duplicated revenue entries. Duplicated revenue can occur because the system records revenue before the switch through order items, and again after the switch through ledger entries. This happens in two main cases:

• Late check-in after end of day

• Product linked to a future reservation

After the editable history window closes

Once the editable history window has closed, run an immediate one-off check:

1. Open the Ledger activity report and filter by accounted date from the switch date onwards.

2. Add the Consumption date column to the report, then filter by consumption date earlier than the switch date.

3. Review the results. These entries are ledger entries created from edits to past transactions within the editable history window — they appear as duplicated revenue.

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

Ledger activity report default view:

Note: By default the report opens on accounting date equal to the last closed business date.

 

Adding consumption date column:

 

Selecting consumption to be before switch date:

Ongoing checks after the switch

For products linked to future reservations, duplicated entries can appear later when the reservation checks in. Repeat the same check in subsequent periods, such as the following month, using the same consumption date filter.

Note: This ongoing check helps you identify revenue that is recorded both before and after the switch, so you can keep your accounting data accurate.