Patient payment link reconciliation is not one workflow but a set of vendor-specific boundaries around record ownership, posting timing, and report location. CareStack documentation describes a receipt-creation queue for external payment link transactions, while NexHealth instructs practices to post gross payment amounts and use separate settlement and payout reports [1][2]. NextGen directs reconciliation through the InstaMed reporting tool rather than its own application [3]. eClinicalWorks documents a Reconciliation Report that identifies missing transactions and enables the user to add them to the EMR as patient payments [4]. Net Health describes manual payment entry with posting actions, not an automated link reconciliation queue [6][8]. These distinctions matter because a workflow that appears automated in one product may require manual matching or an external processor report in another. The following sections examine what each source actually documents, where ownership of the reconciled record sits, and which questions remain unresolved.
Where the reconciled record lives
CareStack places reconciliation inside its Patient Payments area through a Payment Link Transactions screen with tabs for All, Receipt Created, and Receipt Not Created [1]. The documentation states that patient receipts are automatically created and reflected in the patient ledger when a matching patient is found, and that the Create Receipt button appears only when a patient is manually or automatically matched [1]. This means the reconciled record is a receipt tied to a patient account, and the queue is the primary control point for unmatched payments. The source does not describe a separate processor portal for this workflow.
NextGen takes a different approach. Its documentation states that reporting and reconciliation for NextGen Pay powered by InstaMed is done within the proprietary InstaMed reporting tool, and that NextGen Healthcare does not provide training on the reporting features on the vendor website [3]. The application-side workflow involves exporting the InstaMed report to a Microsoft Excel spreadsheet and reconciling it with the Daily Payment report [3]. Here the reconciled record is a comparison between two report outputs, not a single in-application receipt queue. The source does not state that NextGen Enterprise PM automatically matches vendor transactions to patient payments without this report comparison.
Gross versus net posting and fee handling
NexHealth documentation is explicit about the amount that should appear in the ledger. It states that ledgers should accurately show what was charged and paid by the patient before processing fees are deducted, and that Ledger Sync posts the gross payment amount automatically [2]. For practices without Ledger Sync, the instruction is to manually create a payment equal to the gross amount and not adjust ledger entries to account for processing fees [2]. The Payout statement includes columns for gross amount, fees, and net amount received after fees are removed [2]. This separates the patient ledger record from the processor settlement view.
The distinction has practical consequences for reconciliation. A practice using NexHealth would compare the gross payment in the ledger against the gross amount column in the Payout statement, then account for fees separately rather than altering the patient payment [2]. The source does not describe an automated fee allocation to the ledger. CareStack documentation does not address processing fee handling in the same detail; it focuses on receipt creation and merchant ID routing [1]. Net Health documentation describes posting actions such as Post as unapplied, Apply by DOS, and Apply to Claim(s), but does not specify gross versus net posting rules for payment links [6][8].
A suggested validation scenario for payment link reconciliation
A useful hypothetical test would create three payment link transactions with deliberately different matching conditions: one with a complete patient match, one with a partial name match, and one with no patient match. For each transaction, record whether the system creates a receipt automatically, places the payment in an exception queue, or requires a separate processor report. In CareStack, the expectation from documentation is that a matching patient produces an automatic receipt, while unmatched payments appear under Receipt Not Created [1]. In eClinicalWorks, the Reconciliation Report would be checked for missing transactions, with the scheduled nightly job applying the same amount, same patient, and same date linking rule [4]. In NextGen, the test would require exporting the InstaMed report and comparing it with the Daily Payment report [3]. This scenario is a suggestion for evaluation, not a claim that any vendor has passed such a test.
Matching rules and exception queues
CareStack's exception queue is the Receipt Not Created tab. The documentation states that the Create Receipt button is available only when a patient is manually or automatically matched, and that a toast notification appears stating Receipt Added successfully after the action [1]. The source also describes Auto-Assign Merchant ID, which routes payments to the merchant ID linked to the patient's default location, with a fallback to the default merchant ID in External Payments Account Settings when no match is available [1]. This suggests matching depends on patient details entered on the payment form, but the source does not enumerate every matching field.
eClinicalWorks documents a different exception mechanism. Its Reconciliation Report is described as a feature or utility in the EMR that identifies missing transactions and enables the user to add them to the EMR as patient payments [4]. The source states that the utility enables reconciliation by facility and that a scheduled job runs every night to download payment transactions from the central e-payment gateway and reconcile them with the e-payment transactions in the EMR database [4]. If differences are found, the missing e-payments are added to the EMR database. The job links an e-payment to a patient payment when the same amount, same patient, and same date already exists [4]. The report results include date reconciled, facility, posted by, patient name, TRX ID, amount, date and time, status, card number, type, name on card, product, and payment ID [4]. This is a more granular matching record than CareStack's receipt queue, and the source states that the linking job runs automatically on a nightly schedule [4].
Reporting boundaries and processor dependencies
NextGen's documentation draws a hard boundary around reporting ownership. It states that clients can use vendor website reports to reconcile vendor transactions against reports run from the application, and that clients should contact NextGen Pay powered by InstaMed for information on how to run and download report data [3]. The document revision history notes that payment reconciliation functionality through NextGen Enterprise PM was added in version 26.1, while advanced payment functionality by visit, location, and patient was added in 26.2 [3]. This version boundary means reconciliation behavior may differ across deployments, and the source does not describe the 26.1 functionality in detail.
Rivia Health's marketing page makes a different claim: payments post to the EHR within minutes, automatically, with no batch processing or end-of-day manual step [5]. It also states that every transaction across every channel shows up in one reporting view [5]. These are vendor claims on a promotional page, not a user guide, and the source does not document the underlying matching rules or exception handling. WellSky's announcement similarly describes integrated reconciliation within WellSky solutions and cites performance figures attributed to providers using the platform, including a 65% repayment rate and a 9.4 day average reduction in A/R cycle [7]. These figures are vendor-reported outcomes, not independent measurements, and the announcement does not specify the reconciliation workflow steps.
Manual posting as a contrasting baseline
Net Health ReDoc documentation describes patient payment entry through the Payments menu, where a payment can be linked to a specific claim or remain unlinked [8]. The posting actions include Post as unapplied, Apply by DOS, and Apply to Claim(s), with Apply by DOS automatically linking the payment to an existing claim based on patient and date of service [8]. The Global Payments integration documentation describes processing credit, debit, and ACH transactions within the EHR, with authenticated transactions voidable before being applied [6]. This is a manual or terminal-driven workflow rather than a payment link reconciliation queue.
The contrast is useful for evaluating automation claims. CareStack and eClinicalWorks document exception queues or reconciliation utilities that identify unmatched or missing transactions [1][4]. Net Health documents manual payment creation and posting actions, with unapplied payments later applied in a Payment Batch [8]. The source does not state that Net Health ReDoc automatically matches external payment link transactions to patient accounts. A practice comparing these products would need to ask whether the vendor's reconciliation workflow reduces manual posting or simply moves it to a different screen.
Sources & references
- Setup Payment Links & Manage Transactions – CareStack: User Resource Center · carestack.zendesk.com
- Payments reports and ledger reconciliation | NexHealth Help Center · help.nexhealth.com
- https://docs.nextgen.com/en-US/user-guide-for-nextgen%C2%AE-pay-powered-by-instamed-3319139/reporting-and-reconciliation-through-instamed-reporting-tool-374340 · docs.nextgen.com
- ePayments User Guide · primarycarecoalition.attachments6.freshdesk.com
- Payment Processing Solutions - Rivia Health · riviahealth.com
- Patient Payments | Global Payments Integration · help.nethealth.com
- WellSky® Launches New Solution to Modernize Patient Payments and Streamline Payment Reconciliation - WellSky · wellsky.com
- Patient Payments · help.nethealth.com