RFI 18001 Remittance and Imaging Solution_Final.pdf

Request for Information (“RFI”)

RFI #DOR18001

Remittance and Imaging Solution

I. Glossary of Terms

This RFI contains references to many acronyms, abbreviations and terms that may be unique and specific to the Department. The following glossary is presented to offer a quick reference to assist the reader in understanding the acronyms, abbreviations and terminology used throughout the RFI.

CRS – Colorado Revised Statutes, a compilation of Colorado State laws

DPA – Colorado Department of Personnel & Administration

Department – Colorado Department of Revenue, a department of the State of Colorado

ICL – Image Cash Letter

ICR – Intelligent Character Recognition

MICR – Magnetic Ink Character Recognition

OCR – Optical Character Recognition

OIT – Governor’s Office of Information Technology

Offeror – Any individual or entity that submits a response, or intends to submit a response to this RFI

RFI - Request for Information

State - State of Colorado, including Departments of the Executive Branch

VSS - Colorado Vendor Self Service, the State’s solicitation platform where the Department’s solicitations are published at: https://codpa-vss.hostams.com/webapp/PRDVSS1X1/AltSelfService.

II. Solicitation Information

A. Introduction

The State of Colorado, Department of Revenue (“Department”) is issuing this RFI in an effort to gain information regarding a solution for a comprehensive deposit, remittance, return, image processing, data capture and retrieval system. The system is to provide Intelligent Character Recognition

(“ICR”)/ Optical Character Recognition (“OCR”) capture, image assisted data entry, deposit, and remittance processing for the Department. The Department is open to a variety of strategies and is interested in hearing from Offerors who have experience with implementing remittance and imaging solutions.

B. Administrative Information

As provided in Colorado Revised Statute (“CRS”) §24-103-201.5, as amended, the Department is issuing this RFI. The Department is interested in receiving information from interested Offerors.

The intent of this information gathering is to assist the Department with preparation of a solicitation for procurement of goods and services.

THIS IS NOT A SOLICITATION FOR GOODS OR SERVICES.

https://codpa-vss.hostams.com/webapp/PRDVSS1X1/AltSelfService

Information that any interested party wishes to submit will be done so voluntarily and with the understanding that this RFI is for information gathering purposes only and is not a formal solicitation.

A formal or informal solicitation may be issued as a result of this RFI. Cost information will be used solely for the purposes of establishing a potential target budget for the acquisition of the necessary goods and services. Cost information presented during this information gathering process will not be considered as responsive to any solicitation subsequently issued.

Any future solicitation will be published by the Department through the Colorado Vendor Self

Service (“VSS”) system. Vendors may register at the following link: https://codpa-vss.hostams.com/webapp/PRDVSS1X1/AltSelfService. The VSS Help Desk is available Monday through Friday 8:00 a.m. to 5:00 p.m. MT and can be reached by calling (303)-866-6464 or emailing

VSSHelp@state.co.us.

The Department shall be under no obligation to pay for any information or ideas submitted in response to this RFI or any costs incurred by any party as a result of this RFI. The Department may elect to use all or part of the information submitted as a response to this RFI for the development of a solicitation.

The Department reserves the right to contact Offerors for additional information at its sole discretion.

This RFI will be posted to Colorado VSS at: https://codpa-vss.hostams.com/webapp/PRDVSS1X1/AltSelfService. The Department intends to use both VSS and additional methods of notification and may make the RFI available to organizations not currently registered in VSS. In the event that it becomes necessary to revise any part of this RFI, a modification notice will be posted on VSS. It is important that Offerors check VSS on a regular basis, as this is the sole method for communicating changes.

C. Schedule of Activities Activity Date/Time

RFI Issued August 17, 2017

Deadline for Inquiries August 23, 2017/ 4:00 PM MT

Deadline for Submission of Responses September 8, 2017/ 4:00 PM MT

D. Sole Point of Contact

The Department’s sole point of contact regarding this RFI is:

Tara Betz, Purchasing Agent

Colorado Department of Revenue

Purchasing and Contracts Services

Email: tara.betz@state.co.us

E. Inquiries

Inquiries regarding this process, the submission of general or specific information, including the need for any information from Department staff, and any and all other questions shall be submitted in writing. The Purchasing Agent shall be the sole contact for any inquiries. Email is the acceptable and preferred format for inquiries. Inquiries must be submitted via email to the purchasing agent on or before the Deadline for Inquiries identified in the Schedule of Activities. Any email should contain

