Mews to Accounting | Understanding Fallback Accounts

In our accounting integrations that connect Mews PMS with your accounting platform, we always ask our clients to provide fallback ledger account codes for both revenue and payment entries.
​
This article explains why fallback ledger accounts are a required part of your integration setup, how they function within the synchronisation process, and what to do when entries appear on these accounts.

It can occur that not all revenues are correctly mapped to an accounting category in MEWS. Such revenues can be recognized by 'None' under the Revenue section in the Accounting report. Please find an example below.

In order to post all revenue entries from the Accounting Report to their corresponding ledger account codes, the Omniboost integration looks up the mapping between ledger account codes and accounting categories within your Mews configuration. However, the "None" revenue entries shown above indicate that these revenues have not been assigned to any accounting category in Mews. Without this assignment, the integration has no way of determining which ledger account code these entries should be posted to.

This is where the fallback ledger account for revenue serves its purpose. When the integration encounters a revenue entry that cannot be matched to a specific ledger account through the standard mapping, it automatically posts the entry to the designated fallback ledger account instead. This ensures that all revenue is still captured in your accounting platform, even when individual entries are not yet properly categorised in your source system.

For this reason, we request that you create a dedicated fallback ledger account for revenue in your chart of accounts (if one does not already exist) and provide us with the corresponding ledger account code during onboarding.

It can occur that not all payments are correctly mapped to an accounting category in Mews. Such payments can be recognised by the label "None" appearing under the Payments section in the Accounting Report. Please find an example below.

In order to post all payment entries from the Accounting Report to their corresponding ledger account codes, the Omniboost integration looks up the mapping between ledger account codes and accounting categories within your Mews configuration. However, the "None" payment entries shown above indicate that these payments have not been assigned to any accounting category in Mews. Without this assignment, the integration has no way of determining which ledger account code these entries should be posted to.

This is where the fallback ledger account for payments serves its purpose. When the integration encounters a payment entry that cannot be matched to a specific ledger account through the standard mapping, it automatically posts the entry to the designated fallback ledger account instead. This ensures that all payments are still captured in your accounting platform, even when individual entries are not yet properly categorised in your source system.

For this reason, we request that you create a dedicated fallback ledger account for payments in your chart of accounts (if one does not already exist) and provide us with the corresponding ledger account code during onboarding.

As an example, if the fallback ledger account code for payments is 5678, then the unmapped payment amount of 164.80 EUR shown above would be posted to ledger account code 5678 in your accounting platform.

Fallback ledger accounts serve as safety nets within your accounting integration. They ensure that all revenue and payment entries are transferred to your accounting platform, even when certain entries have not yet been fully mapped to an accounting category in Mews. In other words, these accounts guarantee a complete data transfer regardless of the mapping status of individual entries.

You will need two fallback ledger accounts in your chart of accounts: one for revenue and one for payments. These accounts only need to exist in your accounting platform. It is not necessary to create them within Mews itself.

If you notice revenue or payment amounts appearing on your fallback ledger accounts, this is an indication that one or more entries in Mews are not yet assigned to an accounting category. In this case, we recommend reviewing and completing the revenue and payment mapping within your Mews environment to ensure entries are posted to their correct designated ledger accounts going forward.