| Item | Description |
|---|---|
| Error message from M3 | Client received SOAP Fault from server: error in invoicing item line: order number: [<order>], line number: [<linenumber>], subline number: [##], receipt number: [<receipt number>] reason: line already fully invoiced Please see the server log to find more detail regarding exact cause of the failure. |
| M3 programs | APS370, APS200 |
| Type of message | Receipt line already fully invoiced |
| Has the invoice already been (partly) posted in M3? | Yes, partly - the receipt line has already been consumed on another invoice. Check this in M3. |
What does this message mean?
M3 cannot post the invoice line because the receipt line of the purchase order has already been fully invoiced.
What to check
1. Has the invoice been submitted before?
Has this invoice been submitted again from a Reassess invoice not posted in ERP (Log) activity, where it returned an error earlier? Then act on that first error, not on this message.
2. Is this the first time?
- Use the advanced search in AP Automation to search on this order number.
- Verify whether this receipt line is also active on another invoice that has already been completed or posted.
How to process the invoice further
- Remove the data already known in M3 for this invoice.
- Correct the invoice in AP Automation by no longer having the consumed line active on this invoice.
- Process 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.
The platform also has a business validation that catches this situation: Validate if Order Lines are Already Present on Another Invoice.
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.