A financial connection is useful only if your practice can explain what moved, what did not move and how the results tie to its books. A successful transfer notification does not establish that every settlement arrived, every fee was separated or every receipt reached the correct entity.

For owners and managers of staffed U.S. private medical practices, the build-versus-buy decision should start with a defined accounting workflow—not a preference for custom technology or a connector advertised as ready to use.

Choose an available connector when it demonstrably covers your required data, accounting mappings and exception workflow. Consider a custom connection when a material requirement cannot be met through available options and you can assign responsibility for maintaining it. Neither approach removes the need for reconciliation.

This guide focuses on moving financial information between practice systems and accounting workflows. It does not cover API coding, security configuration or dashboard construction.

What You Are Actually Choosing

A custom API connection is a purpose-built integration that uses interfaces made available by the source and destination systems. Your practice might engage a developer or technical firm to build and maintain it. Custom work can tailor transformations and routing, but it cannot extract information that the source does not expose or that your agreement does not permit you to access.

A ready-made integration, or connector, is an existing product that transfers information between supported systems. It may offer configurable mappings and schedules, but the exact data coverage, supported workflows and maintenance terms must be verified.

The distinction is not “complete control” versus “no flexibility.” Both approaches depend on source-system access, destination capabilities, contractual terms and the people responsible for accounting decisions.

For example, a practice might need aggregate patient-payment settlements moved into an accounting clearing account, with fees shown separately and deposits assigned to the correct entity. That is a narrower requirement than transferring every patient transaction. Defining that boundary can simplify both implementation and privacy review.

Start With a Financial Requirements Matrix

Before requesting proposals, have the practice manager and accounting lead document what the connection must accomplish. Involve the person who currently resolves deposit differences; their manual work often reveals requirements that a product demonstration misses.

Use a matrix like this to evaluate both approaches against the same evidence.

Requirement Practice-specific question Evidence to request Acceptance condition
Data coverage Are deposits, gross collections, refunds, fees and reversals available? Field list and representative source reports Required components are available or have a documented alternative workflow
Entity assignment Can each settlement be routed to the correct legal entity and bank account? Test records covering each entity No unexplained or default cross-entity posting
Location mapping Does the source identify location reliably? Examples including shared merchant accounts Location assignments follow an approved rule; unsupported splits are flagged
Accounting mapping Can receipts, fees and clearing balances reach the approved accounts? Proposed mapping document Accounting lead approves the treatment before posting
Timing Which dates govern extraction and posting? Definitions of transaction, settlement and deposit dates Period-end differences can be identified and explained
Exceptions What happens to missing identifiers, rejected entries and unmatched deposits? Demonstration of failure handling Exceptions remain visible and have an assigned owner
Corrections How are reversals and previously transferred records handled? Controlled correction and repeat-transfer tests Corrections are traceable and repeated transfers do not duplicate entries
Reconciliation Can source totals, transferred totals and bank deposits be compared? Sample reconciliation output Differences can be isolated by batch, entity and period
Exit Can the practice obtain its records and mapping documentation? Contract terms and sample exports Books remain supportable after cancellation or replacement

Mark requirements as essential, desirable or out of scope. A location tag may be essential for a per-location P&L, while provider-level detail may be unnecessary for a deposit-reconciliation workflow.

Do not assume that a missing location field can be solved by allocating receipts according to provider schedules. Any allocation method needs accounting approval and should remain distinguishable from directly sourced information.

Compare the Two Approaches Without Assuming a Winner

Decision factor Custom API connection Ready-made integration
Data coverage Can target available source fields specifically; still constrained by access and source capabilities May cover the standard workflow but omit adjustments or less common record types
Mapping flexibility Can support purpose-built rules if they are clearly specified and tested Depends on configuration options and supported accounting structures
Exception handling Must be included in the scope, not left as an afterthought Must be demonstrated; vendor-managed transfer does not necessarily include accounting resolution
Maintenance Requires a named technical owner and an agreement for changes and failures Provider may maintain the connector, while practice-specific mappings and reconciliation still need owners
Implementation cost Includes discovery, development, testing, documentation and handoff Includes setup, configuration, testing, subscription terms and any required services
Ongoing cost Includes monitoring, repairs, interface changes and access administration Includes recurring charges, support terms, configuration changes and manual workarounds
Exit options Depend on rights to code, documentation, deployment materials and data exports Depend on export access, cancellation terms and availability of historical records

A connector can become expensive if staff must repeatedly repair missing classifications. A custom connection can become difficult to sustain if only one contractor understands it. Compare the full operating workflow rather than just the implementation quote.

Separate transfer responsibility from accounting responsibility

A technical provider may confirm that records reached the destination. That does not mean the entries belong in the correct period or that a settlement has been fully explained.

Assign separate owners for:

  • Technical operation: access failures, interrupted transfers and source-system changes.
  • Accounting mappings: accounts, entities, locations and clearing treatment.
  • Exception resolution: investigating missing or rejected records.
  • Reconciliation approval: confirming that source activity and bank movement agree, with documented timing differences.

In a smaller practice, one person may hold several roles. The responsibilities should still be explicit.

Sample Decision: Aggregate Deposits and Settlement Data

