Payment posting is the process of recording payer and patient funds, then applying them to specific claim lines so each account reflects an adjudicated balance. Source documentation from Elation, Exa, Kareo, RXNT and ICANotes describes the same core loop: reconcile the EOB or ERA against the check, allocate payment and adjustment amounts line by line, and carry any unmatched remainder to the next responsible party. The named workflows diverge at fewer than a dozen technical decision points, including whether posting is strictly sequential, whether a $0.00 payment can be recorded, how backdating behaves, and when a saved record becomes visible in financial reports. Those differences matter for reconciliation speed and correction behavior, but the public documents do not support ranking one vendor above another on accuracy or efficiency. No source supplies error rates, time savings, payer coverage statistics or integration maturity data, so those questions remain unmeasured.
The shared posting loop: reconciliation before allocation
Elation Billing instructs users to confirm that the EOB total matches the check amount before posting and to resolve any variance before saving [1]. The glossary then distinguishes paper EOBs from electronic 835 remittances and defines allowed, adjustment and patient responsibility values as separate lines on the same claim [1]. This ordering is consequential: if a payment is applied before reconciliation, an incorrectly parsed adjustment code can silently shift a write-off into patient responsibility without any prompt to reopen the check total.
RXNT places a similar check in software rather than as a preceding manual step. When ERAs arrive, the system automatically populates data and identifies errors from the transmitted EDI information, and users can click an Errors tab to verify corrections before the payment can be posted [4]. Exa describes the same reconciliation target in different terms, instructing users to create the payment, then search for claims on the EOB in the Pending Payments tab by patient, claim or invoice number [2]. None of the documents explains how the ERA auto-population tolerates an 835 that matches the deposit amount but contains a provider-level balance adjustment. The presence of a PLB summary in RXNT's View Summary action suggests the question is visible, not that the workflow resolves it automatically [4].
Unapplied amounts and the zero-balance routing decision
A defining control is what the software does with money that has not consumed every balance. Elation Billing turns the Unapplied box green only when the total applied equals the Payment Amount; any red value signals an imbalance, and the Bill To selection determines where the claim routes next, with $0 routed to Settled [1]. This binary visual state makes an allocation gap harder to skip, but it does not tell a biller how to decide between routing a remainder to a secondary payer, patient statement or internal write-off. That decision is left to the operator.
ICANotes uses status rather than color to encode the same constraint. A payment in the Manual Posting Worklist can be Not Ready, Ready to Post or Posted, and Ready to Post is reached only when the distributed amount matches the payment amount [5]. Batch selection then applies to one or more Ready to Post insurance payments at once [5]. Kareo also supports a $0.00 posting path, since its documentation asks whether to post a zero-amount payment after confirmation [3]. The zero-amount option is useful for recording denials or informational-only remits without creating a phantom transaction, but no source states how a zero-amount line affects downstream denial reporting outside Kareo's separate manual denial tracking guidance [3].
Minimum controls to verify in any payment posting workflow
Reconcile first: confirm the EOB or ERA total equals the deposit before line allocation [1]. Then verify that the unapplied amount must reach $0 or an explicit blocked state before the payment posts [1]. Check whether a $0.00 payment is permitted and how that transaction appears in reports [3]. Review whether backdated posted dates persist after reopening [4]. Confirm whether unposted saved payments are excluded from financial reporting and whether batch posting requires a Ready to Post state [4][5]. Finally, distinguish clearing applied funds from deleting the payment history, since those have different audit consequences [2].
Adjustment handling, reversals and correction audit trails
Adjustment codes create the most visible workflow variation. Exa distinguishes credit adjustments, which remove balances such as small write-offs, from debit adjustments, which add money back such as interest paid, and from refund debits [2]. When existing codes are insufficient, Exa permits new codes to be created in Billing Setup, with a recommendation that users add a billing note when adjusting a payment because the history remains on the claim [2]. Kareo documents reversal as a signed transaction, instructing users to enter a minus sign and the amount when reversing a previously posted adjustment before clicking Post [3].
Claim-level versus payment-level association also changes reporting semantics. Kareo describes two common workflows: posting an adjustment related to a Payment record using that payment's posting date, or posting on the Claim record using the current date, with an option to relate the payment [3]. That choice determines whether an adjustment appears in the same financial period as the original remittance or the correction date. RXNT's View History and Audit Log provide a slightly different control, showing changes, saves and actions on the payment, and the audit log can be printed as a PDF or downloaded as CSV [4]. Exa is more direct about deletion: a payment must be deleted if it needs to be completely removed from claim history, whereas applied funds can be cleared or zeroed in the payment module without erasing the record [2].
Posting state, backdating and batch boundaries
The meaning of "posted" is not identical across products. RXNT states that unposted payments saved or draft-saved will not appear in reports as posted payments and their posted dates will not display in grids [4]. It also specifies a backdating rule: if a user backdates the posted date on an unposted payment and then saves, the backdated date will not be retained when the payment is reopened; the posted date defaults to the access date [4]. This is one of the few explicit temporal constraints in the packet and has direct implications for month-end close procedures.
ICANotes exposes a batch boundary that others do not document. The Manual Posting Worklist allows selection of one or more Ready to Post payments, after which the system distributes payments and adjustments to accounts and shows a success message [5]. A payment can also be posted for a claim submitted outside ICANotes+, provided the encounter was first marked as Billed from the Billing Worklist Unbilled Encounters tab [5]. Elation describes a narrower case for unposted residue: patient copay payments can be applied through an Apply Patient Payments tool across all patients instead of manually per claim [1]. Whether that tool changes the same posted-date and unapplied-balance rules as the manual path is not documented in the supplied excerpt.
A concrete evaluation scenario and what remains unknown
Selection between workflows can be grounded in a repeatable case rather than vendor feature terms. One suggestion: take a payer check for three claims where line one pays in full, line two carries a contractual write-off and patient coinsurance, and line three is denied; then measure how many manual entries are required to reach a settled or correctly routed state, whether the software blocks an unbalanced save, and how a corrected adjustment date appears in financial reports. This scenario is specific but is labeled as a suggestion and is not based on any tested implementation.
The documented claims cannot answer which system reduces posting error rates or speeds reconciliation. No source provides structured A/B results, processing-time measurements, denials-before-and-after data, or payer clearinghouse success statistics. Exa documents CSV export of payment records with filtering by any dropdown field [2]; Elation lists payment search and reports including Provider Payment Report and Charges and Financial Transactions Report [1]; RXNT adds a Resolved and Unresolved error view for ERAs [4]. These are observable capabilities, but their operational value depends on untested variables like staff volume, claim mix and payer behavior.
Sources & references
- Recording & posting a payment in Elation Billing · help.elationhealth.com
- Exa® PACS/RIS - Konica Minolta Healthcare Americas, Inc. · healthcare.konicaminolta.us
- Kareo Payment Posting Guide - Amazon Web Services · kareocustomertraining.s3.amazonaws.com
- Create and Post Insurance Payments – RXNT Help Center · help.rxnt.com
- Batch Manual Payment Posting - ICANotes LLC · help.icanotes.com
- Create and Post Patient Payments – RXNT Help Center · help.rxnt.com
- Integrated Billing User Guide · www.va.gov