---

Transaction Masking (Optional)

This function supports the need for masking or hiding card-based transactions when loaded into ProMaster from personally or dual-liability card programmes.

Due to data protection laws, transactions undertaken on dual-liability card programs managed through ProMaster, may include expenditure for personal reasons, along with transactions for corporate purposes. Due to these laws, it is not appropriate for individuals within a company beyond the owner of the card to review/report on/analyse such expenditure until the cardholder has indicated that it is undertaken for corporate purposes.

When switched on (see The Account Details tab), imported transactions can only be viewed/reported directly by the associated Account Holder. These transactions remain hidden from all user authorities until the Account Holder links the transaction to an expense and processes the transaction forward beyond a status of `Waiting Accountholder' (or Account Holder verification, etc.):

· All account transactions are loaded through the standard load and system administration processes.

· Transactions that are auto-approved on import are automatically linked to an expense and processed forward for export, as such, deemed to be a corporate expense. These transactions are able to be viewed by all appropriate security groups.

· Transactions loaded that are in a status of `Waiting Accountholder', and if the corresponding account type has Mask Transactions switched on, these transactions can only be viewed/reviewed/reported on by the associated Account Holder or users they have assigned their authorities to.

· The Account Holder then reviews all transactions and either:

· Disputes the transaction

· Sets the transaction to Private or Part-Private

· Verifies the transaction and, processes it forward

· Resolves a disputed transaction

· Once a transaction has been verified (linked to an expense) and processed forward, the transaction is then able to be viewed/reported on/analysed by all appropriate security groups based on the customer's organisational hierarchy and security configuration.

· Transactions with a status of Private/Disputed/Dispute Resolved remain hidden and may be archived off at some time in the future.

Inlogik Pty Limited