A billing and bank-account cutover is the controlled change from existing invoice and payment instructions to the instructions authorized for the acquired operation. It includes ownership of receipts, client communication, processor readiness, fraud verification, and reconciliation rather than merely replacing an account number on an invoice template.
What should be decided before clients receive new instructions?
Decide which entity is billing for each service, which party owns the resulting receivable, and which authorized destination should receive payment. Those decisions should reflect the agreed transaction and service arrangements.
The buyer hub introduces the broader acquisition process. This cutover concerns the operational release of payment instructions, while seller-retained receivables reconciliation explains how to allocate money that relates to work on different sides of closing.
Prepare a cutoff matrix identifying existing invoices, new invoices, deposits, prepaid services, credits, and disputed balances. A client may owe the seller for an old invoice and the buyer for a new one at the same time.
Confirm account ownership and authorized signers with the actual financial institution. Do not assume that a seller account, merchant relationship, or payment token may simply be renamed or transferred because the practice keeps its branding.
How should new payment instructions be verified?
Verify account instructions through a controlled process and a secondary communication channel. An acquisition creates a plausible reason for an instruction change, which makes a convincing fraudulent message especially disruptive.
The FBI’s business email compromise guidance recommends using secondary channels or two-factor authentication to verify requests for account changes. It also advises contacting the originating financial institution promptly when fraud is recognized.
Designate one person to prepare an approved instruction and another to verify it against bank-confirmed information. Establish the independent contact method before an unexpected request arrives; relying on a phone number supplied in the suspicious message defeats the purpose.
Avoid publishing sensitive banking information across uncontrolled documents. A portal, approved invoice, or other selected method still needs correct permissions and a way for clients to verify that the instructions came from the practice.
Train staff to escalate unusual requests, account substitutions, urgent overrides, and requests to bypass ordinary checks. A friendly message using the seller’s name should not override the control merely because the transaction is familiar.
Which billing records and integrations need a test?
Test the complete path from authorized invoice generation to receipt posting and bank reconciliation. A template preview does not establish that the processor settles funds to the right entity or that the ledger applies them correctly.
The historical 2012 Journal of Accountancy article on pricing, billing, and collecting fees discusses timely billing, clear fees, and collection processes. Its operational lesson supports treating billing as an assigned workflow; its historical examples are not current payment-system evidence.
Use the technology migration guide to identify billing interfaces and access owners before testing the cutover.
Check legal billing identity, service descriptions, invoice numbering, remit-to details, portal links, processor configuration, recurring schedules, receipts, refunds, and permissions. Confirm the contractual and technical requirements with each relevant provider.
| Component | Test | Release evidence |
|---|---|---|
| Invoice identity | Compare entity and service agreement | Approved billing template |
| Bank destination | Independently verify ownership and details | Authorized reviewer confirmation |
| Payment processor | Follow the approved provider test procedure | Settlement and entity configuration confirmed |
| Ledger posting | Trace receipt to the intended invoice | Receipt allocation reconciles |
| Client instructions | Review notice and verification route | Approved message and support owner |
Use the provider’s approved test procedure instead of sending an improvised transaction that could create charges, refunds, or client confusion. Document exactly which environment was tested and which production settings still need approval.
How should recurring payments and client information be handled?
Determine what rights, authorizations, and technical steps apply to each recurring arrangement before changing it. A list of scheduled payments does not prove that the buyer can charge the same clients through a new entity or processor.
Review the service agreement, payment authorization, provider requirements, and relevant information restrictions. Separate a recurring billing schedule from the underlying permission to use payment credentials or disclose protected information.
The IRS Section 7216 information center provides rules and guidance concerning use and disclosure of tax return information. Establish the applicable basis for any protected data used in the cutover; an acquisition NDA alone should not be treated as that basis.
Keep a status register for recurring arrangements: reviewed, approved, awaiting client action, technically configured, tested, or held. An incomplete authorization should remain an exception rather than being labeled ready because the expected receipt appears in a forecast.
If an arrangement cannot be migrated on time, develop an approved alternative with the client and provider. Do not silently substitute an account or assume a historical instruction authorizes every future payment method.
How can a buyer reconcile the first mixed receipt period?
Reconcile receipts by ownership and settlement timing before classifying available operating cash. The bank balance can contain buyer funds, seller funds awaiting remittance, and transactions still subject to investigation.
Assume an illustrative first week with $50,000 of receipts. Supporting invoices allocate $20,000 to seller-retained balances and $30,000 to buyer services. The agreement requires full remittance of the seller allocation and assumes no collection fee or offset.
A $3,000 buyer-service refund then reduces net buyer cash to $27,000. After that refund, the bank has $47,000 from these transactions: $20,000 due to the seller and $27,000 attributable to the buyer. The equality reconciles the allocation.
If $8,000 of the buyer receipts settles five days later, the immediate settled balance is $39,000 rather than $47,000. Subtracting the $20,000 seller obligation leaves $19,000 of immediately settled buyer cash, plus the pending $8,000.
These figures are invented assumptions, not standard settlement times or deal terms. The thirteen-week acquisition cash forecast should use actual availability dates and exclude seller funds from buyer operating resources.
How should the cutover be performed?
Perform the change through a release process that connects contractual decisions, independent verification, provider tests, and client support. Assign an accountable owner for unresolved items.
- Approve the cutoff matrix identifying billing entities, receivable ownership, deposits, credits, and exceptions.
- Confirm bank accounts, signing authority, processor requirements, and necessary client authorizations.
- Independently verify new instructions and test the approved invoice-to-settlement workflow.
- Release the approved client notice with a known verification channel and a named support contact.
- Monitor receipts, settlement delays, rejected payments, duplicate charges, and unusual instruction requests.
- Reconcile ownership and remittances before retiring old instructions and unnecessary access.
Release dates may differ by payment method or client cohort. A controlled phased change can expose incomplete recurring arrangements without delaying every ready invoice, provided responsibilities and client communications remain clear.
Record which instructions are authoritative for each period. Keep obsolete templates out of active workflows while preserving necessary history. Removing a template from a shared folder is insufficient if staff continue sending a locally saved version.
What should a client notice explain?
Explain the billing entity, effective date, affected invoices, approved payment method, and verification route in clear language. The client should be able to determine what action applies to their own balance.
If old invoices retain different instructions, make that distinction explicit. Avoid a blanket direction to redirect every outstanding payment when the seller still owns particular receivables or when authorizations remain unresolved.
Keep operational payment changes separate from new service pricing or engagement scope. Combining unrelated changes can make disputes harder to diagnose: a client might accept the new payment route while questioning a fee or service change.
When a client reports a suspicious instruction, pause the affected change and preserve evidence. Follow the bank’s process and obtain relevant incident assistance rather than assuming a later ledger correction can recover money already sent away.
After release, review exception counts, unmatched receipts, pending settlements, and client questions. Those observations show whether the cutover is working and where a targeted correction is needed before the next billing cycle.
A few common questions
What else should you know?
Can the buyer redirect every outstanding invoice to a new account?
Only after confirming the relevant ownership, agreements, authorizations, and operating arrangements. Some outstanding invoices may belong to the seller, and some payment methods may need additional provider or client action. Build a cutoff matrix and approved instructions for each category rather than applying one change indiscriminately to every balance.
How should clients verify a changed account instruction?
Provide an established secondary channel that clients can use independently of an unexpected message. Staff should verify the approved instruction against bank-confirmed information and escalate unusual changes or overrides. A transaction announcement makes account changes plausible, so familiarity with the sender’s name or branding should not replace the verification process.
Are recurring payment schedules automatically transferable?
Do not assume so. Review the underlying client permission, service agreement, payment provider requirements, entity identity, and applicable information restrictions. A schedule shows intended timing but does not establish rights to use credentials through another entity. Track missing permissions and configuration separately before placing those receipts in the ready cutover population.
When can mixed receipt funds be used for buyer operations?
Use only funds attributable to the buyer that are actually available under the applicable arrangements. Reconcile seller-owned collections, refunds, disputed payments, and unsettled processor transactions first. A bank total can overstate operating resources when it includes seller remittances or excludes settlement delays. Reflect availability dates in the buyer cash forecast.
Which sources support this guide?
Primary rules and guidance support the factual statements in this article. The worked examples and decision frameworks are original educational analysis.
- Business Email Compromise (BEC) — FBI Internet Crime Complaint Center
- Pricing, billing and collecting fees — Journal of Accountancy
- Section 7216 information center — Internal Revenue Service