Attachment 04 WIC Requirements v.2.docx

DOCX document 296 KB Posted Jan 27, 2023

Attached to: Master Agreement AZ|CTR060124
Contract number: CTR060124
Issued by: Arizona

About this file

Written by GovTribe AI · Oct 9, 2025

This document is a detailed technical requirements specification for a Western States Electronic Access (WSEA) WIC Electronic Benefits Transfer (EBT) system contract. The specification involves three states - Alaska, Hawaii, and Idaho - and their respective WIC (Women, Infants, and Children) programs. The document outlines comprehensive technical, functional, security, and operational requirements for an electronic benefits delivery system to be implemented by an EBT processor/contractor who will manage food benefit transactions for WIC participants across these states.

The contract covers a full-scale EBT system including card production, transaction processing, cardholder and vendor support services, system interfaces, reporting, and technological infrastructure. Key services include electronic benefit account management, point-of-sale transaction processing at authorized vendors, customer support through interactive voice response (IVR) systems and web portals, secure card management, and comprehensive reporting capabilities. The pricing model is based on a cost-per-case-month (CPCM), with invoicing occurring monthly and separately for each state. The system must support multiple transaction types, integrate with state management information systems, provide multilingual support, and meet federal WIC program regulations. Additional state-specific requirements include unique features like online shopping support for Alaska and extensive language support for Hawaii.

View the file

Other files

File	Type	Posted
Attachment 02 and 03 Written Inquiry Responses.docx	DOCX document	Jan 27, 2023
Attachment 07 WSEA Waivers.docx	DOCX document	Jan 27, 2023
Attachment 11 Alaska DHSS Sample Security Authorization.pdf	PDF	Jan 27, 2023
Attachment 12 Written Inquiry Responses.docx	DOCX document	Jan 27, 2023
CTR060124_FIS_WSEA_EBT_Services_Amendment_01-FE.pdf	PDF	Jan 27, 2023
State of Arizona.pdf	PDF	Jan 27, 2023
Attachment 01 Request for Proposals Signature Page v.2.pdf	PDF	Jan 27, 2023
Attachment 02 SNAP Cash Requirements v.2.docx	DOCX document	Jan 27, 2023
Attachment 04 and 05 Written Inquiry Responses.docx	DOCX document	Jan 27, 2023
Attachment 09 SNAP Cash Interfaces.pdf	PDF	Jan 27, 2023
CTR060124_FIS_WSEA_EBT_Services_Amendment_2_-_FE.pdf	PDF	Jan 27, 2023
FIS Waiver of Subrogation GL.pdf	PDF	Jan 27, 2023
US GCL Additional Insured.pdf	PDF	Jan 27, 2023
1 WSEA EBT Services RFP v.8.4.docx	DOCX document	Jan 27, 2023
1 WSEA RFP Written Inquiry Responses.docx	DOCX document	Jan 27, 2023
Attachment 08 State Contract Terms and Conditions v.2.pdf	PDF	Jan 27, 2023
Attachment 08 Written Inquiry Responses - Idaho.docx	DOCX document	Jan 27, 2023
Attachment 10 WIC Interface Configurations.pdf	PDF	Jan 27, 2023
Attachment 12 WSEA EBT Pricing Schedules v.2.docx	DOCX document	Jan 27, 2023
Attachment 13 Federal Procurement Provisions.docx	DOCX document	Jan 27, 2023
CTR060124-Contract_Documents.pdf	PDF	Jan 27, 2023
CTR060124_FISParticipatingAddendum_WSEAEBTServices_Amendment4.pdf	PDF	Jan 27, 2023
SPO_Approval_to_Request_to_Enter_Co-op_and_Contract_Beyond_5_years_-_WSEA_EBT_7..pdf	PDF	Jan 27, 2023
CTR060124_COI_2026-2-1_Cyber__2026-4-1_CGL_AL_WC.pdf	PDF	Jan 27, 2023
Addendum 1 Written Inquiries Responses re WSEA Supplemental Call Center Statistics Tables.docx	DOCX document	Jan 27, 2023
Attachment 03 SNAP Cash Written Responses.docx	DOCX document	Jan 27, 2023
Attachment 05 WIC Written Responses v.2.docx	DOCX document	Jan 27, 2023
Attachment 06 ALERT AMA STARS and REDE file formats.pdf	PDF	Jan 27, 2023
Attachment 08 Written Inquiry Responses.docx	DOCX document	Jan 27, 2023
Attachment_A_-FIS_Cost_Proposal.pdf	PDF	Jan 27, 2023
Attachment_B_-_FIS_Technical_Proposal.pdf	PDF	Jan 27, 2023
CTR060124-Debarrment_Checks_1.27.23.pdf	PDF	Jan 27, 2023
CTR060124_A5_FE_4.14.25.pdf	PDF	Jan 27, 2023
CTR060124_FIS_WSEA_EBT_Services_Amendment_3_-_FE.pdf	PDF	Jan 27, 2023
FIS Waiver of Right to Recover WC.pdf	PDF	Jan 27, 2023

