The Subledger API Transaction Matching process allows you to programmatically push transaction information from your subledger, bank, or other source systems into FloQast. You will then use FloQast's AutoRec Matching functionality to review and match transactions to your ERP data. To implement this process, you and/or your technical team must leverage two publicly available FloQast APIs.

To display submitted data in FloQast, you must enable the Subledger Matching feature on the applicable Reconciliations.

Once your FloQast Reconciliations have been enabled for Subledger API services, you can create an API key and begin following the steps below:

1. Access your FloQast Reconciliation data:
   Begin by pulling down reconciliation data from within FloQast so that we can properly identify the reconciliation accounts using their internal IDs.
   • This can be done via the GET Reconciliations API endpoint with your valid API key.
     
     
2. Match the FloQast Reconciliation IDs with transactions from your subledger source systems:
   The data you receive from Step 1 includes not just IDs but also account names, system IDs, and additional identifying information. This data allows you and/or your team to map the proper subledger transactions to their respective FloQast reconciliation IDs.
   
   
3. Organize the data:
   Whether referencing data from one subledger application or multiple, FloQast requires that the data be prepared into a specific format. This reduces the likelihood of errors when ingesting and processing data.
   • This format can be found on our developer documentation HERE.
     
     
4. Send the data into FloQast:
   Once your data has been organized into our API’s required format, you can call our subledger transactions API endpoint to accept and process the data.
   • When sending in transactions for accounts receivable or accounts payable, we recommend sending all open transactions so that the aging reports capture all currently open invoices and not just the invoices that occurred during the set month.
5. Repeat as necessary:
   This is a programmatic process that reduces the need to manually upload files repeatedly. You can repeat this process as frequently as your business needs require. We typically recommend that clients start with a refresh frequency of 1 hour. If you currently use Cloud Connect today, we recommend sending us subledger data on the same cadence as the Trial Balance.

A high-level overview of the process described above can also be found in the attached graphic:

• If you have any additional questions about functionality, implementation, or expected behaviors, please feel free to contact your ASM.