Asset Verification System (AVS) Interface

What is the Asset Verification System (AVS) interface?

The AVS interface process sends client information to and receives financial institution information from the Public Consulting Group (PCG).

The AVS interface takes place on a nightly basis for outbound client demographic data for clients coded with an AVS authorization of Authorized (A).

NOTE: Nightly files sent to PCG won’t include applications or recertifications for Healthcare for Workers with Disabilities (HWD) (S08) Assistance Units (AUs). Users will need to manually access PCG to submit asset verification requests for S08 AUs.

On the second Saturday of every month, PCG sends an inbound file containing current financial institution data, which is then uploaded into ACES.

What information is sent from ACES to Public Consulting Group (PCG)?

The following information is sent to PCG nightly for applicants, recipients, and financially responsible person(s) with an AVS Authorized code of Authorized (A)

  • Clients First, Middle, and Last Name
  • Spouses First, Middle, and Last Name (if the spouse meets the criteria to send)
  • Client’s Social Security Number
  • Spouse’s Social Security Number (if the spouse meets the criteria to send)
  • Client Identification Number
  • Request Type (Medical Coverage Group and an Application (A) or Renewal (R) indicator)
  • Date of Birth for both client and spouse
  • Residential and Mailing Address (Always the Residential and mailing if present)
  • Financial Institution ID’s  
  • Community Service Office of Record
  • Region of the state that the client resides
  • Household Size of 1 or 2  (if the spouse meets the criteria to send)
  • Head of Household Name
  • Current User’s ACES ID Name

What information is received by ACES from Public Consulting Group (PCG)?

ACES receives a monthly file from PCG with financial institutions data which includes:

  • ID numbers
  • Name or title of the institution
  • Address, city, state, and zip code
  • Updates to existing institutions including those that have closed or stopped participating in asset verification
  • Newly added institutions

Information included in this file overwrites existing financial institution data.

What ticklers are generated from the Asset Verification System (AVS) interface?

Two ticklers generate from actions related to the AVS interface:

  • AVS1 – CLIENT NEEDS AVS AUTHORIZATION. This tickler generates when:
    • The client is active on a Classic Medical Assistance Unit (AU) that requires AVS authorization,
    • The date is approximately 90 days prior to the AU’s review end date, and
    • The AVS Authorized field is blank or coded with Exception (E).
  • AVS2 – REVIEW AVS RESULTS. This tickler generates when a client is active on a Classic Medical AU that requires AVS authorization and the client was included in the nightly batch file.
NOTE: The AVS2 tickler doesn’t display in Barcode until the 16th day after sending the nightly batch file.

Each tickler includes processing steps depending on if the client belongs to a CSD office or an ALTSA office.