Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  •  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)
  •  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 -
    •  Basic error capturing - For Only for Customers, extract and store an error in a FastTrack table per push.
    •  Display information back to the current UI. (FT) I am Tamir is working on it. Extend the errors for all the action types.
  •  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 -
  •  
  • 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 (Sarith)- 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 - Trying to schedule a meeting
    •  Push and Get all the command types from the Dlls
    •  Check the data in the MYOB account
    •  Test Tracking Categories and Transactions Types.
    •  Map all the columns for previous files of MYOB and check nothing is missing in the JSON.
  •  Gap analysis -
    •  Analysis to document differences between exporting by batch vs. API
    •  Define product enhancements to support this.
    •  Product enhancement request submitted.

...