Show all 35

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Attachment 4: WIC Program Requirements

1	WSEA Project Management, Organization and Staffing	6
1.1	Project Management and Organization	6
1.2	Project Staffing	8
2	eWIC Technical and Functional Requirements	11
2.1	General Requirements	11
2.2	Interfaces	12
2.3	Food Maintenance	16
2.4	Account Set Up/Maintenance	19
2.5	Benefit Issuance/Maintenance	21
2.6	Card Production and Management	24
2.7	Card and PIN Issuance	27
2.8	Transaction Processing	33
2.9	Settlement and Reconciliation	38
2.10	Administrative System Functionality	47
2.11	Cardholder Support Services	52
2.12	Vendor Support Services	58
2.13	State Agency Support	62
2.14	System Reporting	64
2.15	Vendor Management	73
2.16	Vendor Mobile App POS/ Wireless POS	89
2.17	System Security Functionality	95
3	eWIC Business Requirements	100
3.1	Invoicing for WIC EBT Services	100
3.2	Accounting and Audit Requirements	102
3.3	Service Level Requirements	103
3.4	Remedying Deficiencies	109
3.5	Change Management	110
4	eWIC Project Deliverables and Documentation	112
4.1	Standardized Deliverables and Documentation	112
4.2	Deliverable and Documentation Provision and Format	112
4.3	Deliverable and Documentation Reviews	113
4.4	Deliverable Acceptance Criteria	114
4.5	Deliverable and Documentation Due Dates	115
5	eWIC Transition/Conversion and Implementation	132
5.1	Requirements for WIC Programs	132
5.2	Transition and Conversion of WIC System	133
6	eWIC System Testing Requirements	140
6.1	System Testing Requirements	140
6.2	Connectivity Testing	142
6.3	Interface Testing	143
6.4	User Acceptance Testing	143
6.5	IVR Testing and/or Client and Vendor Web Portal Testing (as applicable)	145
6.6	Performance Testing	146
6.7	Contingency/Fail-Over Testing	146
6.8	Vulnerability Testing, Conducted to State Agency Security Standards	147
7	State Specific Requirements	149
7.1	Alaska WIC State Specific Requirements	149
7.2	Hawaii WIC State Specific Requirements	151
7.3	Idaho WIC State Specific Requirements	152

