Medical software billing programs are best understood as decision engines rather than invoice printers. The primary documentation for four distinct systems shows the same underlying sequence: a billable event is captured, a payer is selected by rule, a claim format is produced, and the result is reconciled. What changes between systems is who makes each decision and how much of it is configurable at the site level. The Alabama Department of Mental Health's WITS guide describes a strict payer cascade triggered when an encounter is released to billing [2]. The VA's Integrated Billing manual describes modules split by staff role, from insurance verification to third-party bill creation [1][3]. CMS documentation fixes the professional claim formats themselves [4]. Reading these together shows where a software choice genuinely matters and where it is merely a label.

Payer sequencing is the first real differentiator

WITS documents an explicit order of operations. When an encounter is released to billing, the system checks for a third-party liability rate and an active TPL enrollment record; if both exist, the claim is created against that plan. If not, it checks for a Medicaid rate and active Medicaid enrollment, and then for a government contract subject to stated restrictions. A claim paid in full at one payor does not move to the next, and an encounter with none of the three enrollment records cannot be released to billing at all [2]. That last rule is the operationally significant one: incomplete enrollment data blocks revenue before any claim exists.

The VA's Integrated Billing package approaches the same problem through role separation rather than a single cascade. Insurance verifiers use an Insurance Data Capture module to collect and store patient and carrier-specific data, while billing clerks work in the Patient Billing and Third-Party Billing modules [1]. The manual also records that the package stores annual benefits associated with group plans and provides an insurance worksheet for the verifier [3]. In both systems, the payer decision depends on data captured upstream of the bill. A practice evaluating software should therefore ask where enrollment and coverage records are maintained, and what happens to a claim when that record is missing.

Paper and electronic claim formats are fixed outside the software

CMS documentation draws a boundary that no billing vendor controls. The CMS-1500 is the standard paper claim form used by non-institutional providers and suppliers to bill Medicare Administrative Contractors, and CMS permits paper submission only where Administrative Simplification Compliance Act exceptions apply. The 837P is the standard electronic format, with ANSI ASC X12N 837P Version 5010A1 identified as the current version [4]. The National Uniform Claim Committee designs and maintains the CMS-1500 form, while the X12 implementation guide is purchased under an X12 license [4].

Each MAC publishes a CMS-approved Medicare fee-for-service HIPAA 837P Companion Guide that defines Medicare-specific data content used with, but not in place of, the HIPAA 837P standard [4]. CMS describes implementation and companion guides as technical documents that may require help from billing agencies, clearinghouses, or software vendors to interpret [4]. For a buyer, this means the software's job is to populate a fixed envelope correctly, not to define it. A vendor that presents claim-format handling as proprietary differentiation is describing configuration work against a public standard, and the companion guide for the relevant MAC remains the controlling reference.

Practical detail: build the payer test before the demo

Before a vendor demonstration, write down the payer order your organization actually uses and the enrollment record that must exist for each step. Then ask the vendor to show, in a training environment with fictitious data only, what happens when that record is missing. WITS documentation makes the failure mode explicit: without a TPL, Medicaid, or government contract enrollment record, the encounter cannot be released to billing [2]. A vendor that cannot demonstrate the blocked case has not shown you its payer logic, only its happy path.

Where billing modules sit inside a larger record system

The VA manual describes a package that moved from identifying billable episodes of care to owning the billing process through to passing charges to Accounts Receivable, with three added modules for Claims Tracking, Encounter Form Utilities, and Insurance Data Capture [3]. It automates creation of third-party billing forms including UB-82, UB-92, and the HCFA-1500, allowing entry, editing, authorizing, printing, and canceling of bills, and it expands UB-92 functionality to add or edit unlabeled form locators except 49 [1]. Site parameters let medical centers vary package behavior, and users can enter new billing rates and VA pension income thresholds [1][3].

That configurability is a governance question as much as a technical one. A system whose rates and thresholds are locally editable requires a named owner for those values, because the software will apply whatever is entered. The VA manual also notes that management reports supply workload, productivity, statistical, and historical data [1][3], and its sample clerk productivity report shows bills listed by rate type, entry date, status, and amount [3]. Reports of that shape support reconciliation against a deposit or a remittance, which is the practical test of whether a billing module closes the loop or merely opens it.

Laboratory and behavioral health settings diverge sharply

The CAP TODAY product tabulation covers billing, accounts receivable, and revenue cycle systems for laboratory settings, and its entries show deployment variety rather than a single model. One listed product is described as a standalone system designed to interface with any company's laboratory information system and EHR, deployed on a local server or third-party cloud hosting, with updates covered by a standard software maintenance fee [6]. Another entry in the same tabulation describes a modular product that can be tailored to most lab environments with on-premises or cloud deployment [6]. The tabulation states that information is supplied by the companies listed and does not represent an endorsement by the CAP [6].

Behavioral health documentation describes a different center of gravity. The AWARDS BillingBuilder feature bills payers for services recorded in AWARDS, and the listed payer types include Medicaid, Medicare, private insurance, self-paying clients, or any other third-party payer accepting 837I or 837P files, HCFA paper claim forms, or printed invoices [5]. Access is permission-gated, requiring the BillingBuilder button plus executive administration or fiscal buttons unless the user belongs to designated fiscal or executive groups [5]. A laboratory system's central object is a test order and its payer rules; a behavioral health system's central object is a service encounter tied to a client's coverage enrollment. Comparing them on feature counts misses that difference.

A worked evaluation example, and what documentation cannot settle

Consider a hypothetical suggestion, not a tested result: a small multi-clinician practice wants to confirm that its billing module will not release a claim to the wrong payer. The evaluator could build three fictitious patients in a training environment, one with only third-party liability coverage, one with only Medicaid, and one with no enrollment record, then release an encounter for each and observe the outcome. WITS documentation states that the third case cannot be released to billing [2], and its guide instructs users of the testing environment to enter only fictitious data, keep it professional, and use a @test.com domain for any email address on a fictitious account [2]. The same three-case script run against a vendor's training instance would reveal whether the payer logic is documented, configurable, or absent.

Several questions remain genuinely open. The VA manual's revision history shows continuing patches, including a September 2026 update touching sections on American Indian and Alaska Native billing and a prior patch synchronizing copay information between existing copay interfaces within Vista [1]; the public documents do not establish how those changes affect any non-VA deployment. The CAP TODAY tabulation reports vendor-supplied answers and leaves blanks where companies did not respond [6], so absence of a listed capability is not evidence of absence. CMS notes that ASETT, available through its Identity Management System, checks electronic claims for HIPAA EDI compliance across formats including ASC X12 5010 [4], but passing a syntax check does not establish that a claim is payable. None of these documents supports a conclusion about which program is better for a given organization.