Standalone Billing Hub: From Excel Import to Claims and Payment

Direct answer: One Care Portal Billing Hub is a separate module that can run standalone. An agency can upload an Excel workbook, map its columns to claim fields, save a reusable import profile, preview validation results, create claims, and then manage the downstream billing workflow. It can also connect to One Care Portal Case Management or ADHC, but buying a Care Module is not required.

This is useful when operations already document services in another system but billing still depends on emailed spreadsheets, repeated rekeying, or an opaque handoff to a billing vendor. Billing Hub does not magically make source data correct. It creates explicit checkpoints where a billing team can identify missing fields, correct the source, and decide what is ready to submit.

Who the standalone model fits

• Provider agencies keeping an existing EHR, EMR, EVV, scheduling, or documentation platform.
• Billing companies that receive standardized workbooks from one or more provider clients.
• HCBS, case management, adult day, IDD, and related provider teams that want claim visibility without a full operational-system migration.
• Teams that need Medicaid plus other supported payer workflows and are willing to confirm exact payer and clearinghouse fit during implementation.

It is not a promise that every spreadsheet, payer, clearinghouse, or claim type works without configuration. During implementation, One Care Portal confirms the workbook structure, professional or institutional claim needs, payer identifiers, enrollment requirements, and the supported submission path.

Excel-to-claims workflow

Step	What the billing team does	Control point
1. Prepare	Export or assemble billing rows in an .xlsx or .xls workbook.	Keep one reliable patient-account or claim grouping value and consistent dates, identifiers, codes, units, and charges.
2. Upload	Select the provider profile and upload the workbook.	The file enters a preview workflow; upload alone is not submission.
3. Map	Map spreadsheet columns to the required claim fields and apply approved defaults.	Save an import profile for repeatable files instead of remapping every cycle.
4. Validate	Review format and claim-level errors before creation.	Correct errors in the workbook or mapping; do not hide missing source information with guesses.
5. Create and review	Create claims from valid rows and review provider, subscriber, service-line, units, charges, and payer data.	A billing user decides which claims are ready.
6. Submit	Submit selected claims through the configured, supported payer workflow.	Exact payer and enrollment fit must already be confirmed.
7. Follow through	Track acknowledgments and status, work rejections or denials, review 835 ERAs, post payments, and reconcile A/R.	Submission is not the end of the revenue cycle.

What to put in a repeatable spreadsheet

Field requirements vary by claim type and payer. A useful source workbook commonly includes a stable patient account, member and demographic details, payer, billing and rendering provider identifiers, service dates, procedure or revenue codes, modifiers, diagnosis context, place of service, units, and charge amounts. Institutional and professional claims have different requirements.

Billing Hub supports column mapping and reusable import profiles so an agency does not have to rename its internal columns merely to upload a file. Defaults can reduce repetitive data entry, but they should only represent values that are genuinely constant for that provider and workflow.

After claims are created

Pre-submission review

Review claim details and validation findings before selecting claims for submission. When Billing Hub is connected to a Care Module, billing context can originate from operational records. In standalone use, the workbook and configured provider/payer profiles are the primary handoff.

Status, rejection, and denial work

Billing Hub provides a claims workflow for submission state, acknowledgment or rejection visibility, denial follow-up, and resubmission work. A rejected transaction and an adjudicated denial are different events; teams should preserve that distinction when assigning follow-up.

ERA and payment reconciliation

835 ERA workflows support payment and adjustment review, matching to claims, denial reason visibility, and reconciliation. Available fields depend on what the payer includes. Confirm whether electronic remittance delivery and posting fit the agency's payer setup during implementation.

Questions to confirm before implementation

1. Which payers, plans, and trading partner IDs are in scope?
2. Are claims 837P, 837I, or both?
3. Which clearinghouse and payer enrollments are already active?
4. What workbook columns are available, and which values are safe defaults?
5. How are corrections, voids, replacements, secondary claims, and remittances handled for this exact workflow?
6. Who may upload, validate, submit, post, and reconcile?

Billing Hub versus the ERA Dashboard

Billing Hub manages a broader claim workflow. The separate ERA Dashboard is a standalone reader for standard X12 835 files and should not be confused with claims submission. Choose based on whether the team needs the full claim lifecycle or only readable remittance visibility.

Scope note: This page describes product workflow, not payer-specific billing advice. One Care Portal does not claim universal payer support or guaranteed payment. Confirm payer, clearinghouse, enrollment, claim-type, and source-data fit during implementation.

Frequently Asked Questions

Related resources

• Medicaid billing software
• Clean claims checklist
• Denials workflow guide
• EMR/EHR fit and interoperability guide