Skip to main content

How to Configure Tender Bags

Introduction

This document describes how a store can be configured to use Tender Bags for some of its Cash Management functions. Tender Bags are physical bags designed for storing cash collected from a Terminal or from a Safe.

For identification purposes, each of these bags is assigned a Bag ID and a Seal Number. These details will be documented in the relevant Cash Management sessions that are currently Active in the Safes or at the Terminals.

Tender Bags are associated with numerous cash management functions such as:

  • Terminal Float

  • Terminal Pickup

  • Terminal Cashup and Closing Float

  • Terminal Cashup and Empty

  • Terminal Spot Check

  • Terminal Bag Tender

  • Terminal Unbag Tender

  • Safe Bag

  • Safe Float

  • Safe Pickup

  • Safe Cashup

  • Safe Spot Check

  • Safe Banking

  • Safe Unbag Bag

  • Safe Bag Collection

  • Safe Bag Deletion

Additionally, this document will introduce and explain common terminology related to the Tender Bag functions.

Overview

The following configuration entities may need to be modified to enable the Tender Bags to function in a store:

  • User Roles – Ensuring POS, Back Office and Estate Manager users have the appropriate privileges to carry out Cash Management functions.

  • Location – In the Location Maintenance, the method which the Tenders Bags are going to be used will be configured.

  • Cash Management Session Owners – Creating Terminal sessions.

  • Menu – Adding Cash Management functions to the POS and Back Office.

  • Tenders – Enabling Tenders with denominations.

  • Reasons – Configuring Reasons to support the use of Tender Bags.

  • Currency – Configuring denominations.

The following common terms will be used:

Existing Bags – This list compiles the bags that have been generated within the currently open Cash Management session. The composition of this list will differ based on the types of Tender Bags used, aligning with the specific requirements of each Cash Management function.

New Bag – Creating a New Bag while doing a Cash Management function. This will require a Bag Id and a Bag Seal Number.

Loose – Tenders recorded in a session which are not added to a Tender Bag.

Configuration Steps

User Roles

Navigate to User Roles Maintenance using the search or the following path:

Authorisation to run the specific functionality documented here is controlled with privileges maintained in User Roles.

Select the appropriate role to edit, the example used here is SALES_ASSISTANT

Select the appropriate Application Package and configure the required privileges from the table below:

PackageFunction IDDescription
Enactor Cash Managementenactor.safeBagCollection.RunAllows the User to run Safe Tender Bag collection on Back Office.
Enactor Cash Managementenactor.safeBagDeletion.RunAllows the User to delete Bank Deposit Bags and return the money to the Safe.
Enactor Cash Managementenactor.safeBagTenders.RunAllows the Back Office User to run the Safe Bag Tenders.
Enactor Cash Managementenactor.safeCashup.AutoSubmitNewBagsThis will automatically submit the data entered in the New Bag tab in Safe Cashup, without pressing the Bag Tenders button. The Bag Tenders button will be hidden.
Enactor Cash Managementenactor.safeCashup.HideBagSealNumberEnabling this privilege will hide the Seal Number and label and input field in Safe Cashup.
Enactor Cash Managementenactor.safeCashup.HideClearBagValuesButtonEnabling this privilege will hide the Clear Bag button in Safe Cashup.
Enactor Cash Managementenactor.safeCashup.HideExistingBagsTabEnabling this privilege will hide the Existing Bags tab in Safe Cashup.
Enactor Cash Managementenactor.safeUnbagTenders.RunAllows the Back Office User to unbag Safe Tender Bags.
Enactor Cash Managementenactor.tenderBagMaintenance.ListAllows the User to list all entries in the Tender Bag Maintenance application.
Enactor Cash Managementenactor.tenderBagMaintenance.RunAllows the User to run Tender Bag Maintenance.
Enactor Cash Managementenactor.tenderBagMaintenance.ViewAllows the User to view Tender Bag Maintenance.
Enactor Cash Managementenactor.terminalBagTenders.RunAllows the Back Office User to run Terminal Bag Tenders.
Enactor Cash Managementenactor.terminalCashup.HideExistingBagsTabIf the privilege is enabled the user would not be able to load the Existing Bags Tab in Cash Management.
Enactor Cash Managementenactor.terminalCashup.HideNewBagTabIf the privilege is enabled the user would not be able to load the New Bags Tab in Cash Management.
Enactor Cash Managementenactor.terminalSpotCheck.HideBagsTabIf the privilege is enabled the user would be able to hide Bags Tab in Cash Management.
Enactor Cash Managementenactor.terminalUnbagTenders.RunAllows the Back Office User to run Unbag Tenders.
Enactor POSenactor.safeBagTenders.RunAllows the Back Office User to run the Safe Bag Tenders.
Enactor POSenactor.safeUnbagTenders.RunAllows the Back Office User to unbag Safe Tender Bags.
Enactor POSenactor.terminalBagTenders.RunAllows the Back Office User to run Terminal Bag Tenders.
Enactor POSenactor.terminalUnbagTenders.RunAllows the Back Office User to run Unbag Tenders.

