Practice ops
Client & CSV import
Bring a new client practice over in an afternoon, not a month. Import practices and reference data from CSV so onboarding a new client doesn't start with a week of typing. Every new client usually means re-entering providers, payers and patients by hand. What ships here includes csv import for practices and reference data; column mapping. Used day to day by admin, supervisor roles, with availability marked available. Open the sample screen on the right, then walk the steps below — or book a demo and put your hand on the same flow with synthetic data.
Admin console · users & practices
| User | Role | Practices | 2FA |
|---|---|---|---|
| T. Brooks | Supervisor | All | |
| K. Ahmed | Biller | Lakeview, Bayside | |
| L. Ortiz | Accountant | All (finance) | off |
What it is
Import practices and reference data from CSV so onboarding a new client doesn't start with a week of typing.
The problem it solves
Every new client usually means re-entering providers, payers and patients by hand. That delay costs you the first month of collections.
Process
How it works, step by step
- 1
Export from the old system
Start from a spreadsheet or CSV export.
- 2
Map the columns
Match your columns to MEDBIX fields.
- 3
Check before importing
Review issues before anything is written.
- 4
Start billing
The practice is ready inside your company account.
What's included
Everything below is part of client & csv import today.
- CSV import for practices and reference data
- Column mapping
- Pre-import validation
- Imports scoped to the right tenant
- Repeatable for each new client
- Logged in the audit trail
The guardrail
Imports are checked before they're written, and they land only in your tenant.
Where it fits: tenancy model
The structure that lets one billing company serve many practices without ever mixing their data.
- MEDBIX
- 1
Billing company (tenant)
MEDBIXYour company account and staff.
- 2
Client practices
MEDBIXOne space per client.
- 3
Patients, encounters, claims, statements
MEDBIXBelong to a practice.
Audience
Who uses it
These roles work with this feature day to day. Access always follows what your admin assigns.
Works closely with
Deep dive
What Client Import means in daily ops.
Practical context for Client Import: how teams use it, where it sits in the loop, and what to ask in a demo.
- Tied to how billing work actually splits
- Clear on human vs machine responsibility
- Links into related MEDBIX areas
Practice
Where this shows up on a busy day.
From morning eligibility checks to end-of-day posting, Client Import connects to the queues your team already lives in.
- Morning coverage and claim build
- Midday scrub and approval
- Afternoon denials and patient pay
Control
Keep a person on the send button.
Whatever page you're on, MEDBIX keeps AI in a propose role. Approvals, posting and rule activation stay human.
- Named approvals
- Visible AI proposals
- Immutable audit trail
Next
See Client Import against your volume
Bring your payer mix and the friction you feel today. We'll map it onto sample data in thirty minutes.
- Sample data only
- Your questions drive the agenda
- Written follow-up after
Common questions
Can you help with our first import?
Yes, onboarding includes help with your first client imports.
What if the CSV is messy?
Validation shows issues before anything is saved, so you can fix the file.
Can we import historical claims?
Talk to us about history; it depends on your source system.
Want to walk MEDBIX against your real claim mix?
Thirty minutes with sample data. We'll follow one claim through the gate, then talk about your payers, practices and where the rework hurts today.
Notes from the billing floor
Occasional, practical writing on denials, A/R and running a billing company. No spam, unsubscribe any time.