State of Wisconsin
Department of Health Services

HISTORY

The policy on this page is from a previous version of the handbook. 

7.3.2 Calculating Overpayment Claim Amounts

7.3.2.1 Client and Non-Client Error

7.3.2.2 Collecting Client and Non-Client Error Claims Against Participating Food Units

7.3.2.3 Collecting Claims for Client & Non-Client Errors Against Non-Participating Food Units

7.3.2.4 IPV

7.3.2.5 Calculate IPV Claims

7.3.2.6 Allotment Reduction

7.3.2.7 Writing-Off Claims Against Non-Participating Food Units

7.3.2.8 Overpaid Claims

7.3.2.9 Timely Negative Notice

7.3.2.10 Tax Intercept

7.3.2.11 Notice & Review

7.3.2.12 Repayments

7.3.2.1 Client and Non-Client Error

When calculating the overpayment, consider the food unit’s reporting requirements. Do not use income or expenses, or changes in income and expenses that were not reported and were not required to be reported.

 

Use converted income to determine ongoing benefit eligibility for the overpayment calculation. Only use the income and expenses reported or required to be reported for each month of the overpayment period. In claim calculations, disregard income that was not previously reported and was not required to be reported.

 

The "Date of Discovery" is the date you become aware of the potential overpayment. This date is used to establish the look back period. The overpayment period begins with the date of discovery and extends back up to one year for non-client errors and up to six years for client errors. This look back period is the period of time during which the overpayment may have occurred.

 

From this point forward the term “Date of Discovery” will be synonymous with the ‘Date of Awareness.” "Date of Discovery" will be used on all future correspondence. The intent of the policy is that both terms are part of a process to define the overpayment period. The overpayment period consists of the number of months during which there were overpayments within the look back period. The overpayment period begins with the first month had the change been reported timely and acted on timely. It would have been effective up to the month prior to when the case was corrected.

 

The worker must consider information received through SWICA as best available information if income cannot be verified otherwise.

 

Current verification requirements still apply. When all attempts to obtain the verification are unsuccessful the worker must use the best available information to determine the monthly income amount for purposes of the overpayment calculation. The food unit has primary responsibility for providing documentary evidence to support statements in the case record and to resolve any questionable information. The worker must assist the household in obtaining this verification provided the food unit? is cooperating with the agency.

 

The food unit must be given a reasonable opportunity to provide verification of income, and the agency may contact the employer directly for verification. Members should be provided 30 days to provide verification, unless it is determined that additional time is necessary in order to collect and submit the verification requested. If more than 30 days are allowed for provision of verification by the member, document the number of days allowed and the reason. When no other form of verification is available, then SWICA information is considered the best available information and should be used to calculate an overpayment

 

Document clearly in case comments the unsuccessful requests for verification from the household and the employer, and the reason for using a SWICA match as the best available verification of monthly income. Also clearly document how the income amount was calculated from the SWICA match.

 

7 CFR 273.18(d)(1)

In order to meet the established timeliness requirements, overpayment claims must be completed before the last day of the quarter following the quarter in which the IM discovered an overpayment. This holds true for both client and non-client errors. Overpayment claims must be established and recovered even if they are not calculated within this timeframe. Overpayment claims must be established and recovered even if they are calculated late; failing to complete a claim within the given timeframe does not void the overpayment.  

 

Client Error

A client error occurs when the food unit unintentionally:

  1. Failed to provide correct or complete information,

  2. Failed to report a change that was required to be reported, or

  3. Received FoodShare for which it was not entitled pending a fair hearing decision.

 

The look back period for client errors begins with the date of discovery (the day the IM worker discovered the potential that an overpayment may exist) and extends backward:

  1. Six years, or

  2. To the month the change would have been effective had the food unit timely reported it, whichever is most recent.

 

The overpayment period begins with the first month had the change been reported timely, and would have been effective up to the month prior to when the case was corrected.

 

It is essential that the date of discovery be documented in case comments. This date locks in the look back and overpayment period. This date will not change even if the overpayment is calculated untimely.

 

The month the change would have been effective cannot be more than two months after the change in circumstance actually occurred.

 