Location

Navigate to Location configuration using the Search or the path below:

The guide below shows editing of a Location, but this configuration can equally apply to a group of Locations configured with a Location Template.

The configuration for Tender Bags is located in the Cash Management > General tab.

Cash Management > General Tab:

Set the appropriate value in the field as follows:

ConfigurationDescription
Tender Bags

If set, the user can allocate Cash to be stored in a Tender Bag. The following options are available:

  • Allowed: The operator must use a Tender Bag while performing Cash Management Functions that support their use.

  • Disallowed: The operator is not able to use Tender Bags.

  • Optional: The operator can choose whether to use a Tender Bag while performing Cash Management Functions that support their use.

Cash Management Functions

The following section further describes the Cash Management functions that support the use of Tender Bags and will primarily focus on the Optional configuration, where the operator is given the choice whether to use them or not.

Three different types of Tender Bags can be created:

  • Float Bag – A Float Bags can be created in Safe Bag Maintenance. Please refer below for more details. These Bags are used for adding a float to the POS.

  • Banking Bag – Banking Bags are created by the Banking function when cash is being transferred from a store safe to the bank.

  • Pickup Bag – Pickup Bags created by the Terminal Bag and Pickup Bag function.

Terminal Float

The Terminal Float function is used to add Cash to a POS (usually so the operator has sufficient cash to give change to customers). It records the Cash amount transferred from the Safe to the Terminal. Float Bags can be created using the Cash Management – Bag Tenders function at the back office.

Float functions using Tender Bags will be explained further in the following section.

POS

Terminal Float Tender Screen Functions:

FunctionOutcome
LooseThe Float Tender list is displayed
Existing BagsA list of Existing Bags is displayed
NotesFree text notes field
CompleteComplete Terminal Float
VoidVoid Terminal Float

Note that the Loose button is only displayed when the Location's Tender Bag configuration is set to Optional. If it is configured as Mandatory, this button will not be available.

Terminal Float > Existing Bag

When the User clicks on the Existing Bag button, the available Float Bags are shown.

FunctionOutcome
SelectSelects a Bag from the list.
De-SelectDe-selects a Bag from the list.
Remove From BagThe tender amounts will be retrieved from the bag and added to the Terminal’s cash totals.
BackThis will navigate to the Terminal Float screen.

Terminal Float > Loose

When Loose is clicked the Float Tender list will be displayed. The user can add the required Tender values and complete the Float action.

Store Server

Terminal Float tabs on the Store Server:

FunctionOutcome
LooseThe Float Tender is displayed
Existing BagThe list of Existing Bags is displayed
GeneralNotes can be recorded

Terminal Float > Loose

When the user opens the Float screen in the Store Server and the Location's Tender Bag configuration is set to Optional, then the initial tab displayed will be Loose. In this tab, the user can add Float Tenders that are not contained in a Tender bag. The list of available Tenders depends on each Tender’s configuration.

If the Location's Tender Bag option is set to Mandatory, this tab is not accessible.

Terminal Float > Existing Bag

Selecting the Existing Bags tab shows the available Float Bags.

