Overview
You want Aurea to investigate why an ACH payment applied to an account did not get reported to NICOR (utility). You have confirmed on the utility's portal that this payment was not sent. It is expected that outbound 810 transactions reporting the payment get sent to the utility via EDI for all non-EDI payments (Visa, ACH, Lockbox).
Information
This is a product defect in CIS (version [CIS|Major|June2020)).
The fix should already be deployed and available at your end, so, you are not expected to encounter this issue. The system is expected to follow the conditions below for BILL READY- NICOR - NON 820 PAYMENTS
1> Customer INACTIVE for 46 days, payment should NOT be sent to Utility
2> Customer ACTIVE or INACTIVE, the payment against ETF should NOT be sent to utility.
3> Customer ACTIVE, all payments except ETF should be sent to utility.
4> Customer INACTIVE for within 45 days, all payments except ETF should be sent to utility.
In case you come across the issue, please contact your Account Manager directly via email to engage the Professional Services team for a fix.
<supportagent>
The expected application behavior is that for NICOR BILL Ready accounts, whenever a non-EDI or non-820 payment is applied to the customer account, the system is supposed to trigger an 810_03 outgoing transaction towards the utility to inform them.
In this reported case, an outbound 810 transaction for payments is not generated for an account with an ETF invoice.
This is a product defect in the version [CIS|Major|June2020].
The root cause is a problem with the Stored Procedure cspNicor810payment processing the data executed by the Maintenance.MaintenanceQueue job. This bug is fixed by the Engineering team by correcting the mentioned stored procedure.
All clients, serving customers tied to the NICOR utility, who could have been affected by this product defect are likely to have the fix deployed already. In case a support ticket is opened, redirect the requester to their Account Manager.
</supportagent>
Priyanka Bhotika
Comments