Table 1: Project Management and Organization	6
Table 2: Project Management	8
Table 3: General Requirements	11
Table 4: Interfaces	12
Table 5: Food Maintenance	16
Table 6: Account Set Up/Maintenance	19
Table 7: Benefit Issuance/Maintenance	21
Table 8: Card Production and Management	24
Table 9: Card and PIN Issuance	27
Table 10: Transaction Processing	33
Table 11: Settlement and Reconciliation	38
Table 12: Administrative Functionality	47
Table 13: Cardholder Support Services	52
Table 14: Vendor Support Services	58
Table 15: State Agency Support	62
Table 16: System Reporting	64
Table 17: Vendor Management	73
Table 18: Vendor Mobile App/ Wireless POS	89
Table 19: General Security Requirements	95
Table 20: Invoicing for WIC EBT Services	100
Table 21: Audits	102
Table 22: Service Level Requirements	103
Table 23: Remedying Deficiencies	109
Table 24: Change Management	110
Table 25: Standardized Deliverables and Documentation	112
Table 26: Deliverable and Documentation Provision and Format	112
Table 27: Deliverable and Documentation Reviews	113
Table 28: Deliverable Acceptance Criteria	114
Table 29: Deliverable and Documentation Due Dates	115
Table 30: Requirements for WIC Programs	132
Table 31: Transition and Conversion of WIC System	133
Table 32: System Testing Requirements	140
Table 33: Connectivity Testing	142
Table 34: Interface Testing	143
Table 35: User Acceptance Testing	143
Table 36: IVR Testing and/or Client and Vendor Web Portal Testing	145
Table 37: Performance Testing	146
Table 38: Contingency/Fail-Over Testing Requirements	146
Table 39: Vulnerability Testing, Conducted to State Agency Security Standards	147
Table 40: Alaska WIC Requirements	149
Table 41: Hawaii WIC Requirements	151
Table 42: Idaho WIC Requirements	152

WSEA Project Management, Organization and Staffing

Project Management and Organization Table 1: Project Management and Organization

Req #

Section

Req’d (R)

Pref’d (P) Opt’l (O)

Function / Service / Requirement Description

Offeror Complies:

Yes/No Comments:

Project Organization

The EBT contractor shall have coordination between the EBT Contractor’s personnel (the EBT Contractor’s Project Director and assigned State Project Manager) and the State’s EBT Director. It should be noted that there are separate State EBT Directors for SNAP/Cash and WIC EBT programs.

Project Organization

The EBT Contractor shall implement and enforce procedures to provide adequate notification to the States and their EBT Director when potential or actual problems are identified.

Project Organization

The EBT Contractor’s personnel (Project Director and designated State Project Managers) shall have decision-making authority within the EBT Contractor’s organization in relation to this EBT project.

Project Organization

The EBT Contractor shall have a management structure that ensures adequate oversight and executive direction for the EBT Contractor’s personnel (Project Director and assigned State Project Managers).

Project Organization

The EBT Contractor shall notify the State, whenever possible in advance, when the State’s normal contact is expected to be unavailable, and the EBT Contractor must provide the State with contact information for an alternative or back-up contact.

Project Organization

Calls and/or e-mails from the State’s EBT Project Director to any designated contact must be returned within 24 hours.

Project Organization

The EBT contractor shall have lines of authority, communication, escalation, and problem resolution procedures established between the prime EBT Contractor and any subcontractors.

Project Organization

The EBT Contractor shall have the appropriate number and mix of project staff, both on and off site, at all times during each State’s conversion phase to ensure the successful transition and operation of the States’ EBT systems. At a minimum, Offeror shall propose a Project Manager, Technical Lead, Retail Manager, and Test Manager during the conversion phase of the project, along with the anticipated percentage of time the staff will be dedicated to the project.

Project Organization

The EBT Contractor’s State Project Manager, key personnel, or designees shall be available on-site in Alaska, Hawaii, and Idaho within two (2) business days of the State’s request at no cost to the State.

Project Organization

If the State deems it necessary for the EBT Contractor to be on site to respond to emergency or critical situations, the EBT Contractor shall be onsite in the timeframe requested by the requested State or Territory, which will not be less than the timeframes provided in Requirement 1.1.9.

Project Staffing Table 2: Project Management

Req #

Section

Req’d (R)

Pref’d (P) Opt’l (O)

Function / Service / Requirement Description

Offeror Complies:

Yes/No/ Comments:

Project Staffing

The EBT Contractor’s proposed WSEA Project Director shall meet the following minimum requirements:

· At least three years of project management experience, two of which must have been in projects involving State government

· Have successfully managed within the last five (5) years the implementation and/or operation of an EBT or other financial and/or transaction processing system of comparable size and similar complexity as defined within this RFP.

Project Staffing

The EBT Contractor’s proposed State Project Manager for each state shall meet the following minimum requirements:

· Bachelor’s Degree or five years of Project Management experience.

· Minimum of three years of Project Manager experience.

· Five years of work experience.

