NACHA files are uploaded by banks to trigger ACH payments.The information we collect from you will be used to configure the Synctera platform to generate your bank-specific NACHA files.To complete the ACH NACHA file configuration in Synctera’s system, Synctera will need the information in Exhibit A.
The Synctera team will need information on the Bank’s holiday calendar and end-of-day cut off times in order to configure NACHA file generation timings that fit the Bank’s clearing windows. Synctera will need the information in Exhibit B.
Synctera establishes a SFTP with you in order to process incoming and outgoing NACHA files. Synctera will need the public SSH key from you. Please see Exhibit C.
Synctera recommends that you set up a new Fed Direct for Synctera FinTechs. If you already have Fed Direct via your core banking platform, we encourage you to stand-up Fed Direct separately.
Synctera will test your ACH setup end-to-end by opening accounts at your bank as a FinTech proxy. This will allow Synctera to confirm that your configurations are correct in the Synctera Platform, and that NACHA files are generated as expected.Synctera will need applications forms from you to open the following General Ledger (GL) accounts:
FBO account
Operational account
ACH settlement account
Card settlement account
Synctera’s Finance team will then review the application forms and make the necessary requests to open accounts.
When the FinTech originates ACH outgoing debits/credits, the external banks might have problems processing the credit/debit orders for the FinTech. In that scenario, the external will generate a return.Synctera will receive incoming returns for processing. Returns are linked to the original outgoing credit or debit by their ‘original trace Id’ field, therefore when making un-suspense decisions, we will need to check the original debit/credit and trace ID. Typically, the return will be posted to the suspense account for manual processing.