| Menu | Reports & Statistics -> Audit -> Collection Audit. |
The Collection Audit report will compare each collection to aggregated data from the Purchase and the Card Transaction tables. Collections for all PayUnit types will be included in the report, but only PayUnit Card will contain an aggregate from the Card Transaction table.
This function is only available on CWT terminals, updated to report back their collection identifiers when submitting purchase information.
| Note: This page uses enforced filtering For a user to be able to see this page the user must have the Collection Auditor permission set on their user account. See Create User Account. |
The following table explains the items on the page:
Column Name |
Description |
|
|---|---|---|
Terminal ID. |
The friendly identifier of the terminal. |
|
PayUnit |
The unit the purchase or card transactions are made with |
|
Collection Date. |
The date the collection was performed on the machine. |
|
Created in CWO |
The date the record was created |
|
Collection Amount. |
Amount stored in the collection. |
|
Purchase Amount. |
Sum of the amounts in the purchases. |
|
Purchase count |
The number of purchases that are included in the collection. |
|
Purchase mismatch |
No: Collection.Amount = Purchase.Amount Yes: Collection.Amount != Purchase.Amount |
|
Card Transaction Amount |
Sum of the amounts in the card transactions |
|
Card Transaction Count |
The number of card transactions that are included in the collection. |
|
Card Transaction Mismatch |
No: Collection.Amount = CardTransaction.Amount Yes:: Collection.Amount != CardTransaction.Amount |
|
Collection Purchase Count. |
retrieved from the “Total Number” or number in the collections page. Clicking the figure will bring you to the collections page filtered by the selected collection. |
|
Additional Filter fields not visible in the list:
Filter Name |
Description |
|
Node. |
Allows search on a single terminal. |
|
Terminal group |
Search for collection audits for in a terminak group |
|
Company |
Search for collection audits in a specific company. E.g. when working with Company structures |
|
| Note: It should be noted that when these values are populated from the terminal, only collections where all purchases were placed after the update will be correct. So, if the terminal was updated and only half of the purchases have a collection identifier assigned, there will be differences in the audit page. Best practice is to wait until all transactions are populated with a collection identifier. This is not a major factor for card transactions, however coin collections which are done much less frequently could show large variations for the first 6 months after feature activation. |
