LPA offers preprocessed patterns to recognize fraudulent activities at the point of sale and is fully integrated with the SAP POSDM. There are possibilities of marking the transactions based on defined exceptions. These exceptions have defined parameters which can be changed.
SAP provides certain templates for marking fraudulent transactions.
- Exception Basic Template : Basic exceptions are used to create exceptions with the following parameters:
- Transaction Type Group
- Transaction Type
- Means of Payment Group
- Means of Payment
- Transaction Codes
- Transaction Item Information
The transaction type can be specified by combination of two different transaction types. Combination can be And, Or, And not, Or not.
The transaction amount can be defined by entering an interval.
2. Exception Discount Template : Discount template is used to define exceptions based on discount values. Discount Types can be selected from following parameters (to list out a few):
- Item Discount Amount Percentage restricted to Discount Type
- Item Discount Amount restricted to Discount Type
- Item Discount Amount
- Item Discount Amount Percentage
- Item Discount Count Percentage restricted to Discount Type
- Item Discount Count restricted to Discount Type
- Item Discount Count
- Item Discount Count Percentage
For these parameters a threshold value can be entered with the possibility in comparing this by (>, <, <=, >=, == )
This can be further restricted based on Order Attribute or Item Attribute.
3. Exception Item Scan Rate Template : This template is designed to catch exceptions based on average rate at which different cashiers scan items for particular transactions.
There shall be a possibility to define a threshold value by setting a reference value with >, <, >=, <= and =. This value shall represent items scanned per minute.
Additionally there shall be an optional possibility to restrict the transactions which are considered to one transaction type.
4. Exception Late Template : This template is designed to catch exceptions based on two transactions, which have a connection. The connection
can be a void / post void to a transaction or a refund to a transaction.
This template is designed to pick out transactions that may have been fraudulently voided or refunded by the cashier. It allows you to create an exception marking definition, which captures transactions involving a specified transaction type, such as a refund or a post void, and is created at a specified time after the original transaction.
5. Exception Off Hour Template : This template is designed to catch exceptions based on the time the transaction is posted. The user can specify a time interval, which shall be the condition for the exception. The time interval can be defined by entering two time values in (hour : minute) each.
6. Exception Refund After Days Template : This template is designed to catch exceptions based on a refund happening after a specific number of days.
The refund type can be selected to be (All, Staff, Different Tender)
- All: all refunds without restriction
- Staff: only refunds which are conducted on sales for an employee / refunds for an employee. Employees have usually a special condition / discount for buying within the own company.
Different Tender: Refunds which have a different tender as the corresponding sales transaction (e.g. Sales transaction paid by credit card, refund received cash)
7. Exception Refund match Post Void Template : This template is designed to catch exceptions based on a refund transaction, which matches a post void transaction.
Additionally to that condition the user can specify the tender type to cash, amex, visa, cheque….
8. Exception Transaction Before/ After Template : This template is designed to catch exceptions based on a timely relationship between two transactions.
Each of the transactions can be specified by tender type and transactions type.
9. Exception Refund w/o Purchase Template : This template is designed to catch exceptions based on a refund where no corresponding purchase exists. The exception is defined by specifying the tender type of the transactions, which shall be watched.
10. Exception Repeat ESP Transaction Template : ESP stands for Extended Service Plan. ESP items are those with an ESP code in the product ID field of the SKU table in the database. This template allows you to create exception marking definitions which track two consecutive transactions for ESP items processed containing all the following identical information: date, store, cashier, type, number, register.
There are no input variables.
All the parameters listed here shall be in the interface.
11. Exception Same Card Used Template : This exception template allows you to create exception marking definitions which track transactions processed by a specific cashier, or within a defined ring time. It can also be used to identify any cashiers who might be processing transactions they are not authorized to do.
Variables can be an interval of cashier ID or an interval of total ring time.
12. Exception Tender Info Template : This template seeks suspicious patterns related to different tender types based on card number, cheque dates, amount, time of transaction, or other customer-defined exceptions set up in the manual code field in the database.
13. Exception Insufficient Info Template : This template flag transactions with missing information. For example, some retailers require their cashiers to enter a customer phone number with each transaction. This exception helps to identify cashiers who frequently process incomplete transactions.
14. Exception Template first/ last hour Template : This template flag transactions that took place during the period following store opening, or the period right before closing. This exception seeks suspicious activity during the non-busy hours of operation.
15. Exception Measure of Item Attributions : This template creates exception definitions at transaction item level. You can use a definition created with this template to pick out transactions which contain more than two line voids greater than a specified amount.
16. Exception Orphaned Transaction : This template tracks transactions, such as sales and refunds, which are processed in isolation after a lengthy period of inactivity at the terminal. Such situations can indicate that transactions might be processed in the absence of customers and reversed making the proceeds available for removal from the cash register without incurring any cash shortages or overages.
17. Exception Post Void with No Matching Cashier : Marks post-void transactions that were performed by someone other than the transaction’s original cashier. There are no parameters.
Condition is that we have a post void, and the post void is done by a different cashier than the original sales transaction. The data which is looked at is usually within the same day, so only the data from the same day is relevant.
18. Exception Refund with Duplicate Return Information : This creates exception definitions which mark refund transactions containing information
identical to information in previously processed refunds.
There are no parameters. The data which is looked at is usually within the same day, so only the data from the same day is relevant.
19. Exception Transaction On Special SKU’s matching discount/price override amount on order item : Allows to track discount and price override
transactions for specific SKU numbers manually entered in the system.
