Adding staff, opening another location, or operating through another entity changes what your accounting system must handle. More transactions are only part of the challenge. You also need to see which location is profitable, keep entity records separate, control who can change financial information, and close the books consistently.

For a staffed private medical practice, scalable accounting software should preserve financial clarity as complexity increases. A polished dashboard is not enough if payroll allocations are inconsistent or payer deposits cannot be reconciled.

Use this checklist to define requirements, test vendors against your actual workflow, and decide whether to improve your current setup or migrate.

Define the expansion before evaluating software

Write a short requirements brief with your practice manager and accounting team. Include:

  • Operating structure: Current and planned locations and legal entities, confirmed with your advisers.
  • Financial accounts: Bank accounts, credit cards, loans, and which entity owns each account.
  • Staffing: Provider and administrative payroll, employees working across locations, and who approves expenses.
  • Reporting: Required entity financial statements, location P&Ls, and shared-cost reporting.
  • Workload: Current transaction volumes, payroll entries, attachments, and expected growth.
  • Responsibilities: Who enters, approves, reconciles, reviews, and corrects records.

Separate a software limitation from a process problem. Missing location tags may require better coding rules rather than a replacement system. Inability to keep entity books distinct is a different problem.

The IRS guide to starting and keeping business records supports complete records, separate business accounts, and bank reconciliation. Software should make those routines workable; it does not replace them.

Keep accounting separate from billing and clinical systems

Your general ledger should organize financial results and support reconciliation. It does not need to duplicate every patient account or clinical encounter.

Function Primary requirement Accounting system's role
Claims, denials, and patient balances Billing or practice-management workflow Receive appropriate financial summaries and reconcile receipts
Clinical documentation and scheduling Clinical and scheduling systems Avoid unnecessary clinical detail in financial records
Payer and patient receipts Billing records, settlement reports, and bank activity Record receipts without duplicating revenue or ignoring settlement differences
Provider and admin payroll Payroll processing and supporting records Record wages, employer costs, liabilities, and location allocations
Entity and location results General ledger and reporting structure Produce financial statements with clear, consistent classifications

Ask your accountant to define the posting method for your accounting basis. For example, importing both billing revenue and bank deposits as new revenue can duplicate income if the workflow is not designed correctly.

A dashboard displays information; it does not fix missing or misclassified transactions. A custom API transports data; it does not establish the correct accounting treatment. Evaluate those tools only after defining the ledger structure and reconciliation process.

Core accounting requirements checklist

Treat these as demonstration requirements, not promises that any particular product provides them.

Requirement What to verify Evidence to request
Account structure A consistent chart of accounts that supports expansion without excessive duplication Sample account list and process for adding or retiring accounts
Entity separation Distinct books, bank accounts, balances, and financial statements for each entity Entity-specific trial balance and balance sheet
Location reporting Location coding on relevant income, expenses, and payroll entries Side-by-side location P&Ls tied to the practice total
Shared costs Documented allocation methods and visible unallocated amounts Allocation entry, supporting schedule, and report treatment
Permissions Access appropriate to owner, manager, bookkeeper, and reviewer responsibilities Demonstration using separate user roles
Review workflows Clear approval, correction, and close responsibilities Sample transaction review and closed-period correction
Data export Usable access to accounting records and supporting information Downloaded sample files, not just screenshots
Transaction capacity Workable imports, reconciliation, and reporting at expected volume Representative workload test and written limits
Implementation support Clear ownership of configuration, migration, training, and problems Written implementation scope and responsibility list

Account structure, entities, and locations

Keep the chart of accounts consistent enough to compare results. Use a location dimension, where suitable, rather than creating a separate expense account for every office. Confirm whether the system supports the required reporting design before adopting it.

A location is not automatically a legal entity. Offices within one entity may need location P&Ls, while separate entities need distinct books and balances. A combined management report should not obscure those distinctions. Where entities transact with each other, ask your accountant how balances and any combined-report eliminations will be handled.

For shared administrative payroll, rent, or software, document an allocation basis that fits the cost. Show location results before and after allocations where useful. Make missing location codes visible rather than silently spreading them across offices.

Permissions and review workflows

Define access by job responsibility. A location manager may need an office P&L without access to every employee's compensation or another entity's accounts.

Test who can create vendors, change account mappings, post journals, approve payments, and reopen periods. Request a demonstration of available change history and reviewer visibility rather than assuming these features exist.

If a small team cannot fully separate duties, document an owner or independent reviewer check. Software permissions alone do not establish effective oversight.

Transaction capacity and portability

Test a representative busy period, including deposits, payroll summaries, card activity, refunds, and corrections. Measure the whole workflow: import, exception handling, reconciliation, report generation, and review.

Ask about limits on users, entities, locations, imports, attachments, and historical records. Determine which limits require another subscription tier or additional services.

For exports, inspect transaction detail, account lists, trial balances, financial statements, location fields, and attachment availability. Confirm how you would retrieve records if you leave the vendor. A PDF P&L alone is not a portable accounting dataset.

Vendor demonstration script: adding another location

Illustrative expansion scenario: A private medical practice plans to open a second location within its existing entity. Providers will work at both offices, administrative costs will be shared, and the owner wants separate location P&Ls. A separate entity may be considered later, subject to professional advice.

