What comes in
Remittance received
- Claim: 1048
- Payer payment: $160
- Contract adjustment: $40
- Patient balance: $0
Payment PostingIn beta
Match the payment. Know what is still owed.
Caesar posts payments against the right claim and checks for differences. Your team can see the balances that need attention without re-keying each payment by hand.
- Matches payments to the right account
- Flags differences for follow-up
See the work
Matched payments move on. Differences stay visible.
Illustrative ledger examples showing routine posting and a payment that needs review.
What comes next
Account updated
- Claim 1048 matched
- $160 payment posted
- $40 adjustment recorded
- $0 remaining balance
The remittance and claim entries match. Deposit reconciliation can proceed.
What Payment Posting does
- 1Read remittance
- 2Match claim
- 3Post payment
- 4Reconcile deposit
What comes in
Deposit comparison
- Deposit reference: 5724
- Posted payments: $160
- Deposit received: $145
- Difference: $15
What comes next
Reconciliation task
- $145 deposit matched
- $15 difference flagged
- Posting records attached
- Assigned to staff for review
The $15 difference stays visible until your team resolves it.
What Payment Posting does
- 1Collect entries
- 2Compare deposit
- 3Flag difference
- 4Staff review
What it handles
A payment needs more than a posted amount.
Payment Posting is part of Caesar's Revenue Cycle agent. It connects the remittance with the account balance so your team can see what was paid and what remains open.
Read the remittance
Read electronic payment details and match them to the claim and patient account in your connected system.
Post the payment
Record insurance and patient payments, with contractual adjustments applied according to the rules your team configures.
Find the difference
Compare payments with available contract amounts and flag underpayments or entries that do not match.
Reconcile the deposit
Tie posted payments to deposit records and keep unresolved differences available for your team to review.
Fits your practice
Keep the payment trail intact.
Start with the remittance and accounting connections your practice uses. Define how exceptions should reach your posting team.
- 1
Connect the records
Read payment information alongside the claims in your practice management system.
- 2
Match the account
Identify the claim and account before recording a payment.
- 3
Apply the posting rules
Record payments and approved adjustments, with differences flagged.
- 4
Review the exceptions
Leave unmatched entries and deposit differences in a review queue.
Unmatched money needs a person.
Your team sets the adjustment rules and resolves entries the agent cannot confidently match. A short payment should remain available for follow-up rather than disappear into a closed balance.
- Review unmatched payments and adjustments
- Check underpayments against available contract data
Keep your existing system.
We confirm the available connections and functions in your electronic medical record system, or EMR, before setup.
Check your EMR integration
Available functions vary by system and agent.
Before you start
Your questions, answered.
What to expect from Payment Posting, and what your team controls.
How is this different from the full Revenue Cycle agent?
Payment Posting matches remittance and patient payments to accounts, applies approved adjustments and reconciles deposits. It is part of the same Revenue Cycle platform as Coding & Billing, Prior Authorization and Denial Management. An underpayment can continue into the follow-up queue.
How accurate is automated posting?
Reading structured remittance avoids re-keying each payment by hand, but matching still depends on payer data and account records. Unmatched entries go to staff with the source details. Check posting accuracy on your own remittance mix during the beta rollout.
Does it catch underpayments, or just post what the payer sent?
It records the payment and checks claim lines against the available contracted rates. Underpayments and variances are flagged for follow-up instead of being closed as paid in full.
How does bank reconciliation work?
Posted payments are compared with bank deposits. Missing or short payments remain in a review queue, and the connected accounts-receivable (A/R) aging record is updated as payments are posted. Your team resolves the differences.
Which systems does it work with?
It parses EDI 835 remittance into the connected practice management system and reconciles with available bank records. It works alongside EHRs including Epic, athenahealth, eClinicalWorks and NextGen. Payment sources and posting functions are confirmed before setup.
Is the Payment Posting function HIPAA compliant?
Yes. The Payment Posting function runs on HIPAA-compliant infrastructure. A time-stamped audit trail records each posted transaction. Caesar Health executes a Business Associate Agreement (BAA) at contract signing. SOC 2 Type II is in progress.
What is an 835 file?
An 835 is electronic remittance advice explaining a payer's payment, adjustments and remaining balances. Caesar matches those details to the claim and patient account before posting.
Can it post patient payments and contractual adjustments?
Yes. Supported workflows include credit card, check and cash payments, along with insurance remittance. Contractual adjustments and write-offs follow your payer contracts and approved rules. Exceptions remain visible for staff review.
Is Payment Posting live or in beta?
It is in beta. We confirm remittance formats, account matching and posting connections before enabling a payment workflow. Timing depends on the source files and review requirements.
Payment Posting
Trace a payment through your practice.
We will show how remittance can reach the right account and where your team reviews a mismatch.
Book a demo