In the Existing Bag tab, the user selects the appropriate Safe (if more than one is configured against the Terminal’s Location). Any available Tender Bags of type Float are listed.

One or more bags can be selected, and the float value added to the Terminal Session. If the Remove from Bag flag is selected then the tender amounts are retrieved from the Bag and this amount is categorized as Loose tender.

Terminal Float > Notes

Notes can be recorded.

Terminal Pickup

If it becomes necessary to move cash from the POS to the safe during a session (e.g. the cash drawer is over its allowed value), the operator can execute a Pickup function. This action records a transfer from the POS to the safe.

The Pickup functions that make use of Tender Bags are described in the following section.

POS

FunctionOutcome
LooseThe Pickup Tender list is displayed.
Existing BagsThe list of existing Float Bags is displayed.
New BagEnables the creation of a new Tender Bag.
NotesFree text notes field.
VoidVoids the Terminal Pickup.
CompleteCompletes the Terminal Pickup.

The Loose button is only displayed when the Location's Tender Bag configuration is set to Optional. If it is configured as Mandatory, the button will not be available.

Terminal Pickup> Existing Bag

When the User selects Existing Bag, the Float Bags available to the session are listed.

FunctionOutcome
SelectSelects a Bag from the list.
De-SelectDe-selects a Bag from the list.
BackNavigates Back to the Terminal Float screen

From this screen the user can complete a Pickup function for the cash management session.

Terminal Pickup > New Bag

When the user selects New Bag from the Pickup screen, they are directed to add a Bag Number and a Seal Number for identification purposes.

Once the data is captured, the Pickup Tender screen is displayed.

Pickup amounts can be added against any tenders configured for manual Pickup. Selecting Bag Tenders creates a new bag with the declared cash amounts for the Pickup.

Terminal Pickup> Loose

Selecting Loose displays the Pickup Tender list, user will be able to add the required Tender values and complete the Pickup action.

Store Server

Terminal Pickup Tender Screen Functions on the Store Server:

TabOutcome
LooseThe Pickup Tender list is displayed.
Existing BagThe list of Existing Bags is displayed.
New BagEnables the user to create new bags while completing a Pickup.
GeneralFree text notes field.

Terminal Pickup > New Bag

When the user selects the New Bag tab from the Pickup screen, they can add a Bag Number and Seal Number for identification purposes. Subsequently, the user can specify the values for the Pickup Tenders and complete the Pickup Function.

Terminal Pickup> Existing Bags

When the User selects the Existing Bags tab, the applicable Bags available to the session are listed.

Within the Existing Bag tab, the user can choose any existing Bags to transfer from the POS to the Safe. To select a specific bag, the user must mark the Pickup checkbox.

Terminal Pickup > General

Notes and an Uncounted Pickup Reference can be recorded.

Cashup Functions (Safe/Terminal)

When the operator needs to finalize an open session, they can complete the Cashup process and finalize the Terminal or Safe's cash management session.

The Cashup function is available for both Safe and Terminal cash management.

For Safe Cashup, two options are available - Safe Cashup and Safe Cashup and Banking.

For Terminal Cashup, the options available are Cashup and Float, Cashup and Empty and Cashup and Leave.

Depending on the selection of Cashup functions for both the Safe and Terminal, the screens associated with the Tender Bags will vary.

Terminal Cashup and Closing Float

This option allows the operator to perform a count and transfer a portion of the cash to the Safe. The remaining balance stays within the terminal and is considered as the Float for the next session.

POS

Closing Float

On selecting Cashup and Closing Float, the first screen allows the operator to record the Closing Float. Following this, the Cashup is completed.

Cashup

FunctionOutcome
LooseThe Cashup Tender list is displayed.
Existing BagThe list of Existing Bags is displayed.
New BagThe user can create new bags while comleting Cashup
NotesFree text notes field
VoidVoid Event
CompleteComplete Event

If the user clicks on the Void button in the Cashup state, the recorded Closing Float value is not voided. A warning message is displayed:

Terminal Cashup and Closing Float > Existing Bag

When the User selects the Existing Bags function, any available bags are listed. Here the user can select an existing bag to transfer the Cashup amount into.

