Skip to main content
All CollectionsPaymentsLedger sync
Payments with Ledger Sync
Payments with Ledger Sync

Ledger Sync displays open balances from your practice management system, and syncs back completed payments

Updated over a week ago

NexHealth Payments with Ledger Sync reads outstanding balances from your health record system and then automatically posts completed payments directly to your ledger.

Ledger Sync integrations

Ledger Sync is available as a premium add-on for customers using Dentrix, Open Dental, and Eaglesoft.

Ledger sync features

  • See patients with open balances directly in NexHealth, and request payment with a couple of clicks

  • Collect via text and email-to-pay links, through our credit card Terminal, or by charging saved cards on file

  • Send payment request links to guarantors or dependents

  • Automatically send detailed patient statements (no more paper statements)

  • Save time on collections with automated payment reminders

  • Auto-sync payments to the right patient and procedure in the ledger

Patient statements

With Ledger Sync, patient statements are automatically included in every Payment Request. Recipients receive a detailed breakdown of the specific ledger items requested for payment, including:

  • The original ledger item value

  • The impact of any payments, adjustments, and insurance estimates on each item

This ensures transparency, reducing patient confusion and follow-up inquiries.

Because statements include sensitive health information - such as procedures performed and their associated costs – NexHealth has a setting to automatically include a request for patients to verify their date of birth and last name to view the statement and complete the payment. This is an added security measure to protect patients’ information.

You can turn this setting off by navigating to Settings --> Payments configurations --> Auto-Send Statements

Request access

Dentrix, Eaglesoft, and Open Dental users can click here to request access and speak with a member of our team.

Did this answer your question?