A document moves to Error status when something in the processing pipeline breaks — either during extraction or when pushing data to your ERP. The document isn't lost; you can usually fix the issue and reprocess it.
Reading the error
Open the document. You'll see:
A red error banner at the top with a summary of what went wrong
The activity timeline at the bottom shows a "Processing Failed" event — click it to expand the full error details
Common causes
ERP connection error — the connection to Epicor, SugarCRM, or another system returned an error. Usually means the connection is offline or credentials have changed.
Validation failure — a required field couldn't be matched or resolved against your ERP data (e.g., unknown customer code, invalid GL account)
Extraction failure — the document couldn't be read cleanly (corrupted file, unsupported format, password-protected PDF)
Fixing and reprocessin
Read the error message and identify the cause
Fix the underlying issue — correct a field value, restore the connection, re-upload a cleaner file
Click Reprocess (or Retry in the error banner) to run the document through again
You can also reprocess multiple Error documents at once from the Documents list — select them and use the bulk action.
Still failing after retry? Contact support@fluenterp.com with the document ID and the error text from the timeline.