Imbalance Analysis

The Imbalance Analysis utility is available to provide the information required to investigate an out of balance financial report and can be very useful for verification purposes. If an imbalance is found in a report, please contact your local Oracle support office. If the report indicates no imbalances but believe your reports are incorrect, consider regenerating the report. If no imbalance is found, OPERA Cloud displays the message: <Report Name> is in balance..

Running Imbalance Analysis

  1. Enter the following details:
    1. Property: Select a property from the list.

    2. Start Date: Enter the start date to run the imbalance analysis. Date defaults to the business date, but it cannot be equal to or greater than the current business date.

    3. End Date: Enter the end date to run the imbalance (maximum date range to be entered can be 180 days). Date defaults to business date, but it cannot be equal to or greater than the current business date.

      Note:

      You cannot select dates still open when the Income Audit OPERA Control is active
    4. Verification Type: Select from the following:
      1. Guest Ledger with Trial Balance: Run to verify and view the imbalance between the Guest Ledger columns in the Financial_Transactions table and the Trial_Balance table. A grid is displayed informing the user of the transaction, where the difference in figures is originating from, and the dollar amount it is for.

      2. Package Ledger with Trial Balance: Run to verify and view the imbalance between the Package Ledger columns in the Financial_Transactions table and the Trial_Balance table. A grid is displayed informing the user of the transaction, where the difference in figures is originating from, and the dollar amount it is for.

      3. Deposit Ledger with Trial Balance: Run to verify and view the imbalance between the Deposit Ledger column in the Financial_Transactions table and the Trial_Balance table. A grid is displayed informing the user of the transaction, where the difference in figures is originating from, and the dollar amount it is for.

      4. A/R Ledger with Trial Balance: Run to verify and view the imbalance between the A/R Ledger columns in the Financial_Transactions table and the Trial_Balance table. A grid is displayed informing the user of the transaction, where the difference in figures is originating from, and the dollar amount it is for.

      5. Passer By: Run to verify that all the Passer By totals in the Guest_Ledger table are equal. If there is an imbalance, the transaction is displayed along with amount difference.

      6. Cashiers: Run to verify that all of the cashiers transactions are equal. If an imbalance should occur, the transaction is listed along with the difference in the amount.

      7. C/O with Balance: Run to view all the guests that have a "Checked Out" status and folio closed, but still have a balance with the property. Grid displays the name of the guest, Arrival and Departure dates, Reservation Status, and the remaining balance that is still owed.

      8. Invalid Transactions: Run to view all the invalid transactions, if any should develop. A list of the transactions that are invalid is displayed, along with the amount that it is wrong.

      9. Effective Package Ledger: Run to verify the accuracy of packages consumed by guests. A grid displays informing the Reservation and Guest ID, Arrival and Departure dates, Reservation Status, and the dollar amount difference. An Autofix button is available to attempt to fix the imbalance automatically.

      10. Package Ledger with Guest Ledger: Checks that the Guest Ledger's wrapper transaction is equal to the amount posted in the Package Ledger for the room portion amount of the package.

      11. Summary of All: Checks all of the options available in the list, except the AR Health Check, and provides a Send to File button. A file called <property>balance.txt will be created. The file is located in the \runtimes directory in a Thick Client environment and in the \export directory in a Thin Client environment, to ensure that in a Thin Client environment the user will have the ability to download this file to the local PC to send to support.

  2. Click Start.

  3. If an imbalance exists, write down the ledger that is shown as out of balance from running the verification. Next run the imbalance analysis for the verification type for the specific ledger only. This will display the list of dates for which that particular ledger is out of balance and other information regarding the transactions causing the imbalance.

  4. Run the Repopulate Trial Balance action to repopulate the Trial Balance table for a specific date.
    1. Enter the date.

    2. Click Repopulate Trial Balance link and click Start.

    3. Wait for the procedure to complete, click OK to close.

  5. Re-Run the imbalance analysis for the verification type for that particular ledger to see if the trial balance table has resolved the imbalance.
    1. Fix naguestleddetail and deposit_ledger: Fixes the Guest Ledger and Guest Ledger Detail reports for the property, by finding where the data was missing in the Reservation Details table and repopulating the information.

    2. Repopulate missing Bills into Folio Tax: Select this option to find the missing bill information and repopulate it into the Folio_Tax table for a specific date.

    3. Fix Invalid AR Posting: Selecting this option fixes invalid A/R postings/bills in Financial_Transactions table and repopulates the invoice into the AR_Invoice_Header for the property.

    4. Fix DBs For Adjusted Invoices: Selecting this option fixes adjusted invoices in the database.