Skip to main content
Solved

Billing Automation: Why Can the Closing of OTA Bills Not Be Automated?

  • March 14, 2026
  • 5 replies
  • 69 views

DavidFoxx
Forum|alt.badge.img

Yes, billing automation having just gotten smarter was a windfall for our operation. As a small property with few Staff members, all of us hold many roles on a daily basis. We have no accounting or finance department, no IT department, to name just a few. When billing automation rolled out, automatically sorting charges into bills by stay dates and whether they are owned by an OTA or a Guest erased many of the accidental billing issues we had to correct when a Guest was incorrectly charged for a future stay or for an OTA-paid stay, billing the Guest’s credit card instead of the virtual credit card.

I would never want to go back to where we began. I would, however, like to understand why there is not an automated method to close OTA bills like there is for closing Guest-owned bills when they’re at a $0.00. I do not put this task on my Front Desk Staff member because s/he may often be redeployed to assist Housekeeping when we have high Guest turnover during the weekends. Instead, I do this from my office given we have no back office or personnel to do stuff like this in a back office. One bill at a time, I close each OTA bill when the reservation status has reached Due to Checkout or Past. 

Another OTA-related issue no one seems to be able to solve due to the way in which tax brackets are applied and rounded is the $0.01-0.04 variances, credits or debits on at least half of our OTA reservations that must be adjusted off to achieve a $0.00 balance on the bill. We have three tax brackets applied, 6% Florida State sales tax, 1% Pinellas County sales tax, and 6% Pinellas County tourism development tax, a collective 13%. However if any one or more of these brackets result in a tax amount that is rounded up or down to the nearest dollar while one or more of the other tax brackets being applied to the same room rate is rounded up or down to the nearest dollar, this results in either a credit (refund) or debit (payment) that must be applied to get the bill back to a $0.00 balance.

Now that Booking.com has changed its policy for the charging of virtual credit cards [VCC], I can at least look at most future reservations and attempt to get a headstart on these adjustments when looking down the Billing screen for Booking.com to see the occasional pennies to be adjusted. For all other OTA reservations and those from Booking.com that have not yet reached the no cancellation period, I have to wait until the day of arrival when the automated and scheduled payment is posted against the VCC before I can even see where adjustments are needed. The only other means would be to look to see for what amount the VCC has been pre-approved when looking on the Payments screen, then looking at the room/tax amount that will be due at the time of the Guest’s arrival, and with a bit of math, determining if an adjustment is needed, but that adds even more minutes to these manual tasks.

Doing this is entirely manual and requires the posting of an external payment using “Exchange rounding difference” as the type and the manually entering the associated reservation number and Guest name for which the adjustment is being applied. There’s no means to link the external payment (which may be a refund or a payment) to a room reservation. On average each month, I am posting close to 100 adjustments, a number that can go up or down as our room rates go up and down. Daily, about 30-45 minutes of my day is spent posting adjustments and closing OTA bills. These hours add up by the end of the week, time I could better spend managing our business instead of managing menial bookkeeping tasks like these. At the end of each fiscal week, each fiscal month, and each calendar, month, I have reporting to create for our hotel’s owner and his business partner. Leaving OTA bills open and unadjusted does not seem like the appropriate or generally accepted accounting practice.

Am I the only property to have issues like this and if not, how are other properties managing this? Is it not possible to create a checkout summary screen like the Guest reservation checkout summary screen when clicking the Departures donut on the dashboard so I can check boxes down the left margin for all the OTA reservations that need their bills closed? When I asked about this at the time billing automation rolled out, I was told that the ability to close open bills with a $0.00 was limited to only Guest-owned bills. 

Best answer by tristan.gibausset

Thank you David for such a detailed message.
This is incredibly valuable, and it reflects very real operational challenges.

It’s great to hear how much Billing Automation has already improved your day-to-day by routing charges correctly. What you’re describing next is actually the natural next step of that journey: removing the remaining manual work around closing and finalizing OTA bills.
 

In short, you’ve identified a real gap, and it’s one that Mews is actively working to close. The longer-term goal is straightforward: once the right bill is created for the right payer, the rest of the process should require as little manual effort as possible.

That’s the path we’re on now:

On closing OTA bills automatically

You’re absolutely right, until now, the system has only been able to automatically close guest-owned balanced bills, not OTA or company bills.

