Practice Mate posts every remittance line against its own reason code, so a payer denial is never written off as a contract adjustment. Headquartered in Sugar Land, Texas. Posting for practices in all 50 states.
Most practices believe their billing is healthy because their denial rate looks fine. If your team posts remittances into a single adjustment bucket, that number is fine because the denials were never recorded as denials. They were recorded as money the payer was entitled to keep. The claim closed, the balance left accounts receivable, and nothing in your system will ever surface it again. Practice Mate exists to stop that from happening quietly, every month, for years.
Payment posting fails in a specific way that no other billing function shares. It does not leave the claim open for somebody else to catch. It closes the claim, incorrectly, and removes it from every worklist that would have found it.
The claim closes, the balance leaves accounts receivable, and it never reaches a denial worklist. Your denial rate does not move, because the denial was never recorded as one.
A zero pay remit is a denial with no dollars attached. Posted as a payment of zero, the claim balances to zero and closes with the denial reason sitting unused in the adjustment codes.
The payer allowed less than your contract requires. Without an expected allowable to compare against, there is no event to detect. The claim closes correctly at the wrong number.
The payer takes back a prior overpayment out of a current check. Applied to the current claims, the old claim still looks paid and the new ones look short. Three records now wrong instead of one corrected.
A PR balance that never moves to a statement is a balance nobody is collecting. It ages against an insurance follow up process that will never work it.
The primary posted, the remainder was coordination of benefits rather than patient responsibility, and nothing generated the secondary claim. Secondary filing windows often run from the primary remittance date, so the clock started at posting.
Practice Mate posts remittances as a classification function. Automation applies the amounts. People make the decisions about what your practice is prepared to lose.
Electronic remittance advice and paper explanation of benefits posted to one standard, at line level, with reason codes preserved. Many practices run two different standards without realising it, because the paper stream is worked by whoever has time.
Contractual adjustments separated from payer determinations, line by line. Non-contractual amounts route to a denial worklist instead of closing the claim.
Every zero payment line goes to a denial queue before anything is closed. This is a rule, not a judgment call, and it is the single cheapest fix in payment posting.
Payments compared against the expected contracted allowable rather than accepted as received, with variance reported by payer and by code.
Takebacks matched to the original overpaid claim, current claims posted at full remitted value, and the offset recorded as its own transaction so the deposit still reconciles.
Patient responsibility to statements, coordination of benefits balances to secondary claims, documented write-offs recorded as policy rather than as default.
Remittance totals, posted totals and bank deposits reconciled the same day, so a variance traces to a claim instead of becoming an accounting adjustment three months later.
Worked on a standing cycle rather than at year end, because unapplied cash that sits for months becomes untraceable and credit balances that sit become a compliance conversation.
Every adjustment on a remittance carries a group code saying who bears the amount and a reason code saying why. Reading those two correctly is the whole of payment posting, and it is the part most posting services skip.
| Code | Meaning | Where the money goes |
|---|---|---|
|
CO |
Contractual Obligation |
Absorbed by the provider. Cannot be billed to the patient. |
|
PR |
Patient Responsibility |
Belongs on a patient statement. Not a write-off. |
|
OA |
Other Adjustment |
Neither contractual nor patient. Frequently coordination of benefits routing. |
|
PI |
Payer Initiated Reduction |
A reduction the payer applies where it does not consider the provider contractually obliged to accept it. |
The distinction that decides everything: CO is the group code, not the verdict. It does not mean the money is gone. What determines whether an amount is a legitimate write-off is the reason code beside it.
CO-45 reports that the charge exceeds the fee schedule, maximum allowable, or contracted or legislated fee arrangement. This is the ordinary contractual adjustment. Your contract says you agreed to accept it. Writing it off is correct.
CO-97reports that the benefit for this service is included in the payment or allowance for another service already adjudicated. This is a bundling edit, not a contract term, and it is frequently appealable. Posted into the same bucket as CO-45, it disappears permanently.
A claim adjustment reason code, or CARC, states why an adjustment was made and appears on every adjusted claim. A remittance advice remark code, or RARC, adds supplemental detail and does not always appear. Informational RARCs carry an alert marker with resubmission guidance, which is guidance most practices never read because the claim already closed.
Entity anchor Practice Mate posts adjustments against the reason code on the line rather than into a single contractual bucket, so the classification survives for whoever works the claim next.
This is the most expensive failure in payment posting and it is invisible by design.
A contractual adjustment and a denial look identical in a billing system once posted. Both reduce the balance. Both close the line. Both remove the amount from accounts receivable. The only thing separating them is the reason code recorded at the moment of posting. If your process writes everything to one adjustment type, that distinction is destroyed permanently and cannot be reconstructed.
A CO-45 against your contracted fee arrangement is money you agreed not to collect. A bundling edit, a missing information rejection, a medical necessity determination, a duplicate finding or a filing decision are payer determinations, not contract terms. Every one is potentially appealable. Every one, posted as a contractual adjustment, becomes a permanent write-off that nobody decided to make.
The reason this survives for years inside otherwise well run practices is that it produces no symptom. Denial rate looks healthy, because those denials were never recorded. Accounts receivable looks clean, because the balances left it. Clean claim rate is unaffected. Collections are lower than they should be, but there is no baseline, so nothing looks wrong.
Three posting scenarios account for most of the remaining loss, and each one needs a rule rather than a judgment call.
A remittance line with a payment of zero is a rejection. It arrives through the same electronic file as every paid claim, and auto-posting logic written to apply what the remittance says will apply exactly that: zero paid, full amount adjusted, claim balanced, claim closed.
The reason for the denial arrives in the adjustment codes on the same line. It was present at the moment the claim was closed and it was not used.
The correct handling is absolute. Any remittance line with zero payment routes to a denial queue before anything closes, regardless of what the adjustment codes say, and a person decides whether it is appealable.
An underpayment is a claim allowed at less than your contracted rate. From the system’s point of view the claim was paid and closed correctly, which is why detecting one requires a comparison the system cannot make by default: the expected allowable for that code, under that contract, for that payer, on that date of service.
Three reasons this happens more than practices assume. Contracted rates improve at renegotiation and fee schedules in the billing system do not get updated, so the improvement is invisible and the payer keeps the difference. Payers apply their own edits at adjudication, sometimes correctly and sometimes not. And fee schedules are loaded once and rarely audited, with new codes added at defaults nobody chose.
A recoupment is a payer recovering a previous overpayment by reducing a current payment. The money comes out of a check that has nothing to do with the claim being recovered.
Posted correctly, the recovered amount goes against the original overpaid claim, the current claims post at their full remitted value, and the offset is recorded as its own transaction so the deposit still reconciles. Posted as a shortfall on the current claims, the original overpaid claim continues to look correct and the current ones look underpaid. Three records are now wrong and the trail that would let anyone reconstruct it has been overwritten.
Five steps, from remittance intake to monthly reporting.
ERA files retrieved, paper and PDF remittances captured, patient payments and daily deposits collected.
Payments and adjustments applied at line level, each adjustment recorded against its own reason code rather than a generic adjustment type.
Zero pay lines, non-contractual adjustments, underpayment variances, recoupments and unmatched cash pulled out of the automated flow and worked by a person.
Patient responsibility to statements, secondary claims generated and filed with the primary remittance data attached, documented write-offs recorded as policy.
Remittance, posted and deposit totals reconciled the same day. Classification and variance findings reported monthly, with recurring causes raised as process findings rather than reworked claim by claim.
Automated posting is correct for most remittance lines and it is the only practical way to handle volume. The question is not whether to automate. It is what the exceptions are.
Always a denial. Always routed before closing.
The amount posts, the claim routes to review rather than closing.
These require matching to an original claim, which automation cannot do reliably.
Underpayment or overpayment, both need a person.
Goes to a holding account, never onto the nearest claim with an open balance.
Denials worked at root cause, recurring mechanisms reported as findings, monthly reporting delivered to the practice.
Posting generates the most useful management data in the revenue cycle, and most practices never see it, because their reporting is built around what was collected rather than around what was given up.
| Report | What it tells you |
|---|---|
|
Adjustments by reason code |
Separates contract obligations from decisions. The most useful report in billing and the one the Section 5 exercise depends on. |
|
Underpayment variance |
Allowed against expected allowable, by payer and code. How contract underperformance becomes visible and how renegotiation gets evidence. |
|
Denial classification by payer |
Only accurate when zero pay and non-contractual adjustments route correctly. An artificially low denial rate is usually a posting problem, not a good payer mix. |
|
Posting lag |
Days from remittance receipt to posting, with the downstream queues it is holding up. |
|
Credit balance and unapplied cash aging |
By age, because exposure is a function of how long it has been sitting. |
None of these are exotic. They exist in most practice management systems and they are empty or meaningless in any practice posting adjustments to a single bucket, because the classification they depend on was never recorded.
Posting lag is the number of days between a remittance arriving and the payment being posted. It is a smaller number than charge lag in most practices and it blocks more downstream work per day.
Four things cannot happen until the remittance is posted. The denial cannot be worked, because it has not been identified. The secondary claim cannot be filed, because the primary remittance data is not attached to anything. The patient statement cannot be produced, because the patient responsibility amount is not known. And accounts receivable reporting is wrong for as long as the lag lasts, because adjudicated claims are still showing as outstanding.
That last point matters for management as much as for cash. A practice with a week of posting lag is making decisions from an AR report that is a week out of date in a way the report does not disclose.
Ask whether your practice can produce an adjustment report sorted by reason code for last month, and whether anybody has looked at it. If the answer to both is yes, your posting is probably sound and the case for moving it is about capacity rather than quality. If the answer to either is no, the issue is not who performs the posting. The classification is not being recorded, and that does not fix itself with more staff.
The second question is what happens when your poster is out. Payment posting is unusually intolerant of absence, because remittances keep arriving whether or not anyone is there to post them, and denials, secondary claims and patient statements all stop behind the queue.
| In-house | Practice Mate | |
|---|---|---|
|
Cost structure |
Fixed. Salary, benefits, software and training continue whether volume rises or falls. |
Variable, scaled to volume or collections depending on engagement. |
|
Coverage during absence |
Remittances queue. Everything downstream stops behind them. |
Continuous. Turnover is our problem, not the practice’s. |
|
Adjustment classification |
Usually a single bucket, because nobody specified otherwise. |
Posted against individual reason codes, non-contractual amounts routed. |
|
Underpayment detection |
Requires loaded expected allowables, which most practices do not maintain. |
A standing function with a variance report behind it. |
|
Reconciliation |
Frequently monthly, sometimes at year end. |
Daily, against remittance and deposit. |
|
Visibility |
Collections reporting, which does not show what was given up. |
Adjustment classification, underpayment variance and denial classification, monthly. |
Three things determine whether these charges survive. Standardized instrument screening requires a scored, documented instrument, not an informal question set in the narrative. Several of these codes are denied as inclusive to the preventive exam depending on payer policy, which is a policy problem to be known in advance rather than a coding problem to be appealed after. And psychological and neuropsychological testing is reported with the 96130 through 96139 family. CPT 96100 is deleted and is not a valid code, despite still appearing in guidance published elsewhere.
Every adjustment posted against its own reason code, with non-contractual determinations routed to a denial worklist instead of closed. This is the entire difference, and it is the thing most posting services do not do.
Payments checked against contracted rates rather than accepted as received, with variance reported by payer and code, so contract underperformance has evidence behind it at renegotiation.
What needs a person in a Medicaid-weighted book is not what needs a person in a commercial one. The rules are configured per practice, not applied from a template.
Posting, denials, receivables, patient billing and charge capture sit with one team. When an underpayment traces back to a fee schedule line, the same team fixes both ends.
Onboarding is one meeting, a review of recent remittance history, and a team assigned to your account.
The findings report belongs to your practice, whatever you decide afterward.
FaqsPayment posting records what a payer did with a claim. It applies the payment, records adjustments with their reason codes, assigns any remaining balance to the patient or a secondary payer, and closes or routes the claim. It sits between adjudication and denial management in the revenue cycle.
An ERA is the electronic remittance advice, a structured file carrying claim and line level detail that can post automatically. An EOB is the human readable explanation of benefits on paper or PDF, posted manually. Many practices run different standards on each without realising it.
CO is contractual obligation, absorbed by the provider and not billable to the patient. PR is patient responsibility and belongs on a statement. OA is other adjustment. PI is a payer initiated reduction the payer does not consider contractually required. The group code decides where the money goes.
A contractual adjustment is an amount your contract requires you to accept. A denial is a payer determination that may be appealable. Both reduce the balance and close the line, so a denial posted as a contractual adjustment leaves accounts receivable permanently and never reaches a denial worklist.
Pull adjustment detail at line level with reason codes attached, then separate the contractual adjustments taken against your contracted fee arrangement. What remains was adjusted for reasons that are not your contract. If the report cannot be sorted by reason code, that is itself the finding.
It routes to a denial queue before the claim closes. A zero payment line is a denial with no dollars attached, and the reason arrives in the adjustment codes on the same line. Posted as a payment of zero, the claim balances and closes with that information unused.
The recovered amount posts against the original overpaid claim, current claims post at their full remitted amount, and the offset is recorded as its own transaction so the deposit still reconciles. Applying the shortfall to current claims makes three records wrong instead of correcting one.
It is where denials are identified, underpayments become visible, secondary claims are triggered and patient balances are released to statements. Every downstream recovery function works from what posting recorded, so posting quality sets a ceiling on what the rest of the cycle can collect.
Yes. Dental remittances carry a different structure, plan year maximums and a materially larger patient responsibility share than medical, which makes balance routing the primary failure point rather than adjustment classification.
Yes. It is commonly taken as a standalone engagement, particularly where remittance volume has outgrown the staff handling it or where absence causes posting to queue. It can also run as one stage of a full revenue cycle engagement.
Practice Mate posts inside the practice management and EHR system your practice already uses. There is no migration or data conversion required to begin
FaqsThree to four weeks for most endocrinology practices. We run parallel processing so claims never stop going out. Practices with DSMT program accreditation work or large open AR balances may take five to six weeks.
No. Guaranteed in writing. If your clean claim rate drops below your previous rate in the first 60 days, we work three months at no charge until we close the gap.
We don't issue accreditation — that comes from ADA or ADCES. We do walk you through the application, documentation, program NPI setup, and the billing structure once you're accredited. If you already have accreditation but aren't billing G0108/G0109, we can start within two weeks.
Yes. We audit your CGM patient panel for RPM eligibility, document the 16-day data threshold, set up time-tracking for 99457/99458, and bill monthly. Most practices haven't billed RPM at all — we typically recover six months of eligible RPM revenue in the first 90 days.
Yes. We bill under your NPI and Tax ID. No re-credentialing. No re-enrollment. If you have open credentialing in progress, we manage it as part of onboarding at no additional charge.
Yes. We execute a Business Associate Agreement (BAA) before accessing any patient record. Encrypted transmission. Access-controlled environments. HIPAA-auditable pipeline.
Percentage based on collections. We are paid when you are paid. No flat monthly fees. No per-claim fees that reward volume over accuracy. Written fee proposal before any agreement is signed.