When determining if an overpayment occurred due to an unreported increase in total gross monthly income, compare the total actual unconverted income amount to the income reporting limit for the FoodShare assistance group size to determine if the income should have been reported.

 

In overpayment calculations, do not apply the 20% earned income disregard to earned income that was required to be reported but was not reported timely. Disregard income that was not previously reported and was not required to be reported due to reduced reporting requirements. If expenses were reported correctly at the time of the overpayment, use those same expenses when calculating the overpayment. If expenses were incorrectly reported, and subsequently verified (examples: the expense was considered questionable and the IM worker requested and received verifications, or the expense was verified through a QC review or a WHEAP data exchange, etc.) use the verified amount in the overpayment calculation. If the IM worker knows the expense is incorrect and verification was requested but was not received, do not allow the expense in the overpayment calculation.

 

Earned income needs to be verified when determining income to be used in an overpayment calculation.

 

For Earned Income:

  1. Dated check stubs of income that should have been reported that caused the overpayment.

  2. Earnings reports, a statement from the employer, or ECF forms, signed by the employer, with all needed information.

 

Note: IEVS may indicate that income was earned from an employer sometime during three months of the work quarter. Do not use IEVS in calculations and overpayments.

 

Non-Client Error

A non-client error occurs when the state or local agency:

  1. Takes an incorrect action on a FoodShare case,
  2. Does not take prompt action on a change the food unit reported,
  3. Fails to correct an action,
  4. Incorrectly enters information or fails to include information that results in expedited eligibility,
  5. Misapplies policy, or
  6. System programing error, such as failure to include W-2 or SSI benefit increase.

 

The look back period for non-client errors begins with the date of discovery (the day the IM discovered the potential that an overpayment may exist) and extends backward:

  1. Twelve months, or

  2. To the month the error was effective had the change been acted on timely, whichever is most recent.

 

The overpayment period begins with the first month the change would have been effective up to the month prior to when the case was corrected.

 

It is essential that the date of discovery be documented in case comments. This date locks in the look back and overpayment period.  This date will not change even if calculated untimely.

 

Example 1: At Jeff’s renewal on June 5, 2012, he reported income of $800 per month. His IM worker miscalculated Jeff’s income and budgeted $400 per month instead of the $800 per month that Jeff reported. When Jeff submits his SMRF on December 5, 2012, the IM worker discovers her error and corrects the case effective January 1, 2013. While reviewing Jeff’s income, the IM worker discovers that Jeff started a second job on August 1, from which he earns $600 per month.

 

To calculate the overpayment, the IM worker budgets the correct income amount of $800 from the job Jeff reported. The IM worker does not use the income in the overpayment calculation from the second job, because this income was not required to be reported due to reduced reporting requirements. Jeff reports this change on his December 2012 SMRF and this income is budgeted effective January 1, 2013.

 

  • The date of discovery is December 5th, 2012.

  • The look back period is December 2011 through December 2012 (non-client error).

  • Had the June 2012 change been acted on accurately the change would have been effective July 1, 2012, therefore the overpayment period is July 1, 2012 through December 31, 2012.

 

Example 2: Margaret submitted a complete SMRF on April 22. On the SMRF Margaret reports her income decreased from $700 to $500. On May 20, Margaret’s worker discovers the error and corrects the case effective July 1. While determining if Margaret has an underpayment, the IM worker learns that Margaret began a second job on May 1, from which she earns $120 per month. The additional income does not put Margaret’s income over 130% of the FPL, so she is not required to report the change until her next renewal, due to reduced reporting requirements.

 

  • The date of discovery is May 20.

  • The look back period is the past 12 months (non-client error).

  • Had the April 22 change been acted on timely the change would have been effective June 1. Therefore, the overpayment period is June 1 through June 31.

 

The IM worker does not use the income from Margaret’s second job because it was not required to be reported.

 

Example 3: Matt submitted a complete SMRF on August 4, 2013. On August 8, 2013, Matt’s IM worker discovers that Matt started a job on April 5, 2013, that should have been reported because the income from this job puts him over the 130% FPL threshold. The IM worker corrects the case and closes it effective August 31, 2013.

 

  • The date of discovery is August 8, 2013.

  • The look back period is August 2005 through August 2013 (client error).

  • Had the April 5, 2013, change been reported timely, the case would have closed as of May 31, 2013. Therefore, the overpayment period is June 1, 2013 through August 31, 2013. Section 6.1.1.2 Change Reporting for All Other Food Units (Reduced Reporting) applies, and the change must be reported by the month following the month in which the total income exceeded 130% of the FPL.

