File-based end to end monitoring is for all orders that are instructed towards a bank via a file or message interface.
These instructions (CT, DD, FX, etc.) can be transferred via our communication server on several communication protocols.
As shown in above diagram, the steps 1 till 5 generate availabilty reports. On every step we can store the actual screen as shown to a customer. Where needed we utilize the accounts to create the real transactions and monitor the end-to-end flow.
The below picture shows how monitoring is implemented at most of the banks before using our implementation.
You can see that internally everything is monitored. However, the front-end is not always part of the monitoring process. In the future, these front-ends can be made more complex as FinTech parties will also be part of the end-to-end chains.
When a foreign branch (or partner bank) is added, 9 out of 10 have they there own monitoring systems in place and will not always tell you if there are issues. This is particularly annoying if the branch has the same brand as you. Your big customer does not see the difference in processing between you and the branch and will hold the ordering bank responsible.
Since our monitor is end-to-end (aka the money should end up at the other branch) we DO see the issues in processing if they occur. The speed at which we can detect a problem depends on the signals we can receive back from the originating and counterparties