Daily Reconciliation for OPERA Cloud PMS and Oracle Payments

Use this workflow to verify that card revenue posted in OPERA Cloud PMS matches the amounts processed, settled, and paid out in Oracle Payments. Finance and front-office teams typically complete the process in about ten minutes per Business Day.

This guide covers:

• One-time setup
• Daily pre-check
• Eight-step reconciliation process
• Daily checklist
• Troubleshooting

Download the latest reconciliation guide: Daily Reconciliation Guide (PDF)

Before You Begin

One-time setup

Complete these steps when you first go live with Oracle Payments and return only if the OPERA Night Audit schedule changes permanently.

1. In Oracle Payments Cloud Service Portal, open Settings and select Business Day. For the full procedure, see Define a Business Day for the Organization.
2. Set the Business Day close time to match the OPERA Night Audit time so that daily totals stay aligned across systems.
3. Before saving, verify that:
   • Duration is 24 hours.
   • Time zone matches the property location.
   • Fulfillment method is Fulfilled to group transactions by the date and time they are posted in OPERA.
4. Save the configuration. Oracle Payments applies the schedule automatically each day.

Daily pre-check

Before starting reconciliation, confirm whether Night Audit ran at the scheduled time.

• If Night Audit ran on schedule, proceed with the daily steps.
• If Night Audit ran earlier or later, adjust the Business Day close time in Oracle Payments after the Business Day ends. You can update past Business Days up to 90 days old, one day at a time, and it may take up to 12 hours for data to reflect the change. See Adjust a Business Day for guidance.

Important: The Business Day in Oracle Payments must always reflect the actual Night Audit time for that date. Make any adjustment before bank payouts arrive and before reconciliation begins.

Daily Workflow

Work through the reconciliation tasks in order. Each task opens in its own topic with detailed instructions.

1. Generate the OPERA Credit Card Summary
   Run the finjrnlbytrans report and capture the Grand Total from the Credit column.
2. Open the Oracle Payments Accounting Report
   Locate the Business Day row and review Net Sales, Net Proceeds, Paid Out, Variance, and payout status.
3. Match Net Revenue to Net Sales
   Confirm that the OPERA Grand Total equals Oracle Payments Net Sales.
4. Match Expected Payout to Actual Payout
   Confirm that Net Proceeds equals Total Paid Out and note the variance.
5. Read Any Variance
   Determine whether the variance is within the normal settlement window or requires investigation.
6. Drill into Outstanding Transactions
   Identify partially paid or unpaid transactions and capture their payment references.
7. Assess Aging and Identify Follow-up Needs
   Use the Aging column to decide whether to monitor or escalate to support.
8. Review Deposits for the Business Day
   Reconcile bank deposits, verify payout amounts, and record payout references.

Result

When the workflow is complete, the OPERA Grand Total matches Oracle Payments Net Sales, Total Paid Out matches Net Proceeds, and any outstanding transactions are documented for follow-up.

Daily Checklist

Use this checklist before closing reconciliation for the day.

Before you start

• Confirm that OPERA Night Audit completed successfully.
• Confirm that Night Audit ran at the scheduled time, or that the Business Day was adjusted to match the actual time.

Step 1 - OPERA report

• Run finjrnlbytrans for the Business Day with all relevant card transaction codes and chronological sorting.
• Record the OPERA Grand Total.

Steps 2-4 - Accounting Report

• Open the Accounting Report and locate the Business Day row.
• Confirm that Net Sales equals the OPERA Grand Total.
• Confirm that Total Paid Out equals Net Proceeds, or document the variance and status.

Steps 5-8 - Variance investigation (only if variance exists)

• Note the variance amount from the Accounting Report.
• Identify transactions with Partially Paid or Not Paid status in the drill-down view.
• Check the Aging column and flag any transaction that is eight or more days outstanding.
• Review the Deposits tab to confirm what was sent to the bank and what remains pending.

Troubleshooting

Symptom	Likely cause	Action
Net Sales does not equal the OPERA Grand Total.	Business Day alignment mismatch or a transaction exists in one system but not the other.	Verify the Business Day schedule, then search the Transaction Summary drill-down by amount or by the last four card digits.
Variance exists and the status is Partially Paid.	A refund, chargeback, or settlement delay is affecting one or more transactions.	Use the drill-down to review Partially Paid rows and monitor the Aging column.
A transaction shows an Aging value of eight or more days.	Settlement may be stalled because of a chargeback or another processing issue.	Capture the Payment Reference and contact Oracle Payments Support.
Status shows Not Paid for a recent Business Day.	Settlement has not yet been initiated.	No immediate action is needed; check again the following day.
Totals keep mismatching across consecutive days.	Night Audit time changed without a matching update to the Oracle Payments Business Day schedule.	Update the Business Day close time to reflect the current Night Audit schedule.

Parent topic: Reconciliation