7.3.2.2 Collecting Client and Non-Client Error Claims Against Participating Food Units

7 CFR 273.17(d)(4)

7 CFR 273.18(e)

Establish collection of overpayment claims against participating food units unless:

  1. The claim is collected through an offset, or

  2. Claims are protected by the Federal Bankruptcy Code

 

Do not charge any interest on the claim.

 

If the member wishes to pay the whole claim at once, he or she may do so.

 

A participating food unit is one that is still open and receiving FoodShare benefits.

7.3.2.3 Collecting Claims for Client & Non Client Errors Against Non-Participating Food Units

7 CFR 273.18(e)

Establish overpayment claims for non-participating food units only if the amount of the claim is $125 or more.

 

A non-participating food unit is one that is closed and not receiving FoodShare benefits.

7.3.2.4 IPV

Establish a claim due to an Intentional Program Violation (IPVIntentional Program Violation 3.14.1) only when one of these conditions exists. The food unit member:

  1. Signs a waiver of the disqualification hearing,

  2. Signs a disqualification consent agreement after being referred for prosecution, or

  3. Is convicted of a FoodShare felony or found guilty of IPV in an Administrative Disqualification Hearing or judicial proceeding.

 

7 CFR 273.16 (c)

An applicant or member commits an IPV when he or she intentionally:

  1. Makes a false or misleading statement or misrepresents, conceals or withholds facts, including their identity or place of residence, to become eligible or to remain eligible for benefits; or

  2. Commits any act that constitutes a violation of the Food and Nutrition Act of 2008, the Supplemental Nutrition Assistance Program Regulations, or any Wisconsin statute for the purpose of using, presentating, transferring, acquiring, receiving, or possessing, or trafficking of FoodSharebenefits or QUEST cards. See 3.14 for a definition of trafficking.

 

The cardholder is the only person that can make authorized purchases on the QUEST card, unless he or she verbally authorizes another person to make purchases on their behalf for their assistance group.

 

An unauthorized individual who uses a QUEST card without the cardholder’s consent is committing fraud. Unauthorized individuals using the card to make purchases for themselves without the cardholder’s consent are also committing fraud. If the cardholder knows the card is in the hands of an unauthorized individual, both the cardholder and unauthorized individual may be accused of fraud.

 

Example 4: Ellen is receiving FoodShare for herself, and her two children. Ellen is sick and gives her QUEST card to a friend to buy food for the FoodShare assistance group, and her friend buys food for Ellen's family. Since Ellen authorizes her friend to buy food for Ellen’s family, the friend is considered an authorized buyer even though there is no written documentation of the authorization.

 

Example 5: Steve is a single FoodShare member who has been in jail for the last four months. Steve gives his QUEST card to a friend to use while he is in jail. His friend is not buying food for Steve, the person eligible for the FoodShare benefits. His friend is an unauthorized buyer, and both are guilty of committing fraud.

 

If a FoodShare member has a pending IPV hearing, the IM worker should establish the claim as a non-client error.

 

If the case has been referred to the DA for prosecution, the IM worker should discuss the claim establishment with the DA or the agency's legal counsel.

 

If the DA or agency's legal counsel advises that processing a claim as a client error may create bias against an IPV judgment, do not process the claim until the IPV determination is made.

7.3.2.5 Calculate IPV Claims

7 CFR 273.18(c)

7 CFR 273.16(c)(2)

For eligibility-related IPV claims, do not apply the 20% earned income deduction to earned income which was required to be reported, and was not reported timely. If expenses were reported correctly at the time of the overpayment, use the same expenses when calculating the overpayment. If not, then do not use the expenses in the calculation.

 

In claim calculations, disregard income that was not previously reported and was not required to be reported.

 

For trafficking-related claims, establish the claim as determined by:

  1. The individual’s admission,

  2. The amount ordered through adjudication, or

  3. The documentation that forms the basis for the trafficking charge.

 

