- 13 Oct 2022
- Print
- PDF
Synctera Internal accounts overview
- Updated on 13 Oct 2022
- Print
- PDF
Overview
This document discusses the types, purpose, and reconciliation of internal accounts on the Synctera platform.
The Synctera platform differentiates 3 main types of accounts - customer, external and internal. Internal accounts are Fintech program accounts that have a 1:n corresponding account in the sponsor bank’s core and are used to facilitate timing differences and granularity differences on money movements; help a FinTech to structure their P&L, hold suspense transaction items; depict reserves and reserve usage as well as facilitating necessary treasury money movements. These accounts are vital for the double book keeping of the ledger and for the reconciliation with the bank’s FBO accounts. Jointly these accounts represent the only way to move money in and out of the program.
Introduction to internal accounts
When looking at a Fintech in BaaS, the Synctera ledger is considered a FinTech centric subledger. From an accounting perspective, a FinTech program is defined as the unique combination between a bank and a Fintech.
Each Fintech program has accounts of the Fintech’s end customers (“customer accounts”). These accounts roll up into one or many FBO or Loan GL accounts on a per program level depending on the balance sheet position to which the customer accounts need to aggregate to. In addition, each program by nature has to balance from a double sided book keeping and requires accounts that are non customer accounts. These non customer accounts can be considered the GL accounts of the program (“internal accounts”) and the balances in these accounts are within the program and therefore roll up into FBO accounts on a bank level. The nature of these balances is different and mostly temporary. Therefore these internal accounts roll up into different FBO accounts on a bank level and will ultimately be assigned to different balance sheet positions in the bank’s balance sheet.
Types of internal accounts
The Synctera platform differentiates the following internal accounts and account types:
Mapping to the Bank's core ledger
Equivalents of Internal accounts on the bank’s core ledger:
Secondary postings
The Synctera ledger creates secondary posting as a result of a customer transactions. These postings are typically for reserve or treasury purposes and don’t affect the customer account at the time. Examples of secondary postings are:
- Forced ACH return debit that pushes a customer’s deposit account into a negative balance
- For the amount of the negative balance, a secondary posting would be made to debit the reserve account and credit a allocated reserve account.
- Should the negative balance clear with other postings, the allocated reserve will be automatically posted back
- Should the negative balance be written off, the write of will debit the allocated reservce and credit the customer account which now can be closed
- In a lending program, whenever a line of credit is disbursed or paid back and the Fintech has an agreed buy-back ration of 95%
- When money is disbursed, 95% of the amount will also be debiting the repurchase reserve and crediting the repurchased asset account.
- When transferring this to the program accounts and the balance sheet of the bank, the repurchase account will reduce the liabilities towards the Fintech (it’s a prefunded account) and the repurchased asset account will be an offset to the asset side of the bank
Secondary postings are only incurred on internal accounts.
End of day processing
- Networks and Customers instruct transactions by using their cards or by using the Fintech’s app to transfer money, fund their accounts, mRDC checks, etc.
- This is controlled by Synctera and the Fintech
- At the end of the bank business day, a time mutually agreed between the sponsor bank and Synctera, Synctera will increase the transactional posting date. This happens every day, not just every bank business day. Synctera will now prepare the end of day FBO updated files as separate ACH files and SFTP these files to the sponsor bank
- Currently Synctera does not yet issue the files (coming in Q4/2022)
- Sponsor Bank would use Synctera Money Movement report to make the postings from the respective accounts to the FBO account
- When Automatic FBO Transfer functionality is complete, the bank has to ingest the FBO transfer .csv file(s) to update the respective balances. The FBO transfer .csv files are balanced files
- Currently Synctera does not yet issue the files (coming in Q4/2022)
- The Synctera ledger will transmit all transactions and balances to the reconciliation platform
- This is automated by Synctera
- The networks will settle intra day or next day with the bank. Initially, the Sponsor banks will have to use Synctera reports to split the settlements and post the amounts to the payment rail specific settlement account of each FinTech
- Synctera provides a Settlement Report that allows the bank to make the respective postings
- Synctera will provide automatic .csv Network Distribution files by end of Q4/2022
- Synctera will ingest the balances and transactions of all program accounts from the sponsor bank
- Bank will provide daily files containing the balances and transactions for all program accounts
- Synctera will close the reconciliation loop and post all money that was received into the program or that has left the program in its own ledger based on the movements in the sponsor bank
- Synctera will automate this in Q4/2022
- This is done by Synctera Payments Ops team
Fund flow and timing on internal accounts
FBO transfer - Posting scheme and responsible parties
Settlement accounts
Customer is using their Debit Card and spend $100.
Synctera Ledger
At the end of the FBO transfer, the FBO Transfer Account is 0.
Transactions are now extracted and pushed into Synctera Reconciliation
Sponsor Bank Ledger
All program accounts balances and transactions are now sent to Synctera Reconciliation via extract or Electronic Account Statement.
Synctera Reconciliation will now perform the reconciliation. Synctera Insights provides the amounts to be swept to the Money-in-and-out account. The movement is performed by Synctera Payment Ops.
P&L Accounts
Customer receives $3 interest at the end of the period
Synctera Ledger
At the end of the FBO transfer, the FBO Transfer Account is 0.
Transactions are now extracted and pushed into Synctera Reconciliation
Sponsor Bank Ledger
The Pay-in or Pay-out of P&L values as well as of reserves should happen via the Synctera Platform
All program accounts balances and transactions are now sent to Synctera Reconciliation via extract or Electronic Account Statement.
Synctera Reconciliation will now perform the reconciliation. Synctera Insights provides the amounts to be swept to the Money-in-and-out account. The movement is performed by Synctera Payment Ops
Suspense Accounts
Suspense Accounts are “instead of customer accounts” and therefore will not be transferred in the FBO Transfer. The offsetting posting for all suspense accounts is an internal settlement account
Reserve Accounts
Customer has a forced overdrawal on a checking account for $10. The actual customer transaction is not shown below, only the secondary postings.
Synctera Ledger
At the end of the FBO transfer, the FBO Transfer Account is 0. The transfer line to the FBO would be netting to 0, therefore, therefore, not posting is initiated.
Transactions are now extracted and pushed into Synctera Reconciliation
Sponsor Bank Ledger
There is a periodic trigger (can be daily) to re-stock the reserve account or to pay back overages in the reserve account. This is a treasury function, not part of the FBO Transfer.
All program accounts balances and transactions are now sent to Synctera Reconciliation via extract or Electronic Account Statement.
Synctera Reconciliation will now perform the reconciliation. There is no sweep movement on secondary accounts
Treasury accounts
Treasury Accounts are also secondary accounts are an treated like Reserve Accounts.
Core accounts
Core Accounts do only exist in Synctera’s Ledger and are not transferred to the bank’s ledger.
FBO Transfer - Transaction Types and Granularity
Transaction types
Each movement in Synctera will have its own transaction types and addenda information that is provided in the files.
Here is the list of transaction types:
- FBO Transfer (Debit) - addenda specifies which Account is Transferred
- FBO Transfer (Credit) - addenda specifies which Account is Transferred
- ACH Settlement (Debit)
- ACH Settlement (Credit)
- Wire Settlement (Debit)
- Wire Settlement (Credit)
- ICL Settlement (Debit)
- ICL Settlement (Credit)
- AFT/OCT Settlement (Debit)
- AFT/OCT Settlement (Credit)
- P&L Settlement(Debit)
- P&L Settlement(Credit)
Granularity
For Automated Movements, Synctera will use the external networks abilities and standards and the best level of granularity for reconciliation as a guidance to perform the FBO Transfers. Goal is it to create and easy alignment between the Network, the accounts and the different cut-off times.
Additional Diagrams