“RFI #DOR18001/ Remittance and Imaging Solution” in the subject line.

Inquiries will be compiled and responses will be posted on VSS.

https://codpa-vss.hostams.com/webapp/PRDVSS1X1/AltSelfService mailto:tara.betz@state.co.us

F. Submission of Responses

Responses may be submitted by to the purchasing agent in an electronic PDF format, or by mail to the address below.

Responses emailed to the purchasing agent and should containing “RFI # DOR18001/ Remittance and

Imaging Solution” in the subject line.

The electronic copy of the responses can be mailed through an overnight delivery service to the following address:

Tara Betz, Purchasing Agent

Colorado Department of Revenue

Purchasing and Contracts Services

RFI# DOR18001/ Remittance and Imaging Solution

1375 Sherman Street Room 323

Denver CO 80203

The Department requests that be received on or before the deadline for submission of responses identified in the Schedule of Activities.

G. Meetings/Presentations

Offerors responding to this RFI may be invited to meet with and provide a presentation to the

Department and other stakeholders. However, the Department does not guarantee that submission of information by an Offeror will result in a scheduled meeting.

Demonstrations/meetings with the Department and other stakeholders may begin upon receipt of responses from Offerors. The dates and times will be coordinated and mutually agreed upon by the

Department, other stakeholders, and the Offeror, with the Department making the final decision in the absence of a mutual agreement. Meeting may be conducted via telephone. Offeror demonstrations may be completed live at the Department or via a web based conferencing system maintained by the

Offeror. The purchasing agent will schedule and facilitate any meetings or presentations.

H. Disclosure of Responses

The Department reserves the right to have information submitted in response to this RFI be reviewed by other entities within the State for purposes of compiling and analyzing possible options.

Otherwise, the materials submitted in response to this RFI will not be publicly disclosed until such time that a competitive solicitation has been issued and an award has been made by the Department.

At such time, all materials will be made available for public disclosure with the exception of those materials determined by the Department to be confidential or proprietary (see Section II. I.).

In the event that the Department determines that a competitive solicitation will not be issued as a result of the RFI process, the materials submitted in response to this RFI shall be open to public inspection in accordance with the provisions of the “Colorado Open Records Act”.

I. Confidential/Proprietary Information

Any restrictions of use or inspection of material contained within the response outside the process identified in Section II.H, shall be clearly stated in Offeror’s response. Written requests for confidentiality shall be submitted by the Offeror along with a justification for the materials should be considered confidential or proprietary. The Offeror must state specifically what elements of its proposal are considered confidential or proprietary and/or those considered to be intellectual property of the Offeror.

Confidential/proprietary information must be readily identified, marked and packaged separately from the rest of the response. Co-mingling of confidential/proprietary and/or intellectual property and other information is NOT acceptable. Neither a response, in its entirety, nor response price information will be considered confidential and proprietary. Materials that would not be considered confidential in response to a solicitation will NOT be considered confidential for the RFI response.

The Department Purchasing Unit Manager will make a written determination as to the apparent validity of any written request for confidentiality. In the event the Department does not concur with the Offeror's request for confidentiality, the written determination will be sent to the Offeror. (refer to

CRS §24-72-201 et. seq., as amended, Public (open) Records)

III. Purpose and Background

A. Purpose

The purpose of this RFI is to evaluate if the Department has industry standard best practices in place and/or if significant improvements could be achieved in the areas of mail opening, imaging, data capture, payment processing, and system interfaces. Some questions in this RFI relate to specific areas where the Department believes improvements might be attainable while other questions relate to features of the current system that the Department finds advantageous. However, please do not limit your response to only these specific questions as the Department is interested in all options available.

B. Background

The Department administers a wide variety of taxes, licenses, and fees from individuals and business entities which are the principle source of revenues for Colorado state government. The Department is also charged with administering a variety of other revenue and licensing programs, including those of the Division of Motor Vehicle, Lottery, and Enforcement (Gaming, Marijuana, Liquor, Tobacco, Racing, and Auto Industry).

The Department of Personnel & Administration (“DPA”) provides Central Services to state agencies and political subdivisions that include a full range of micrographic, digital imaging, microfilm conversion, data entry, system development, and on-line web based forms design. In addition to these services, DPA provides print and mail services, document imaging, project management, and consulting services to include business workflow design, digital storage and object migration to other media. DPA provides data entry and imaging services to the Department for tax processing.