Offset the IPV claim against any restoration amount owed to the FoodShare assistance group. Start collection action for the remaining balance.

 

A worker must collect an IPV claim previously handled as a client error claim. Start the IPV procedure for collection whenever a client error is later determined to be an IPV.

 

Change the error type from “client error” in CARES to “IPV” error. This will update the CARES system to take the correct IPV recoupment amount for repayment of the debt. CARES will auto-generate overpayment notices and the Notice of Repayment Agreement.

 

Note: Sending a new notice and RPA starts the claim collection process all over again, providing new hearing rights on the merits of the claim.  A new notice would disrupt the entire collection process that was already occurring. In addition, these claims could already be delinquent and in process of Federal and State tax offset, a new RPA would make the client think they could again make voluntary payments on an already delinquent claim, or disrupt an existing RPA.  The IPV determination is entirely separate from the collection of the claim, with it’s own hearing rights for that process. For example:  we already could legally collect the claim as a client error, we already notified them of the amount/ dates/ calculations, etc. which is required by law.  The only thing that would trigger the legal requirement for a new notice would be increase of the balance we were trying to collect.  The IPV determination process and recoupment notices notify the client of the change.  The determination should have no effect on the collection that was already occurring.  

 

Once the repayment process has started on a claim, do not send a new repayment agreement form related to the same claim unless there is an increase in the claim balance.

 

Note: The systems do not allow interest to be charged on a claim.

 

IPV information is entered in CARES as soon as possible after the date of decision.

 

If the document does not contain the offense type, obtain more information from the party who issued the IPV. The Sanction Duration field should not be updated by IM workers unless it is necessary to override a sanction duration based on legal documents that indicate a different sanction duration period.

 

Sanction duration is the number of months a member is disqualified from receiving FoodShare. Code 999 is permanent disqualification. No sanction end date will appear if the sanction duration is 999.

 

7.3.2.6 Allotment Reduction

7 CFR 273.16(g)(1)

An overpayment due to any type of error will be recovered from a FoodShare assistance group participating in the program by reducing their allotment.

 

The type of error determines the amount that will be recovered each month.

  1. Client/non-client error: CARES will reduce the allotment by the greater of 10% of the FoodShare assistance group's monthly allotment or $10 each month. The $15 minimum benefit level for one or two person groups applies before CARES reduces the allotment.

  2. IPV: CARES will reduce the allotment by the greater of 20% of the group's monthly entitlement or $20 each month. The entitlement is the amount of benefits the group would have received if not for the disqualification of a FoodShare group member. The $15 minimum benefit level for one or two person groups applies before CARES reduces the allotment.

 

CARES will not allow you to reduce the recovery amount to less than $10 for client/non-client and less than $20 for an IPV.

7.3.2.7 Writing-Off Claims Against Non-Participating Food Units

7 CFR 273.18(e)(8)

Claims against non-participating food units and FoodShare assistance groups may be written off if reasonable collection efforts have been made and the debt is determined to be uncollectable.

 

Claims that have been referred to and or have resulted in a successful tax intercept should not be written off but should remain open until paid in full.

 

Recommendation to write-off can be made if proper documentation is submitted to demonstrate that the claim meets any of the following criteria:

  1. It is found to be invalid in a fair hearing, administrative or judicial decision.

  2. It is against a household in which all adultA person who is 18 years old or older members are deceased and the State does not plan to pursue collection against the estate.

  3. It has been discharged through bankruptcy or a bankruptcy stay is in effect.

  4. It cannot be substantiated from case records.

  5. The state agency has determined, after exhausting collection efforts, that it is not cost-effective to collect the claim. If the request to write off the claim is made on this basis, the following criteria should be used:

    1. The claim has an outstanding balance of $24 or less and has been past due for 90 days or more.

    2. The claim is from $25 to $499 and:

      1. Three past due notices have been sent,

      2. It was referred for tax intercept, if the tax intercept was successful the account

      3. should remain open for 3 years or until paid in full, and

      4.  It has been past due for 3 years.

    3. The claim is from $500 to $4999 and:

      1. Three past due notices have been sent,

      2. It was referred for tax intercept (if the tax intercept was successful the account should remain open for 5 years or until paid in full),

      3. It has been considered for referral to a collection agency or credit bureau, and

      4. It has been past due for 5 years.

    4. The claim is over $5000 and:

      1. Three past due notices have been sent,

      2. It was referred for tax intercept (if the tax intercept was successful the account should remain open for 10 years or until paid in full),

      3. It has been considered for referral to a collection agency or credit bureau, and

      4. It has been past due for 10 years.

 

