Financial Management Requirements - AHCCCS

northcarolinasweekManagement

Nov 10, 2013 (3 years and 11 months ago)

71 views


Page |
166














Appendix
B
4


Financial Management
Requirements

Solicitation N
o
.:

YH12
-
0023




O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4




Page |
167


B.4

FINANCIAL MANAGEMENT

The following sections identify the major requirements for key components of the Financial Management functional
areas. The key componen
ts of each are presented below:




Manage Advance Payments of the Premium Tax Credit and Cost Sharing Reductions



Manage Premiums and Payments by



Supporting and tracking premium collection facilitation and processing for both private insurance and public
prog
rams



Managing
AZ
-
HIX

fees




Supporting other
AZ
-
HIX

financial operations including general ledger, trial balance, reconciliation functions
and more



Manage premium stabilization (reinsurance, risk adjustment, and risk corridors)



Collect claims and encounter

data from the small group and individual markets for use by the State in risk
adjustment calculations



Collect enrollee and rate data from outside
AZ
-
HIX

for use by the State in risk adjustment calculations


D
escriptions for each of these business requirem
ents

are summarized below:




Manage Advance Payments of the Premium Tax Credit and Cost Sharing Reductions

Per ACA guidelines, the advance payments of the premium tax credits will assist qualifying individuals
participating in
AZ
-
HIX

with premiums. At the s
ame time cost sharing reductions will limit the cost
burden for out
-
of
-
pocket spending for qualifying individuals.
AZ
-
HIX

will connect to the CMS/IRS
calculator to get the advance payment of the premium tax credit and/or cost sharing reduction of the
quali
fying individual.
AZ
-
HIX

will record and submit this information to CMS so that payments can be
made on behalf of the qualifying individual to the issuer.




Manage Premiums and Payments

AZ
-
HIX

will facilitate and track the premium collection process for pu
blic and private insurance as well
as SHOP.
AZ
-
HIX

will pass the payments to the insurers through this process. This function will include
the facilitation of electronic payments, creation and management of list bills to employers, forwarding
appropriate p
ayments to QHPs net of
AZ
-
HIX

fees.
AZ
-
HIX

will also manage the payments by paying
Navigators under the Navigator program.
AZ
-
HIX

and its
Offerors

will not be responsible for active
premium collection; this will be the responsibility of the QHPs. Late p
ayments, payments not received
or partial payments must support the application of associated rules and actions required to address
notification, enrollment and eligibility.




Manage Premium Stabilization (reinsurance, risk adjustment, and risk corridors)

A
Z
-
HIX

will manage premium stabilization by:



Mitigating the impacts of potential adverse selection



Stabilizing premiums in the individual and small group markets



Stabilizing plan participation in the individual and small group markets



Maintaining viability
of
AZ
-
HIX


The financial management solution must be able to provide the necessary information and services to
calculate reinsurance, risk adjustment and risk corridors. The
Offeror

will work with Arizona to
support proactive management in this area.

O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4




Page |
168





Da
ta Collection

AZ
-
HIX

will support additional data collection process to support Premium Stabilization including:



Collecting claims and encounter data from the small group and individual markets for use by the
State in risk adjustment calculations



Collectin
g enrollee and rate data from outside
AZ
-
HIX

for use by the State in risk adjustment
calculations


N
ARRATIVE
I
NSTRUCTIONS

The Financial Management Requirements narrative must include the following:


1.

How the solution meets all Federal guidance and requireme
nts including the Seven Conditions and
Standards and ACA Section 1561

2.

Detailed description and diagrams, (if available) of the technical and database architecture for the
solution

3.

How the solution/service will integrate with AZ
-
HIX based on the integrati
on standards provided in the
technical requirements.

4.

A detailed description and diagrams, if available, of the technical and database architecture of the
proposed solution, if appropriate for the Business Area

5.

The State’s engagement plan, including communi
ty and partner engagement. The State wants to
understand how the Offeror team will be integrated with the AZ
-
HIX project, what resource
expectations and level of effort are expected and in what time frames. This State engagement plan
should address prop
osed approach for project communication and administration.

6.

The AZ
-
HIX training plan which should address the types of materials and media to be provided, the
specific training approach to be provided, engagement of users and time required, ongoing support

for training. The Offerors are expected to provide all training facilities and materials for their solution
and will be responsible for communication and scheduling.

7.

Maintenance plan for this requirements area. Indicate whether upgrades are automatic or

require
additional programing for configurable or customized Mandatory requirements. This maintenance
plan must be consistent with the technical requirements set forth for each business area included in
this RFP.

8.

Offeror insights and counsel to Arizona f
or this business area.