The Department is responsible for form identification, payment processing, balancing, and sending deposits to the bank (Check21). DPA in Pueblo performs 99% of the mail opening, mail prep, and scanning. DPA also performs 100% of the data entry functions outside what is required for payment processing. (e.g. balancing and low confidence OCR MICR reads).

Process Flow Chart

DPA Mail Services Collect mail from

USPS GMF in

Denver and deliver to

Pueblo

DOR Incoming Mail Receive documents from mail, cashiers, and other DOR sources and deliver to

Remittance Processing

DPA Prep Team Zip Code sort, XRay, Cut Mail and deliver to Prep room

DPA Prep Team Prep mail for scanning and sort out any exceptions to return to DOR

DPA Imaging Team Jog and scan all transactions, Paper documents go to warehouse for destruction after 90 days.

DOR Remittance

Processing Prep and scan all transactions received, Paper documents go to storage for destruction after

90 days.

DOR Remittance Processing Manually Identify any forms not read by system and adjust forms to meet business rules

Money

Transactions

No Money

Transactions Invalid/Exception

Transactions

DOR Remittance

Processing

Key Scanlines, Amount Paid, Check

Amount, Review all information, and balance money

Check21

Deposits Sent to Bank

Output 1

Payment outputs created

Output 3

Image

Outputs

Created

DPA Data Entry

Team

Key all return data that has failed validation and business rules

Output 2

Return data outputs created

Output 3

Image data outputs created for No Money

Transactions

DPA Exception

Processing Team

Review all invalid and exception transactions found at any point in the system and determine if they need to be pulled and returned to

DOR, rescanned, or if further instructions can be provided for processing and returned to workflow

DOR Imaging BA Team

Review and correct any output 2 or 3 files that have errors and verify all files are loaded into GenTax

Outputs

Sent to

GenTax

DPA and Department Tax Volumes Fiscal Year 2016

Month Mail Received Images Scanned Total Keystrokes # Checks Deposited

Jul-16

93,524 871,364 15,912,688 119,177

Aug-16

140,870 924,085 12,145,113 141,475

Sep-16

203,016 1,404,190 11,715,660 187,149

Oct-16

145,810 1,502,776 12,927,626 159,074

Nov-16

129,549 604,993 12,342,148 108,057

Dec-16

111,405 687,523 4,954,271 111,622

Jan-17

158,872 1,482,820 8,946,041 192,449

Feb-17

222,127 1,686,023 31,520,329 112,237

Mar-17

212,067 2,043,898 22,328,177 152,965

Apr-17

555,723 4,052,040 28,299,488 428,838

May-17

208,481 1,453,447 41,429,886 135,972

Jun-17

169,232 1,044,168 18,538,925 159,862

Totals 2,350,676 17,757,327 221,060,352 2,008,877

IV. Overview

The Department is seeking a solution that can meet or exceed the following minimum requirements:

A. System Capabilities

Ability to interface with other systems. 1.

Ability to create a payment data file and a tax return data file that can be matched in a 2.

backend interface.

Ability for system’s image quality to meet or exceed X9.37 industry standards. 3.

Ability to virtually order the documents in a transaction. 4.

Ability to research exception issues. 5.

Provide a clear/understandable mixed integrity rules with simple configuration at the 6.

batch and transaction level.

Provide reporting and tracking functionality so that images and data may be tracked the 7.

entire way through the system and reconciled.

Ability to add additional hardware. 8.

Ability to route items to different queues. 9.

Ability to handle processing of envelopes. 10.

B. OCR/ Magnetic Ink Character Recognition (“MICR”) Performance

High OCR accuracy for names, addresses, and numbers. 1.

Ability to read forms from different printers and from multiple sources. 2.

Ability to accept items indexed from barcode sheets. 3.

Ability to perform basic index and output at the scanner level instead of fully setting up a 4.

data entry system.

C. Data Entry

Ability for operators to utilize short cut keys for ease of use and to reduce the number of 1.

key strokes.

Ability to have multiple items on screens while keying items. 2.

Ability to move items within batches and transactions to correct document ordering error 3.

during capture.

Ability to split documents containing data on both sides of the page. 4.

Ability to insert/create virtual items within a transaction and/or batch. 5.

Ability to change items within the system during processing without having to pull and 6.

rescan an item.

Ability to perform quality control of images prior to form identification. 7.

Ability to read 1D and 2D barcodes. 8.

Ability to work at transaction and batch level. 9.

Ability to fix issues at any time in the work flow process. 10.

