There is no single national endpoint for electronic workers’ compensation forms. In 2026, states differ in whether they accept forms through a portal, EDI, XML/API, SFTP, or paper; which documents each route covers; what setup and testing are required; and whether a separate claimant copy or service step remains. Build a separate, versioned workflow for each state and form, and verify the agency’s current technical instructions before changing production filing.
What a state-specific integration needs to handle
A connection that successfully sends one transaction does not necessarily file every document associated with a claim. Treat each state’s filing process as a set of distinct capabilities rather than a single “electronic filing” switch.
- Endpoint and coverage: Record the accepted channel—such as portal, XML/API, EDI, or SFTP—and the particular forms or transactions it supports. Keep a separate route for documents that must be uploaded or mailed.
- Sequence and prerequisites: Identify events that must exist first, such as initial claim creation, and any required acceptance before a later form can be filed.
- Access and testing: Track account registration, trading-partner relationships, technical testing, and production approval separately for each jurisdiction and channel.
- Payload rules: Version schemas, form templates, transaction releases, file formats, size limits, filename rules, and naming conventions.
- Evidence and service: Store portal receipts, acknowledgments, rejections, claim-history references, and proof of any separate delivery to the claimant or another party.
- Effective dates: Make mandate dates and transition notices operational configuration—not assumptions embedded in code.
State-by-state filing differences
| State | Channels and coverage | Sequence, setup, and technical rules | Receipt, claimant delivery, and change notes |
|---|---|---|---|
| New York | The Workers’ Compensation Board lists eCase, XML submission over secure file transfer protocol, and an API that exchanges XML for electronic forms. The eForms page identifies RFA-1LC and RFA-2 channels and form-specific filing information. | XML and API participants must successfully complete mandatory testing before filing. The Board describes eCase submissions as requiring no additional testing or registration steps for that method. The Board posted an RFA-1LC XML template/schema and requirements update on March 16, 2026, and a new request reason effective March 20, 2026. | The Board’s February 17, 2026 notice set March 20, 2026 as the effective date after which paper insurer/employer RFA-2 forms would not be accepted or acted upon, and said the legacy RFA-2 web form would become obsolete. Its OnBoard page separately says payer RFA-2 eForm use is mandatory as of April 8, 2026, and paper forms postmarked after April 7 would not be accepted or acted on. Because the notice and page express the boundary differently, use the current form-specific instruction and confirm with the Board if a postmark or submission date is disputed. |
| Pennsylvania | WCAIS claim-tab uploads, certain forms generated in WCAIS, accepted EDI transactions for specified forms, and hard-copy mail are among the routes. The Department of Labor & Industry identifies particular forms for which EDI alone does not satisfy filing requirements. | An initial First Report of Injury (FROI) is required to establish the WCAIS claim. The Bureau cannot attach forms received before that transaction because a claim does not yet exist in the system. The agency prefers upload to the individual claim’s Actions tab when possible; some uploads should be made one form at a time to create separate claim-history entries. | When information is submitted through EDI or upload, a true and correct copy must still be provided to the claimant as required by applicable law, regulation, or policy. For example, the newest LIBC-751 suspension/modification notice must be signed and dated, delivered to both claimant and Bureau within seven days of its effective date, and preceded by the relevant EDI acceptance. |
| Texas | TXCOMP accepts uploads for workers’ compensation participants, including medical reports, insurance forms, hearing documents, appeals, and other DWC forms. DWC also offers secure SFTP exchange for Austin carrier representatives, insurers, and other professional organizations. | TXCOMP uploads must be Word, Excel, read-only PDF, or TIFF; each file must be under 10 MB and its filename under 60 characters. The portal prohibits certain special characters in filenames. The SFTP route accepts read-only PDFs, uses To_DWC and From_DWC folders, and publishes file-naming standards; access is requested from the agency with company and contact details. | A TXCOMP profile is needed to upload and receive a printable receipt. SFTP stamps files with the date received and returns a copy; some filing groups also receive a daily Excel acknowledgment. Do not assume that the additional acknowledgment applies to every document group. |
| Colorado | The state’s Online Filing of First Reports page points EDI stakeholders to vendor resources and discusses transition to CoComp. | The state page reports that Verisk began accepting only EDI 3.1 filings on July 9, 2026. Confirm the current release requirement, test status, and technical details with the state and relevant vendor before deployment. | Detailed operational requirements are not stated in the material available here; verify the live state page and linked technical guidance. |
| Alabama | The Workers’ Compensation Division describes electronic reporting by trading partners and names insurers, self-insureds, TPAs, and servicing agents or vendors as possible senders. | The state describes a trading partner as a business entity that has established a relationship with the Division to report claims electronically. Confirm the current relationship or approval process; the description does not establish that every vendor is approved. | Specific file constraints, acknowledgments, claimant-copy rules, and version dates are not stated in the material available here; confirm these in the current state guidance. |
How to design the filing workflow
1. Make the state and form—not just the claim type—the routing key
Maintain a capability matrix with one row per state/form/channel combination. Include whether the document is covered by EDI, whether a portal or separate form upload is required, the applicable schema or transaction release, and the agency’s effective date. Pennsylvania’s distinction between EDI-covered forms and forms requiring another route illustrates why a general “claim filed” status is too coarse.
2. Model prerequisites and dependencies explicitly
Represent claim creation, transaction acceptance, document submission, agency acknowledgment, and claimant delivery as separate events. In Pennsylvania, an initial FROI must establish the WCAIS claim before later forms can be attached. For the specified LIBC-751 workflow, the relevant EDI acceptance precedes the notice, and delivery to the claimant and Bureau remains a separate requirement. Avoid marking a case complete merely because the EDI transmission succeeded.
Recommended Free Tools
#1 Best Overall
3. Gate technical connections before production
Keep sandbox or test approval, trading-partner setup, credentials, and production activation as distinct deployment gates. New York requires successful testing for XML/API eForms; its eCase route has different setup expectations. Alabama’s trading-partner description likewise makes the relationship with the Division a separate onboarding item. Confirm each state’s current access process rather than assuming that approval for one route or vendor covers another.
4. Validate documents before transmission
Apply each endpoint’s constraints before creating an upload job. For Texas TXCOMP, validate the allowed document format, the under-10-MB limit, the under-60-character filename limit, and prohibited characters. For SFTP, use DWC’s published naming standards and the accepted read-only PDF format. For XML/API, pin the applicable schema and form-specific edit rules; New York’s March 16, 2026 RFA-1LC requirements update and March 20 request-reason change show why a once-valid payload may need revision.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
5. Preserve evidence for filing and service
Store the outbound payload or document, submission timestamp, destination, agency receipt or acknowledgment when provided, any rejection details, and the claim-history reference. Track claimant delivery separately where required, including method, date, and proof. Pennsylvania expressly retains the claimant-copy obligation for information sent by EDI or upload, so an agency transmission record alone does not establish that delivery occurred.
6. Maintain exception and change-management paths
Keep a supported route for forms that require a separate upload or paper submission, and define who handles rejected, late, or unattachable documents. Monitor agency change notices for schema edits, mandate dates, release transitions, and vendor changes. Colorado’s reported EDI 3.1 transition is a release-version concern; New York’s RFA-2 notice and OnBoard page also show that date boundaries can be expressed differently across agency materials.
Scope and verification
This overview covers official guidance from New York, Pennsylvania, Texas, Colorado, and Alabama; it is not a complete inventory of every state’s forms, deadlines, or EDI specifications. Requirements can change, and the Colorado and Alabama details summarized here should be checked against the live agency pages. Before a production change, verify the target jurisdiction’s current form list, accepted channel, technical guide, test and trading-partner requirements, claimant-service rules, and effective dates with the agency.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
