Payment Posting
Post payments quickly with intelligent posting workflows. Support for manual entry, ERA auto-posting, batch imports, and patient payments via Square integration. Every transaction is recorded with a complete audit trail.
Works with
- ERA/EOB ProcessingImport and auto-post electronic remittance advices with intelligent payment matching.
- Patient StatementsGenerate, batch, and send patient statements with multiple delivery methods.
- Financial ReportingComprehensive billing reports including AR aging, collections, payer mix, and denial analytics.
Payment posting is the moment money that arrived in the bank is recorded against the charges it paid. Done well, the ledger tells the truth: what each claim was paid, what was adjusted, what the patient still owes. Done badly, a practice can be collecting well and still not know it. Payment Posting handles every way money arrives and records each one with the same audit trail.
Insurance payments arrive as ERAs and post through the review-and-commit workflow, with the remittance identifiers stored on every line. Patient payments arrive through Square from a statement link or by mailed check and post to the patient account. Payment files can be imported as batches and matched to the charges they cover.
Nothing posts twice. Each payment carries the identifiers of its source: the remittance and service line for an ERA, the transaction reference for a card, the batch and sequence for an import. A second attempt to post the same source is recognised and refused, which is the difference between a ledger you reconcile and a ledger you trust.
Key Benefits
ERA auto-posting
Batch import capability
Square payment integration
Complete audit trail
What payment posting does
ERA auto-posting with review
Electronic remittances are matched line by line and committed behind a guard that refuses to post onto a charge that changed since staging.
Manual posting
Paper EOBs and individual payments are entered against the charge with the adjustment reason, in the same structure as electronic postings.
Batch import
Payment files load as a batch, match to charges, and post with the batch reference on every line.
Square patient payments
Card payments from statements and the patient portal post to the patient account with the Square transaction reference.
Idempotent by design
Every posting stores its source identifiers. The same remittance line, card transaction, or batch entry cannot be posted a second time.
Complete audit trail
Who posted what, when, from which source, and the balance before and after, on every transaction. Reversals are recorded as new entries, never as edits.
How It Works
Receive
Payments arrive as ERAs, card transactions, checks, or imported payment files. Each is identified by its source reference.
Match
Each payment is tied to the charge or patient account it belongs to. Unmatched items go to an exceptions queue rather than a suspense account nobody reviews.
Post
Matched payments are committed to the ledger with their adjustment reasons and source identifiers.
Reconcile
Posted totals are compared with deposits by day and by source, so the month closes against the bank statement rather than against a hope.
Frequently asked questions
How does the platform prevent double posting?
How do patient card payments reach the ledger?
What if a posting was wrong?
Ready to transform your payment posting?
Built for healthcare practices that are done fighting their billing software.