When AP Automation submits an invoice to M3 and M3 cannot process it, an error message is returned. You see that message in AP Automation on the invoice, in an ERP error activity.
This section describes the most common M3 error messages. Each message has its own article, so you can search directly for the text you receive.
This article is the starting point of that section. It does not contain a list of all messages, but shows how they are organised and describes the approach that applies to all of them.
What does each article contain?
- The error message as M3 returns it.
- What the message means and what to check in M3 or in AP Automation.
- How to process the invoice further in AP Automation afterwards.
Each article also states whether the invoice has already been fully or partly posted in M3 at that point. That determines whether you may submit the invoice again or have to correct it first.
Where to find which message
The error messages are spread across four subsections. If you know the text of the error, search for it. If you do not, choose the subsection that is closest to your situation.
| Subsection | What you will find here |
|---|---|
| M3 - Procedures and reference | The procedures that apply to several messages: removing data in M3, moving an invoice forward with "Corrected in ERP", and which M3 program to use for what. |
| M3 - Error messages during validation and posting | NOK messages and posting errors: rejected coding, exceeded tolerances, missing configuration and master data. |
| M3 - Error messages about the connection to M3 | Time-outs and connection errors between AP Automation and the M3 or MEC server. |
| M3 - Error messages when reversing or resubmitting | Messages that occur when an invoice is already fully or partly present in M3. |
Always act on the first error message
An invoice that has been submitted before may return a different message on a second attempt than it did the first time. That second message is then a consequence, not a cause.
When to contact support
Raise a ticket with ISPnext when the article tells you to, or when the message keeps occurring after you have carried out the checks described. State the following in the ticket:
- Which invoice this concerns and in which activity the invoice is stuck.
- The exact error message from AP Automation.
- What you checked in M3 and what the outcome was.
More information
Is the recording of an invoice failing without a specific M3 message? Then the general guide ERP Error Messages applies, which describes what to check first for all ERP packages.
Is a message missing from this overview, or is something incorrect? Report it through a ticket with ISPnext and we will extend the set.
Disclaimer
These articles describe the most common M3 error messages when using AP Automation. Your own configuration, permissions and M3 version may differ. Always follow your organisation's change management process and involve your M3 administrator or implementation partner where needed.