Understanding Notices
Notices are alerts that Mod AI creates when it detects an issue on a document that needs human attention. They are the system's way of telling you something needs to be reviewed, corrected, or verified before an invoice can move forward.
Where Notices Appear
Notices show up in two places:
- Invoice detail page -- Open any invoice and look for the notices section. Each notice includes a description of the issue and options to resolve it.
- Invoice list -- A badge count on each invoice row tells you how many unresolved notices exist without having to open the invoice.
Blocking vs Non-Blocking Notices
Not all notices are equal. Some prevent the invoice from moving forward, while others are informational.
- Blocking notices must be resolved before the invoice can proceed to the next stage (e.g., approval). For example, an Unknown Vendor notice blocks the invoice because the system cannot process a payment without knowing who to pay.
- Non-blocking notices are warnings or informational alerts. They do not prevent the invoice from advancing, but you should still review them. For example, a Low Confidence Extraction notice warns you that some fields may be inaccurate.
Blocking notices are clearly marked in the interface. You will see which notices must be resolved before you can submit the invoice for approval.
Severity Levels
Each notice has a severity level that tells you how urgently it needs attention:
| Severity | Meaning | Action Required |
|---|---|---|
| Critical | Must resolve. The invoice cannot proceed until this notice is addressed. | Resolve immediately. |
| Warning | Should review. Something looks off and could cause problems if ignored. | Review and resolve or dismiss. |
| Info | Awareness only. The system is flagging something for your visibility. | Review at your discretion. |
Notice Types
Mod AI detects a range of issues across your documents. Here is every notice type with a brief description:
| Notice Type | Description |
|---|---|
| Unknown Vendor | The vendor on this invoice does not match any vendor in your directory. |
| Duplicate Invoice | This invoice may be a duplicate of another invoice already in the system. |
| External Sender | The email that delivered this invoice came from an unrecognized address. |
| Banking Info Changed | The banking/payment information on this invoice differs from what is on file. |
| Line Item Sum Mismatch | The sum of line item amounts does not match the invoice total. |
| Low Confidence Extraction | The AI could not confidently extract one or more fields from the invoice. |
| Missing Purchase Order | This invoice does not have a matching purchase order. |
| Attachment Processing Failed | Mod AI was unable to process one of the attachments on this invoice. |
| Document Unreadable | The AI cannot read the document -- it is too blurry, dark, or otherwise unreadable. |
| Duplicate Purchase Order | A potentially duplicate purchase order was detected in the system. |
| Duplicate Receipt | A potentially duplicate receipt was detected in the system. |
| Price Variance | The invoiced price for a line item differs from the expected price in your item master. |
We are always adding new notice types. If you need a custom notice for your workflow, reach out to us at support@usemod.ai.
Resolving Notices
Each notice type has its own resolution steps, but the general workflow is the same:
- Open the invoice detail page.
- Find the notice in the notices section.
- Review the issue described in the notice.
- Take the appropriate action -- match, correct, dismiss, or escalate.
Once all blocking notices are resolved, the invoice can proceed to the next stage.
Learn More
- Actions -- Tasks triggered by notices or created manually to resolve issues.
- Reviewing an Invoice -- Walkthrough of the invoice detail page.
- Invoice Statuses -- Understand where invoices are in the lifecycle.