A freelance medical billing service is a small healthcare operations business, not a laptop side hustle. Before the first claim is touched, you need a defined client scope, secure access, a written agreement, a privacy/compliance setup, software and clearinghouse responsibilities, a method for receiving remittances, and rules for who owns coding, authorizations, refunds, statements, and old A/R. The business can be viable for someone with real billing experience, but it is a poor place to learn basic billing by trial and error on a client’s revenue.
Define the service before choosing a fee model
A therapist who asks for “full billing” may mean claim submission only, while a small practice owner may expect eligibility, charge entry, denial appeals, patient statements, payment posting, credentialing, and collections. Those are different workloads and risks. Build a scope matrix for every proposal. State who supplies codes, how documentation questions are handled, whether you touch patient balances, who approves write-offs or refunds, and whether legacy A/R is included. A percentage-of-collections fee can look simple but becomes ambiguous if the contract does not define which money counts, what happens to old balances, and how refunds or takebacks are treated.
Client intake before you quote
| Area | Question to resolve | Why it changes scope |
|---|---|---|
| Claims | monthly encounters, specialties, payers, locations | drives volume and complexity |
| Coding | client-provided or biller-performed | changes expertise and liability |
| Payments | ERA/EFT access and posting owner | determines reconciliation work |
| Denials | correct/resubmit only or full appeals | changes research and deadlines |
| Patients | statements, calls, payment plans | adds consumer-facing workflow |
| Systems | client PM/EHR or your platform | changes access, data transfer, cost |
HIPAA starts with architecture, not a template policy
If you create, receive, maintain, or transmit PHI on behalf of a covered client, the relationship and systems need appropriate HIPAA controls. A Business Associate Agreement is one part of that, not the whole solution. Decide where PHI lives, how access is granted and removed, whether local downloads are allowed, how credentials are stored, what happens to files at contract end, and how incidents are reported. HHS’s minimum-necessary guidance is a useful baseline for limiting routine access. Do not use a personal email account, shared family computer, or consumer file-sharing habit merely because the client is small.
Your clearinghouse and software choices change the operating model
Some freelancers work inside the client’s existing practice-management system; others supply billing software and a clearinghouse relationship. The second model creates more onboarding work: payer IDs, ERA enrollment, user permissions, claim edits, data imports, reports, and offboarding all need ownership. Ask who pays transaction or software fees and who controls the account if the contract ends. A client should not discover after termination that its claim history or remittance files are trapped in an account it cannot access.
1099, LLC, and workers’ compensation are different questions
Calling yourself a contractor, forming an LLC, and being classified correctly under labor or tax rules are separate issues. For federal tax classification, the IRS says the facts are evaluated across behavioral control, financial control, and the type of relationship; a contract label or the fact that someone receives nonemployee compensation does not decide the question by itself. State rules can use different tests and also differ on workers’ compensation obligations and exemptions. If you build a small service, use professional tax/legal guidance for your structure and insurance obligations rather than copying another freelancer’s setup. For the narrow state-by-state workers’ comp question, a state-by-state guide to workers' comp exemption is an adjacent reference; it does not replace advice about classification, contracts, HIPAA, or professional liability.
Protect the client from your learning curve
Do not sign a specialty you cannot bill safely just to get the first client. Start with work you have already handled, create a written escalation path for coding or payer-policy questions, and keep a dated work log. Track first-pass acceptance, denials by category, unresolved A/R, payment posting exceptions, and turnaround—without promising that every unpaid claim is recoverable. A trustworthy billing service tells the client which defects originate at registration, documentation, authorization, coding, or payer adjudication instead of presenting every problem as “collections.”
Offboarding belongs in the first contract draft
Define how long you retain records, how account credentials are returned, which reports and claim files the client receives, how open appeals are handed off, and when your access is terminated. A clean exit protects both parties and makes the service more credible at onboarding. Small healthcare businesses often focus intensely on getting the first claim out the door; experienced operators design the end of the relationship before the beginning.
Price the risk you are taking, not just the claims you submit
A percentage-of-collections contract and a per-claim contract create different incentives and different administrative burdens. Percentage pricing requires a clear definition of collections, exclusions, refunds, take-backs, patient payments, old A/R, and termination-period receipts. Per-claim pricing needs a definition of what counts as a claim, corrected claim, resubmission, or encounter. Neither model is safe when the scope is vague. The contract should also state who controls coding decisions, who supplies documentation, who approves write-offs, how payer portal credentials are handled, and how both parties respond to a suspected privacy or security incident.
Freelance billing also means you are operating a business that may handle PHI as a business associate. A BAA is not decorative paperwork; it should fit the actual systems and subcontractors you use. Keep client data out of personal email, consumer cloud folders, and local spreadsheets unless the client has explicitly approved the architecture and it meets the applicable safeguards. Separately, entity formation, worker classification, business insurance, taxes, and workers’ compensation obligations depend on jurisdiction and facts. Forming an LLC does not automatically make a worker a lawful 1099 contractor or create a workers’ compensation exemption.