Codat & FastTrac360 | Guided Evaluation Summary and Next Steps

Owned by Tamir Ezer, created
Last updated: 01 August 2023
2 min read

This page contains all the steps needed for a proof of concept related to pushing data through a CODAT API, which will replace the file loading.

Customer -

Push all the customers from the FastTrack table or Update if it does not exist.
Get the Customer Key after each push and store it in a FastTrack table.

Sales -

Push all the Invoices from the FastTrack table.
Get the Invoice Key after each push and store it in a FastTrack table.
Push single and multiple items per invoice.

Journals -

Push all the Journals from the FastTrack table.
Get the Journal Key after each push and store it in a FastTrack table.
Push Multi transaction types per one JSON.
Check there is no limit to the number of transactions per push. (CODAT)

Supplemental data -

Push the reference.
Push Custom Fields.

Codes -

Extract from CODAT all the charts of accounts and store them in FastTrack tables.
Extract from CODAT all the Tracking Categories and store them in FastTrack tables.

Error handling -

Delete -
This functionality is currently only supported for QuickBooks Online integration. For Xero, the process is to update the invoice status to VOID using the PUT Invoice call.

Solving Asynchornize processes - When I try to run not in a debug mode, I found out that the GUID is not populated in the Debtor's table because the process hasn't been finished

Mapping - Pushing all the fields from the FastTrack tables. (Currently, we are pushing only a few). (FT)

Un-invoice in Sales and Unpaid in Wages - These can be pushed as journal entries and reversal entries. Verify the process with CODAT.

Missing Accounts - Create a pre-validation step to capture all the missing accounts (FT)

Run the same process for MYOB -

Gap analysis -