Illustrative example: A practice operates two locations within one legal entity. It wants aggregate patient-payment settlement information in its accounting workflow, without transferring patient names or individual patient balances.

For one settlement batch, the source report shows:

Settlement component Illustrative amount
Gross payments $24,000
Refunds deducted ($600)
Processing fees deducted ($400)
Expected net settlement $23,000
First bank deposit received $15,000
Remaining deposit received later $8,000

The bank deposits alone do not show the gross collections, refunds and fees. Importing only the net deposits may therefore leave the accounting team without the detail needed for its approved treatment. Conversely, importing the gross activity and separately treating the bank deposits as additional revenue could double-count receipts.

The accounting lead must define how settlement activity and clearing balances will be recorded. Settlement data also does not, by itself, establish revenue earned during that period; receipts may relate to earlier patient balances.

When the ready-made connector fits

Suppose a candidate connector demonstrates that it transfers the batch identifier, required settlement components and approved location codes. It supports the practice's accounting mappings, exposes rejected records and allows both deposits to be matched to the settlement without duplicate posting.

If it passes testing and its support and exit terms are acceptable, there may be no financial reason to commission a custom connection.

When custom work deserves consideration

Suppose instead that the available connector transfers only net deposits and cannot provide a stable batch reference. Staff would still need to retrieve settlement reports and manually separate fees and refunds.

A custom connection deserves consideration if the source API makes the missing information available and the resulting workflow can be maintained. The practice should compare that investment with the continuing cost and risk of a documented manual reconciliation process.

Custom work is not justified merely because the practice has multiple locations. If the source does not contain reliable location detail, neither approach can manufacture it. The practice may need to revise its reporting expectations or source workflow before purchasing an integration.

Test Completeness Before Relying on Either Approach

A demonstration with a few successful records is not an acceptance test. Test the connection against independently obtained source reports and the bank activity used in the practice's close.

The IRS discusses complete business records and reconciling bank records in Publication 583. For this decision, the practical implication is straightforward: the accounting team needs evidence that the transfer supports complete, reconcilable records—not just evidence that a connection runs.

1. Establish the baseline

Identify the authoritative reports for each component: settlement activity, adjustments and bank deposits. Define the test period, date conventions, included accounts and entities, and any known timing differences.

Record source counts and totals before transferring anything. A matching total alone is insufficient because an omitted record and a duplicate record can offset each other.

2. Include ordinary and difficult transactions

Select representative activity that includes routine settlements, refunds, reversals, split deposits and period-end timing differences. Cover each relevant entity and location. Where unusual events are unavailable in historical data, ask the technical provider how they can be tested safely before live reliance.

3. Compare every stage

Reconcile:

  • Source records and amounts to extracted records and amounts.
  • Extracted records to accepted and rejected destination entries.
  • Expected settlements to bank deposits and remaining clearing balances.

Investigate differences by batch and date rather than accepting an unexplained net difference. Document any source fields that are intentionally excluded.

4. Test failure and recovery

Confirm what happens when access expires, a mapping is missing or a transfer stops partway through. Repeat a transfer and verify that it does not create duplicate accounting entries. Test a correction to previously transferred activity and confirm how the accounting team will identify it.

The owner does not need to inspect code. The owner does need understandable evidence of what failed, who is notified and how completeness is restored.

5. Approve the first close

Run the proposed workflow alongside the existing process for a representative close before retiring the old method. Define acceptance criteria in advance: no unexplained missing or duplicate records, approved mappings, reconciled balances and documented ownership of outstanding exceptions.

Set a fallback process so payroll funding and other cash decisions do not depend on an unproven feed.

Involve Technical and Privacy Specialists at the Right Time

Bring in a technical specialist before committing when the workflow involves multiple systems, custom transformations, uncertain API access or unclear recovery behavior. Ask for an assessment of feasibility, dependencies, maintenance responsibilities and handoff—not just a build estimate.

Bring in the practice's privacy or legal adviser when evaluating what information will move and which organizations will receive or maintain it. Do this before supplying production samples.

Aggregate settlement data may meet the accounting purpose without patient-level detail, but review the actual fields and exports. Removing names alone should not be treated as proof that a dataset is outside privacy requirements.

HHS guidance on covered entities and business associates explains why accounting-related services can involve business-associate responsibilities when protected health information is involved. Its minimum necessary guidance provides relevant context, with exceptions that require appropriate review. Neither a custom build nor a purchased connector establishes compliance by itself.

Use approved channels for sensitive information. Do not put patient-identifiable records into ordinary Slack messages or general-purpose AI tools to troubleshoot a financial discrepancy.

Make the Decision With a Written Operating Plan

Before signing, document the required fields, approved mappings, acceptance tests, exception owners, maintenance terms and exit process. Include how historical records will remain accessible and who will support reconciliation during a replacement.

Choose the approach that produces supportable books with a maintenance burden your practice can actually manage. If neither option meets the essential requirements, retain a controlled manual workflow while resolving the gap rather than automating incomplete information.

Lucid Financials provides CPA-led bookkeeping, tax and CFO services for staffed U.S. private medical practices, combining AI-assisted financial work with a human finance team. Its practice-finance role includes clean books and location/entity visibility. Specific integration availability and implementation responsibilities must be confirmed separately; financial support should not be taken as a promise that a particular connector is supported.