Back office routines - transaction flow

1. Trader enters transaction in Deal Input. In some cases the trader writes a deal slip with transaction details and gives it to back office.

2. Back Office (BO) opens Confirm - start (Back Office Menu) and selects transactions by for example deal date, deals done a certain deal date. The transactions are verified and reviewed against the deal slip or a confirmation from the bank/FX match. To see the full deal input screen double click on the reference number or press F9. If everything is OK confirm the transaction (use icon ‘Confirm transaction’). The transaction status changes from REG to CONFIRMED and is thereby locked for changes.

3. Confirmations/MS Word - Generate confirmations and send by email or print them and send by fax or mail.

4. Pay/Advice Transactions – Administration of payments. Search for outgoing payments in the Pay tab and incoming payments in the Advice tab. Select by due date. Pass on the transactions to the netting tab, set netting criteria’s. Pass on the transactions to the pending tab. Run export preview to see the transactions to be exported. Create a payment file (to be sent to the bank) or a payment instruction with a MS Word template.

5. Automated coding - Batch creates account coding for the confirmed transactions. Make selections to ensure that all confirmed transactions are coded. The account codings can be viewed in Transaction status overview. The coding can also be deleted in Transaction status overview.

6. Journal entry creates journal entries for transactions with account codes. Journal entries can also be created automatically when running automated coding batch (see item 5 above). Each journal entry is given a unique journal entry number. The Journal entry layout can be designed by the user.

7. Export - Journal Entries creates an export file specially designed for the specific general ledger in your ERP system.

Transaction flow - Closing the books

1. Coding of unrealised Profit/Loss creates account coding for Accrued interest, FX gain/loss and Interest gain/loss. The transactions have to be coded at start (see item 5 above) before unrealized coding can be made.

2. Journal entry creates journal entries for coded transactions. Journal entries can be created automatically when running Coding of unrealised Profit/Loss which means that you can go directly from item 1 to 3.

3. Export of journal entries creates an export file specially designed for the specific general ledger.

Transaction flow - Maturing transaction

2. Pay/Advice Transactions – Administration of payments. Search for outgoing payments in the Pay tab and incoming payments in the Advice tab. Select by due date. Pass on the transactions to the netting tab, set netting criteria’s. Pass on the transactions to the pending tab. Run export preview to see the transactions to be exported. Create a payment file (to be sent to the bank) or a payment instruction with a MS Word template

3. Automated coding - Batch creates account coding for the confirmed transactions. Make no selections to ensure that all completed transactions are coded. The account codings can be viewed in Transaction status overview. The coding can also be deleted in Transaction status overview.

4. Journal entry creates journal entries for coded transactions. Journal entries can be created automatically when running automated coding batch (item 3). Each journal entry is given a unique journal entry number. The Journal entry layout can be designed by the user.

5. Export av journal entries creates an export file specially designed for the specific general ledger in your ERP system.