When the document has finished processing, it can be one of the following:

  • ready
  • not_ready
  • trash

Also, if the document contained multiple transactions, it will become:

  • parent

The usual flow of document states is:

  • uploaded > extracting > ready
  • uploaded > extracting > templating (if extracting failed) > ready
  • uploaded > extracting > trash (if the document meets certain criteria, like a small png image that is part of email signature)
  • uploaded > extracting > templating > not_ready (if we did not capture relevant fields or the document was not an invoice)
  • uploaded > file_duplicate (if we find the same hashsum of a previously uploaded file in the same folder)
  • uploaded > file_duplicate > extracting > ready (if the user confirms that he wants to process again)
  • uploaded > file_duplicate > extracting > templating > ready
  • uploaded > extracting > data_duplicate (if the supplier name and invoice number match to a different invoice in the folder)
  • uploaded > extracting > templating > data_duplicate

The following statuses are used for exporting into Xero and Quickbooks:

  • exporting
  • auto_exporting
  • exported
  • auto_exported

So these are not relevant for you. Although if you connect the folder to Xero and export, you could see one of these. Also, they can change to:

  • repairing > ready
  • data_duplicate (if manually edited and there is a match to another invoice)
  • trash
  • exported > exporting > exported (when you re-export)

The user / API can send the document for repair - this means that the user asks us to repair our "fingerprint / template" ... it is the equivalent of processing

So the flow could be:

  • uploaded > extracting > ready > repairing > ready

We no longer use the following:

  • verifying
  • verifying_individual
  • extracting_items
  • extracted
Did this answer your question?