Overview
In AR Remittances, the Status column in the Documents table shows the current workflow or processing state of each remittance record.
Document Status helps you quickly identify:
Where a remittance is in the review, reconciliation, or write to SoR process.
Which records need manual attention.
Which records have successfully completed processing.
You can also see the same status on the Document Information page for individual remittances.
Tip: Use the Status filter at the top of the Documents table to quickly find records in a particular workflow state (for example, all “New”, “Failed to Reconcile”, or “Record Needs Review By User” documents).
Table 1. Document Status values – AR Remittances
| Status Value | Description |
|---|---|
| New | Newly created or newly ingested remittance records. These should be reviewed and edited (if required) before writing to the System of Record (SoR). |
| Edited | Remittance records where a user has made changes on the Documents tab or Document Information page (for example, updating Customer, amounts, or line details). These changes are stored and the record may need to be written (or re‑written) to SoR. |
| Record Needs Review By User | During extraction and validation, missing, inconsistent, or invalid remittance fields were identified (for example, totals not reconciling, missing customer, or low‑confidence critical fields). The user should manually review and correct the record before writing to SoR. |
| Failed to Reconcile | A write or reconciliation attempt failed due to validation or matching issues (for example, line‑level amounts do not reconcile with the header total, or necessary SoR data is missing). The record remains in Active Data and requires user review and correction before trying again. |
| Update in Progress | A Write to SoR operation is currently in progress for this remittance (for example, posting or updating a payment in the SoR). The status will update when the operation completes successfully or fails. |
| Record Updated | The Write to SoR completed successfully, and the remittance data has been written/updated in the SoR and synced back to Auditoria. This represents a successful end‑state for the write operation. |
| Failed to sync to SoR after write | The Write to SoR operation itself was successful, but syncing updated data back from the SoR to Auditoria failed (for example, due to an API or connectivity issue). The user may need to investigate the sync issue and, if required, re‑sync or re‑write the record to clear this status. |
| Large File Please Review | Auditoria received a large remittance file (for example, a multi‑page or multi‑tab file above the configured size/complexity threshold). The record is available, but the user should review it carefully to ensure extraction and matching are correct before writing to SoR. |
| Manual Remittance (if enabled) | The remittance record was created manually by a user (rather than automatically ingested from email or connectors). Use this status to distinguish user‑created remittance entries from system‑ingested ones. |
| Record is Not a Remittance | The attachment or file associated with this record is not classified as a remittance document (for example, a statement or unrelated spreadsheet). These records are typically not eligible for Write to SoR under AR Remittances. They can be reviewed and then dismissed if not needed. |
| Written to SoR with File Upload Error | The data for the remittance was written to the SoR successfully, but the file attachment upload failed. Users can manually attach the remittance file in the SoR and then write the record again to clear this error in Auditoria, if desired. |
Working with Document Status
Use New and Edited statuses to identify records that have not yet been written or that have pending changes.
Pay special attention to:
Record Needs Review By User – indicates a remittance that requires manual correction before write.
Failed to Reconcile – indicates a failed attempt to process or write, often due to validation or matching issues.
Large File Please Review – signals complex remittance documents where extraction accuracy should be confirmed manually.
Treat Record Updated as your primary success indicator for a completed Write to SoR operation.
Use Record is Not a Remittance and Written to SoR with File Upload Error to manage edge cases and clean up noise or partial write outcomes.
By monitoring Document Status in AR Remittances, you can quickly see which documents are ready to be written to SoR, which ones need attention, and which have completed processing successfully.