01
Payment Posting Is More Than Entering a Check
Posting should show which service was paid, allowed and paid amounts, adjustments, responsibility, denied portions, unapplied balances, and remaining A/R. It should also connect remittance to available EFT, check, deposit, or batch information.
Inaccurate posting can create false or missing A/R, incorrect patient balances, hidden denials, missed underpayment indicators, and reconciliation problems. Accurate payment posting is a revenue-cycle control, not just a clerical task.
- Which claim or service was paid?
- How much did the payer allow and pay?
- What adjustment was applied?
- Is there supported patient responsibility?
- Was any portion denied or unpaid?
- Is money still unapplied?
- Does the payment match the available deposit information?
- Does the remaining balance require follow-up?
02
What We Review During Payment Posting
Apex uses available remittance, payment, and claim information to post supported transactions and preserve exceptions.
ERA Payments
Review electronic remittance information and apply available payment and adjustment details to the appropriate claims.
EOB Payments
Review explanation-of-benefits information when posting depends on non-ERA documentation.
EFT Reconciliation
Compare available electronic payment information with remittance data. The service does not assume direct bank integration.
Contractual Adjustments
Post reported contractual or payer adjustments from available remittance information and practice workflow without inventing amounts.
Patient Responsibility
Identify adjudicated deductible, copay, coinsurance, or other supported patient responsibility.
Denials and Zero-Pay Claims
Identify unpaid claims or lines and route them for appropriate follow-up rather than unsupported adjustment.
Explore Denial Management →Partial Payments
Identify cases where some services were paid while other lines or balances remain unresolved.
Unapplied Payments
Identify money that cannot yet be correctly matched or applied and preserve it for research.
03
ERA, EOB and EFT Are Related but Not the Same
An ERA provides electronic remittance information explaining claim adjudication. An EOB provides payer explanation information and may arrive electronically or in another format depending on the workflow. An EFT is the movement of funds.
Money may appear through EFT while the practice still needs the corresponding remittance. A banking transaction is not a complete posting record.
04
Payment Posting Should Reconcile Back to the Money Received
Depending on available systems and information, reconciliation may compare ERA or EOB totals, EFT deposits, checks, payment batches, and posted transaction totals. Discrepancies should be researched rather than ignored.
This is payment and remittance reconciliation within the agreed RCM workflow, not a promise of complete accounting or financial-statement reconciliation.
- Duplicate or missed posting
- Incorrect payment amount
- Unmatched EFT or check
- Unapplied payment
- Payment posted to the wrong claim
- Incomplete remittance information
05
Payment Posting Is Often Where Denials Become Visible
Remittance can expose denied lines, zero-payment claims, non-covered services, authorization or eligibility issues, coding or modifier concerns, documentation-related issues, and payer adjustments. Those responses should not be blindly written off.
Exceptions should flow into denial management or A/R follow-up with the payer response and balance intact.
06
Patient Responsibility Must Be Posted Correctly
Deductible, copay, coinsurance, non-covered amounts where appropriately assigned, and secondary-insurance considerations can affect the remaining balance. Incorrect responsibility may produce inaccurate statements, patient confusion, collection problems, and unreliable A/R.
Patient responsibility should be based on payer adjudication and applicable workflow, not guessed from pre-service estimates.
Explore Eligibility & Benefits ↗07
Payment Posting Can Trigger the Next Claim Step
After primary adjudication, patient responsibility may remain, secondary insurance may need to be billed, or additional claim information may need to move downstream. A remaining balance alone does not establish that secondary coverage exists.
Posting should preserve the primary payer information needed for the appropriate secondary or corrected-claim workflow.
Explore Billing & Claims ↗08
Payment Posting Can Reveal Underpayment Indicators
A paid amount may differ from available expectations, a line may be unexpectedly reduced, an adjustment may appear inconsistent, or reimbursement may differ from available fee-schedule or contract information. These are indicators for research, not automatic conclusions.
Potential underpayments require comparison with available contractual, payer and claim information before conclusions are reached. Apex does not assume access to every payer contract or rate.
09
Unapplied Payments Should Not Disappear Into a Holding Account
A payment may remain unapplied when the patient or claim match is unclear, remittance is missing, payer information is incomplete, an EFT or check cannot be matched, or account information conflicts.
Unresolved unapplied money should be researched and documented within the payment-posting workflow. It should not become invisible merely because it cannot be immediately assigned.
10
Adjustments Need a Reason
Adjustments should correspond to documented payer, contractual, workflow, or approved account-resolution reasons. A balance should not be reduced without a supportable reason and appropriate documentation in the practice workflow.
The objective is a defensible balance, not simply a lower balance. Unsupported adjustments can hide collectible A/R, denials, or posting errors.
11
How Apex Approaches Payment Posting
The workflow connects payment and remittance to claim-level transactions, exceptions, follow-up, and batch control.
- 01
Match the Payment and Remittance
Associate available ERA, EOB, check, or EFT information with the appropriate payer and payment batch.
- 02
Apply Payments
Post supported payer payments to the appropriate claim or service lines.
- 03
Post Adjustments and Responsibility
Record supported contractual or payer adjustments and adjudicated patient responsibility.
- 04
Identify Exceptions
Flag denials, zero or partial payments, unapplied money, unexpected adjustments, and potential underpayment indicators.
- 05
Route Follow-Up Work
Send appropriate items to denial management, A/R, claim correction, payment research, secondary billing, or patient-balance workflows.
- 06
Reconcile the Batch
Confirm posted totals align with available payment and remittance information under the practice workflow; this is not formal financial-statement reconciliation.
12
Inaccurate Posting Creates Inaccurate A/R
If a payment is not posted, A/R may appear too high. An incorrect adjustment can make a collectible balance disappear. A denied line written off incorrectly can remove a follow-up opportunity. Incorrect responsibility assignment or a partial payment treated as full payment can leave the wrong balance in the wrong queue.
Explore Accounts Receivable ↗13
Denials Should Flow Out of Posting and Into Follow-Up
Posting is not the end of the workflow when remittance shows a denial. The payer response should be preserved, categorized, and routed to the team responsible for claim correction, research, reconsideration, appeal support, or other appropriate action.
Explore Denial Management ↗14
Pre-Service Estimates and Final Patient Responsibility Are Different
Eligibility and benefits verification may provide available cost-sharing information before treatment. Final patient responsibility is established through payer adjudication and may differ from the earlier estimate.
Explore Eligibility & Benefits ↗15
Can Apex Handle Payment Posting With Our Existing Billing Team?
Potentially. Payment posting may be part of broader RCM support, a defined outsourced function, or a workflow alongside an existing billing team when systems, access, responsibilities, remittance handling, and reconciliation processes are clear.
Compatibility depends on the operating environment and cannot be guaranteed for every EMR, clearinghouse, bank, or billing company.
16
What We Look for in a Payment Posting Review
A focused review can identify where payment, remittance, exception, or reconciliation work may be incomplete.
- Unposted ERA or EOB
- Unapplied payments
- Unresolved EFT or remittance matches
- Zero-pay and partial-payment claims
- Denial routing
- Adjustment patterns
- Patient-responsibility posting
- Secondary-billing workflow
- Potential underpayment indicators
- Payment-to-A/R consistency
The scope of a review depends on the payment, remittance, claim and system information available.
Request a Revenue Cycle Review ↗Posting and reconciliation questions
Physical Therapy Payment Posting FAQs
What is payment posting in a physical therapy practice?
+
Payment posting applies payer payments, adjustments, denials, and responsibility from remittance information to claims or service lines, then preserves unresolved balances for follow-up.
What is the difference between ERA and EFT?
+
An ERA provides electronic claim-adjudication and remittance information. An EFT moves funds. The practice may receive money through EFT while still needing the related ERA or other remittance information to post it accurately.
Can payment posting identify denials?
+
Yes. Remittance information may identify denied, adjusted, or zero-paid services. Those items still require categorization and appropriate follow-up; posting alone does not resolve the denial.
Can payment posting identify underpayments?
+
It can identify potential discrepancies. Determining whether a payment is an underpayment requires comparison with available contract, payer, claim, and reimbursement information.
What are unapplied payments?
+
They are payments received but not yet matched or posted to the appropriate patient, claim, service, or account. Missing remittance, unclear references, or conflicting information may require research.
Can Apex handle payment posting without replacing our billing company?
+
Potentially. A defined posting function may operate alongside an existing billing team when system access, responsibilities, remittance handling, exception routing, and reconciliation workflows can be established.