The latest buzzword in FinTech is without a doubt "open banking", but whether or not this becomes a lasting concept depends on a plethora of factors.
A wiki stub may be all you need to put a name to "the use of open APIs that enable third party developers to build applications and services around the financial institution, greater financial transparency options for account holders ranging from open data to private data, and the use of open source technology to achieve the aforementioned". And that name is... open banking.
The biggest craze is, by far, in Europe, and that's the doing of PSD2, but while EU's changes in banking regulations were still being drafted, the UK jumped the gun establishing the Open Banking Work Group (OBWG), in September 2015.
Its purpose was (and still is) to analyze how data could be used in order to help everyone easily transact, save, lend, borrow and invest. In fact, it set out a standard for creating, sharing and using open banking data that we'll definitely hear plenty about.
Still, Europe's quasi-antipode, Australia, is probably the most surprising in the matter. How so? Well, the Australian House of Representative Standing Committee on Economics filed a report in November 2016 regarding future banking regulations imposed by what they called "the oligopoly of Australia’s banking sector".
In short, the Committee reviewed the four major banks in Australia and came to the conclusion that competition must be improved. The steps recommended in this matter include, among others, the launch of a Banking Tribunal and the creation of a data sharing framework for consumers' and small businesses' data.
EU stands by what Australia managed to explicitly state, but does so with velvet gloves, since it is a delicate matter and banks are highly uncomfortable with this emerging concept. But the truth is... beating around the bush doesn't do anyone any good. So let's set sail!
After all, this whole open banking concept is in line with what Allevo first had in mind in 2011 when we spread the word that we intended to migrate to a more open business model. What we tried back then was to anticipate the evolution of the main actors in the financial ecosystem (whether vendors, banks or SMEs) and keep up with their pace. To this we say "so far, so good".
Experts agree that in order to minimize the amount of work involved, it is good practice to carry out bank reconciliations on a daily basis, preferably assisted by specialized accounting software.
FinTP's ReconS feature provides real-time automated / manual reconciliation of incoming or outgoing payments with bank statements. Not only does it lead to more timely reactions to risks, thus contributing to standards improvement and manual effort reduction, but it also helps reduce the overall cost.
In fact, here is a brief list of characteristics, which we may further expand upon request, especially since ReconS is also available as a stand-alone product:
1. Ledger vs. Statement Reconciliation (NOSTRO)
ReconS reconciles NOSTRO SWIFT statement and general ledger (GL) items and provides "offered", "suspended" and "confirmed" matching functionality depending on the percentage of the satisfied criteria.
High-quality matches can be confirmed automatically, while others are submitted to the operators, in order to make an informed decision (suspend, confirm or unmatch).
ReconS also compares SWIFT payments vs. VOSTRO statements reconciliation, offering the possibility to check the quality of the statements delivered to customers.
The app automatically prompts operators to confirm the reconciled transactions based on a combination of criteria defined when configuring the system.
Certain confirmed transactions from the current session or from the transactions history can be reactivated in order to be corrected.
ReconS monitors the balance in NOSTRO/VOSTRO accounts and checks whether the limit exposure is exceeded for accounts, accounts groups, or currency types, using a variety of SWIFT messages.
It also makes forecasts based on the information in: the statements received from SWIFT, NOSTRO accounts transactions, and total amount of the payments about to be performed, reporting the status of the unreconciled transactions, consolidated on various currencies.
Identifying the unreconciled transactions, ReconS offers the possibility to either suspend them for further investigations, or to insert an explanation and to print these matches.
It also gives the user the possibility to point out or assign (in electronic format) the unconfirmed transactions to other applications/departments or users for further investigation.
Reports in ReconS can be generated based on various criteria, like account, currency, bank, currency date, or booking date, as well as a combination of these.
Besides reporting the available and booking balance separately on each account and globally on all accounts, the app also reports the manually confirmed matches, detecting the ones that were incorrectly confirmed with a different currency date.
Other predefined reports are available, along with the possibility to define customized reports for monitoring the user activity in order to optimize operations.
First of all, it addresses the problem of identifying and managing the exceptions (reconciliation problems that cannot be automatically solved using the defined business rules), highlighting the data that has failed to be automatically matched and proposing solutions to facilitate the operator's decision.
Last but not least, endowed with a powerful reporting and query engine, ReconS allows users to extract any information in order to run a comprehensive analysis of accounts and matching information, by means of a user-friendly graphical interface.
This multi-platform product works both in Unix/Linux and Windows environments, offering connectors for SWIFT interfaces and GL applications, and supporting both SWIFT FIN and ISO 20022 message standards, as well as various data sources and formats.