External payment type for closing historical open balances

Hi,

We have a complex setup involving several booking systems that do not integrate seamlessly with one another. Since the implementation of Mews less than a year ago, we have been working through historical issues and discrepancies that arose during and after the go-live phase.

One recurring challenge is that some bookings are marked as paid in external systems, while the corresponding balances remain open in the guest ledger in Mews. As a result, we need a way to close these historical outstanding balances without creating additional accounting entries.

I have reviewed all available external payment types in our setup, but it appears that each of them generates an accounting posting when applied.

Is it possible to create or configure an external payment type that simply closes the balance on a booking without generating any accounting entries? Our objective is to clean up legacy discrepancies rather than record new financial transactions.

Any guidance would be greatly appreciated.

Hi Daira,

same issue here, not on several system but on our internal accounting..

Our city ledger shown 141.000 EUR on open balance but there is no option to fix that… so we just ignore it. Same as on the old PMS.

Johannes Rott wrote:

Hi Daira,

same issue here, not on several system but on our internal accounting..

Our city ledger shown 141.000 EUR on open balance but there is no option to fix that… so we just ignore it. Same as on the old PMS.

Hi Johannes,

Thanks for your reply.

I’m curious how you’ve been able to manage this in practice. Doesn’t leaving these balances unresolved create challenges over time?

For example, are you still able to reconcile your ledger account balances against the open items in Mews? How do you ensure that payment reminders are accurate as more historical items accumulate? And when reviewing outstanding receivables, are you able to clearly identify who actually owes you money and how much?

These are some of the concerns we’re facing, which is why I’m hoping to find a way to clean up the historical balances rather than simply leaving them on the ledger.

​@daira we do track that on our external accounting system, but i would love to see it the other way round… but our accounting is a bit old fashioned but no chance.

We are planing to use a reconcillation tool to avoid all the manuel work which we are facing by now.

For outstinding amounts we do receive a pdf document weekly to take care of. Payment reminders are manually done with that list so quite annoiying…

Johannes Rott wrote:

​@daira we do track that on our external accounting system, but i would love to see it the other way round… but our accounting is a bit old fashioned but no chance.

We are planing to use a reconcillation tool to avoid all the manuel work which we are facing by now.

For outstinding amounts we do receive a pdf document weekly to take care of. Payment reminders are manually done with that list so quite annoiying…

Thanks for sharing your experience.

What I’m hearing from you is very similar to what we’re seeing on our side. Instead of reducing manual work and improving efficiency, the current setup seems to create additional administrative tasks, workarounds, and frustration, while making it harder to maintain a clear overview and control of outstanding balances. With the technology available today, I would expect these processes to be far more automated, reliable, and transparent.

thats so true… but it is a mixture of internal procedures and limitation on MEWS.

Hi ​@daira :grinning_face:

Thanks for your question.

In standard Mews behavior, external payment types are part of the accounting configuration and are intended to be mapped to accounting categories. Because of this, applying an external payment will normally create an accounting impact.

For situations like historical discrepancies or legacy balances, there isn’t a standard payment type that can simply close the guest ledger balance without any accounting entry being created.

A common approach is to create a dedicated external payment method specifically for legacy cleanup and map it to a separate accounting category agreed upon with your finance team (for example, historical receivables, legacy deposits, bad debt, or another reconciliation account). This allows you to clear outstanding balances in Mews while maintaining a clear audit trail for accounting and reconciliation purposes.

In practice, many properties:

  • Create a dedicated payment method for historical corrections only.

  • Map it to a separate accounting category used for cleanup activities.

  • Restrict its use to one-off legacy adjustments rather than day-to-day operations.

This keeps the process controlled, traceable, and auditable, while helping resolve historical balances that no longer reflect the reality of the external systems.

Given the accounting implications, I’d recommend aligning the setup with your accountant or finance team before proceeding.

Hope this helps!

Hi Daira,

