Payments
Payment posting
Post once, into a ledger that only ever adds. Allocate payer payments to claims and lines. Financial history is append-only: corrections are new entries, never edits, so you can always see how a balance got where it is. When a past posting can be overwritten, month-end reconciliation becomes detective work. What ships here includes claim and line-level allocation; append-only financial history. Used day to day by accountant, biller roles, with availability marked available. Open the sample screen on the right, then walk the steps below — or book a demo and put your hand on the same flow with synthetic data.
A/R aging · payer responsibility
What it is
Allocate payer payments to claims and lines. Financial history is append-only: corrections are new entries, never edits, so you can always see how a balance got where it is.
The problem it solves
When a past posting can be overwritten, month-end reconciliation becomes detective work. Accountants need to trust that history stays history.
Process
How it works, step by step
- 1
Start from remittance
Open a normalized ERA or record a payment.
- 2
Allocate
Apply amounts to claims and service lines.
- 3
Write to the ledger
Each posting becomes a permanent entry.
- 4
Correct with new entries
Mistakes are fixed by adding reversing entries, so the trail stays complete.
What's included
Everything below is part of payment posting today.
- Claim and line-level allocation
- Append-only financial history
- Reversals instead of edits
- Patient responsibility carried to statements
- Feeds aging and reports instantly
- Every posting tied to a person
The guardrail
No one, including admins, can silently rewrite a posted amount.
Where it fits: the full rcm loop
This is the whole job of a billing company, end to end. Every step lives in MEDBIX, so nothing falls into the gap between two tools.
- MEDBIX
- Clearinghouse / payer
- Person decides
- 1
Patient & insurance on file
MEDBIXDemographics and coverage, from import, EHR ingest or entry.
- 2
Eligibility (270/271)
Clearinghouse / payerCoverage confirmed through the clearinghouse before billing.
- 3
Charge capture → claim draft
Person decidesEncounter becomes a draft claim in the builder.
- 4
Deterministic scrub
MEDBIXRules run; AI can explain any finding.
- 5
Human review & approve
Person decidesRequired before anything leaves.
Audience
Who uses it
These roles work with this feature day to day. Access always follows what your admin assigns.
Works closely with
More in Payments
Deep dive
What Payment Posting means in daily ops.
Practical context for Payment Posting: how teams use it, where it sits in the loop, and what to ask in a demo.
- Tied to how billing work actually splits
- Clear on human vs machine responsibility
- Links into related MEDBIX areas
Practice
Where this shows up on a busy day.
From morning eligibility checks to end-of-day posting, Payment Posting connects to the queues your team already lives in.
- Morning coverage and claim build
- Midday scrub and approval
- Afternoon denials and patient pay
Control
Keep a person on the send button.
Whatever page you're on, MEDBIX keeps AI in a propose role. Approvals, posting and rule activation stay human.
- Named approvals
- Visible AI proposals
- Immutable audit trail
Next
See Payment Posting against your volume
Bring your payer mix and the friction you feel today. We'll map it onto sample data in thirty minutes.
- Sample data only
- Your questions drive the agenda
- Written follow-up after
Common questions
How do we fix a wrong posting?
Add a correcting entry. The original stays visible, which is what auditors want to see.
Does posting update A/R?
Immediately.
Can AI post payments?
No. Posting is always a human action.
Want to walk MEDBIX against your real claim mix?
Thirty minutes with sample data. We'll follow one claim through the gate, then talk about your payers, practices and where the rework hurts today.
Notes from the billing floor
Occasional, practical writing on denials, A/R and running a billing company. No spam, unsubscribe any time.