Secondary claim workflows move a balance from a paid primary claim to the next payer, and the software's core job is to reproduce the primary payer's decision accurately enough that the secondary payer can adjudicate what remains. In Carepatron, a secondary claim is created directly from the processed primary claim, and the system carries forward the primary payer's payment and adjustment details automatically so the secondary payer has the coordination-of-benefits context it needs [1]. Pabau describes the same transfer: the software carries the primary payer's payments and adjustment codes onto the secondary claim, preventing re-entry of the second payer's required detail [4]. The workflow is not a fresh claim. It is a derived document whose validity depends on the remittance data selected, the payer sequence recorded, and the adjustment reason codes mapped at the service-line level.
The decision points are concrete and recurring. A user must first establish which payer is primary, because that sequence drives what the primary returns and what the secondary expects [1]. The user must then obtain a remittance, either as an electronic ERA posted automatically or as a manually recorded payment from a paper EOB or payer correspondence [1][4]. Finally, the secondary claim form must expose the primary's paid amount and each adjustment group, code, and reason description, since that line-level data is what the secondary payer uses to determine its own liability [1]. Systems differ in how they structure these steps, how they handle missing remittances, and where they enforce validation.
The workflow is a remittance transfer, not a re-bill
The foundational design choice is whether the secondary claim inherits its structure from the primary claim or is assembled as a new document. Carepatron's documented flow creates the secondary claim from the processed primary claim through a dedicated action in the claim header [1]. The interface asks the user to confirm or adjust three fields: the claim remittance, the secondary insurance, and the billable items [1]. The most recent remittance is selected automatically, but the user can choose a different remittance or add a new claim remittance manually when the primary did not return an ERA [1].
Pabau uses a worklist approach to surface the same transfer. Two chips above the claims list separate work into "Secondary due" for paid primaries awaiting a secondary and "Secondary rejected" for claims returned by a clearinghouse or payer [4]. When the primary pays, the user finds the paid primary claim and submits the secondary; Pabau sends the primary's paid amount and adjustment codes on each service line to its clearinghouse as the coordination-of-benefits information [4]. The difference is navigational: one system exposes the action from the processed claim record, while the other groups pending secondaries in a queue.
Missing remittances expose a manual branch
Every secondary workflow depends on a primary remittance, but payers do not always send an electronic one. Carepatron addresses this by letting users manually create a remittance when the primary responded on paper or by phone [1]. The saved remittance then becomes available for selection when the user creates the secondary claim from that same primary claim [1]. Users can also upload a paper EOB or payer correspondence to keep on file, and the instruction states that once saved, the remittance is available for the secondary claim creation step [1].
Pabau documents the same failure mode with specific consequences. If no ERA arrives, the primary claim remains in a Submitted state, and the secondary cannot be billed because the secondary needs the primary's result [4]. The user must open the submitted primary claim and use a "Record payer payment" action to enter the payment date, payer claim reference, paid amount per charge line, and adjustment group from the EOB [4]. This manual path is not an edge case in either system; it is a required branch of the workflow whenever the primary payer does not return an electronic remittance.
A concrete evaluation: two-payer professional claim with a paper primary EOB
Suppose a practice handles a professional claim where a commercial payer is primary and a second payer is secondary, and the primary returns a paper EOB rather than an ERA. In Carepatron, the user would open the processed primary claim, create the secondary claim, and select or add the claim remittance manually because no ERA arrived [1]. The manual remittance would record the payment and adjustment data from the paper EOB, and once saved it becomes selectable for that primary claim's secondary [1]. In Pabau, the user would instead find the primary claim stuck on Submitted, open "Record payer payment," and enter the payment date, payer claim reference, paid amount per line, and adjustment group from the EOB before submitting the secondary [4].
The observable difference is not whether the secondary can be created, but where the manual capture lives and how the system signals that capture is required. Carepatron presents the remittance as a selectable record within the secondary claim panel [1]. Pabau blocks the secondary until the primary result is recorded, and the primary claim itself displays the missing payment step [4]. A reviewing practice should test both paths with a real paper EOB, and should also examine how each system exposes the final line-level adjustment groups and reason codes on the secondary claim, since that is the data the secondary payer uses to determine liability [1]. This example is a suggested evaluation scenario, not a claim that either system has been tested in that exact sequence.
Where coordination-of-benefits validation is enforced
Secondary claims carry strict coordination-of-benefits arithmetic, and a secondary payer may reject a claim because the figures do not reconcile rather than because of any clinical issue [4]. AlohaABA documents one recurring validation failure: the "Charge Should Equal Paid and Adjusted Amount" error [6]. This error appears when the charge amount on the secondary claim does not match the total paid and adjusted amounts from the primary remittance, and the documented fix is to review the primary remittance or ERA and enter the corresponding amounts in the primary remittance section of the secondary claim [6].
The timing of that validation matters. AlohaABA instructs users not to bill a secondary claim if the primary still needs correction, such as a denial on one charge line [6]. Its workflow allows either automatic balance transfer to secondary when ERAs are auto-posted, or manual transfer upon manual payment posting [6]. The system also advises submitting one secondary claim to each payer initially to confirm acceptance in the payer portal before mass billing [6]. This is a specific operational caution from the vendor's documentation, not a general statement about all clearinghouse integrations, and it reflects the risk that payer-specific COB rules vary.
Payer-specific and form-specific rules change the flow
Secondary billing is configured around the receiving payer, not just the patient's coverage. Optum's Assurance documentation separates two setup tasks: remit import options, which deal with the payers that are the source of the remit data, and secondary billing, which deals with the payers that will receive the secondary or tertiary claims [2]. This separation matters because the rules differ by direction. Remit import concerns where payment information comes from, while secondary billing criteria apply to any payer to whom the practice will send a secondary or tertiary claim [2].
Known payer rules introduce form-specific options. For example, a "Swap Display of Insured/Other Insured (1500)" option changes where the active payer information displays on a 1500 claim, swapping field locations for display only without changing the information on printed forms [2]. A separate Medi-Cal split claim option sends secondary claims to a known payer based on Medi-Cal payer requirements, splitting secondary claims to meet a 14-service-line requirement by default [2]. These are configuration decisions tied to a specific payer's requirements, and they exist alongside rules such as checking for a previous bill to avoid creating a duplicate secondary claim [2].
Manual entry systems expose the required data elements
Novitas Solutions' PC-ACE guidance for Medicare secondary claims shows the data elements a secondary claim must carry when the user is entering it without automatic transfer. For the professional Part B claim, the instructions require a "Y" in the COB field on the Patient Info & General screen to indicate the patient has Medicare as a secondary payer [3]. On the COB Info (Primary) tab, the user enters a code "D" amount for what the primary insurance paid, along with the claim adjudication date from the primary's processing [3]. The line-level entry requires paid units and CAS adjustment fields, where the primary paid amount plus CAS fields equals the total charge [3]. The "EAF" amount for what the patient still owes appears in the institutional Part A instructions, not in the professional Part B sequence [3].
The BlueCross BlueChoice My Insurance Manager guide describes a similar screen sequence for professional secondary claim entry, asking whether the selected plan is the primary payer and directing the user to choose No for a secondary entry [7]. The Other Payer Information screen requires the patient's other insurance information and the amount the other payer paid [7]. The adjustment screen then requires a group code, reason code, amount, and optional quantity [7]. These manual-entry documents clarify what the automated carryover systems are supposed to populate on the user's behalf: the primary paid amount, the adjudication date, and the line-level adjustment group and reason codes.
Sources & references
- Submitting secondary claims in Carepatron | Carepatron Help Center · help.carepatron.com
- Set up secondary billing · pas01.arm.optum.com
- PC-ACE User Guide: Section 3 - Enter a Medicare Secondary Claim · www.novitas-solutions.com
- Submitting secondary claims in Pabau · support.pabau.com
- MIM: Claims Entry · member.bluechoicesc.com
- Secondary Billing in AlohaABA · support.alohaaba.com
- MIM: Claims Entry - provider.bcbssc.com · provider.bcbssc.com