· Has supported at least 2 State government projects, including the implementation of at least one financial transaction processing systems.

· PMP is desirable.

Project Staffing

The Contractor’s State Project Manager shall start work on a State’s project no later than 15 days after the effective date of the contract between the Offeror and the State and will continue through the State’s written acceptance of the successful conversion of the current EBT system to the EBT Contractor’s EBT system and into the operations phase.

Project Staffing

Each WSEA State will continue to have an assigned Contractor’s State Project Manager for the entire length of the operations phase. During the operations phase, the State Project Manager must maintain regular and frequent contact with the State’s EBT Program Director and designated staff members.

Project Staffing

During the contract, the State may request the replacement of the Contractor’s State Project Manager for any legitimate performance reason and the replacement will also be subject to State approval. Staff replacement occurring at the State’s request shall be performed within 30 calendar days of receipt of the request.

Project Staffing

Key personnel from the EBT Contractor subject to the approval of the State are:

· Retail Manager;

· Technical Conversion Coordinator;

· System Test Manager; and

· Technical System Lead.

Project Staffing

WSEA States may conduct interviews of key personnel prior to award in order to determine acceptability.

Project Staffing

If any of the proposed key personnel or project managers are not currently in the employ of the Offeror, a letter of intent to accept employment shall be included in the response.

Project Staffing

If a change in key personnel is made after award, the Offeror shall present the replacement to the impacted State, and the State will have right of refusal privileges.

eWIC Technical and Functional Requirements General Requirements Table 3: General Requirements

Req #

Section

Req’d (R)

Pref’d (P) Opt’l (O)

Function / Service / Requirement Description

Offeror Complies:

Y/N Comments:

eWIC Standards

The eWIC System shall meet all applicable federal and state regulations, including WIC Regulations 7 CFR Part 246.

eWIC Standards

The eWIC System shall conform to the current version of the WIC State MIS-EBT interface specification in use. The eWIC Processor shall work with the states if an upgrade is requested to the current WUMEI version.

eWIC Standards

The eWIC System shall conform to the FNS Operating Rules for WIC EBT dated September 2014 or the most recent version at the time development is initiated.

eWIC Standards

The eWIC System shall conform to the FNS WIC EBT TIG dated September 2018 or the most recent version at the time development is initiated.

eWIC Standards

The eWIC System shall conform to the most recent version of the American National Standards Institute (ANSI) X9.93 - 2014 standards and future updates as described in the Technical Implementation Guide (TIG) 2018 and future updates.

eWIC Standards

The eWIC System and the eWIC Processor shall uphold the confidentiality of WIC participant information and WIC Vendor information to the extent required by §246.26 of the WIC Regulations (7 CFR §246).

eWIC Standards

In the following order of precedence, the eWIC System shall process transactions in compliance with:

· 7 CFR §246 and FNS WIC memos and guidance

· FNS Operating Rules for WIC EBT

· Prevailing industry technical and performance standards

eWIC Standards

The eWIC Processor shall provide, at no cost to a WSEA WIC State Agency, any eWIC System software enhancements or upgrades developed on behalf of other WIC State Agencies. The WSEA State Agency may, at their option, elect to implement these enhancements. The eWIC Processor may charge for any additional services, such as implementation, configuration, and materials beyond the provision of software.

Interfaces Table 4: Interfaces

Req #

Section

Req’d (R)

Pref’d (P) Opt’l (O)

Function / Service / Requirement Description

Offeror Complies:

Comments:

Interface with the MIS

The eWIC Processor shall establish secure, high performance connectivity between the eWIC System and the MIS to accommodate available and reliable message-based and file-based system interfaces.

Interface with the MIS

The eWIC Processor is expected to use the current WSEA WIC MIS-EBT interface specification. It is anticipated that there will be no changes made to the WSEA State MIS to support the interface. Information regarding the current WSEA WIC MIS-EBT Interface has been provided in Attachment 10: State Interface Documents

Interface with the MIS

The eWIC Processor shall establish secure, high-performance connectivity between the eWIC production and fail over systems and the MIS production system.

Interface with the MIS

The eWIC Processor shall establish secure, high performance connectivity between the eWIC production and fail over system and the MIS disaster recovery system.

