| Item | Description |
|---|---|
| Error message from M3 | Invoice number XXXXX already exists |
| M3 programs | GLS037, APS050, APS450, APS110 |
| Type of message | Invoice number already exists in M3 |
| Has the invoice already been (partly) posted in M3? | Yes, partly - M3 processes the posting up to the point at which the ERP error is returned. |
What does this message mean?
For M3, an interfaced invoice still processes part of the posting, even though an ERP error is returned. M3 processes up to the point at which the error is returned.
If you then submit the invoice again without taking action in AP Automation or M3, you will get this message.
What to check
Check the audit in AP Automation to see whether this is the first time the invoice has entered an ERP error activity.
How to process the invoice further
There are two routes.
- The invoice has been processed correctly in M3. Move it forward with the option Corrected in ERP, or ask ISPnext through a case to do so.
- The invoice has to be submitted again. First remove the known data in M3 and then submit the invoice again with a unique reference.
More information
If you want to submit the invoice again, first remove the data that is already in M3. See Manual corrections to data in M3.
Once you have corrected the invoice in M3, you move it forward in AP Automation with the option Corrected in ERP. See Moving an invoice forward with "Corrected in ERP".
The article M3 error messages - introduction shows how the M3 error messages are organised and describes the approach that applies to all of them. If you are looking for a specific message, search for the text of the error.