An Electronic Remittance Advice, or ERA, is the X12 835 transaction that tells your billing team exactly how a payer processed each claim: what was paid, what was adjusted, and why. In a ChiroTouch practice, these files carry the line-level detail that lets you post payments to the correct patient ledger without manually cross-referencing a bank deposit against a stack of paper remittances. When the 835 arrives and posts cleanly, the workflow is nearly invisible. When it doesn't, the same bank deposit that should reconcile in minutes becomes hours of research, and your aging report starts to look unreliable.

Where 835 Files Travel and Where They Get Stuck

The delivery path for an ERA in most ChiroTouch practices runs through three checkpoints: the payer's EDI department generates the file, your clearinghouse (for many practices, CT ProClear powered by TriZetto, or a third-party vendor like Availity or Infinedi) receives it and forwards it, and then the file lands in the designated inbound folder on your ChiroTouch server or Cloud instance. ChiroTouch supports both the 837 claim and the 835 remittance transactions as part of its EDI trading-partner framework, and the configuration screens let you define the file-name masks, segment terminators, and folder paths that control how each file is recognized. For server-based installations, those inbound folders follow a predictable pattern under the CTData directory, for example the EDI subfolder for whichever clearinghouse you use. Knowing that path lets your IT contact or ChiroTouch support pull the raw file and confirm whether it actually arrived before you escalate the issue upstream.

Most delivery failures in 2026 trace back to one of three spots. At the payer level, the ERA may never have been generated because your enrollment record is stale or the correct trading-partner ID is missing. At the clearinghouse level, the file sits in the portal waiting to be pushed, often because SFTP credentials expired or a multi-factor-authentication requirement was added and the receiving connection was never updated. At the ChiroTouch level, the file may have landed in the right folder but failed to parse—typically a delimiter mismatch, a broken ISA/IEA envelope, or a segment count that doesn't balance. Each of these looks different to the billing staff. A payer-side miss means the clearinghouse portal shows nothing. A clearinghouse-side miss means the file is visible in the portal but never appears in your ChiroTouch EDI folder. A parsing failure means the file is in the folder but the import log shows an error and the patient ledger stays untouched.

A practical first step when a batch of ERAs is missing is to log into your clearinghouse portal and search the date range in question. Most clearinghouses retain ERA history for several years, so even a file from a few months ago can often be downloaded as a raw 835 and uploaded manually into ChiroTouch as a stopgap. While you do that, verify the SFTP or file-transfer settings on the Trading Partners screen in ChiroTouch. Confirm that the ETIN, application code, and file-name mask still match what the clearinghouse expects, and check whether the Usage Indicator is set to Production rather than Test. If you recently migrated clearinghouses or updated your server, the inbound folder path may need to be re-pointed so that new files drop into the location ChiroTouch is watching.

Finally, treat your EDI configuration as a living document, not a one-time setup. Payer companion guides change, clearinghouses rotate credentials, and ChiroTouch updates can shift how files are validated. Schedule a quarterly review with your office manager or IT contact: confirm that every active payer still has a current ERA enrollment, that the trading-partner records in ChiroTouch reflect the latest identifiers, and that the inbound folder is clean of orphaned or partially written files. For practices running CT ProClear, the integration handles much of the routing automatically, but configuration drift after a software update or a clearinghouse-side change can still interrupt the flow. Catching a small credential mismatch during a routine check saves your billing team from discovering it the morning a large Medicare or commercial deposit lands with no matching remittance detail.

Sources and further reading