/
Effective date not being retained between Payment Entry searches

Effective date not being retained between Payment Entry searches



Description of Issue

Payment Entry is not honoring the AR User Preference for Retain effective date while using Bill Inquiry.

Payment Entry effective dates are resetting between find sets.



Context
  • Munis

  • Accounts Receivable

  • AR

  • Payment Entry

  • arbilinq

  • AR User Preferences

  • arusrmnt



Cause




Resolution

Development is currently researching the issue. As a workaround, within a Payment Entry session, on the bill find screen, click the ribbon option for Preferences which will initialize your user preferences and cause the effective date to be retained, if enabled.



Additional Information












Related content

Payment entry retains the effective date from the previous search
Payment entry retains the effective date from the previous search
More like this
Effective Date and Last Activity Date for payments made towards Payment Plan periods not due yet does not match Payment Entry batch effective date
Effective Date and Last Activity Date for payments made towards Payment Plan periods not due yet does not match Payment Entry batch effective date
More like this
Payment Reversal Effective Date Incorrect
Payment Reversal Effective Date Incorrect
More like this
Print Invoices SQL statement effective date error
Print Invoices SQL statement effective date error
More like this
General Billing Print Invoices Not Calculating Interest
General Billing Print Invoices Not Calculating Interest
More like this
DIA Condition - Accounts Receivable Bill Header Missing Installment X Billed Date
DIA Condition - Accounts Receivable Bill Header Missing Installment X Billed Date
More like this