Maximum number of pages for Financial Management narrative section is
three (
3
)

pages

O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
169



B.4
.1

F
INANCIAL
M
ANAGEMENT
B
USINESS AND
T
ECHNICAL
R
EQUIREMENTS
M
ATRIX
I
NSTRUCTIONS

Offerors must also complete the matrix below. Insert the pri
mary Offeror Name in the heading and complete the columns for each requirement statement.


Each of the Business and Technical Requirements are numbered and ident
ified as Mandatory or Desirable
. Instructions for responding to each requirement
follow:

a.

For
Mandatory Requirements (M), the Proposal must always indicate explicitly whether or not the Offeror’s proposed services meet
the requirement.

b.

For Desirable requirements items, the Proposal must always indicate explicitly whether or not the Offeror's propo
sed services meet the requirement.
The Desirable items must be priced separately from the mandatory items by Business Area in Appe
ndix
D
, Pricing Template. Offerors may also provide
additional functions and features in the table following the requirements
table. These functions, features or services should only be included if they are
provided by the
Offeror

at
no cost

to Arizona. [Reminder: Arizona is NOT seeking Medicaid or other eligibility and enrollment functions, features or
solutions. Arizona has

an eligibility solution that will serve as the centerpiece of the Arizona HIX and that provides the Enterprise Service Bus th
at will
facilitate integration of the solutions being requested in this proposal. Accordingly, proposals submitted that include e
ligibility and other operations not
related to the solutions requested in this RFP may be eliminated as non
-
compliant.]

c.

Arizona’s strong preference is to have Offerors propose highly configurable solutions. Indications that a requirement is con
figurable w
ill be rated higher
than the non
-
configurable items.

d.

The
Offeror

shall provide a list of assumptions while responding to the technical and functional requirements


Complete the Business and Technical Requirements matrices below using the following instruc
tions.


Mandatory/Desirable

Pre
-
filled

Offeror

Response


Check the appropriate column using the following key.

CC

Client Configurable
: Requirement is available and can be configured by the Client without
Offeror

support or involvement.

VC

Vendor

Confi
gurable
: Requirement is available and can be configured by the
Vendor
.

M

Modifiable
: Requirement is available and can be configured by the
Offeror
, but will require some level of modification.

EE

Expandable/Extensible
: Software/Solution can be easily
expanded or extended with a third
-
party product to meet new requirements

C

Custom:
Requirement is not available and would have to be customized for Arizona.

NS

Not Supported:
Requirement is not supported and will not be modified or expanded to meet the

requirement during this project.

In Productive Use?

Enter

Yes or No. Each requirement must be in production and currently in use by a client.

Comments

Offeror

may include a brief statement as to whether it meets or exceeds each requirement; if the re
sponse is “
M
” or “
C
”,
楮T楣慴攠睨整h敲e楴⁷楬氠l敥琠瑨攠牥qu楲敤⁴業敬楮攮⁉e捬cT攠瑨攠to獴so映捵獴fm楺慴楯n⁩渠瑨攠䙩 慮捩慬⁐牯po獡氯P物捩ng⁳ he
Tu汥l




O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
170



Financial Management Business Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


1.


The Financial Management solution shall have the capacity to
handle the financial transactions associated with advance
payments of the premium tax credit and cost sharing reductions.

M









2.


The Financial Management solution shall provide monthly reports
on all individuals enrolled in QHPs for the upcoming month along
with the amounts
of Advance Premium Tax Credits and Cost
Sharing Reductions a
ssociated with the Individuals

M









3.


The Financial Management solution shall get the information
from CMS about the amounts of
Advance Premium Tax Credits
and Cost Sharing Reductions

paid to all QHP Issuers and
Individuals.

M









4.


The Financial Management solution shall support premi
um
payments by facilitating and tracking the premium payments for
both public and private insurance and will pass the premiums to
the insurers net of
AZ
-
HIX

fee

M









5.


The Financial Management solution shall have a payment module
to pay the navigators

based on the navigator program rules set by
Arizona

M









6.


The Financial Management solution shall need to support passing
the commissions for the non
-
assisted applications to
AZ
-
HIX

M









7.


The Financial Management solution shall have the capaci
ty to
electronically receive information on non
-
exchange enrollees
from individual, small group, and self
-
funded plans outside of
AZ
-
HIX

and receive non
-
QHP plan and rate
-
setting data from CMS as
well as other State process The State receives enrollee data

for
plans outside
AZ
-
HIX

from Issuers. In addition, the State receives
rate setting data and enrollment counts for plans outside
AZ
-
HIX