FunctionOutcome
SelectSelects a Bag from the list.
De-SelectDe-selects a Bag from the list.
Remove From BagThe tender amounts are retrieved from the bag and are categorized as Loose tender.
BackNavigates to the Terminal Cashup screen.

Terminal Cashup > New Bag

On selecting the New Bag button from the Cashup screen, the user is directed to add a Bag number and a Seal Number for identification purposes and the Bag will be created during the Cashup process.

Once the Bag information is entered the user is directed to the Cashup applicable tender list. This list is defined by Tender configuration – any applicable Tenders where Cashup Tender is configured are shown in the list.

Once the Tender is added to the Cashup process, when the user clicks the Bag Tenders button a new bag is created, and the values added to the new bag forms part of the Cashup action.

Terminal Cashup > Loose

When the Location's Tender Bag configuration is set to Optional, the Loose button is available. In this screen, the user can add Cashup Tenders that are not related to a Tender bag and are transferred directly to the safe. The list of available Tenders will be based on the configuration in Tender Maintenance.

If the Location's Tender Bag option is set to Mandatory, this button is not visible.

Store Server

The POS functions described prior are also available on the Store Server. The following section shows the Store Server screens.

Closing Float

Closing Float >Loose

Closing Float > Existing

Closing Float > General

Cashup

Cashup > Loose

Cashup > New Bag

Cashup > Existing Bag

Cashup > General

Terminal Cashup and Empty

The Terminal Cashup and Empty process doesn’t include a float declaration and moves the entire contents of the cash drawer either into a Tender Bag, or into the Safe.

The following section describes the Terminal Cashup and Empty screens and available functions on the POS and Store Server.

POS

Terminal Cashup > Existing Bag

When the user selects Existing Bags, the available Bags are listed. The user can select an existing Bag to move money into and complete the Cashup Function.

FunctionOutcome
SelectSelects a Bag from the list.
De-SelectDe-select a Bag from the list (only visible when a bag is selected).
BackNavigates to the Terminal Cashup screen.

Terminal Cashup > New Bag

On selecting the New Bag button from the Cashup screen, the user is directed to add a Bag number and a Seal Number for identification purposes and the Bag will be created during the Cashup process.

Once these values are recorded, the user can record the Tender values to add to the new bag.

Terminal Cashup > Loose

The Loose option is only displayed when the Location is configured with Tender Bags as Optional. A Loose declaration moves the tenders directly into the safe.

Store Server

The POS functions described prior are also available on the Store Server. The following section shows the Store Server screens.

Cashup > Loose

Cashup > New Bag

Cashup > Existing Bag

Cashup > General

Safe Cashup

The Safe Cashup function allows the user to finalize the Safe session, concluding the cash management session.

The Safe Cashup can completed on the Store Server - the following section describes the Safe Cash management flow.

Store Server

Store Server > Loose

On selecting the Safe Cashup option, if the Location's Tender Bag configuration is set to Optional, then the initial tab displayed is Loose.

Store Server > New Bag

The Tab is used to create a new bag while performing the Safe Cashup function. The user adds the Bag Id and the Seal Number to create the bag.

Store Server > Existing Bag

The Existing ag tab displays the bags which need to be cashed up in the active session. This displays the list of Pickup bags which have been transferred from Terminal to Safe using the Terminal Pickup function, and any Float bags that have been created.

Store Server > General

Any Notes related to the Safe Cashup action can be recorded here.

Terminal Bag Tender

This function allows the operator to create a Bag of type Pickup.

Only new bags are created during this process, and these are accessible for Terminal sessions only. The upcoming section explains how the function operates on both the POS and the Store Server.

POS

FunctionOutcome
OKAllows the user to continue after the Bag ID is entered.
CancelCancels the process.

FunctionOutcome
OKAllows the user to continue after the Seal Number is entered.
CancelCancels the process.

FunctionOutcome
OKSelects the highlighted tender.
NotesAllows the user to enter notes in a free text field.
VoidVoids the process.
CompleteCompletes the process.

Store Server

Terminal Bag > New Bag

