Controlling Transactions

There are several Roles controlling access to and creation of transactions.

Role MANAGE_TRANSACTION allows some fields to be edited – those relating to the status of subs invoices and Auxiliary invoices. Allows a REFUND to be issued for eWay or PayPal receipts.
Also includes all permissions of the Roles described below.

Role TRANSACTION allows creation of any type of Transaction, except Invoices and Credits related to a booking. The latter are created when the Admin Price of a booking is changed, requiring BOOKINGS role. Allows a REFUND transaction to be created when a bank transfer was used to refund. Refunding an online payment requires MANAGE_TRANSACTION.

Ability to create a specific type of transaction can be granted to an Access Level at level below that granted MANAGE_TRANSACTION through a Role named e.g. TRANSACTION_RECEIPT. Ability to reverse is granted by TRANSACTION_REVERSE, but access to create the type of transaction being reversed is also required. When using these specific Roles, you need to create the Role if it does not already exist. In general, these Roles should be given to a lower level than the TRANSACTION Role, otherwise they will have no effect. Note that TRANSACTION_REFUND does not give ability to initiate an online payment refund, it only allows creation of a REFUND transaction to reflect a refund by bank transfer.

Role TRANSACTION_REPORT allows read-only access to transactions, including ability to download a PDF version and send an email.

Ability to bulk upload transactions using a CSV file is given by Role UPLOAD_TRANSACTION_DATA.

In general, transactions cannot be deleted, only reversed. Note that reversing a REFUND processed by eWay or PayPal will not recover the funds. In general when we see this type of reversal, it is a mistake.