Back Office

Created by Erik Åkerlund, Modified on Mon, 20 Feb 2023 at 02:28 PM by Erik Åkerlund

Back office 


The Back Office menu includes functions for

  • Confirmation
  • Settlement
  • Printing / Sending confirmations.
  • Account coding
  • Printing / Exporting journal entries to external accounting system
  • File export to other systems such as banks, accounting and matching systems.
  • Payments / Bank Account reconciliation.
  • Import of Cash Pool Balances



Back office routines – transaction flow

Transaction flow – New transaction 

Deal Date, Value Date

  1. Trader enters transaction in Deal input. The trader writes in some cases a deal slip with transaction details and gives it to back office.
  2. Back Office (BO) goes into confirm start (back office menu) and selects transactions for example by deal date, deals done a certain deal date. The transactions are controlled 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 and incoming payments in the Pay/Advice/Delay tab. Select by due date. Net the transactions that should be netted according to 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).
  5. Automated coding - Batch creates account coding for the confirmed transactions. Make no 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 made account codings. Journal entries can be created automatically when running automated coding batch (item 5) which means that you can go directly from item 5 to 7. Each journal entry is given a unique journal entry number. The Journal entry layout can be designed by the user. The coding information can be entered manually in the general ledger or transferred via file.
  7. Export - journal entries creates an export file specially designed for the specific general ledger.

Advanced System parameters settings - Register > Setup > System Parameters - Accounting tab.


If you check Automatic journal entries , the journal entries are created automatically  when the transaction has  been coded.


Transaction flow – Closing the books. 

Unrealised date

  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 (item 5 above) before unrealized coding can be made.
  2. Journal entry creates journal entries for made account codings. Journal entries can be created automatically when running Coding of unrealised Profit/Loss (item 1) which means that you can go directly from item 1 to 3.
  3. Export av journal entries creates an export file specially designed for the specific general ledger. .


Transaction flow – Maturing transaction


Maturity date

  1. Back Office (BO) goes into confirm close (back office menu) and selects transactions for example by maturity date, deals with a certain maturity date. To see the full deal input screen double click on the reference number or press F9. Set spot at maturity rate on transactions in foreign currency. Click on icon 'Confirm transaction' to complete transaction. The transaction status changes from CONFIRMED to COMPLETED.
  2. Pay/Advice Transactions – Administration of payments. Search for outgoing and incoming payments in the Pay/Advice/Delay tab. Select by due date. Net the transactions that should be netted according to 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).
  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 made account codings. Journal entries can be created automatically when running automated coding batch (item 3) which means that you can go directly from item 3 to 5. Each journal entry is given a unique journal entry number. The Journal entry layout can be designed by the user. The coding information can be entered manually in the general ledger or transferred via file.
  5. Via Export av journal entries creates an export file specially designed for the specific general ledger

    If you check Automatic complete, confirm close, coding and creating journal enteries ( bullet 1,3 and 4 above) will be done automatically when running automated coding according to bullet 3.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article