Ability to see both stubs and checks on the same screen while balancing transactions. 11.

Ability to handle large transactions exceeding 100 pages. 12.

Ability to handle at a minimum the following exceptions: 13.

a. Incorrect Form IDs

b. Double feeds detected after scanning

c. Bad check images

d. Transaction type issues

e. Items that must be pulled due to issues with the forms

f. Rescans

g. Reject/re-entry

h. Delete/insert items and transactions

Ability to manually route to specific review queues. 14.

Ability to attach comments to items and redirect the routing for others to review the 15.

comments.

D. Reconciliation and Banking

Ability to send files directly to the bank that includes at a minimum: creation, sending 1.

(after balancing), confirmation and system detection to prevent duplicate files sent to the bank and an interfaced system.

Allows for on demand Image Cash Letter (“ICL”) file transfers throughout the day. 2.

Contain reconciliation capabilities of system for accuracy with images and return data at 3.

output.

Ability to reconcile with another interfaced system. 4.

Notification to users of issues with failed transactions and files. 5.

E. Reporting

Canned and custom reporting capabilities. 1.

Ability to report real time, accurate reports of the following: image counts, keystroke 2.

counts, OCR read rates and document counts by form type.

F. Configuring the System & Requirements Gathering

Ability to update configurations due to annual income tax and legislative changes. 1.

Ability to process documents from other state agencies at the same time as the 2.

Departments.

G. Technical Aspects

Ability to work in different locations over 100 miles apart. 1.

Ability to work in a virtual domain and have multiple active directories. 2.

Work across multiple networks. 3.

Auto archive log files with no manual intervention or risk of system failure. 4.

Push software updates and fixes in accordance with Governor’s Office of Information 5.

Technology’s (“OIT”)’s major incident change management policy, available at https://docs.google.com/document/d/1psee75taa8JBS_MbSpLwJvDfgA-dkLWRsk-wn1xk7uY/edit.

Ability for services to remain logged in to system and run without a Windows user 6.

account.

Have API or another easy interface into the system for 3rd party applications to connect 7.

for receivable confirmation.

Encryption while system is at rest. 8.

Have a version control system available. 9.

Comply with OIT standards and securities policies, including, but not limited to: security, 10.

privacy, change management IT enterprise architecture and/or hardware where applicable. Any system will be subject to security reviews by OIT’s Office of Cyber

Security during the design phase and before acceptance. Any system must meet OIT-

OCS security standards. The State’s Information Security Standards and Policies, available at: http://www.colorado.gov/cs/Satellite/OIT-Cyber/CBON/1249667675596.

V. Response Information and Format

Based on the information provided in this RFI, please respond to the items below. In addition to the specific items, any information and ideas submitted may also address, in general terms, any features, conditions or provisions the Offeror feels should be considered that would generate additional value in terms of effectiveness and efficiency for the solution.

PLEASE RESPOND IN WRITING TO EACH OF THE ITEMS BELOW:

A. Offeror Information

Identify Offeror point-of-contact for any questions or concerns specific to its response 1.

Provide name, title, address, telephone number, and e-mail 2.

Provide a brief description of the solution or solutions with particular attention to the 3.

goods and services identified in this RFI

B. System Capabilities

Describe any particular challenges you have encountered or foresee interfacing with any 1.

of the systems and the backend systems your solution currently interfaces with including any image repository systems.

Describe your expected system speed rates (response times) for the following at a 2.

minimum: Data entry, Image Viewing and Item capture.

Describe your system’s capability to meet or exceed X9.37 industry standards and any 3.

challenges you have encountered or foresee with meeting these standards.

Describe your system’s ability to virtually order the documents in a transaction. Can 4.

your system do this automatically? How would you handle reordering multi page forms where a taxpayer submits multiples of the same form type in one transaction?

Describe your system’s process for researching exception issues. 5.

Does your system provide some means of editing and re-exporting out of the imaging 6.

system for tracking purposes when a data output file needs a manual adjustment?

https://docs.google.com/document/d/1psee75taa8JBS_MbSpLwJvDfgA-dkLWRsk-wn1xk7uY/edit https://docs.google.com/document/d/1psee75taa8JBS_MbSpLwJvDfgA-dkLWRsk-wn1xk7uY/edit http://www.colorado.gov/cs/Satellite/OIT-Cyber/CBON/1249667675596

Please describe your system’s capability to provide clear/understandable mixed integrity 7.

rules with simple configuration at the batch and transaction level.

