The production environment has the following issues:

1. Large volume of credit transactions that are not matched to Payments. This leaves the Transaction OPEN and causes performance issues on the customer profile screen

The above needs to be corrected using the following steps:

1. Build an Auto-Allocation process that works as follows:
   1. Picks up a list of Credit Invoices that have an outstanding amount
   2. Using the oldest ON-Account payment for the customer, match the credit invoice.

1. Complete procedure
2. Add a new process to handle allocation
3. System and UAT

1. The change will be available in versions: 15.00 and 14.90.230901 Patch

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

1. Added a new process named "POS018 - Point of Sales On-Account Payment Auto-Allocation"
2. This process will use the parameters provided to automatically allocate ON-Account Payments to "Unpaid Invoices"
3. Filters are provided to restrict the group of invoices that should be auto-allocated
4. "Invoice Cut-Off Days" is used to determine how many days to pass before picking up the invoice for auto-allocation
5. The oldest invoice is allocated first
6. When allocating invoices, we follow these rules:
   1. Pick the oldest payment that has an "On-Account Amount" that matches the Invoice's "Outstanding amount"
   2. If we cannot find the exact payment amount, we pick the first payment that has an "On-Account Amount" Greater than the "Invoice Outstanding amount"
   3. If we still cannot find a payment that meets these criteria, we take the next available payment with an "On-Account Amount". Note that in this case, the allocation process may need a few iterations before the invoice is fully paid.

3. Affected Areas:

1. New Process
2. Payment Allocation

4. The issue was caused by:

1. New Feature

5. Other Relevant Notes:

6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT

PART B - Development Reference (Place descriptor for objects changed):

Figure 1 - New Process POS018 for Order On-Account Allocation

Hi Vineet, the changes have been tested in development. 

Can you proceed with verifying this on the OTGL environment and get them to sign off on the way this works before applying this to production?

1. The change will be available in versions: 15.00 and 14.90.230905

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

1. Added a new parameter to "Exclude Invoices" based on the contents of "Notes" on the invoice. 
2. Invoices that contain specific words can be excluded from auto-allocation. 
3. For Example, you can configure the parameter "Exclude Invoices" with the value "Dispute". Then update the "notes" of an invoice with this word, such as "Customer Disputes this invoice. Refer to case XXX". The auto-allocation process will not allocate this invoice as it has the word "dispute" in the Notes of the invoice.

3. Affected Areas:

1. Process POS018 - Auto Payment allocation to Credit Invoices

4. The issue was caused by:

1. Improvement

5. Other Relevant Notes:

1. If you have a LARGE VOLUME of HISTORY transactions to allocate, this process can take a very long time to run. You can work around this by setting the "CUT OFF DAYS" configuration so that the system can allocate a batch of 10,000 transactions per run. For example, if you have 4 years of Un-allocated Invoices, set the "Cut-Off Days" to "3 years * 365 days". Let this process run, then reduce to 2 years, 1 year then 30 days.
2. The Cut-Off Days configuration is used to determine which Invoices will be allocated. 

6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT

Environment Details

1. OS version: Win11
2. Application version: 14.
3. Setup on:
   1. Server: LinkQA4
   2. Database: LinkSOFT
   3. LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
4. Login Details: Standard username and password for user "admin"

Next Step: Closure