Use synthetic or de-identified sample records. Give every vendor the same tasks and ask them to perform the workflow rather than show slides.

  1. Build the structure. “Show both locations under the current entity. Then explain how a future separate entity would maintain distinct books and accounts.”
  2. Record receipts. “Post sample payer and patient receipt summaries, match them to bank deposits, and explain how settlement differences are resolved without duplicating revenue.”
  3. Post payroll. “Allocate provider payroll between offices using an approved supporting schedule. Keep shared administrative payroll identifiable.”
  4. Allocate shared costs. “Show the allocation calculation, its review, and how we change the method prospectively.”
  5. Run reports. “Produce each location's P&L, an unassigned-cost report, and the entity total. Explain why they reconcile.”
  6. Test access and corrections. “Sign in as a location manager, then as a reviewer. Demonstrate a restricted action and how a correction to a closed period is handled.”
  7. Test scale and exit. “Process a representative batch, resolve an import error, and export the resulting records with entity and location fields.”
  8. Explain delivery. “Identify what is included, what needs an add-on or manual work, and who owns setup and ongoing exceptions.”

Record the configuration used, unresolved questions, and evidence received. A feature available only through an untested add-on is not yet a demonstrated solution.

Use a pass-question-gap scorecard

Assign each requirement a priority before the demonstration:

  • Pass: Demonstrated with evidence and an acceptable operating process.
  • Question: Plausible, but evidence, scope, or ownership remains unclear.
  • Gap: Not supported or requires an unacceptable workaround.

The following results are illustrative only, not an assessment of a real vendor.

Requirement for the hypothetical expansion Priority Example result Required follow-up
Location P&Ls reconcile to entity totals Must-have Pass Retain sample reports and coding rules
Future entity books remain separate Must-have if entity is added Question Demonstrate separate balances and confirm scope
Shared payroll allocation is reviewable Must-have Pass Assign an allocation schedule owner
Manager cannot access restricted payroll detail Must-have Question Test every relevant report and export permission
Missing location codes are visible Must-have Gap Resolve before relying on location profitability
Busy-period processing is workable Must-have Question Complete a representative volume test
Detailed exports preserve location fields Must-have Pass Save and inspect sample export files
Migration and training ownership is clear Must-have Question Obtain a written implementation plan

Do not let several convenient features outweigh a critical gap. An unresolved entity-separation or reconciliation requirement should block approval until there is a tested solution. Accept a workaround only when its owner, recurring effort, review step, and cost are explicit.

Plan migration as an accounting project

Migration effort depends on data quality, history requirements, and changes to the reporting structure—not just whether an import tool exists.

Before conversion

Clean up unreconciled balances, duplicate accounts, missing location codes, and unresolved payroll liabilities. Agree on the conversion date, accounting basis, account mapping, opening balances, and amount of transaction history to move.

Determine which older records will remain accessible elsewhere. Do not assume a summary-balance migration preserves supporting detail or permits destruction of source records. Confirm applicable recordkeeping requirements with your CPA and other advisers.

During testing

Reconcile the converted trial balance, bank and card balances, payroll liabilities, and other applicable control accounts to the old records. Verify location totals and inspect representative transactions and attachments.

Compare reports on the same accounting basis and date range. Use controlled parallel reporting where helpful, but avoid uncontrolled duplicate posting in both systems.

Before go-live

Name the person who approves the conversion, handles failed imports, trains staff, and supports the first close. Document escalation contacts and an agreed fallback plan if acceptance tests fail. Keep access to the old records until the new setup and historical access have been validated.

Compare total operating cost, not just subscriptions

Request a written scope covering both setup and recurring work.

Cost area What to include
Software Users, entities, reporting options, storage, and transaction limits
Implementation Cleanup, mapping, conversion, testing, training, and temporary overlap
Routine operations Coding, reconciliation, allocations, review, and exception handling
Connected systems Connector subscriptions, file preparation, monitoring, and maintenance
Changes and exit New-location setup, revised reporting, exports, and transition assistance

Manual work is not automatically unacceptable. A controlled payroll-summary import may be practical. An undocumented spreadsheet needed to repair every location report is a larger operating dependency.

Also clarify what support covers. Software troubleshooting, bookkeeping, tax work, and CFO advice are different services. Ask who answers each type of question and who is responsible for completing the work.

Minimize unnecessary patient information

Use financial summaries wherever they meet the accounting need. Avoid placing patient-identifiable information in demonstration files, ordinary Slack messages, or general-purpose AI tools.

If a proposed workflow involves protected health information, have the appropriate privacy, legal, and technical advisers evaluate the arrangement. HHS explains business-associate responsibilities and the minimum necessary standard and its exceptions. Neither establishes that a particular accounting vendor or service is compliant.

Make the decision around a reliable close

Choose the system that lets your team explain cash, reconcile balances, separate entity records, and produce useful location results through a repeatable close. Require evidence for must-haves and a named owner for every accepted workaround.

Lucid Financials provides CPA-led bookkeeping, tax, and CFO services for US private medical practices, combining AI-assisted financial work with a human finance team and support through Slack. Its approved service focus includes clean books, catch-up bookkeeping, and location/entity financial visibility. Discuss the service scope separately from the software requirements.

FAQs

Does opening another location require new accounting software?

Not necessarily. Your current system may support location reporting with better configuration and coding procedures. Test permissions, allocations, reporting, and workload before deciding to migrate.

Can one accounting system support multiple entities?

Potentially, but verify separate books, balances, account ownership, permissions, and reporting. A location label alone does not demonstrate adequate entity separation. Confirm the required setup and accounting treatment with your advisers.

Do we need custom APIs or real-time dashboards?

Only if they solve a defined workflow need. Start with accurate postings, reconciliations, and financial reports. A scheduled summary import may be sufficient; custom connections add implementation and maintenance responsibilities.

What should stop us from signing a contract?

Unresolved must-haves should pause approval: reports that do not reconcile, unclear entity separation, unsuitable access restrictions, unusable exports, or undefined migration responsibilities. Obtain evidence or an acceptable tested solution before committing.