iVend Retail – Transaction Rollup

The Transaction Rollup feature is used to reduce the volume of transactions integrated into an ERP. It is recommended to use this feature when transaction volumes are large.

Note: In this article we will use SAP Business One (SBO) as our example.

This feature rolls-up sale, refund and exchange transactions in iVend before they are integrated and posted to SBO. This process substantially reduces the number of A/R Invoices and A/R Credit Memos created in SBO.

 Note

In this feature, only the following transaction types will be rolled up:

· Sale

· Sale Refund

· Sale Exchange

 Note

The following transaction types are not included in roll-ups and will be posted as one SBO transaction per iVend Transaction:

· Special Orders

· On Account Payments

· Layaways

· Layaway Cancellations

· Layaway Payments

· Deliveries

· Sale Transactions with Fulfilment

How to enable transaction roll-up in the Management Console

To setup Transaction Roll-up, follow this procedure:

· Login into the iVend Management Console and go to: Administration > System Initialization > Enterprise

Please remember this option is only available at the iVend Enterprise.

Figure 1 Transaction Roll up settings

Refer to the table below for detailed information on each Transaction Roll-up setting.

· Specify all the details in the Transaction Roll-up settings as per the above table.

Figure 2 Management console -Transaction Rollup

· Choose the [Ok] button to save the changes made for the Transaction Roll-up.

Figure 3 Click on Ok

How the Transaction Roll-up process works in iVend Retail

Once you have enabled the above settings in the iVend Enterprise, iVend POS transactions will be rolled-up based on the following grouping criteria:

· Store ID (Warehouse Code)

· Customer Code

· Transaction Type, i.e. – Sales, Sale Refunds, Sale Exchanges

· Item Code

· Item Price

· Tax Code

Additionally, payments by Credit Cards and Cheques (Checks) attached to the transactions are rolled-up as well.

Examples for Transactions being Rolled-up:

The following example simulates the roll-up process based on the above mentioned roll-up criteria.

Accumulated Transactions at the iVend Enterprise:

Explanation for Roll Up processing:

· Since there is only one transaction for Customer C1000 in Store S1, the transaction T10001 cannot be rolled up. This transaction is copied directly to the Transaction Consolidation table and is allocated a new transaction number TC0001 and the same transaction (TC0001) will be integrated to SBO.

· Customer C2000 has 3 transactions T10002, T10003, and T10004 in Store 1, therefore these can be rolled up. Also, note that since item P3000 is used in transactions T10002 and T10004, the quantities of these 2 lines can be clubbed into a single line. The rolled up result of these transactions is copied to the Transaction Consolidation table and is allocated a new transaction number TC0002 and the same transaction (TC0002) will be integrated to SBO.

· Customer C1000 has 2 transactions T20001 and T20003 in Store 2, therefore these can be rolled up. Also note that item P5000 is used in transactions T20001 and T20003, however since their Tax Codes are different, the quantities of these 2 lines cannot be clubbed together. The rolled up result of these transactions is copied to the Transaction Consolidation table and is allocated a new transaction number TC0003 and the same transaction (TC0003) will be integrated to SBO.

· Since there is only one transaction for Customer C3000 in Store S2, the transaction T20002 cannot be rolled up. This transaction is copied directly to the Transaction Consolidation table and is allocated a new transaction number TC0004 and the same transaction (TC0004) will be integrated to SBO.

Rolled-Up Transactions at the iVend Enterprise: