What is physical cash concentration testing?

Physical cash concentration testing checks whether banking systems correctly record and consolidate cash collected from branches, automated teller machines (ATMs) or other locations at a central cash point. It validates the workflow and data for cash movements, including amounts, currencies, custody status, interfaces and reconciliation. The exact scope depends on how the organisation defines and operates its cash collection process.

What physical cash concentration testing covers

A test may follow cash from a source location through a collection instruction, dispatch, transport acknowledgement and receipt at a cash centre. It checks that the system associates each movement with the correct location, currency, amount, collection reference and status. Where cash is recorded by denomination, tests should also check that denomination totals equal the reported amount.

The process can involve branch or ATM systems, a treasury management system (TMS), a cash-in-transit provider interface and accounting or reconciliation services. Integration testing checks that messages and status changes pass correctly between these components. End-to-end testing follows the movement across the workflow, including any accounting entries required by the organisation’s rules.

Physical cash concentration concerns notes and coins recorded as moving between locations. Electronic cash pooling combines or manages account balances and is a related but different process. A treasury platform may support both, so test scenarios should identify which process and accounting rules are in scope.

How to design useful test scenarios

Start with the configured lifecycle and identify when the system considers cash collected, in transit, received and reconciled. Confirm which event triggers any balance change or accounting entry. This matters because a system that records a dispatch may treat custody and ledger balances differently from one that records a movement only after receipt.

Prepare controlled test data for source locations, currencies, denominations, collection references and expected statuses. Include normal movements, partial receipts, amount mismatches, rejected or delayed acknowledgements, duplicate messages and cancelled instructions. Check that the system prevents invalid transitions and retains enough information to investigate an exception.

Verify results at each relevant layer: the source record, the receiving system, movement status, location balances, accounting output and reconciliation result. Compare totals by currency and location. Check that retries do not create duplicate movements or postings, and that a failed interface message can be identified and safely reprocessed according to the configured rules. Environment drift, stale reference data or inconsistent calendars can also produce misleading results, so confirm that connected test systems use compatible configuration.

Worked example

Assume two branches submit collection records for the same currency: Branch A reports £8,400 and Branch B reports £5,600. The cash centre’s receipt records total £14,000. The expected result is a consolidated receipt of £14,000 linked to both source records, with the configured receipt status and accounting treatment. The test should also confirm that each branch’s movement is included once and that the reconciliation identifies both records as matched.

Run a separate case where the cash centre records £13,950. The system should show a £50 difference and follow the configured exception process. It should not report the collection as fully reconciled if the business rule requires the amounts to match. Check the exception reference, affected locations and audit history, then verify that correcting the receipt or recording an authorised adjustment updates the outcome without duplicating the original movement.

What a passing result means

A passing test shows that the tested software workflow handles the defined cash movement and its records consistently under the selected scenarios. It does not, by itself, prove that physical cash was counted or transported correctly. Operational controls, such as custody checks and approvals, need their own evidence when they form part of the scope.