from CMS. The State compares the Issuer supplied enrollee data
with enrollment data supplied by CMS. If discrepancie
s are
found, the Financial Management solution should issue
enrollment discrepancy reports to the Issuer and CMS.

M










O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
171


Financial Management Business Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


8.


The Financial Management solution shall have the capacity to
receive, process, and maintain claims and encounter data from
non
-
gra
ndfathered individual and small group Issuers inside and
outside
AZ
-
HIX
. The Financial Management solution should
generate a detail and summary report to the Issuer regarding
what data has been accepted and rejected

M









9.


The Financial Management so
lution shall have the capacity to
calculate reinsurance payments to Issuers that cover high
-
risk
individuals in order to help stabilize premiums for coverage.
Reinsurance payments apply to Issuers of non
-
grandfathered
individual QHP plans. The Financial M
anagement solution should
provide enrollment data monthly, the total cost of providing
benefits, and the reinsurance contribution payment to the
Reinsurance Entity. The Reinsurance Entity will receive the data
and process the reinsurance contribution paym
ents.


M









10.


The Financial Management solution shall have the capacity to
calculate the risk adjustment payments or charges to Issuers
based on the actuarial risk of enrollees within a plan when
compared to the State average actuarial risk. The Fina
ncial
Management solution should be able to assess charges to low
actuarial risk plans and make payments to high actuarial risk
plans.


M









11.


The Financial Management solution shall have the capacity to
receive enrollee data for individual and smal
l group, participating
inside
AZ
-
HIX
, extract and merge claims/encounter data, enrollee
data, and rate setting data previously collected. The Financial
Management solution shall have the capacity to calculate State
and plan average actuarial risk and calc
ulate risk adjustment
payments and charges, and notify the Issuer.

M










O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
172


Financial Management Business Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


12.


This Financial Management solution shall have the capacity to
collect risk adjustment charges from Issuers and remit risk
adjustment payments to Issuers. The Financial Manageme
nt
solution should be able to update Issuer accounts with Issuer risk
adjustment payment and charge data. The Financial
Management solution shall have the capacity to notify Issuers of
the risk adjustment charges (net negative balance issuers),
receives p
ayments from those Issuers, and monitor for unpaid
risk adjustment charges. The Financial Management solution
should be able to determine the available funding for risk
adjustment payments and remit risk adjustment payments to net
positive balance Issuers
. The Financial Management solution
shall have the capacity to generate the annual risk adjustment
financial report as required by the State or CMS

M









13.


The Financial Management solution shall support electronic
payment methods that supports multi
ple mechanisms such as
credit card,
PayPal
,
BillPay,
online check
, electronic funds
transfers,

and others

M









14.


The Offeror shall conduct continuous internal audits,
reconciliations and other analysis to actively insure that the
appropriate payments
are made to QHPs and
AZ
-
HIX

fees are
appropriately identified and collected. The Offeror shall report
monthly the reviews conducted and the results and associated
corrections made to ameliorate errors identified in these review
processes.

M












O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
173



F
inancial Management Technical Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


1.


The Financial Management solution shall have a Service Oriented
Architecture (SOA) that
is consistent with MITA

M









2.


The Financial Management solution shall support common bi
-
directional interface modalities including generic web services or
APIs

M









3.


The Financial Management solution shall
support the current
version of NIEM
, XML, HL7, TIPS and HIPAA related transactions
such as 820

and

834

M









4.


The Financial Management solution shall have modular and
reusable services and components

M









5.


The Financial Management solution shall have a flexible
architecture that

can easily incorporate changes and new
features

M









6.


The Financial Management solution shall meet the Service Level
Agreement (SLA) and other performance standards set by Arizona

M









7.


The Financial Management solution shall meet ADA and LE
P
requirements set by ACA

M









8.


The Financial Management solution shall meet the HIPPA, NIST,
HITECH, FIPS and FIPs standards as required by ACA

M









9.


The Financial Management solution shall be easily and seamlessly
integrate with
AZ
-
HIX
, Plan
Management, Plan Selection, SHOP,
Appeals Management, Data Warehousing and other solutions
that are a part of the HIX solution in Arizona.
The integration
shall be done through the AZ
-
HIX ESB.
The Offeror shall work on
the integration of their solution wi
th the AZ
-
HIX ESB during the
pre
-
implementation phases of this project.

Because of the fact
that all the Federal requirements have not been finalized and
available yet, there may be some future requirements that could
require
AZ
-
HIX

to have other supportin
g solutions. Hence Arizona
wants the

O
fferor’s solution to have the capacity to integrate
with those solutions if necessary. The solution should be able to
integrate with the Connect2Coverage portal through skinning

M