Interface with the MIS

In the event of a difference in interpretation in the interface specification, the MIS Maintenance Entity will make the final determination with the consultation with the State Agency.

Interface with the MIS

The eWIC System shall accept and transmit data to and from the MIS in message-based interface or in batch system interface (batch files). The eWIC System shall be able to accept batch files 24 x 7 x 365, with the exception of scheduled maintenance down time.

Interface with the MIS

The following message-based functions shall be supported:

· Add EBA

· Update EBA

· Get EBA Details

· Add or Update Benefits

· Get Benefit Balance

· Get Benefit Maintenance History

· Get Benefit Redemption History

· Add Cardholder/Card

· Add or Update PIN

· Get Cardholders/Cards

· Update Cardholder/Card

· Get Card History

· Request warehouse authorization

· Void warehouse authorization

· Get warehouse authorization

· Get warehouse authorization code

Interface with the MIS

The following batch file-based functions shall be supported:

· Report Card Updates

· Add or Update Vendor

· Add or Update Category /Subcategory Information

· Add or Update UPC/PLU Information

· Report WIC Benefit Redemptions

· Report Benefits Purged

· Report WIC Benefit Changes

· Request ACH Payment (optional)

· Report ACH Payments (optional)

· Batch File Confirmation

Interface with the MIS

There is potential during the life of this contract one or more of the WSEA State Agencies may undergo a technology refresh which would include updating the MIS-EBT interface to the version of the WUMEI current at that time. It is expected that the eWIC Processor would update their portion of the MIS-EBT interface in conjunction with the MIS updates. It is understood that USDA is in the process of updating the WUMEI to provide a more detailed specification and anticipate it will follow a JSON format.

To the extent possible, any work already performed for another WIC State Agency to update the MIS-EBT interface to comply to the current version of the WUMEI will be made available to the State Agency at no additional cost. The State Agency shall work with the eWIC Processor using a change request process to address any additional development costs for the interface update.

Interface with the MIS

The eWIC System shall be available twenty-four (24) hours per day; seven (7) days per week for batch file and message transfer with the MIS and retail systems, except during scheduled maintenance.

Interface with the MIS

Scheduled maintenance of the eWIC System shall not exceed two (2) hours per month, unless other timeframes are agreed upon by the State Agency. Advance notice of scheduled maintenance must be provided no less than forty-eight (48) hours prior to the maintenance.

Interface with the MIS

Downtime shall be scheduled during periods of low transactions (e.g., between 1 AM and 5 AM State Agency Local Time). This time will be defined by the State Agency with the eWIC processor during the requirements validation phase of the project.

Interface with the MIS

The eWIC Processor shall provide the State Agency with thirty (30) day advance notification of any scheduled downtime outside of the time required for routine maintenance. Such downtime shall be pre-arranged with and approved by the State Agency. At the discretion of the State Agency, shorter notice may be approved, depending on the urgency of the situation.

Interface with the MIS

The eWIC Processor shall provide the State Agency with a schedule developed with the State Agency’s input and coordination, for routine maintenance with a minimum of 6 months’ notice for scheduled downtime.

Batch Files

When the eWIC System receives a batch file it shall transmit a confirmation to the sending party (MIS, vendor system, etc.) that a batch file was received.

Batch Files

The eWIC System shall accept a confirmation from the sending party that a batch file was received.

Batch Files

The eWIC System shall accept batch level error reports from the sending party.

Batch Files

Batch level errors (e.g., wrong sequence, wrong record count, etc.) shall be reported by the eWIC System to the sending party.

Batch Files

Detail record errors (e.g., provide specific record identifier and indication of specific error) shall be reported by the eWIC System to the sending party.

Batch Files

The eWIC System shall accept detail record error reports from the sending party.

Batch Files

If a batch file is transmitted with no records this indicates that no action is to be taken by the receiving system.

Coordination with the MIS Maintenance Entity

The eWIC Processor shall coordinate interface related update, testing, and implementation tasks as needed with the MIS Maintenance Entity.

Coordination with the MIS Maintenance Entity

