Duve now supports improved handling of pre-authorizations in Opera Cloud (OHIP).

With this update, pre-authorized amounts for incidentals are no longer posted as financial transactions in Opera Cloud folios. Instead, they are added as reservation comments/notes, helping hotel teams clearly distinguish between:

• Actual collected payments
• Temporary authorization holds

This improves folio accuracy and reduces operational confusion during check-in and check-out processes.

What Changed

Previously, when a pre-authorization was created through Duve, Opera Cloud displayed the amount as an actual payment in the guest folio.

As a result:

• Folio balances appeared higher than expected
• Hotel staff could not easily differentiate between collected payments and temporary holds
• Teams often needed to manually compare Opera records with their payment provider data

With this enhancement:

• Pre-authorizations are no longer posted as payments in Opera Cloud
• Folio balances are not impacted by authorization holds
• Pre-authorizations appear only as reservation comments/notes in Opera Cloud

Actual payments collected through Duve continue to behave as before and are still posted to the folio as financial transactions.

Supported Flows

This update applies to Online Check-in payment flows using Opera Cloud (OHIP).

Supported Scenarios

Immediate Payment + Incidentals Pre-authorization

When:

• The stay payment is collected immediately
• An incidentals deposit is authorized separately

Duve will:

• Post the stay payment to the Opera folio as a transaction
• Add the incidentals authorization as a reservation comment/note only

Incidentals Charges After Check-out

If additional charges are collected after the stay:

• Charges processed through Duve are synced to Opera as transactions
• Charges processed directly in the PMS are also reflected in Duve

If no incidentals are charged:

• The authorization hold is released according to the hotel's payment provider flow

How Pre-authorizations Appear in Opera Cloud

Hotel staff can identify pre-authorizations through reservation comments/notes.

These entries:

• Are informational only
• Do not affect folio balances
• Are not considered payments in Opera Cloud

This allows operations teams to verify guest coverage for incidentals without impacting financial reporting in the PMS.

Important Notes

• This functionality applies only to Opera Cloud (OHIP)
• Opera On-Prem behavior is unchanged
• Multiple pre-authorizations per reservation are supported
• Existing payment and refund flows remain unchanged

FAQ

Will pre-authorizations appear in the guest folio?

No. Pre-authorizations are no longer displayed as financial transactions in the Opera Cloud folio.

How are pre-authorizations displayed in Opera Cloud?

They are added as reservation comments/notes for operational visibility only.

Do actual guest payments still appear in the folio?

Yes. Collected payments continue to be posted to Opera Cloud as financial transactions.

Does this change affect refund flows?

No. Existing payment and refund behaviors remain unchanged.

Is this supported for Opera On-Prem?

No. This enhancement applies only to Opera Cloud (OHIP).