ClerkedHelp Center

Resolve validation issues

Understand validation issues, correct the cause, and recheck the current invoice state.

What to do

  1. Read the issue. Open the invoice’s exception or warning indicator to see the affected area, explanation, and available action. Checks can differ by company and by the point in invoice processing.

  2. Open the affected context. Use the available field link or action to find the field, line, match, or document detail that produced the result. In a line-items section, a validation icon opens the affected field. Some issues include extra details or a guided decision, such as comparing possible duplicates.

  3. Correct the cause. Update a wrong invoice value, coding choice, vendor, match, or other supported input. Complete a required review when the data itself is correct.

  4. Wait for the new result. Saving a change can run the applicable checks again. Confirm the issue clears, changes to a warning, or leaves the intended review task.

  5. Use the available action. At an intermediate validation step, select Submit for Review. At the final validation step, a blocking issue uses Fix exception for one displayed exception or Fix N exceptions when N is the displayed count. Select it to reach the affected field, correct it, and wait for the save before submitting again. At the first AP review, before anyone has recorded a decision, make corrections here and select Submit for Review instead. Return for review is the validation-phase action after review has progressed and requires a reason. Return to AP is the approval-phase action when it is available, requires a reason, and restarts AP validation without requiring a field edit. Returning preserves saved facts and history, retires the current review cycle, and requires fresh approvals. Clerked checks the current workflow when you submit; after the blocking issue clears, Submit for Approval returns. Review findings and warnings remain actionable.

  6. Escalate an unavailable resolution. Contact support with the invoice identifier and exact issue text when the required action is missing. Do not repeatedly edit an unrelated field just to trigger another check.

Recheck export readiness

Some integrations also check that the invoice and its attachments are ready to export before final submission or approval. A missing PDF or an attachment over the size limit can stop that action even when the invoice fields are valid. Some checks run before export and stop an invoice that your connected accounting system would reject.

If export readiness is the remaining issue, Submit for Approval or Approve can stay available so you can run the check again. The invoice cannot finish validation or approval while the issue remains. After the PDF or another external requirement is repaired, retry the available action. You do not need to edit an unrelated field or reload the page. Saving a field change alone does not clear an unresolved export-readiness message. A review vote that still leaves other reviewers to act does not clear it either.

Failed ERP exports appear in the Export Failed disclosure. When AP can act, a Resolve Task directs the export owner to the available recovery actions.

If submission reports that accounting information changed during review, inspect the refreshed values before submitting again. Clerked may return the invoice to AP when a selected accounting reference changes after review.

Announced in Clearer invoice review, validation, and Return to AP.