Customer Invoice In Error

Hi ​@Ram2212 ,

From the look of it, the correction invoice itself is probably not the real issue. The failure seems to be on the auto-created zero commission invoice, and the message suggests that when IFS tries to book it, it is referencing a ledger item that is no longer there / not created / already cleared. The exact same question was posted on IFS Community on March 23, 2026, but there was no accepted reply yet.

What I would check first:

1. Original invoice / correction invoice relationship
   • If the correction invoice had no value or quantity change, IFS may have auto-processed it as paid/cleared.
   • Then the commission invoice may still be trying to link back to the original ledger item, but that ledger item is already closed or was never created in the way the commission logic expects.
2. Commission setup
   • Check whether the commission posting logic expects an open customer ledger item even when the commission invoice is zero value.
   • I have seen these “Invoice.ACCERROR1” messages behave as generic accounting/booking wrappers, where the real cause is in the underlying posting or object reference rather than the text shown to the user. Similar community threads note that ACCERROR1 is often generic and needs drilling into the detailed posting/error context.
3. Customer Invoice with Errors / posting details
   • Open the failed invoice in Customer Invoice with Errors and inspect:
     • posting lines
     • commission invoice reference
     • payment/ledger status
     • whether there is a linked ledger item ID that no longer exists
4. Background job / event timing
   • Sometimes the zero invoice is generated after the correction is already marked paid, so the commission logic is running against a document state it does not expect.

My best guess is:

• zero-value correction invoice auto-cleared
• zero commission invoice still attempts ledger booking
• booking routine cannot find a valid ledger item
• therefore ORA-20105: Invoice.ACCERROR1: Error (The Ledger Item does not exist.)

What I’d try next in practice:

• check whether this only happens for zero correction invoices
• test the same flow with a small non-zero correction
• compare the failing invoice against a normal commission invoice that books correctly
• review whether this is a known defect in your Apps/Cloud update level, because community replies on similar ACCERROR1 invoice-booking issues often end up as IFS support cases / bug fixes rather than pure setup mistakes.