...
Portlet Description | FlowAP Document Status | Status Count |
|---|---|---|
Received FlowAP Documents | Received | Total count of FlowAP documents with received status. |
Converted FlowAP Documents | Converted | Total count of FlowAP documents with converted status. These are FlowAP documents that have been successfully converted to NetSuite transactions. |
FlowAP Documents for Processing | Processing | Total count of FlowAP documents currently undergoing processing. |
FlowAP Documents for Conversion | Converting | Total count of FlowAP documents currently undergoing conversion. |
Incomplete FlowAP Documents | Incomplete Duplicate Reference Number | Total count of FlowAP documents that did not complete the processing stage. Documents that failed to be processed have issues related to XML data. This list also includes FlowAP documents with Reference Numbers that are already used by an exiting vendor bill/credit. |
Failed FlowAP Documents | Failed | Total count of FlowAP documents that did not complete the conversion stage. Documents that failed to be converted have issues related to NetSuite data. |
...
Fix incorrectly configured FlowAP configuration.
Resolve XML-related issues by getting a new XML from the scanning service or editing/replacing the XML errors.
Failed subsidiary lookup may be because of due to mismatching lookup criteria between the XML data and the subsidiary record data.
Failed vendor lookup may be because of mismatching lookup criteria between the XML data and the vendor record data.
Override transaction data by manually selecting the transaction data fields (e.g.: Vendor, Subsidiary etc).
| Note |
|---|
When a transaction data field is overridden, the FlowAP Document status is automatically changed into “For Processing”. The FlowAP document must start from the Processing stage to override the transaction data that was already parsed. |
FlowAP Document Status: Failed
...