Short answer: a bank or payment cutover is ready only when every approved account and payment path has an owner, cutoff time, source balance, destination configuration, in-flight transaction treatment, ledger result, exception route, rollback decision, and reconciliation sign-off. Seeing a successful test payment does not prove that deposits, reversals, fees, owner funds, and reports will remain correct.
Buildium's current payment and accounting guidance separates pending transfers from cleared funds and emphasizes reconciliation, returned-payment handling, and the connection from payment to ledger and owner reporting. This independent checklist turns those ideas into a vendor-neutral control record. It is educational guidance, not an accounting opinion, banking instruction, trust-account determination, payment-network rule, or substitute for qualified review of contracts and jurisdiction-specific requirements.
Define the exact cutover boundary
List each bank account, legal owner, purpose, property or entity scope, payment rail, processor, settlement account, ledger account, portal, integration, and report affected. Separate operating, reserve, deposit, owner, vendor, and other controlled funds according to the structure approved for the business. Record what is explicitly outside the change.
Freeze source evidence at a named time
Preserve source statements, book balances, property or owner subledgers, open receivables, payables, deposits, pending transfers, uncleared items, returns, disputes, fees, and scheduled payments at a stated timezone and cutoff. Use the data migration cutover sign-off for the broader record-mapping and approval sequence.
Map every transaction state
Define how initiated, authorized, pending, submitted, settled, failed, returned, reversed, disputed, refunded, voided, and cancelled transactions appear in the processor, bank, ledger, resident balance, owner report, and audit trail. Do not treat a pending amount as available cash unless the approved accounting treatment supports it.
Download the payment cutover checklist
Download the editable bank account and payment cutover reconciliation checklist (CSV). It records scope, source evidence, credentials, test payments, settlement, fees, returns, balances, ledgers, owner funds, integrations, communications, exceptions, rollback, and approvals.
Test the payment-to-ledger chain
Run controlled examples for rent, recurring charges, owner contributions, vendor payments, owner distributions, refunds, fees, returns, and partial or duplicate scenarios where applicable. Confirm amount, date, payer or payee, property, unit, account, reference, fee, status, and posting result. Connect the evidence to the three-way reconciliation checklist.
Reconcile in-flight and uncleared items
Assign each open item a source status, expected destination treatment, responsible person, expected settlement or resolution date, and final evidence. Prevent duplicate submission during the overlap period. Record how stale checks, rejected transfers, processor holds, chargebacks, and late bank files will be handled without hiding them in a balancing entry.
Verify access and separation of duties
Test who can view accounts, change bank details, initiate or approve payments, release owner funds, issue refunds, edit posted transactions, reconcile, export, and administer integrations. Include denied tests and emergency access. Use the role permissions matrix to preserve the approved baseline.
Set blocking conditions and rollback authority
Define what stops launch: unexplained balance differences, missing transaction history, unverified account ownership, failed settlement, incorrect ledger posting, broken notifications, unresolved permissions, or unavailable evidence. Name the go-or-no-go approver, latest safe rollback point, source of restoration, and communication owner.
Close through formal reconciliation
After launch, compare processor totals, bank deposits, book balances, property or owner balances, fees, returns, and exceptions for a defined period. Preserve the reports and approvals used to close the change. Carry unresolved items into the monthly close checklist rather than declaring success because transactions are moving.
Frequently asked questions
Should all payment methods switch at the same time?
Not automatically. Sequence depends on contracts, processor behavior, risk, testing, staffing, resident communication, and the ability to prevent duplicate or missing transactions. Record the approved scope and overlap controls.
Can software automatically approve reconciliation?
Matching can reduce manual work, but material differences, unusual entries, access changes, and final sign-off still need the qualified review defined by the organization.