O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
174


F
inancial Management Technical Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


10.


The State will continuously

analyze the total AZ
-
HIX solution
(which includes the solutions in this procurement) for scalability
and performance. This testing will include the specific AZ
-
HIX
components, including but not limited to the ESB. The State will
conduct load, concurrenc
y and other performance testing before
implementation and on a regular basis after implementation. The
Offeror shall participate in and cooperate with the State’s
conduct of these tests. Further, the Offeror shall work with the
State in analyzing the scal
ability and performance of the AZ
-
HIX
and shall make all necessary changes to their solutions to achieve
the performance levels identified in the Service Level Agreement
as well as industry standard performance expectations as agreed
to with the State of A
rizona. These integrated tests should be in
addition to regular and ongoing performance and scalability tests
that the Offeror should conduct for each individual solution it
provides to the State. The State will require monthly updates of
performance tes
ts conducted, production performance and
changes made to improve results.

M









11.


The Financial Management solution shall be able to integrate
with the Health Plan solutions through a standard 820, 834,
270/271 API or Web Services

M









12.


The Fina
ncial Management solution shall support the following
browsers at a minimum:



Internet Explorer version 6 and above



Google Chrome version 16 and above



Safari version 4 and above (on both Windows and Mac
operating system)



Firefox version 6 and above

M









13.


The Financial Management solution shall support multiple
operating systems such as Windows, Mac, UNIX and Linux

M










O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
175


F
inancial Management Technical Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


14.


The Financial Management solution shall support small devices
that will include the following mobile phones and tablets at a
min
imum:



iPhone



iPad



Android phones and tablets



Blackberry phones and tablets



Windows Mobile phones and tablets

D









15.


The Financial Management solution shall be able to allow a batch
or real time upload of the data that will be required for
AZ
-
HIX

datab
ase to have for SHOP

M









16.


The solution must meet the maintenance schedule followed by
AZ
-
HIX (note: this will be scheduled in a way to minimize
downtime for users).

M









17.


The Offeror shall their solutions are provided on hardware that is
cur
rent within three (3) years unless otherwise agreed to by the
State.

The Offerors software should be current on all the patches
and versions unless otherwise agreed to by the State. The
Offeror will provide a monthly update of patches and other
maintenanc
e performed during the month.

M









18.


The Offeror shall conduct testing to insure backward
compatibility of its solutions and their integration with AZ
-
HIX, It
is expected that these tests will be conducted for any changes,
upgrades to hardware or pat
ches applied.

M









19.


The Offeror shall follow the release schedules set forth in the SLA
and otherwise established for the AZ
-
HIX.

M









20.


The Offeror shall work with AZ
-
HIX team in advance of any
release or change to allow AZ
-
HIX team to adequate
ly test, verify
and train to support the smooth operation of AZ
-
HIX and its
supporting solutions.

M









21.


Offeror

The Financial Management solution shall have the ability
to interface with other solutions to send the financial transaction
data

M










O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
176


F
inancial Management Technical Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


22.


The Offeror shall provide access to their test and training
environments for AZ
-
HIX QA and Training team to ensure the
correct implementation of changes before the changes are
released to the production environment.


M









23.


The Offeror shall provi
de version control management capability
and integrate version control with the State’s content
management solution. All the changes to the solution shall
reported and approved by the State, be maintained in the
Offeror’s version control management soluti
on, which shall be
available to the State for review and audit as needed.

M









24.


The
Offeror

shall submit
detailed documentation

to the State on
the following: the following:



Plan for maintaining the Financial Management solution



Plan for making sure

that the Financial Management
solution always stays current on all the required patches
and software versions and how the
Offeror

team will
work with
AZ
-
HIX

team on following the same solution
maintenance schedule as
AZ
-
HIX



Plan for deploying changes to t
he Financial Management
solution



Testing requirements for changes in the Financial
Management solution



Plan for ensuring backward compatibility on changes



Plan for working with
AZ
-
HIX

team on integrating the
changes into the Financial Management solution



Plan for business continuity



Resource requirements from
AZ
-
HIX

team



Plan for the proposed integration with AZ
-
HIX and its
supporting solutions



Detailed description of the technical and database
architecture of the solution

M









25.


The
Offeror

shall pro
vide their current SSAE 16 certification

for
their solution and the hosting environment in which the solution
will be hosted

to the State of Arizona

M










O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
177


F
inancial Management Technical Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


26.


The
Offeror

shall get their SSAE 16 certification

for their solution
and the hosting environmen
t in which the solution will be hosted

every year and provide that to the State of Arizona

M









27.


