Invoicing (cisli)

With LN 10.2 or later, the Invoicing package is restructured to allow for better handling of Invoices. This specifically counts for the way Invoice data is calculated, posted to the General Ledger, and for archiving/deleting of invoicing data. The introduction of a new Invoicing 360 session required an improved data model.

As a consequence, the data in the ‘existing’ invoicing tables require conversion. These conversions will apply to the different statuses of the Invoice (Lines);

• Invoice Lines that still must be composed (for example; On Hold, Canceled and Confirmed): do not change these lines. The lines will be processed by the Data Upgrade Engine (DUE).
• Invoice Lines that have status Composed/Printed/Posted: see further in this section for the comments on Invoice level.
• Invoice Lines/Invoices that have status Composed: these are decomposed. The Billing Request remains and contains the same Invoice Lines. The Billing Request must be Composed/Printed/Posted again in LN 10.2 (or later version) against the new logic and data model.
• Invoice Lines/Invoices that have status Printed: These must be processed till no Invoice Lines/Invoices remain with status Printed! This is described later.
• Invoice Lines/Invoices that have status Posted: These are processed by the Data Upgrade Engine (DUE) and do not require further manual processing before the installation and upgrade of LN 10.2 (or later versions). As this data becomes redundant, a Post Upgrade session can remove the data, see Infor LN Post-DUE steps.