That’s exactly why you’re currently going through them one by one.

👉 This is actively being addressed, and developed. A few property are on Beta since a few days.

Mews is rolling out an improved bill closing logic that changes this behavior:

  • At check-out, when the option to close balanced bills is enabled

  • The system will automatically identify all bills linked to the departing reservation

  • And close all balanced bills, including:

    • OTA bills

    • Company bills

    • Companion profile bills

At the same time, it keeps control where it matters by leaving open:

  • Bills with future revenue

  • Bills linked to other stays

  • Paymaster or group bills that need manual review

💡 In practice, this means that once this is active, and your Billing Automation is correctly set up,
your OTA bills at 0.00 will no longer need to be closed manually, one by one.

We’re already seeing strong impact with properties on beta saving meaningful time every day on exactly this task.


On sending bills automatically

You also mentioned the manual effort around sending, and this is another key piece.

Today, even when bills are closed automatically, they are not always sent automatically.

👉 This is also being solved.

A new capability is currently being developed that will allow:

  • Automatic sending of bills that are closed at check-out

  • Directly to the bill owner (guest, OTA, or company)

  • Using your existing email templates

Once enabled at the property level:

  • Bills close automatically

  • And are sent automatically to the right payer

This completes the full flow:
routing → closing → sending, without manual intervention.


On the 0.01–0.04 rounding differences

You are definitely not alone on this. This is a known industry-wide behavior linked to how taxes are calculated and rounded across multiple tax layers.

Today, there are two important points here:

  • These differences come from each tax being calculated and rounded independently

  • Small variances are expected in those scenarios, especially with OTA comparisons

👉 In Mews, there is already a configuration called Tax rounding correction that can automatically adjust these differences directly on the bill. (Settings → Property → Finance → Accounting configuration, if available depending on your profile and if your not in DACH country). You can also adjust Tax precision (number of decimals used for tax) - Changes are not retroactive.

This can potentialy avoids having to:

  • Post manual external payments

  • Or create separate adjustments for each reservation

At this stage, there isn’t a feature that automatically posts “rounding difference” adjustments per OTA reservation, but using tax correction significantly reduces the manual workload.

 

Thank you again for sharing such a detailed breakdown of your workflow and the time impact behind it. It gives important context to the problem and helps make the case for continued improvements.

Stay tuned: more updates are coming, and they’re aimed at making this process much more seamless for teams like yours.


 

5 Replies

MattJones
Forum|alt.badge.img+2
  • March 18, 2026

Will be honest, this is a pain point for many properties. Found one that had nearly 500 open OTA bills but were reporting on closed revenue, so you can imagine how that played out as 500 bills were not closed to report revenue 😨

 

There is no specific ‘workaround’ per se for this unless using a custom API integration - the API does have the route for closing bills so there may be an integration that does this however cannot see it being a standalone thing… so in short there is no actual workaround aside manual right now that I am aware of.

 

Would be worth adding a feature request using the ‘Ideas’ link at the top of the screen?


DavidFoxx
Forum|alt.badge.img
  • Author
  • Navigator
  • March 18, 2026

Thank you, ​@MattJones, for your response. I can imagine the pain of 500 open bills. To pay for an integration to do something that is happening automatically for Guest bills seems counterintuitive within the world of Mews.


tristan.gibausset
Mews Employee
Forum|alt.badge.img

Thank you David for such a detailed message.
This is incredibly valuable, and it reflects very real operational challenges.

It’s great to hear how much Billing Automation has already improved your day-to-day by routing charges correctly. What you’re describing next is actually the natural next step of that journey: removing the remaining manual work around closing and finalizing OTA bills.
 

In short, you’ve identified a real gap, and it’s one that Mews is actively working to close. The longer-term goal is straightforward: once the right bill is created for the right payer, the rest of the process should require as little manual effort as possible.

That’s the path we’re on now:

On closing OTA bills automatically

You’re absolutely right, until now, the system has only been able to automatically close guest-owned balanced bills, not OTA or company bills.

That’s exactly why you’re currently going through them one by one.

👉 This is actively being addressed, and developed. A few property are on Beta since a few days.

Mews is rolling out an improved bill closing logic that changes this behavior:

  • At check-out, when the option to close balanced bills is enabled

  • The system will automatically identify all bills linked to the departing reservation

  • And close all balanced bills, including:

    • OTA bills

    • Company bills

    • Companion profile bills

