Check the File Before a Rental Deposit Record Transfer
An administrative checklist for moving deposit records between systems while preserving source, status, and authority.
By PortfolioRental Editorial Team · · Updated 2026-09-15
Moving a deposit record between systems can break the connection between an amount, resident, lease, transaction history, and governing account. A transfer check protects that chain. It does not authorize movement of funds or decide how a deposit must be handled under local law.
The property record source register identifies origins, while the lease signature gap review keeps packet exceptions separate.
Quick Overview
List the properties, leases, record cutoff, source system, destination, and responsible roles. Freeze the export version used for comparison. Exclude records outside the approved scope rather than moving them because they appear in the same report.
Common Mistakes
Compare the lease identifier, resident reference, recorded amount, transaction dates, status, and source account reference. Use controlled identifiers in working sheets. Any total comparison should retain the underlying row-level evidence and the person who reviewed the exception.
Common Questions Answered
Administrative staff may prepare exports, map fields, and report differences. They should not change an amount, release funds, choose a legal classification, or approve a bank transaction unless their documented authority covers that act. Route legal and accounting questions to the proper professionals.
Ready to verify after import
Compare destination records with the frozen source population. Record missing, duplicate, and transformed values. Do not delete the source evidence after a successful import. Retention, privacy, and access rules still apply, and the final acceptance should name the authorized reviewer.
Published September 15, 2026.
See the IRS rental recordkeeping guidance for general records context.