Error 107: Balance Is Busy

Error 107: Balance Is Busy

This occurs when the system believes the table is being held open by a clerk.

The first step is to press the table number button which will list any open tables.  It will list the tables and where the system believes the table is held open it will show the clerk number that has it open and the ECR that it is open on.  At this point, you should ask that clerk to logon on the till listed and open the table.

If this still fails the next step is to perform a reset of the balance busy status.  On your manager screen, you will find a button that says 'Reset Balance Busy Status'.  Log on to your master till and press this button.

This will allow you to open the tables and deal with them

    • Related Articles

    • Error 7502: Balance Server Error

      If you are seeing a '7502 balance server error' on your terminals. First point of call here is to do some checks; Confirm the till terminal which acts as the balance server is running (one of the tills will be set as the balance server which the ...

    • Using Balance Plan to create table plans and room layouts

      Creating a Table Plan using Bal Plan The Balance Planner is configured and maintained via the balance server of a unit running GPOS. On your GPOS screen if you click on Bal Plan  This will take you to the Table planning screen e.g. Balance Plan. If ...

    • Error Opening Data source

      If you are noticing the following error message; (Screenshot 1.1) When first switching on your till terminal throwing up the error message; 'Error opening data source!' The first thing to check to confirm the 'SQL Server (Fidelity)' is running which ...

    • Adjusting and Recharging Customer Balances

      This article applies to Instant CRM version 2.5 and higher - screenshots are taken from Instant CRM version 2.7. Click Customers to open the Customer record list - by default all Customer records are displayed. Adjusting Balances Single Customer ...

    • Device Configuration Error when Cashing Off

      Check the payment type for the Cashless flag. If it is set, GPoS will try and cash off the transaction against a cashless device first which will cause the error.