The eWIC Processor shall schedule and conduct remote meetings with the MIS Maintenance Entity as needed to address interface updates, testing and implementation. This shall include preparation of meeting agenda and provision of meeting summaries.

Food Maintenance Table 5: Food Maintenance

Req #

Section

Req’d (R)

Pref’d (P) Opt’l (O)

Function / Service / Requirement Description

Offeror Complies:

Comments:

Add/Update Category/Subcategory Information

The eWIC System shall accept the initial WIC Category Sub-Category file generated by the MIS.

Add/Update Category/Subcategory Information

The eWIC System shall accept WIC Category Sub-Category files containing changes and/or additions to the State Agency WIC Category Sub-Category file from the MIS data.

Add/Update Category/Subcategory Information

If the begin date is not present, then the eWIC System shall assume the current date as the effective date.

Add/Update Category/Subcategory Information

If an end date is not provided, then no end date shall be applied to the record by the eWIC System.

Add/Update Category/Subcategory Information

When Category Sub-Category deactivation (end) dates are reached, any UPCs associated with the Category Sub-Category shall also be deactivated.

Add/Update Category/Subcategory Information

When an end date is received by the eWIC System for subcategory records, the eWIC System shall have no active or future benefits associated with the subcategory on that end date before the subcategory is deactivated.

Add/Update WIC UPC/PLU/NTE Data File

The eWIC System shall accept the initial WIC UPC/Price Look-Up (PLU)/NTE file from the MIS that includes peer group pricing for each item following WUMEI standard.

Add/Update WIC UPC/PLU/NTE Data File

The eWIC System shall accept WIC UPC/PLU/NTE files containing changes and/or additions to the State Agency WIC UPC/PLU/NTE database that includes peer group pricing for each item.

Add/Update WIC UPC/PLU/NTE Data File

The WIC UPC/PLU/NTE file shall be in the format consistent with the WSEA State MIS-EBT Interface Specification in compliance with the WUMEI for use in providing an APL consistent with the ANSI X9.93 standards

Add/Update WIC UPC/PLU/NTE Data File

Upon receipt of the UPC/PLU/NTE file, the eWIC System shall validate whether the UPC/PLU record already exists for the WSEA State Agency.

Add/Update WIC UPC/PLU/NTE Data File

If the UPC/PLU record does not exist, the eWIC System shall add the UPC/PLU record. The new UPC/PLU record will become active immediately unless there is a future active date.

Add/Update WIC UPC/PLU/NTE Data File

If the UPC/PLU record does exist, the eWIC System shall update the existing UPC/PLU record. The UPC/PLU change will become active immediately unless there is a future begin date. Changes include NTE updates by peer group, updates to active dates, and changes to descriptions, amounts, unit of measure or category/subcategory.

Add/Update WIC UPC/PLU/NTE Data File

The eWIC System shall completely replace the existing UPC/PLU record with the data in the most recent UPC/PLU/NTE file.

Add/Update WIC UPC/PLU/NTE Data File

In support of creating multiple APLs, the UPC/PLU/NTE file shall include indicators for the specific APL type for which the product shall be included. The eWIC system shall process this data and apply the UPCs/PLUs to the appropriate APL.

Add/Update WIC UPC/PLU/NTE Data File

The eWIC System shall accept the UPC/PLU/NTE files containing deactivations of specific UPCs or PLUs.

Add/Update WIC UPC/PLU/NTE Data File

A UPC or PLU record will no longer be eligible for purchase after the UPC/PLU end date has been reached or immediately if the designated end date is in the past.

Access to APL

The eWIC System shall provide user and WIC Vendor access to the APL. The MIS will generate the Category/Subcategory file and UPC/PLU/NTE file and remit to the eWIC system which will create the APL in X9.93 format on a daily basis.

Access to APL

At a minimum, the eWIC system shall generate the APL on a daily basis.

Access to APL

The eWIC System shall generate the WIC Vendor APL file on-demand as requested by the State Agency.

Access to APL

The APL shall not display nor contain not-to-exceed (NTE) data.

Access to APL

The eWIC System shall make the APL file available on a secure data retrieval site for download by WIC Vendors.

Access to APL