Terminal Bag > General

Terminal Unbag Tenders

This function allows the user to unbag any Float and Pickup type bags in the active Terminal Cash Management session. The list displayed is determined by the bag type. An authorised user can perform this function at the POS or the Store Server.

The following section describes the flow on the POS and Store Server.

POS

FunctionOutcome
SelectSelects a Bag from the list.
De-SelectDeselects a Bag from the list.
VoidVoids the process.
CompleteCompletes the process.

Store Server

Unbag > General

Safe Bag

The Safe Bag function allows users to create Banking and Float bags. Once created, these Bags can be selected for banking and terminal float functions.

Store Server

Safe Bag > New Bag

The Bag can be created by adding the Bag Number, Seal Number and Bag Type. The Bag Type selected here can be either a Banking bag or a Float bag.

Safe Bag > General

Safe Unbag

The Safe Unbag function can be used to unbag Pickup bags that have been sent from the Terminal to the Safe. The following section describes the Store Server process for unbagging bags.

Store Server

Safe Unbag > Existing Bag

If the user selects the Unbag Tender option against the Bag Id, then the selected bag is unbagged and the Tenders within it are returned to the safe.

Safe Unbag > General

Safe Bag Collection

In this function the user can select the bags which are sent to the bank. The user can select the applicable bags collected for Banking. An authorized user can do this function in the Store Server. The following section describes the Store Server screens for Safe Bag Collection.

Store Server

When the user selects the Selection flag and selects the Done button, a confirmation popup is displayed. When the user selects the Ok button then the selected bag is marked as collected.

A Tender Bag Collection by Transaction report is generated.

Safe Bag Deletion

The Safe Bag deletion function can be used delete a safe bag. This could be used if an incorrect seal number has been given to a bag or if there is a miscount. The following section describes the Safe Bag Deletion process.

Store Server

When the user selects a bag and selects the Done button, a confirmation popup is displayed to delete the bag.

Banking

The Banking function allows the recording of Tenders which are removed from the Safe and transferred to the Bank. Only Banking type Bags can be banked.

Banking is the final stage in the Safe Cash Management process and concludes the active safe session.

Store Server

Banking > Loose

The Loose option is only displayed when the Location is configured with Tender Bags as Optional. Adding tenders in the Loose tab allows the banking of tenders that haven’t already been added to a Banking Bag.

Banking > New Bag

The New Bag tab allows the user to create a new banking bag.

Banking > Existing Bag

In the Existing bag tab, the user can select an existing Banking Bag to be banked.

Banking > General

This tab records the Banking details and the user can record any Notes related to the Banking action.

Safe Cashup and Banking

This function allows the Safe Cashup and the Banking processes to be combined.

Store Server

Store Server > Loose

If the Location's Tender Bag configuration is set to Optional, then the initial tab displayed is Loose.

Store Server > New Bag

This tab is used to create a new bag while completing the Safe Cashup function. The user adds the Bag Id and the Seal number while creating a bag.

Store Server > Existing Bag

The Existing bag tab displays the bags which need to be Cashed Up in the active session. This screen lists Pickup bags which have been transferred from Terminal(s) to the Safe using the Terminal Pickup function, plus Float and Banking bags.

Store Server > General

The user can record any Notes related to the Safe Cashup action.

Banking > Loose

The Loose option is only displayed when the Location is configured with Tender Bags as Optional. The Loose tab allows Banking Tenders that are not associated with a physical bag to be recorded.

Banking > Existing Bag

In the Existing bag tab, the user can select the any pre-existing Banking Bags to be banked.

Banking > General

This tab records the Banking details and the user can record any Notes related to the Banking action.

Terminal Spot Check /Safe Spot Check

This Terminal Spot Check and Safe Spot Check functions are used to check the counted amounts versus the expected amounts for either a Terminal or a Safe, without performing a formal declaration.

POS

Spot Check > Existing Bag

When the User selects Existing Bag, the Bags available to the session are listed.

The user can search for the existing bags by using the Bag ID.

Once the Bag ID has been entered, the user can add the bag using the Add button so that it is included in the Spot Check.

Store Server