Error messages in the Review Center

Error message	Meaning	Reason	Occurrence
Workflow errors
An error occurred while triggering the BOD.	A system error occurred while attempting to create and send the Business Object Document (BOD) to M3 for processing.	This could be due to data formatting issues, incorrect API endpoints, network connectivity problems, or a temporary M3 system outage.	At the final stage of the Review Center workflow, after an invoice has been corrected and submitted for processing.
Header-related errors
The Supplier's invoice number is missing.	The unique invoice number assigned by the supplier is missing from the extracted data.	This is a mandatory field in M3 to prevent duplicate payments and tracking purposes. The OCR may have failed to find or read this number.	This error is triggered during the final data validation before creating the BOD, as M3 requires this number.
The Invoice date is missing.	The invoice date, a mandatory field for creating a supplier invoice in M3, was not found on the document.	The date was either not present on the invoice, or the IDP could not read it due to an unusual format or placement.	This error is flagged during the header validation stage, as the invoice date is critical for financial posting and payment term calculations.
Total amount is missing.	The invoice's total amount due could not be extracted from the document.	The total amount is a fundamental requirement for creating an invoice record. Its absence is a critical data extraction failure.	This is a Missing Information error that occurs during the initial validation check, as the total amount is necessary for header-level validation.
Supplier information was not found on the invoice.	Essential supplier identification data (such as VAT registration number, supplier name, or address) was not found on the invoice document.	The invoice layout is non-standard, or the required supplier identifiers are not present on the document. Without this, the system cannot proceed to validate the supplier in M3.	This error is flagged during the initial data validation check after OCR, when the system confirms that all mandatory fields for supplier identification have been captured.
No matching supplier was found in M3.	The supplier details extracted from the invoice, such as VAT number, and name, cannot be matched to a unique, active supplier record in the M3 supplier master (CRS620).	The supplier may not exist in M3; the extracted details may be incorrect, or multiple suppliers may match the provided criteria, causing ambiguity.	This appears after the supplier lookup phase, when the system attempts to reconcile the extracted supplier information with M3 master data.
The purchase order was not found in M3 or has an incorrect status.	The Purchase Order number referenced on the invoice header is not a valid or open PO in M3 (PPS200).	The PO number may be incorrect; it may have been fully invoiced already, or it could be closed or deleted in M3.	This error is triggered during the header validation step when the system first attempts to find and validate the referenced PO.
The delivery number was not found in M3.	A delivery note number, either at the header or line level, specified at the on the invoice header level could not be validated against a record in M3.	The delivery number may have been transcribed incorrectly by the OCR, or the corresponding delivery has not been registered in M3, such as in (PPS360).The header delivery note number is either incorrect or not yet registered in M3 delivery files.	This occurs during header validation when an invoice is being matched based on a delivery note instead of a PO number.
The supplier does not match the supplier on the purchase order.	The supplier identified on the invoice is different from the supplier registered on the referenced Purchase Order (PO) in M3 (PPS200).	The wrong PO number may have been referenced on the invoice, or the invoice was incorrectly sent by a different legal entity of the supplier.	After both the supplier and PO have been identified, and the system cross-references the two records.
Order or line charge details were not found on the invoice.	The invoice indicates header-level or line-level charges (e.g., freight, handling), but the RPA was unable to extract the specific details like charge description or amount.	The charge information may be in an unusual position on the invoice, be in a non-standard format, or be missing entirely despite a total amount suggesting charges exist.	During the validation phase when header charges are expected but cannot be identified from the extracted data.
Line-related errors
The item or alias on the invoice was not found in M3.	The item code or alias number extracted from an invoice line does not exist in the M3 item master (MMS001) or the item alias file (MMS025).	The supplier may have used a new or incorrect item number, or the alias mapping for this supplier item number has not been configured in M3. The item may also be inactive (status < 20).	This error occurs during the line-item validation step, specifically when matching invoice lines to M3's item data.
The purchase order line number was not found for item.	The system could not automatically match an invoice line to a specific line on the Purchase Order.	This is often due to a mismatch in item code, quantity, or unit price between the invoice and the PO line. It can also occur if the same item appears on multiple PO lines, creating ambiguity.	This appears during the automated matching process for PO-based invoices, when line-level reconciliation fails.
The delivery number was not found in M3.	A delivery note number specified at the invoice line level is not found or is invalid in the M3 system.	The delivery number may have been transcribed incorrectly by the OCR, or the corresponding delivery has not been registered in M3, such as in (PPS360).	This appears when validating line items that have individual delivery note references, and the system cannot find a matching delivery record.
The charge description on the invoice could not be verified.	A charge (either at the header or line level) could not be validated against the defined business rules or costing elements in M3.	The charge description may not have a corresponding mapping in the ION Business Rules, or the resulting costing element is not configured in M3, such as in (PPS280).	When processing additional charges on the invoice, after the main line items have been validated.
Invoice U/M does not match purchase order line U/M for item.	The Unit of Measure (U/M) for an item on the invoice (e.g., "Box") is different from the U/M specified on the Purchase Order (e.g., "Each").	This mismatch prevents the system from accurately validating the invoiced quantity against the PO quantity, as the units are not comparable.	This validation error occurs during the line-item matching process when the system compares the invoice line details against the corresponding PO line details in M3.
The item number is missing on the invoice.	An invoice line is missing the item number or alias needed to identify the product or service being billed.	The IDP failed to extract the item code from the line item on the invoice document, making it impossible to match the line to the PO.	This is a Missing Information exception that shows after data extraction when the system detects that a mandatory field for a line item is empty.
Total amount is missing.	The invoice's total amount due could not be extracted from the document.	The total amount is a fundamental requirement for creating an invoice record. Its absence is a critical data extraction failure.	This is a Missing Information error that occurs during the initial validation check, as the total amount is necessary for header-level validation.

