Processing bank transactions can occur in 3 scenarios:
| Table of Contents | ||
|---|---|---|
|
Process daily transactions on a bank account using a bank statement import file
Process daily transactions on a bank account using a bank statement import file
User flow:
User should have a bank statement file (CAMT or MT940) at hand which can be imported in the system. System can match payments to reservations (auto-matching), throw a suggested match (user validation required) or cannot match (manual assigning or parking as unassignable payment required).
User steps:
- Download daily bank statement from online banking environment
- Upload bank statement file to MXT server
Open Payments module and select applicable bank account of Administration Organisation
- Add new bank statement and select automatic import
- Browse on server environment for CAMT/MT940 file (EU) or qfx/qbo/ofx file (USA)
- After all payments are (automatically) allocated the statement can be processed via the ‘commit’ button. Manual allocation requires selection of either a Reservation and Payer, or a contraledger to park the transaction as unassignable payment.
Process daily transactions on a bank account via manually adding transactions
User flow:
User should have the bank transactions and corresponding reservations or ledgers at hand, when creating a bank statement and adding manual entries
User steps:
Open Payments module and select applicable bank account of Administration Organisation
Create a new bankstatement for manual processing payments
Add end balance of new bank statement
- After all payments are allocated the statement can be processed via the ‘commit’ button. Manual allocation requires selection of either a Reservation and Payer, or a contraledger to park the transaction as unassignable payment.
Process earlier registered unassignable payments for which the allocation information is now available
User flow:
User parked unassignable payments on an unassignable payments account, when processing the daily bank statement. The information where to allocate the payment to is now available and the user wishes to pickup the unassignable payment and allocate is correctly.
User steps:
Open Payments module and select applicable Unassignable Payments account of Administration Organisation
Create a new statement for manual processing on the Unassignable Payments account
- Observe the unassigned payments on the account via Unassignable payments tab
- Select and assign payment(s) for which the allocation became clear
- The assigned payment is added to the bank statement
- After all payments are allocated the statement can be processed via the ‘commit’ button.
Process individual transactions on a miscellaneous account for one or more bank accounts which are not processed in MXT system
User flow:
Context is the presence of a bank account which is not directly processed via MXT system, potentially because of very little reservation transactions or a mixture of transactions which makes auto-importing less efficient. User updates received payments from this bank account manually in the system when they occur.
User steps:
Open Payments module and select applicable Manual payments account (Miscellaneous account without end balance check) of Administration Organisation
Create a new statement for manual processing transactions
- After all payments are allocated the statement can be processed via the ‘commit’ button. Manual allocation requires selection of either a Reservation and Payer, or a contraledger to park the transaction as unassignable payment.