Home > News > Income reporting issue with new APR and e-Snaps

Income reporting issue with new APR and e-Snaps

November 8, 2013

There is an issue that has cropped up with the new APR reporting and e-Snaps. “This issue is caused by a data quality issue in ServicePoint. This prevents the APR from finding a category for the client so they are skipped. This then leads to the error message in eSNAPS.”

The Bowman Industry Compliance Officer is getting clarification from HUD on this issue and will be updating the 0631 in November to make it “easier to find” these clients.

The issue arises where the Client record has the following:

  1. They have Income Received assessment question answered “Yes (HUD)”.
  2. They have no valid income assessment records as of their exit date
  3. They have a value in the Total Monthly Income assessment question

Or

  1. They have Income Received assessment question answered “Yes (HUD)”.
  2. They have no valid income assessment records as of their entry date
  3. They have a value in the Total Monthly Income assessment question

“This combination is preventing the report from finding the proper column for the client.”

Why is this an issue? HUD programming guidance given to Bowman on the use of the income recording by category vs the Total Monthly Income field for this report.

Prior to the new APR, the logic that has been used was an either / or. Either use the Sub-assessment to record the clients income OR use the Monthly income. With the “Total Monthly Income” used when there was data in both.

In the new APR the logic has been changed and focuses on recording all earned income in the sub-assessment and reporting more completely on income, use of the “Total Monthly Income” field has presented some issues.

We hesitate to suggest making any changes in client data until we hear more from ServicePoint re the HUD guidance on this and the updates that Bowman does to accommodate the new guidance.

Categories: News