Workflow errors

An error occurred while triggering the BOD.

A system error occurred while attempting to create and send the Business Object Document (BOD) to M3 for processing.

This could be due to data formatting issues, incorrect API endpoints, network connectivity problems, or a temporary M3 system outage.

At the final stage of the Review Center workflow, after an invoice has been corrected and submitted for processing.

Header-related errors

The Supplier's invoice number is missing.

The unique invoice number assigned by the supplier is missing from the extracted data.

This is a mandatory field in M3 to prevent duplicate payments and tracking purposes. The OCR may have failed to find or read this number.

This error is triggered during the final data validation before creating the BOD, as M3 requires this number.

The Invoice date is missing.

The invoice date, a mandatory field for creating a supplier invoice in M3, was not found on the document.

The date was either not present on the invoice, or the IDP could not read it due to an unusual format or placement.

This error is flagged during the header validation stage, as the invoice date is critical for financial posting and payment term calculations.

Total amount is missing.

The invoice's total amount due could not be extracted from the document.

The total amount is a fundamental requirement for creating an invoice record. Its absence is a critical data extraction failure.

This is a Missing Information error that occurs during the initial validation check, as the total amount is necessary for header-level validation.

Supplier information was not found on the invoice.

Essential supplier identification data (such as VAT registration number, supplier name, or address) was not found on the invoice document.

The invoice layout is non-standard, or the required supplier identifiers are not present on the document. Without this, the system cannot proceed to validate the supplier in M3.

This error is flagged during the initial data validation check after OCR, when the system confirms that all mandatory fields for supplier identification have been captured.

No matching supplier was found in M3.

The supplier details extracted from the invoice, such as VAT number, and name, cannot be matched to a unique, active supplier record in the M3 supplier master (CRS620).

The supplier may not exist in M3; the extracted details may be incorrect, or multiple suppliers may match the provided criteria, causing ambiguity.