The Offeror shall provide a solution that specifically addresses
high availability, scalability, redundancy in order to meet the SLA
set by Arizona

M









28.


The Offeror shall have Disaster Recovery (DR) and Continuance of
Operations Program (COOP) established for their solutions. The
Offeror shall provide their DR and COOP plan and mechanisms to
the State for each of their solutions as part of this subm
ission.
The DR and COOP mechanisms for the Offeror’s solution shall
meet the National Institute of Standards Technology (NIST)
standards,
http://csrc.
nist.gov/publications/nistpubs/800
-
34
-
rev1/sp800
-
34
-
rev1_errata
-
Nov11
-
2010.pdf
.


M










O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
178


F
inancial Management Technical Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
Use?

Comments


M or D

Check Response

(See code table above)

Yes or No


29.


The Offeror shall host the solutions they are providing to the
State unless alternative arrangements are made to host the
Offeror’s solutions on the AZ
-
HIX c
loud, in which case, the Offeror
will be required to pay the proportionate share of the cloud set
up and operating costs. The Offeror must inform the State in
their response to this RFP which of the following options they are
proposing to host their sol
utions:



Offeror Hosted



Offeror Cloud Hosting



Participation in the AZ
-
HIX Cloud


If the solution is Offeror Hosted, the Offeror must meet the SSAE
16 audit requirements and submit the current SSAE with it
s
proposal. If the Offeror cho
o
s
es to host in a clou
d environment
of their own or participate in the AZ
-
HIX cloud environment, the
Offeror must meet the Federal security standards set for the
cloud
environments
http://www.cio.g
ov/documents/Federal
-
Cloud
-
Computing
-
Strategy.pdf
. The Offeror shall include a detail
hosting plan for each solution as well as evidence that they meet
the SSAE 16 requirements and/or cloud computing requirements
set forth above.

M












Additional

Offeror Features Available to Arizona at NO cost

In Production?

How Long in
Production?

In Production for which Client?

a.






b.






c.






d.









O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
179



Financial Management Operational Service Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
U
se?

Comments


M or D

Check Response

(See code table above)

Yes or No


1.


The
Offeror

shall provide technical and other support for the
Financial Management solution issues and questions based on
the SLA set by Arizona

M




2.


The
Offeror

shall create and ma
nage list billing to the employers

M


3.


The
Offeror

shall allow the State to audit without prior notice

M


4.


The
Offeror

shall have intern al audit controls and procedures

M


5.


The Financial Management solution shall maintain the history of
all trans
actions and payments

M


6.


The Financial Management solution shall maintain a general
ledger

M


7.


The
Offeror

shall reconcile the transactions on a regular basis as
directed by the State

M


8.


The
Offeror

should examine accounting records, financial
s
tatements, and other financial reports to assess accuracy,
comprehensiveness, and conformance with reporting and
procedural standards on an ongoing basis as directed by the State

M


9.


The
Offeror

shall follow a process of projecting revenues and
expenses

on an ongoing basis as directed by the State

M


10.


The
Offeror

shall follow a process of
performing financial
investigations, undertaking audits, composing reports, and
detecting fraud on an ongoing basis as directed by the State

M


11.


The
Offeror

shall

follow a process of
providing assurance
regarding the authenticity of information contained in financial
reports and their adherence to statutory and government
requirements on an ongoing basis as directed by the State

M


12.


The Financial Management solu
tion shall generate regular
financial reports as directed b y the State

M


13.


The
Offeror

shall follow a process for
preparing periodic
statements that compare budgeted costs to actual costs on an
ongoing basis as directed by the State

M


14.


The
Offero
r

shall assist the State in creating budgetary and
accounting policies

D



O
FFEROR

N
AME
:


F
INANCIAL MANAGEMENT
R
EQUIREMENTS


S
OLICITATION
N
O
.:

YH12
-
0023

Appendix B4



Page |
180


Financial Management Operational Service Requirements

Mandatory/

Desirable

CC

VC

M

EE

C

NS

In Productive
U
se?

Comments


M or D

Check Response

(See code table above)

Yes or No


15.


The
Offeror

shall have continuous monitoring and make ad
-
hoc
and on
-
demand adjustments of staffing, equipment and other
infrastructure that are required to handle unexpected chan
ges of
needs

M


16.


The Offeror shall provide technical and help desk support for the
Financial Management solution

M


17.


The Offeror shall conduct continuous internal audits,
reconciliations and other analysis to actively insure that the
appropriate paym
ents are made to QHPs and
AZ
-
HIX

fees are
appropriately identified and collected.


The Offeror shall report
monthly the reviews conducted and the results and associated
corrections made to ameliorate errors identified in these review
processes.

M