Technical Overview – Transaction Registers
Voucher Register (vouchers.dbf-autofilled)
The voucher register stores details of referral and bill back vouchers for all branches.
Each voucher has a unique identifying key made up of a fixed scope (“M”), the branch code and a unique 6-digit number and is auto filled in blocks per the system setup (normally 1000).
Each voucher record has a one-to-m any to one relationship to the transaction register (internal invoices, credit notes and referral commission receipts if a direct settlement)
Referral Commission Receipts Register (receipts.dbf-autofilled)
The receipts register stores details of all referral commission receipts against direct settlement voucher charges (internal invoices).
Each receipt has a unique identifying key made up of a fixed scope (“M”), the branch code and a unique 6-digit number and is auto filled in blocks per the system setup (normally 500). Each receipt record has a one-to-many relationship to the transaction register (commission receipts).
Transaction Register (trans.dbf)
The transaction register stores the following details for all branches:
+ Direct Settlement referral commission internal invoices, credit notes and receipts
+ Bill back internal invoice and credit note requests
Each transaction has a unique identifying key made of a scope key (voucher type = bill back
(“B”) or referral (“M”)), the branch code, the transaction type and a unique 6-digit number. Except for un-allocated referral commission receipts, each transaction is a child of the voucher register and, if a receipt, a child of the receipts registers as well.
Notepad Table (notepad.dbf)
The notepad table stores, among other items, the voucher special instructions (printed on the voucher), private administration notes and void reasons (if applicable).
Each voucher entry has a unique identifying key made up of a fixed scope (“Vch”), the branch code and the voucher number.
Commission Debtors Movement and Ageing (movement.dbf)
The movement tables store a summary of the transaction movement on each supplier’s commission debtor account per month per issue currency. This enables the system to generate debtors’ control and ageing information far more quickly than if it had to scan the transaction register (it only has to scan one record per supplier per month)
Each record has a unique identifying key made up of a fixed scope (“M”), the branch code, supplier code, currency code and period
Each record contains a total turnover/commission/vat/transaction count accumulation as well as per transaction type (invoice, credit notes, allocated and un-allocated receipts) and the periodic ageing from current to 150+ days.