Construct an X12 820 premium payment transaction and reconcile it against payer enrollment records to ensure premium credits are posted correctly for each subscriber
Open the 820 with the BPR segment specifying the payment method code, total payment amount, currency, and the effective entry date; follow with TRN to provide a trace number that links this 820 to the ACH or wire transaction
Build the 1000A payer loop with N1*PR to identify the premium payer and the 1000B payee loop with N1*PE to identify the insurance carrier receiving the payment
For each subscriber, create a 2000 loop with RMR01 set to the reference identification qualifier and RMR02 set to the member or policy identifier; populate RMR03 with the payment action code and RMR04 with the payment amount being credited to that subscriber
Include DTM segments within the 2000 loop to specify the coverage period start and end dates the premium payment applies to, and ENT to group members under the same policy or employer group
Transmit the 820 to the carrier or TPA and retain the BPR TRN trace number to match against the carrier's acknowledgment and subsequent 834 effectuation or termination events
Reconcile each RMR02 member ID and payment amount against the carrier's remittance report or 835-equivalent premium statement; flag discrepancies where the posted amount differs from the 820 remitted amount
Known gotchas
The BPR payment amount must equal the sum of all RMR04 amounts in the transaction; mismatches cause automated posting failures at the carrier even if the ACH deposit clears successfully
Different carriers implement the 820 ENT grouping segment differently; some expect one ENT per employer group while others expect one ENT per coverage type — confirm the trading partner guide before building the loop structure
Premium credit postings are timing-sensitive: an 820 received after the carrier's effectuation cutoff date may result in the member being terminated for non-payment even if the payment was transmitted on time
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp