Pre-billing documentation review
A Human-Controlled Pre-Billing Documentation Review Workflow
Use documentation QA to identify possible gaps before the organization's billing review—without treating an AI signal as a billability or compliance decision.
Written by One Care Portal · Reviewed by One Care Portal · Updated September 19, 2026
Separate documentation review from the billing decision
Pre-billing documentation review can identify records that may need clarification before a separate billing-readiness process. It does not determine whether a service or claim is billable and does not replace payer rules, contracts, coding expertise, or qualified billing judgment.
Define a bounded review sequence
- Select the program, record type, review period, and criteria.
- Confirm the manually uploaded PDF is the intended source record.
- Inspect possible findings and their page evidence.
- Record the finding disposition: confirm, dismiss, or resolve.
- Record the document decision: approve, return, or escalate.
- Send only the human-reviewed outcome into the organization's separate billing workflow.
Review information the document can actually support
Depending on the selected criteria and the information present, reviewers may inspect expected signatures or attestations, dates, times, locations, units, narratives, internal consistency, and possible goal or service-plan disconnects. Do not infer information that is absent from the source.
Protect the handoff
Preserve the source record, criteria version, evidence, human disposition, and follow-up history. The billing team should know whether an item is an unresolved signal, a dismissed signal, or a completed organizational follow-up.
State what the workflow cannot conclude
The workflow does not certify or determine compliance, billability, fraud, clinical adequacy, or legal sufficiency. It does not guarantee payment or audit outcomes, and it does not invent missing documentation.
Sources and scope
This guide is operational education, not legal, billing, clinical, or compliance advice. Confirm current requirements with the applicable program authority and qualified organizational leaders.
Two different product paths
Need to run caseloads, plans, visits, notes, authorizations, and supervisor workflows? Choose Case Management.
Need a separate review layer for manually uploaded PDFs from a system you must keep? Explore Documentation Intelligence and its product-validation boundaries.
Read the supervisor note-review workflow guide → · All documentation review resources →
Discuss your pre-billing review workflow
Map the PDFs, criteria, reviewers, and handoff your organization uses before its separate billing decision. Do not include PHI, service-recipient names, clinical details, or records in the booking flow.
Frequently asked questions
Does pre-billing review mean a record is billable?
No. It is a documentation QA step before the organization's separate billing decision.
Can a possible finding be sent directly as a denial or fraud determination?
No. A possible finding requires human verification and is not a fraud, noncompliance, or payment determination.
What is the source of truth?
The retained source record and applicable guidance remain authoritative; the review workflow records the organization's human disposition.