H.R. 6956 requires that any Federal tax return prepared electronically but printed and filed on paper include a scannable code that can be used to convert the return into electronic format, and it directs the Internal Revenue Service to use barcode scanning technology to read those codes. The bill also requires the IRS to use optical character recognition (OCR) or similar technology to transcribe paper-filed returns that were not prepared electronically, paper correspondence received by the agency, and any electronically prepared paper return that cannot be accurately converted via barcode scanning.
The statute includes a narrowly drawn exception allowing the Treasury Secretary to suspend these automation requirements if the technology proves slower or less reliable than manual transcription or other IRS processes, provided the Secretary reports the determination to the House Ways and Means Committee and the Senate Finance Committee within 30 days. The bill phases in the requirements on different return types with staggered effective dates, creating a predictable window for the IRS and private-sector vendors to implement scanning, barcode, and OCR capabilities.
At a Glance
What It Does
Requires electronically prepared but paper-filed Federal tax returns to carry a scannable code and directs the IRS to use barcode scanning to convert those returns to electronic data; mandates OCR (or similar) for non-electronic paper returns and most paper correspondence. Allows a regulatory exception if automation performs worse than manual processes, subject to a mandatory report to congressional tax committees.
Who It Affects
IRS operations and technology teams, tax software vendors that generate printable returns, tax preparers who print e‑filed returns, commercial barcode/OCR vendors, and individuals or businesses that still file paper returns or send paper correspondence to the IRS.
Why It Matters
It pushes the IRS toward automated capture of paper intake, which can lower manual-entry error and processing time but requires software updates, scanning infrastructure, and new quality-control workflows across the federal tax system.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The BARCODE Efficiency Act targets a very specific gap: taxpayers who use electronic preparation tools but still mail a printed return, and all other paper documents the IRS receives. For returns that begin their life as an electronic file and then are printed and mailed, the bill mandates that the printed return include a machine-readable code that, when scanned, reproduces the return data in electronic form.
The IRS must use barcode scanning technology to read that code and ingest the data.
If a return was never electronically prepared, or if for any reason the barcode scan cannot accurately reproduce a return’s data, the bill requires the IRS to use optical character recognition or functionally similar technology to transcribe the paper content. The OCR requirement also applies to most paper correspondence the IRS receives, except for documents that were already transmitted electronically to the agency.The statute does not lock the IRS into a particular vendor or a fixed optical standard; it allows “functionally similar” technologies, which gives the agency flexibility to adopt different scanning and text-recognition systems.
At the same time, the Secretary of the Treasury may suspend either the barcode or OCR requirement if the agency determines—based on speed and reliability—that manual transcription or another process is superior. That suspension cannot take effect without a 30-day report to the House Ways and Means Committee and the Senate Finance Committee explaining the determination.Finally, the bill staggers when requirements begin to apply: a shorter lead-in for individual income returns, a longer lead time for estate and gift returns, and an intermediate schedule for other returns and correspondence.
Those staggered start dates create predictable implementation windows for both the IRS and private-sector software and service providers.
The Five Things You Need to Know
The bill requires a scannable code on any Federal tax return that was prepared electronically but printed and mailed; the code must convert the return’s data to electronic format when scanned.
The IRS must use barcode scanning to capture data from those scannable codes and must use OCR (or functionally similar technology) to transcribe paper returns not prepared electronically and most paper correspondence the agency receives.
The Secretary of the Treasury can exempt the IRS from the barcode or OCR requirements only if the technology is slower or less reliable than manual transcription or another IRS process, and the Secretary must report that determination to the House Ways and Means Committee and Senate Finance Committee within 30 days.
The bill allows technologies described as "functionally similar" to OCR—meaning the agency can adopt different scanning/text-capture approaches rather than a single technical standard or vendor.
The statute phases in compliance: individual income returns take effect on Jan. 1 of the first calendar year beginning more than 180 days after enactment; estate and gift returns take effect on Jan. 1 of the first calendar year beginning more than 24 months after enactment; other returns and correspondence take effect on Jan. 1 of the first calendar year beginning more than 12 months after enactment.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Gives the Act its public name: the Barcode Automation for Revenue Collection to Organize Disbursement and Enhance Efficiency Act, or the BARCODE Efficiency Act. This is purely titular but clarifies how the statute will be cited in future references and regulations.
Barcode requirement for electronically prepared, paper-filed returns
Requires any Federal tax return that began as an electronic preparation but is printed and filed on paper to "bear a code" that converts the return’s data to electronic format when scanned. It also directs the IRS to use barcode scanning technology to perform that conversion, subject to the exception in subsection (c). Practically, this compels tax-preparation software developers and professional preparers to embed a machine-readable code in their printable output and forces the IRS to accept and process that encoded data via scanning workflows.
OCR requirement for non-electronic returns and paper correspondence
Requires the IRS to use optical character recognition or functionally similar technology to transcribe (1) returns that were not electronically prepared, (2) electronically prepared returns whose data cannot be accurately converted via the barcode, and (3) paper correspondence received by the IRS (except correspondence already received electronically). This provision expands the agency’s mandated automation beyond only barcode-scannable returns to most of the agency’s paper intake.
Exception where automation is slower or less reliable; reporting requirement
Gives the Secretary of the Treasury authority to suspend the barcode or OCR requirements if the Secretary finds the relevant technology is slower or less reliable than manual transcription or other IRS processes. Any such determination triggers a mandatory report to the House Ways and Means Committee and the Senate Finance Committee within 30 days. That reporting requirement creates a congressional oversight checkpoint before an exception takes effect.
Staggered effective dates by return type
Sets phasing rules: individual income returns become subject to the statute beginning on January 1 of the first calendar year that starts more than 180 days after enactment; estate and gift returns receive a 24‑month-plus lead time before January 1 of the first calendar year after that interval; all other returns and correspondence have a 12‑month-plus lead time. These staggered dates aim to give the IRS and private parties different implementation windows depending on return complexity.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Paper filers who use e‑file software but mail prints—faster processing and fewer manual-entry errors should translate into quicker confirmations and potentially faster refunds for many taxpayers.
- IRS processing and case teams—automation reduces repetitive data-entry work, lowers typographical error rates in intake, and can free staff for higher-value adjudication or enforcement tasks if the agency manages transition well.
- Tax software vendors and large preparers—clear statutory demand creates a market for embedding compliant machine-readable codes in printable returns, allowing vendors to productize a capability that many clients will soon require.
- Commercial OCR and barcode technology vendors—new procurement demand from the IRS and possibly from third-party preparers will create contract opportunities for scanning hardware, recognition software, and validation services.
- Taxpayers and businesses that send voluminous paper correspondence—automated capture can speed routing and initial triage for multi-document submissions, improving response times for common routine matters.
Who Bears the Cost
- Internal Revenue Service—must invest in scanning hardware, OCR engines, software integration, validation and QA, and training; initial capital and integration costs could be substantial across field offices and mail processing centers.
- Small tax-preparation businesses and boutique software vendors—must update print layouts, integrate barcode generation, and validate output; these development and compliance costs fall disproportionately on smaller market participants.
- Taxpayers who continue to mail returns—if paper is misprinted, the barcode is illegible, or OCR misreads handwriting, filers may face processing delays and additional correspondence to resolve errors.
- Third-party service providers and contractors maintaining legacy ingestion systems—may need to replace or heavily modify systems to interoperate with new barcode/OCR workflows, or face loss of contracts.
- IRS oversight and compliance units—the agency must build validation, reconciliation, and error-resolution processes to handle cases where the barcode/OCR capture diverges from taxpayer intent, increasing short-term operational complexity.
Key Issues
The Core Tension
The bill’s central trade-off is efficiency versus risk: it forces automation that can materially reduce manual workload and error rates, but it shifts technical complexity, costs, and operational risk to the IRS and private vendors without prescribing interoperability standards, encryption, or minimum accuracy thresholds—leaving a difficult balancing act between speed, reliability, vendor burden, and taxpayer protections.
Two practical problems stand out. First, the bill mandates machine-readable capture but does not specify technical standards for barcode format, encoding schema, encryption, or error-correction.
That creates interoperability risk: different vendors could embed incompatible codes or encode fields differently unless the IRS issues clear implementation guidance, and the burden of that standard-setting will fall to the agency during rulemaking or procurement.
Second, OCR accuracy varies dramatically with handwriting quality, document condition, form variation, and language; the statute delegates the decision on whether automation is acceptable to the Secretary but ties any suspension to a 30‑day congressional report rather than a pre-implementation validation regime. That timing and the lack of mandated quality thresholds mean the IRS must design internal metrics (accuracy, throughput, false-positive rates) and remedial processes (human review, taxpayer notice, appeals) to avoid creating a new class of processing errors and taxpayer disputes.
Additionally, privacy and security concerns arise because embedding full return data in a barcode could increase exposure if not encrypted or access-controlled, a point the bill does not address.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.