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.
- Push the reference by using the Supplemental data. (CODAT)
- 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)
- 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 -
- Basic error capturing - For Customers, extract and store an error in a FastTrack table.
- Display information back to the current UI. (FT) Tamir is working on it.
- Delete Invoices -
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. - 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 a 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 - Trying to schedule a meeting.
- Gap analysis -
- Analysis to document differences between exporting by batch vs. API
- Define product enhancements to support this.
- Product enhancement request submitted.