Who Controls Your Funeral Home Payment Account? A Buyer's Checklist

This guide focuses on account control and continuity. It does not prescribe a processor, interpret your agreement or establish a universal right to move payment credentials. The provider's account structure and contracts determine what is available.

Separate the software, processor and bank account

Draw the relationship in plain language. Identify the funeral home legal entity, software provider, payment processor, any platform or connected-account arrangement and the destination bank account. Add the business contact responsible for each relationship.

A payout reaching the firm's bank does not by itself establish which dashboard the firm can access or which party can initiate a refund. Likewise, a payment button inside the case system does not prove that the software vendor is the merchant for every transaction. Ask for the actual arrangement rather than inferring it from the interface.

For a group with multiple locations or legal entities, repeat the exercise for each relevant account. Shared branding can conceal separate processing relationships. Make sure the office can identify which account belongs to a disputed or refunded transaction.

What should the owner be able to access?

Ask how an authorized business administrator signs in, reviews payouts, updates appropriate settings and obtains reports. Confirm which actions are available directly and which require the platform's assistance. Record the recovery process if the original administrator leaves.

Use business-controlled contacts and appropriate access permissions. Do not solve continuity by sharing one password among everyone in the office. Give the accountant the information needed for reconciliation without automatically granting unrelated administrative powers.

Ask who can change the payout bank information and how such a change is verified. The answer should describe a process, not simply state that the account is secure. Your internal approvals should match the provider's supported controls.

Account control is different from data portability

A downloadable case export may contain a payment amount and transaction reference without including reusable payment credentials. Treat those as different categories. Never ask staff to copy full card details into a spreadsheet to make a software switch easier.

Stripe's account-copy guidance illustrates the distinction: some customer and payment-method data can be copied through its defined process, while individual charges and other historical objects are not copied in the same way. That example does not establish what another processor or platform will permit.

Ask your own provider to describe the supported migration path, approval requirements, exclusions and timing. A token that works in one processing environment should not be assumed to work in another. Keep any sensitive credential transfer inside the providers' approved process.

Plan refunds and disputes after a switch

Changing case software does not erase the history of earlier transactions. Ask how the business will find an old payment, process an eligible refund, receive a dispute notification and submit evidence after new payments begin elsewhere. Clarify any continuing access or fees.

Separate the original payment reference from the new case-system reference. If the same case moves to another platform, the accounting team still needs to connect the historical transaction to the correct family account. Keep the relationship documented during migration.

Ask when an old account can safely be closed and who makes that determination. Do not close it merely because the first new payment succeeds. Outstanding refunds, disputes, reserves, reporting and contract obligations may require further attention from the provider and the firm's advisers.

A practical account-control worksheet

Complete the worksheet for the current and proposed setup. An unanswered line is a follow-up task, not automatically evidence of wrongdoing. The purpose is to expose assumptions while there is time to resolve them.

Test reconciliation with a small example

Ask the vendor to demonstrate a payment, a partial refund and the related account view using approved test data. Identify the gross amount, fees, net payout and case balance. Determine which system records each element and who resolves a mismatch.

If QuickBooks is involved, inspect the supported accounting flow rather than assuming the word integration means every event transfers in the same way. Ask how duplicates, adjustments and historical transactions are handled. Your accountant should review the result against the firm's reporting needs.

A transaction can be recorded correctly in the processor while the case balance is incomplete, or vice versa. A useful acceptance check reconciles both. Keep the provider's transaction identifier so the office can investigate later without relying solely on a family's name.

A fictional transition example

A funeral home changes case software at the start of a month. New payments use the new setup, but a family requests a partial refund for an earlier transaction. The office has retained the original processor reference and knows which authorized employee can access the old record.

The employee follows the old provider's supported refund process and records the result against the migrated case. The accountant checks how the refund appears in the old payout reports and in the current case balance. The team does not issue a second payment from the new system and assume that it is equivalent to refunding the original transaction.

The same transition plan identifies who watches dispute notifications for the old account. That responsibility continues according to the applicable arrangement, even though daily case work has moved elsewhere.

Questions to ask before signing

Which costs belong to software and which belong to processing? Are there cancellation or continuing-access terms? What happens if processing is suspended while the software remains available? How are account changes approved? Who is responsible for communicating an incident to the business?

Obtain the answers from the party responsible for the service and retain the current terms. A salesperson's general explanation can be a useful start, but it should not replace the agreement where the business is relying on a specific commitment.

The FTC's information-security guide provides general principles for limiting sensitive data and controlling access. It is not a substitute for payment-provider requirements, accounting advice or review of your contracts.

How to evaluate FuneralHQ on the same basis

FuneralHQ offers payments within its broader features, alongside case work, documents, online arrangements and cemetery workflows. Ask the team to explain the account arrangement and demonstrate the actions your office needs. Do not assume this guide promises a particular migration right or administrative capability.

Use the blank payment-account worksheet with your owner, accountant and provider. Finish with a clear record of who controls each action and how historical activity remains traceable. That record is useful both when adopting a system and when planning an eventual change.