Skip to main content

Validation failure notice

The Validation Failure notice means one or more validation rules or hooks generated blocking errors on this invoice. The notice carries the full list of errors. The invoice waits in Pending Validation status until you fix the underlying issues and re-run validation.

Where the notice appears

The notice appears as a row inside the Document notices panel on the left side of the invoice detail page (between the breadcrumb and the document viewer). The panel header reads N Exceptions. Click the header to expand. The Validation Failure row shows a count of errors and a short summary of the first error.

The Document notices panel is on the left side of the page. Click the panel header to expand it, then click the Validation Failure row to see every error.

What triggers it

A validation failure notice is a roll-up. When validation runs and any rule or hook produces a result with severity error, the invoice surfaces a single Validation Failure notice that lists every error that fired. You see one notice on the invoice, even if several different rules contributed errors.

What the notice contains

The notice shows:

  • The total number of errors.
  • The first error field and message (so you have a starting point).
  • A list of every error, each with:
    • The field affected.
    • The error code.
    • A human-readable message.
    • The severity (always error in this list, since warnings do not produce a validation failure notice).
    • The category (match, required, business_rule, format, sum_check, or general).

Each error appears as its own row inside the expanded Validation Failure section. Click any error row to scroll the right-side panel to the field that error is on — the field highlights briefly in purple so you can see exactly which one needs attention.

Resolve the notice

For each error in the list:

  1. In the expanded Validation Failure section of the Document notices panel, click the error row. The right-side panel scrolls to the affected field and the field highlights in purple for ~2 seconds.
  2. Click the field itself to edit. The fix depends on the category:
    • required: fill in the missing value.
    • format: change the value to match the required format.
    • match: reconcile the mismatch (often a matching issue with the PO or receipt).
    • business_rule: read the message; the integration hook explains what is wrong.
    • sum_check: line item totals do not add up to the invoice total. Either correct a line item, correct the total, or correct the tax / fees.
    • general: read the message and apply the suggested fix.
  3. Repeat for every error.

Once you have addressed every error, click the Validate button in the action bar at the top-right of the invoice detail page (the action bar shows Reject / Submit / Hold / Validate / Cancel Invoice — Validate appears once a validation failure is present). Validation re-runs against the current state. See Soft Revalidation for more on this action.

If everything now passes, the notice clears and the invoice moves out of Pending Validation. If errors remain (you missed one, or the fix introduced a new one), the notice updates with the new error list. Repeat as needed.

Fix many errors at once with Copilot

If multiple line items have the same kind of error (for example, all line items are missing a Department dimension), Copilot can apply the fix in one prompt: "Set Department to Marketing on every line item." Review the diff and accept. Then click Validate to re-run.

When the same error keeps coming back

If you fix the field, click Validate, and the same error still fires, the issue is one of:

  • The field still does not match the rule's expectation. Re-read the message; you may have fixed something close to but not exactly what was required.
  • A separate rule is failing on the same field. Check the full error list, not just the first one.
  • An admin has set the rule severity in a way that always fires for your data. If your team finds a rule incorrect for your business, see Configuring rule severity to discuss adjusting it.

Acknowledge a warning instead

If the issue you are seeing is a warning rather than an error, you can acknowledge it and proceed. The acknowledgment dialog appears when you take an action that depends on resolving warnings. See Soft Revalidation.

We use cookies to understand how visitors use our site.