At the same time, it keeps control where it matters by leaving open:

  • Bills with future revenue

  • Bills linked to other stays

  • Paymaster or group bills that need manual review

💡 In practice, this means that once this is active, and your Billing Automation is correctly set up,
your OTA bills at 0.00 will no longer need to be closed manually, one by one.

We’re already seeing strong impact with properties on beta saving meaningful time every day on exactly this task.


On sending bills automatically

You also mentioned the manual effort around sending, and this is another key piece.

Today, even when bills are closed automatically, they are not always sent automatically.

👉 This is also being solved.

A new capability is currently being developed that will allow:

  • Automatic sending of bills that are closed at check-out

  • Directly to the bill owner (guest, OTA, or company)

  • Using your existing email templates

Once enabled at the property level:

  • Bills close automatically

  • And are sent automatically to the right payer

This completes the full flow:
routing → closing → sending, without manual intervention.


On the 0.01–0.04 rounding differences

You are definitely not alone on this. This is a known industry-wide behavior linked to how taxes are calculated and rounded across multiple tax layers.

Today, there are two important points here:

  • These differences come from each tax being calculated and rounded independently

  • Small variances are expected in those scenarios, especially with OTA comparisons

👉 In Mews, there is already a configuration called Tax rounding correction that can automatically adjust these differences directly on the bill. (Settings → Property → Finance → Accounting configuration, if available depending on your profile and if your not in DACH country). You can also adjust Tax precision (number of decimals used for tax) - Changes are not retroactive.

This can potentialy avoids having to:

  • Post manual external payments

  • Or create separate adjustments for each reservation

At this stage, there isn’t a feature that automatically posts “rounding difference” adjustments per OTA reservation, but using tax correction significantly reduces the manual workload.

 

Thank you again for sharing such a detailed breakdown of your workflow and the time impact behind it. It gives important context to the problem and helps make the case for continued improvements.

Stay tuned: more updates are coming, and they’re aimed at making this process much more seamless for teams like yours.


 


DavidFoxx
Forum|alt.badge.img
  • Author
  • Navigator
  • March 18, 2026

On the 0.01–0.04 rounding differences

You are definitely not alone on this. This is a known industry-wide behavior linked to how taxes are calculated and rounded across multiple tax layers.

Today, there are two important points here:

  • These differences come from each tax being calculated and rounded independently

  • Small variances are expected in those scenarios, especially with OTA comparisons

👉 In Mews, there is already a configuration called Tax rounding correction that can automatically adjust these differences directly on the bill. (Settings → Property → Finance → Accounting configuration, if available depending on your profile and if your not in DACH country). You can also adjust Tax precision (number of decimals used for tax) - Changes are not retroactive.

This can potentialy avoids having to:

  • Post manual external payments

  • Or create separate adjustments for each reservation

At this stage, there isn’t a feature that automatically posts “rounding difference” adjustments per OTA reservation, but using tax correction significantly reduces the manual workload.

Thank you, Tristan. 

I can confirm that being in the US, we are not in the DACH region. I looked at our accounting configuration and have been unable to find the Tax rounding correction you mentioned. As the super admin for our property, I would think that unless there’s another reason why I’m not seeing, it’s not showing as an Option. The knowledge base says it’s available to properties using gross pricing. I don’t believe we are using gross pricing because taxes are added to the net rate in our rate tables. If I’m wrong and I should be seeing this somewhere, please let me know where.

 

According to the Knowledge article, https://help.mews.com/s/article/what-is-the-accounting-configuration?language=en_US#tax-rounding-correction, tax precision is not available to properties in the US. 

 


tristan.gibausset
Mews Employee
Forum|alt.badge.img

Hi David,
I did not checked where your property stands. You’re absolutely right: Tax rounding correction is not currently available for US properties. Sorry for pointing you in the wrong direction earlier.

The reason is that the feature was originally built for simpler tax environments, typically where pricing is gross and a single tax logic applies. The US works differently. Properties often operate with net pricing and multiple stacked taxes, such as state, county, city, and tourism taxes, sometimes with different bases and rounding rules.

Because of that, a simple rounding correction can produce the wrong result in some scenarios. Rather than introduce something that could create accounting or compliance issues, Mews has taken a more cautious approach.