Today, we formally announced that Bricknode has started the application process for a brokerage/securities license in Sweden. Ever since Bricknode started in 2010, we have had the ambition to add a subsidiary to the company group where we can be the primary broker and custodian for our software users. This will boost our own scalability and help deliver a complete service to many customers.
In order to understand the benefits that acquiring a brokerage license will bring our different customer groups, it is helpful to know how we work with them today.
Within the brokerage product division today, we see two groups of customers. The first group are customers who have their own full regulatory permissions to carry customer accounts. These companies can be rather complex and relative to our other customer groups, there are fewer of these around.
In terms of Bricknode solutions, these companies consume pure software, and they can also outsource their back-office operations to Bricknode if they do not want to manage this themselves.
Today, these companies must also establish their own relationships with banks, brokers, exchanges, fund companies etc. to access financial instruments that they would like to distribute.
This means that each customer needs to have their own relationships which can be less cost effective and take a lot of time to cut through red tape. This is bad from a few standpoints.
First, even if Bricknode delivers the software solution on the same day that it is ordered by the customer, it could still take months before the customer gets approval by institutional brokers and fund networks that it might need to access. In addition, it can take years before relationships are set up to manage international tax withholding and other administrative things that should just simply work.
Second, time to market for new valuable products is greatly increased and companies can go out of business even before getting to first base.
The second customer group is characterized by firms that lack full regulatory permissions for carrying or operating their client accounts in their own firm. Some are simply not interested in having the administrative overhead that is required for those accounts like tax reporting, corporate actions, MiFID II reporting and so on. These can be financial advisors or various types of FinTech companies.
There are many of these companies around but today they need to find an external party that holds the required licenses and that has relationships with various trading venues. This third party might already have a different software provider to Bricknode, so the deals are ultimately lost if the third party does not want to go through the process of switching core systems.
The problem is that Bricknode cannot supply the full plug and play brokerage solution for this group of customers, since we must go through a third party which can introduce more costs for the potential customer and make the whole setup less attractive.
By setting up a subsidiary of Bricknode with a brokerage license we can merge our administrative services into the brokerage division, and we become a one-stop-shop for customers that do not have their own regulatory permissions.
Bricknode is then the only party that must set up and maintain the relationships with trading venues and issuers of financial products and we can obtain economy of scale.
When it comes to the other customer group that has full permissions, we can now present them with a choice where they could either maintain their own external relationships or switch to Bricknode as their primary brokerage firm. The latter would enable them to participate in the cost savings that this would generate both from shrinking the administrative overhead and from lower trading fees.
From a revenue perspective, obtaining a license would greatly increase the market opportunity for Bricknode in the short and long term. It will help create higher margins and shorten sales cycles in general.
As the provider of accounts, Bricknode would have a direct legal relationship to each account holder. This would enable us to apply all our internal tools and knowledge to optimize processes and the end customer experience.
Not that long ago, big UK-based fintech Revolut decided against setting up their own regulated securities firm when they launched equities investments on their app. Instead they made a partnership with another company that is providing and carrying those accounts and making the trading facilities available. It makes a lot more sense for our prospective customers to let Bricknode take care of everything under the hood too, so they can just focus on the end customer.
There are still very few alternatives today for this sort of service and no one is in control of the full back-office software like Bricknode is with Bricknode Broker. By controlling all technology, Bricknode can be agile and quick in ways that other companies who rent their back-office systems for this purpose can only dream about.
Bricknode will provide these accounts and facilities as a pure back-end service and will not have its own B2C offering that could compete with the services of our customers. During the years Bricknode has established technology and the required facilities to provide a wide array of financial instruments like global equities, funds, bonds and more. We see no technical limitations with regards to the products that we can provide, and we think that this complete service bundle will be revolutionary.
Together with front-end partners like Additiv we will be able to provide financial advisors with stellar tools to manage their customers and a full suite of financial products to distribute. This is all the while making sure that the financial advisor builds their own brand and customer loyalty. This is something that is not being done today when financial advisors are forced to place their customer accounts with standard retail brokers that compete for the same customers.
Why now, you might ask. Simple, it’s because we have not been ready for this in the organization. Thanks to the IPO we have been able to onboard the right team members for this and we now have the necessary resources to do this with great quality. We have also been able to conduct the full administration for current software customers which has enabled us to build up the required internal routines and learn everything first-hand.
Getting a license to perform regulated activities will not do any harm to the current pure Software-as-a-Service offering where business is expanding aggressively over multiple product lines based on Bricknode Core. It will, however, add a whole new dimension to Bricknode and unleash us from many limitations impacting customer acquisition today.
As with any software solution it is of the utmost importance that it is being used conceptually correct in order for the user to gain the most value from it. This is true in every sense when it comes to Bricknode Broker and thus we want to emphasis some powerful features in this article.
The most important daily task for the back office team is to conduct reconciliations to make sure that the assets and liabilities that are listed in Bricknode Broker agrees with the rest of the world. To help automate this we have developed two distinct account worlds in Bricknode Broker, one world is called BFS-accounts and the other world is called Custody-accounts.
Everything that resides within a BFS-account should be viewed by you as a liability. For example, if a customer of yours has 100 EUR in their account this means that You are on the hook for these 100 EUR. No matter what happens you need to make sure that you have these 100 EUR on your own bank account or in a segregated client account with your bank. You could also have another asset with an equivalent value placed somewhere but you have to make sure that your assets at least match your liabilities to your customers.
The Custody-accounts that you should have set up within Bricknode Broker reflects how much assets you have with your custodians (banks, brokers etc. where you have placed your assets). If you have lower assets in your Custody-accounts compared to your liabilities in the BFS-accounts you have a problem and a loss for your company since you have to cover this difference.
Within Bricknoder Broker it is very important to always use the correct Custody account when you perform any transactions that will move assets from one Custody account to another. If you move assets between BFS-accounts it is not certain that you will have to perform a move of those assets in the outside world and thus you will not have to make the same transaction in the Custody world.
Bricknode Broker is called a Sub-ledger system. This means that it should function as a Sub-ledger to the general ledger of your company.
For example, if you have 100 customers with total assets of 100,000 EUR where each customer owns, or has the right to, 1,000 EUR each you should not create one accounting account for each customer in your general ledger system but instead have one accounting account in the general ledger system which might be called Client Assets and use a liability account in your accounting.
The general ledger system will not have any idea of who these 100 customers are, and it does not care! All the individual accounts are created and managed within Bricknode Broker as the Sub-ledger system which keeps track of who owns what on an individual level.
Traditionally a financial institution would have summarized each asset in the liability accounts (like BFS-accounts) in a report and then compared these to the account statements from the custodians. With Bricknode Broker, used correctly, the user only has to list the aggregated assets of the Custody-accounts and then compare these to each account with the custodian.
For those users that utilize MFEX (Mutual Funds Exchange) as a custodian for their investment fund holdings there is an automated function for reconciliation. Bricknode Broker simply contacts the MFEX system and retrieves a list of holdings from the custodian which it then shows in Bricknode Broker and highlights any differences between the Custody-accounts in Bricknode Broker compared to MFEX.
In the near future we will enable this feature for other institutions and then have the whole reconciliation process fully automated for our users.
The transition to fully automated reconciliation will be much easier if the user already is using the Custody-account function of Bricknode Broker and thus we highly recommend that you follow this recommendation.
To actually list the positions in your Custody-accounts you simply navigate to All Positions and then select the account type called Custody Account.
No need to first summarize the total assets for each individual BFS-account but simply list the Custody-account assets and you are done! Custody-account management is included in the core components of Bricknode Broker and if you have not tried it you can sign up for a free trial today!