The eWIC System shall make the APL file available on a secure data retrieval site for download by third party processors.

Access to APL

The eWIC System shall provide the State Agency with user view of APL data (current and previous), including the ability to view APLs by specific dates.

Access to APL

If multiple APLs are used by the State Agency, eWIC System shall be able to limit vendor access to specific APLs. For example, if there is a full APL and a limited APL for pharmacies, pharmacy vendors shall only be able to access the pharmacy APL.

Access to APL

The eWIC Processor shall provide reporting and query functionality that shall identify when a vendor last downloaded the APL for those vendors that access the sFTP site directly.

Access to APL

For those vendors that access the sFTP site directly, the eWIC Processor shall provide reporting and query functionality that shall identify those vendors who have not downloaded the APL within a designated period of time (i.e., have not downloaded the APL in five (5) days or more).

Account Set Up/Maintenance Table 6: Account Set Up/Maintenance

Req #

Section

Req’d (R)

Pref’d (P) Opt’l (O)

Function / Service / Requirement Description

Offeror Complies:

Comments:

Create EBA

The eWIC System shall process account set-up messages from the MIS (Add EBA message).

Create EBA

The eWIC System shall validate the uniqueness of the household number (no duplicate household numbers allowed).

Create EBA

At a minimum, the eWIC System shall accept the type of account (e.g., household, training, compliance) and the household number. Once an account type is assigned to an account it cannot be changed.

Create EBA

The eWIC System shall be able to limit access or view of account information for user profiles based on account type. For example, a clinic user would not be able to view training or compliance accounts based on their user profile.

Create EBA

The eWIC System shall support segregation of reporting by account type. For example, training and compliance accounts may be excluded from certain reports or reports may only include data for a specific account type.

Create EBA

The eWIC System shall accept demographic data (if included in the account set up message).

Create EBA

The eWIC System shall establish an EBA for the household and assign a unique EBA identification (ID).

Maintain EBA

The eWIC System shall accept messages from the MIS to change the household demographic data (if used by the State Agency). (Update EBA)

Maintain EBA

The eWIC System shall validate the household number exists.

Maintain EBA

The eWIC System shall update household demographic data.

Maintain EBA

The eWIC System shall provide via message data detailed EBA information upon request from the MIS using the household number. (Get EBA Details message)

Benefit Issuance/Maintenance Table 7: Benefit Issuance/Maintenance

Req #

Section

Req’d (R)

Pref’d (P) Opt’l (O)

Function / Service / Requirement Description

Offeror Complies:

Comments:

Issue/Credit Benefits to the EBA

The eWIC System shall receive and process message data of benefit issuance (credit) from the MIS. (Add/Update Benefits message)

Issue/Credit Benefits to the EBA

The eWIC System shall validate that the household number and the EBA exist and are active.

Issue/Credit Benefits to the EBA

The eWIC System shall validate that the benefit issuance records are correct in format, including a valid combination of category code and sub-category code and that the benefit ID is unique.

Issue/Credit Benefits to the EBA

The eWIC System shall, to the extent possible, reject duplicate benefit issuance and remit a message to the MIS informing the MIS of the reject and reason for reject.

Issue/Credit Benefits to the EBA

The eWIC System shall validate that the benefit quantity (units available) for the category code and sub-category code on a given date does not exceed the maximum balance (999.99).

Issue/Credit Benefits to the EBA

The eWIC System shall reject benefits whose dates are not synched with other benefit availability dates.

Issue/Credit Benefits to the EBA

The eWIC System shall allow an unlimited number of issuances to a household for a single month.

Void/Debit Benefits from the EBA

The eWIC System shall receive and process message data of benefit voids (debits) from the MIS. (Add/Update Benefits message)

Void/Debit Benefits from the EBA

The eWIC System shall validate that the household number and EBA exist and are active.

Void/Debit Benefits from the EBA

The eWIC System shall validate that the Benefit ID, beginning benefit date and ending benefit date exactly matches the benefit information in the EBA for the categories and sub-categories to be debited.

Void/Debit Benefits from the EBA

The eWIC System shall only void the benefit if there is sufficient balance to post the entire void.