Documentation of the following information is required:  

  1. The age of the claims,

  2. Actions taken to collect, and

  3. Documents relevant to the specific claim, e.g., death certificates, bankruptcy discharge orders, and administrative or judicial decisions.

 

Recommendations for the writing-off of claims must be submitted to the Public Assistance Collection Unit, via mail at: P.O. Box 8938, Madison, WI 53708-8938; or via email at dwspacu@wisconsin.gov.

7.3.2.8 Overpaid Claims

7 CFR 273.18(h)

The Department of Children and Families Bureau of Finance, Public Assistance Collections Unit (PACU) Section monitors and processes all refunds centrally at the State level. This section monitors all accounts for refunds. If a refund is due on a FoodShare overpayment and the FoodShare case is open, the PACU Collections Section will contact the appropriate agency to issue a FoodShare supplement benefit in the amount of the refund due. If an agency notices that a refund has not been processed, the agency can contact the PACU Collections Section at dwspacu@wisconsin.gov.

7.3.2.9 Timely Negative Notice

FoodShare benefits issued solely because the 10-day negative notice requirement cannot be met are not an overpayment. Do not establish a claim or recover this type of issuance.

7.3.2.10 Tax Intercept

7 CFR 273.18(g)(8)

The State of Wisconsin Public Assistance Collections Unit uses tax intercept from both state and federal tax refunds to recover overpayments claims from anyone who has become delinquent in repayment of a claim.

 

To use tax intercept, the overpayment must be considered delinquent. Delinquency is defined as failing to make the monthly payment by the due date three times over the life of the debt. The collection system sends three dunning, or past due, notices for each of the three missed payments. The debt must meet all six of the criteria below:

 

 

State Debt Criteria

Federal Debt Criteria

1

Valid and legally enforceable

Valid and legally enforceable

2

All error types

All error types

3

$20

$25

4

At least 30 days after the third notification of the tax intercept.

At least 120 days from notification of overpayment.

5

Free from any current appeals.

Free from any current appeals.

6

Incurred by someone who is not currently in bankruptcy.

Incurred by someone who is not currently in bankruptcy.

7.3.2.11 Notice & Review

State tax intercept notices include a 30 day fair hearing right. The Division of Hearings and Appeals conducts the fair hearing. Federal intercept notices have a 60 day administrative review process. The Public Assistance Collections Unit conducts the federal administrative desk review. The member must provide evidence showing the claim is not past due, or is not legally enforceable. If the member cannot provide that evidence, the case will be sent for intercept.

 

The case is not subject to the state tax intercept while under appeal with the Division of Hearings and Appeals. A State fair hearing has no effect on a Federal Tax Intercept Action. A Federal desk review does not stay a Federal tax intercept action.

7.3.2.12 Repayments

7 CFR 273.18(e) (4) and (5)

A member who makes a repayment agreement may not be subject to tax intercept as long as he or she is meeting the conditions of the agreement. Failure to sign and return a repayment agreement may result in further delinquency collection action. If a member’s repayment agreement becomes delinquent, which is defined as three missed payments over the life of the debt and has been sent three dunning, or past due, notices, he or she is subject to both tax intercept and monthly repayment.

 

The policies for monthly repayments are listed on the repayment agreements:

  1. Overpayments less than $500 should be paid by at least $50 monthly installments.

  2. Overpayments $500 and above should be paid within a three-year period either by equal monthly installments, or by monthly installments of not less than $20.

 

 

This page last updated in Release Number: 18-01

Release Date: 01/08/2018

Effective Date: 01/08/2018

 


Notice: The content within this manual is the sole responsibility of the State of Wisconsin's Department of Health Services (DHS). This site will link to sites outside of DHS where appropriate. DHS is in no way responsible for the content of sites outside of DHS.

Publication Number: P-16001