First, the hard truth: there is no payment type in Mews that closes a balance with zero accounting impact, and you don’t actually want one. A true zero-impact close would break double entry and your books would never reconcile. What you want isn’t “no entry,” it’s the correct entry. Adrianne’s dedicated cleanup payment type is right for one of the cases below, but not all of them, so before you build it, sort your open items into three buckets. We cleared a few hundred of these after our own go-live, and the method matters more than the tool.

The rule: the correct fix depends on where the revenue is actually recognized.

Bucket A. Cash was collected in the other system, and the Mews charge is your real revenue.
The balance is open only because the payment is missing in Mews, not the charge. Post a payment, but through a dedicated external payment type mapped to a balance sheet clearing/suspense account, not a revenue account. This is exactly what Adrianne described. It records cash that genuinely came in (just outside Mews) and parks the offset in a clearing account your accountant reconciles against the external system. You aren’t inventing revenue, you’re recording a real receipt.

Bucket B. The revenue is recognized in the other system, and the Mews charge is a duplicate of it.
Do not post a payment here. If you do, you leave a phantom charge on your Mews books and your revenue is overstated by that amount. The correct fix is to rebate the original charge on the guest profile. The rebate removes the charge and the balance together, and reverses revenue that was never really yours in Mews. This is the part missing from the thread, and it’s the one most people get wrong by trying to “pay off” everything.

Bucket C. The money is genuinely owed and won’t be collected.
That’s a write off, not a cleanup. Rebate it, or use a bad debt payment type mapped to a bad debt expense account, so it hits the right line and doesn’t sit forever as a fake receivable.

How to sort them fast, instead of one by one:
Export your open guest ledger items, then export the “paid” list from each external system, and match them on name, dates and amount. Anything that matches a paid record is Bucket A or B, depending on where you book the revenue. Anything with no match is Bucket C or a genuine open item to chase. This also fixes the other three worries you raised: once everything is in a bucket, your receivables view is clean again, reminders only go to real debtors, and you can actually say who owes what. We matched ours in a spreadsheet against the OTA and external exports to catch the ones showing as debts that were already settled.

One caveat on rebates (Buckets B and C): the rebate lands in the period you post it, at the original VAT rate. If that revenue was already declared in a closed VAT period, post the rebate in thecurrent open period and flag it to your accountant so you don’t reopen a filed period.

Net: build the cleanup payment type Adrianne suggested for Bucket A, use rebates for B and C, and bucket everything first by matching against your external exports. That gives you a clean ledger and a full audit trail, which is the part Mews support will want to see anyway.

Erick
The Haus Group

Erick Adorno wrote:

Hi Daira,

First, the hard truth: there is no payment type in Mews that closes a balance with zero accounting impact, and you don’t actually want one. A true zero-impact close would break double entry and your books would never reconcile. What you want isn’t “no entry,” it’s the correct entry. Adrianne’s dedicated cleanup payment type is right for one of the cases below, but not all of them, so before you build it, sort your open items into three buckets. We cleared a few hundred of these after our own go-live, and the method matters more than the tool.

The rule: the correct fix depends on where the revenue is actually recognized.

Bucket A. Cash was collected in the other system, and the Mews charge is your real revenue.
The balance is open only because the payment is missing in Mews, not the charge. Post a payment, but through a dedicated external payment type mapped to a balance sheet clearing/suspense account, not a revenue account. This is exactly what Adrianne described. It records cash that genuinely came in (just outside Mews) and parks the offset in a clearing account your accountant reconciles against the external system. You aren’t inventing revenue, you’re recording a real receipt.

Bucket B. The revenue is recognized in the other system, and the Mews charge is a duplicate of it.
Do not post a payment here. If you do, you leave a phantom charge on your Mews books and your revenue is overstated by that amount. The correct fix is to rebate the original charge on the guest profile. The rebate removes the charge and the balance together, and reverses revenue that was never really yours in Mews. This is the part missing from the thread, and it’s the one most people get wrong by trying to “pay off” everything.