Please describe your ability to provide reporting and tracking functionality so that images 8.

and data may be tracked the entire way through the system and reconciled.

Does your system provide the ability to reuse image files to reprocess when issues arise 9.

as opposed to requiring the file be fixed or rescanned from hard copy?

Does your system have the ability to provide a direct link to transmit data to an outside 10.

vendor (e.g. bank)?

Please describe the types of queues used to track and perform various work items: 11.

Money, No money, large dollar, etc. Are they configurable?

Please describe how your system handles adding additional hardware and the compatible 12.

types of scanners. Colorado currently uses IBML, Canon Scanners, and Kodak scanners

Describe your systems process for building sort patterns and the ease of sort pattern 13.

changes.

Does your system have the capability to ingest images from a file rather than directly 14.

from a scanner?

How are customers similar to us handling items such as correspondence and Index Only 15.

forms in your system?

Describe your system’s capabilities for routing items to different queues. Do you have the 16.

ability for users to specify a queue for a work item to be routed to?

How does your system handle prioritization of queues? 17.

How does your system handle prioritization of transactions within queues? Do you have 18.

the ability to manually prioritize if needed?

How does your system handle Envelope Processing: Double feed detect off or another 19.

option to replace and capture the envelope separate?

Is your system transaction based or batch based? If it is a mixed system, at what point do 20.

you switch from batch to transaction level? For example, if transactions are scanned as a batch, at what point does it break into transactions?

Describe the usual type of outputs customers similar to us typically use for interfacing 21.

with other systems (e.g. flat file, XML).

C. OCR/MICR Performance

Describe your system’s OCR capability such as: the number and types of OCR engines 1.

used; the voting process and how is the confidence level nominalized between the OCR engines to avoid having the least conservative engine win?

On a typical good quality machine printed form, what would be the expected read rate 2.

and accuracy? Of the OCR errors generated, what percentage would be flagged for correction verses the number of errors not detected and passed through? Describe the process for achieving the best OCR read rates and accuracy for your system.

Describe the process and challenges encountered for “tuning” OCR templates as forms 3.

are printed and received from multiple sources and printers.

How does your system handle items that are indexed from a barcode sheet? 4.

Describe your system capability to perform a basic index and output from the scanner 5.

level to avoid having to be fully set up in a data entry system?

D. Data Entry

Describe your data entry environment and how work items are presented to operators. 1.

Describe your data entry environment’s ability to accept short cut keys for ease of use by 2.

the data entry operators and to reduce the number of keystrokes. Describe the ease of balancing and keying items your system provides. Can you see multiple images at the same time? How do you move directly to items within a batch or transaction?

How many images can you have on the screen while keying items: Checks, Stubs, Etc. 3.

Can you or how do you move items within batches and transactions to correct document 4.

ordering errors during capture. Eg. Sorting errors from mail opening double feeds at scanner.

Does your system have the capability to split documents containing data on both sides of 5.

a page: front and back once captured at the page (e.g. front/rear) level?

Do you have the ability to insert/create virtual items within a transaction/batch? If so, 6.

describe the process.

Describe your system’s capability for changing items within the system during 7.

processing without having to pull and rescan an item. For example, if a form is ID’d incorrectly, can it be corrected at any point in your system without needing to be deleted and rescanned?

Does your system have the capability to allow for quality control of images prior to form 8.

identification?

How does your system handle 1D barcodes and 2D barcodes: reading, read rates, data 9.

validation, ease of changes, scan area adjustability, etc.

Describe your system’s ability and ease to work at a transaction level vs. batch level. 10.

Is a user able to change form type any time in the work flow? We would like the ability 11.

to fix issues on the fly rather than physically pulling an item and rescanning.

While balancing transactions, does your system provide the capability to see both stubs 12.

and checks on the same screen?

Does your system provide the ability to jump to individual documents rather than having 13.

to page through every document in a large multi transaction?

Describe your system capabilities to handle very large transactions or documents that are 14.

100 pages or more. Include any challenges you have encountered or foresee with this.

Describe your system capabilities for handling exception items to include the following 15.

items at a minimum:

Incorrect Form ID’s

Double Feeds detected after scanning

Bad check images

Transaction Type Issues

Items that must be pulled due to issues with the forms

Rescans

Reject /reentry

Delete/insert items and transactions

Does your system allow for items to be manually routed to specific review queues for 16.

different tax groups based on operator questions or issues?

Is your system capable of allowing comments to be attached to the item and having it 17.

