October 2026 ReadMe

Overview

This document contains a list of upcoming major changes to Oracle Hospitality APIs.

What will Change Details of the Change Target Product and Version Impact Call to Action

What will Change	Details of the Change	Target Product and Version	Impact	Call to Action
The affected APIs will reject charge, payment, or balance amounts that have more decimal places than the property’s configured currency precision. Previously, such amounts could be rounded during posting.	Affected operations: Cashiering: `postBillingCharges`, `postBillingPayment`, `generateFolio`, `postArticlesSale`, `postPasserBySale`, `postCreditBill`, `postSupplementalFolio`, and `postDepositFolio`. Accounts Receivable: `postInvoice`, `postChargesToAR`, and deprecated `postARCharges` (use `postChargesToAR` instead). The validation was temporarily rolled back in OPERA Cloud 26.2.2.3 to give API consumers time to prepare.	OPERA Cloud 26.5	Requests with excessive decimal precision may fail with `OPERAWS-FOF01952`, interrupting posting or billing workflows. This can include requests that reuse calculated amounts returned by a GET API.	Prepare Now: Check each target property’s currency precision using the getHotel operation: `GET {{HostName}}/ent/config/v1/hotels/{{hotelId}}?fetchInstructions=General`. Read `currencyFormatting.decimalPositions` in the response. For example, `"currencyCode": "FJD"` and `"decimalPositions": 3` means amounts for that property must have no more than three decimal places. Update integrations to submit amounts at that precision, keeping charges, taxes, payments, and totals reconciled. Test the affected operations with both valid and excessive-precision amounts. Once the Change is Live: Monitor for `OPERAWS-FOF01952`. Correct and reconcile rejected amounts before retrying.

The affected APIs will reject charge, payment, or balance amounts that have more decimal places than the property’s configured currency precision. Previously, such amounts could be rounded during posting.

Affected operations:

Cashiering: postBillingCharges, postBillingPayment, generateFolio, postArticlesSale, postPasserBySale, postCreditBill, postSupplementalFolio, and postDepositFolio.
Accounts Receivable: postInvoice, postChargesToAR, and deprecated postARCharges (use postChargesToAR instead).

The validation was temporarily rolled back in OPERA Cloud 26.2.2.3 to give API consumers time to prepare.

OPERA Cloud 26.5

Requests with excessive decimal precision may fail with OPERAWS-FOF01952, interrupting posting or billing workflows. This can include requests that reuse calculated amounts returned by a GET API.

Prepare Now:

Check each target property’s currency precision using the getHotel operation: GET {{HostName}}/ent/config/v1/hotels/{{hotelId}}?fetchInstructions=General. Read currencyFormatting.decimalPositions in the response. For example, "currencyCode": "FJD" and "decimalPositions": 3 means amounts for that property must have no more than three decimal places. Update integrations to submit amounts at that precision, keeping charges, taxes, payments, and totals reconciled. Test the affected operations with both valid and excessive-precision amounts.

Once the Change is Live:

Monitor for OPERAWS-FOF01952. Correct and reconcile rejected amounts before retrying.