This appears after the supplier lookup phase, when the system attempts to reconcile the extracted supplier information with M3 master data.

The purchase order was not found in M3 or has an incorrect status.

The Purchase Order number referenced on the invoice header is not a valid or open PO in M3 (PPS200).

The PO number may be incorrect; it may have been fully invoiced already, or it could be closed or deleted in M3.

This error is triggered during the header validation step when the system first attempts to find and validate the referenced PO.

The delivery number was not found in M3.

A delivery note number, either at the header or line level, specified at the on the invoice header level could not be validated against a record in M3.

The delivery number may have been transcribed incorrectly by the OCR, or the corresponding delivery has not been registered in M3, such as in (PPS360).The header delivery note number is either incorrect or not yet registered in M3 delivery files.

This occurs during header validation when an invoice is being matched based on a delivery note instead of a PO number.

The supplier does not match the supplier on the purchase order.

The supplier identified on the invoice is different from the supplier registered on the referenced Purchase Order (PO) in M3 (PPS200).

The wrong PO number may have been referenced on the invoice, or the invoice was incorrectly sent by a different legal entity of the supplier.

After both the supplier and PO have been identified, and the system cross-references the two records.

Order or line charge details were not found on the invoice.

The invoice indicates header-level or line-level charges (e.g., freight, handling), but the RPA was unable to extract the specific details like charge description or amount.

The charge information may be in an unusual position on the invoice, be in a non-standard format, or be missing entirely despite a total amount suggesting charges exist.

During the validation phase when header charges are expected but cannot be identified from the extracted data.

Line-related errors

The item or alias on the invoice was not found in M3.

The item code or alias number extracted from an invoice line does not exist in the M3 item master (MMS001) or the item alias file (MMS025).

The supplier may have used a new or incorrect item number, or the alias mapping for this supplier item number has not been configured in M3. The item may also be inactive (status < 20).

This error occurs during the line-item validation step, specifically when matching invoice lines to M3's item data.

The purchase order line number was not found for item.

The system could not automatically match an invoice line to a specific line on the Purchase Order.

This is often due to a mismatch in item code, quantity, or unit price between the invoice and the PO line. It can also occur if the same item appears on multiple PO lines, creating ambiguity.

This appears during the automated matching process for PO-based invoices, when line-level reconciliation fails.

The delivery number was not found in M3.

A delivery note number specified at the invoice line level is not found or is invalid in the M3 system.

The delivery number may have been transcribed incorrectly by the OCR, or the corresponding delivery has not been registered in M3, such as in (PPS360).

This appears when validating line items that have individual delivery note references, and the system cannot find a matching delivery record.

The charge description on the invoice could not be verified.

A charge (either at the header or line level) could not be validated against the defined business rules or costing elements in M3.

The charge description may not have a corresponding mapping in the ION Business Rules, or the resulting costing element is not configured in M3, such as in (PPS280).

When processing additional charges on the invoice, after the main line items have been validated.

Invoice U/M does not match purchase order line U/M for item.

The Unit of Measure (U/M) for an item on the invoice (e.g., "Box") is different from the U/M specified on the Purchase Order (e.g., "Each").

This mismatch prevents the system from accurately validating the invoiced quantity against the PO quantity, as the units are not comparable.

This validation error occurs during the line-item matching process when the system compares the invoice line details against the corresponding PO line details in M3.

The item number is missing on the invoice.

An invoice line is missing the item number or alias needed to identify the product or service being billed.

The IDP failed to extract the item code from the line item on the invoice document, making it impossible to match the line to the PO.

This is a Missing Information exception that shows after data extraction when the system detects that a mandatory field for a line item is empty.

Total amount is missing.

The invoice's total amount due could not be extracted from the document.

The total amount is a fundamental requirement for creating an invoice record. Its absence is a critical data extraction failure.

This is a Missing Information error that occurs during the initial validation check, as the total amount is necessary for header-level validation.