rerouted back to the original queue for an operator to view comment and process or to route it to another queue for exception processing?

E. Reconciliation and Banking

Describe your process for sending files to the bank to include at a minimum: creation, 1.

sending (after balancing), confirmation and system detection for duplicate files sent to

Bank and another system.

Does your system allow for on demand ICL file transfers throughout the day? 2.

What methods are used for ICL File transfer and data file outputs: protocol / method? 3.

Describe the reconciliation capabilities of your system to ensure all images and return 4.

data are accounted for at output.

Do you have the ability to reconcile with other interfaced systems to ensure all output 5.

files, images, and return data were successfully transmitted?

How does your system notify the user if there are issues with failed transactions and 6.

files? Please describe this capability at all levels in the system (e.g. from the scanner to your system and from output to another interfaced system.)

F. Reporting

Describe your system’s capabilities for canned and custom reports. 1.

Does your system allow for real time, accurate reporting of image counts, keystroke 2.

counts, OCR read rates, and document counts by form type?

What does your system consider a counted keystroke, page or image? 3.

G. Configuring the System & Requirements Gathering

Describe the methods and tools used to update configurations due to annual income tax 1.

and legislative changes.

Describe your system’s annual form change process, new form creation, and new job 2.

creation process. Include details on any flexibility or ease built into the process. Does your system provide the ability for the Department to set up new jobs and forms themselves without having to go to the Offeror for setup?

Describe how your solution could be configured to accomplish separation of jobs, system 3.

processing and work queue flow.

H. Technical Aspects

Work is processed in two different physical locations over 100 miles apart. This includes 1.

scanning and data entry at both locations. The two locations are on two different networks and cross multiple firewalls and have multiple active directory domains.

Additionally, the team responsible for checking all output files and handling any file errors is at a third location and also on a separate network. Given this information, describe the required IT system architecture for your system.

Describe your system’s ability to handle multiple active directory domains and networks. 2.

Is it capable of working with a virtualized domain service?

Does your system auto archive log files so that they don’t require manual intervention or 3.

risk system failure?

Describe your process for pushing updates and fixes from one environment to the next. 4.

Describe any automation or other steps that make the process easier. 5.

How are your release notes written and verified prior to providing them to your 6.

customer?

Does your system rely on the knowledge of the implementer to know what services to 7.

stop and start and in what order and on what server or does it provide uniform dependency that eliminates the room for error?

Services shouldn’t require a Windows user account to remain logged in for it to stay 8.

active. Please describe your system’s ability to meet this requirement.

Does your system provide API or some easy interface into the system for 3rd party apps 9.

to connect for receivable confirmations?

Does your system provide encryption at rest? 10.

What, if any, version control system do you utilize (e.g. Git)? 11.

Describe your current platform and what technologies are used. 12.

Is there any software being used in the system which is now or will soon be deprecated 13.

(e.g. Microsoft Silverlight)?

If so, what is your process for migrating off the deprecated software? 14.

I. Forms Review and Feedback

The Department forms are created on a 6 x 10 grid and tax software vendors are required 1.

to reproduce forms on the same grid. Tax software vendors must submit samples to DOR for approval prior to deployment in their tax software. Tax software vendors are required to print a 2D barcode on the DR 0104 and the higher volume schedules that are filed with

Individual Income Tax Returns. The 2D barcode contains all of the taxpayer data that is printed on the tax form. The Department’s 4 highest volume forms are listed below.

a. Form/DR 0104, Individual Income Tax Return

b. DR 0104EP, Colorado Estimated Income Tax Payment

c. DR 0100, Sale Tax Return

d. DR 1094, Colorado W-2 Wage Withholding Tax Return

Using the links below, please review the current version of the four highest volume forms listed above. Make comments or suggest design changes that could improve OCR read rates and accuracy.

https://www.colorado.gov/revenue (link to DOR’s website) https://www.colorado.gov/pacific/tax/forms-number-order (link to web page with forms sorted by form number)

Does your system have the ability for items to be keyed by one operator and reviewed by 2.

another operator for training purposes within the production environment?

J. Pricing Information

Explain potential pricing and terms for the solution. Projected costs should include major 1.

line items as well as a final inclusive cost projection.

Please provide pricing for development, ongoing maintenance and hourly rate for change 2.

requests/tasks orders.

Identify any cost savings to be considered 3.

https://www.colorado.gov/revenue https://www.colorado.gov/pacific/tax/forms-number-order