Bucket C. The money is genuinely owed and won’t be collected.
That’s a write off, not a cleanup. Rebate it, or use a bad debt payment type mapped to a bad debt expense account, so it hits the right line and doesn’t sit forever as a fake receivable.

How to sort them fast, instead of one by one:
Export your open guest ledger items, then export the “paid” list from each external system, and match them on name, dates and amount. Anything that matches a paid record is Bucket A or B, depending on where you book the revenue. Anything with no match is Bucket C or a genuine open item to chase. This also fixes the other three worries you raised: once everything is in a bucket, your receivables view is clean again, reminders only go to real debtors, and you can actually say who owes what. We matched ours in a spreadsheet against the OTA and external exports to catch the ones showing as debts that were already settled.

One caveat on rebates (Buckets B and C): the rebate lands in the period you post it, at the original VAT rate. If that revenue was already declared in a closed VAT period, post the rebate in thecurrent open period and flag it to your accountant so you don’t reopen a filed period.

Net: build the cleanup payment type Adrianne suggested for Bucket A, use rebates for B and C, and bucket everything first by matching against your external exports. That gives you a clean ledger and a full audit trail, which is the part Mews support will want to see anyway.

Erick
The Haus Group

Very well explained! :backhand_index_pointing_up::smiling_face_with_sunglasses:

Erick Adorno wrote:

Hi Daira,

First, the hard truth: there is no payment type in Mews that closes a balance with zero accounting impact, and you don’t actually want one. A true zero-impact close would break double entry and your books would never reconcile. What you want isn’t “no entry,” it’s the correct entry. Adrianne’s dedicated cleanup payment type is right for one of the cases below, but not all of them, so before you build it, sort your open items into three buckets. We cleared a few hundred of these after our own go-live, and the method matters more than the tool.

The rule: the correct fix depends on where the revenue is actually recognized.

Bucket A. Cash was collected in the other system, and the Mews charge is your real revenue.
The balance is open only because the payment is missing in Mews, not the charge. Post a payment, but through a dedicated external payment type mapped to a balance sheet clearing/suspense account, not a revenue account. This is exactly what Adrianne described. It records cash that genuinely came in (just outside Mews) and parks the offset in a clearing account your accountant reconciles against the external system. You aren’t inventing revenue, you’re recording a real receipt.

Bucket B. The revenue is recognized in the other system, and the Mews charge is a duplicate of it.
Do not post a payment here. If you do, you leave a phantom charge on your Mews books and your revenue is overstated by that amount. The correct fix is to rebate the original charge on the guest profile. The rebate removes the charge and the balance together, and reverses revenue that was never really yours in Mews. This is the part missing from the thread, and it’s the one most people get wrong by trying to “pay off” everything.

Bucket C. The money is genuinely owed and won’t be collected.
That’s a write off, not a cleanup. Rebate it, or use a bad debt payment type mapped to a bad debt expense account, so it hits the right line and doesn’t sit forever as a fake receivable.

How to sort them fast, instead of one by one:
Export your open guest ledger items, then export the “paid” list from each external system, and match them on name, dates and amount. Anything that matches a paid record is Bucket A or B, depending on where you book the revenue. Anything with no match is Bucket C or a genuine open item to chase. This also fixes the other three worries you raised: once everything is in a bucket, your receivables view is clean again, reminders only go to real debtors, and you can actually say who owes what. We matched ours in a spreadsheet against the OTA and external exports to catch the ones showing as debts that were already settled.

One caveat on rebates (Buckets B and C): the rebate lands in the period you post it, at the original VAT rate. If that revenue was already declared in a closed VAT period, post the rebate in thecurrent open period and flag it to your accountant so you don’t reopen a filed period.

Net: build the cleanup payment type Adrianne suggested for Bucket A, use rebates for B and C, and bucket everything first by matching against your external exports. That gives you a clean ledger and a full audit trail, which is the part Mews support will want to see anyway.

Erick
The Haus Group

Thank you, Erick! I agree with Robin - very well explained :slight_smile: