How to accept rental opening balances without importing hidden errors

Accept rental opening balances only after fixing one scope and cutoff, preserving the source records, checking sign and field meanings, tying every control total to record-level detail, reconciling cash to external evidence, and recording exceptions. Reject unexplained plugs, missing deposit ownership, crossed tenant balances, or a target that cannot reproduce the accepted reports.

Preview the answer, sections, action steps, and questions this guide actually contains. This map describes the page's structure; it is not a rating or completion measure.

Start with the action you are making, then read the section that uses the closest wording. When there is no wording match, this follows the guide's written order.

The line shows where the linked section appears in this guide. It is not a priority, completion, or confidence score.

List each opening class separately: tenant receivables, tenant credits, refundable-deposit liabilities and detail, bank cash, uncleared items, vendor payables, prepaid amounts, owner contributions or equity, loan balances, and any controlled suspense accounts. Name the legal entity, account, property scope, currency, sign, and source report for each class.

Do not use “balance” as a universal field definition. One export may show amount due as positive and credits as negative; another may expose lifetime net activity. Record source meaning, target meaning, transformation, effective date, null behavior, and acceptance test. Include examples for zero, negative, future-dated, inactive, and transferred records.

A twelve-unit source ledger reports $7,800 of net tenant receivables, and the target also reports $7,800. The total appears ready, but the detail tells another story.

Two internal systems can reproduce the same wrong amount. Tie each imported bank balance to the reconciled external statement and documented outstanding items. For refundable deposits, compare resident-level detail with the deposit-liability control account and the applicable bank or restricted-cash evidence for the same boundary and cutoff.

Do not force all three deposit figures to equality with a portfolio plug. A difference may come from an unallocated receipt, an outstanding transfer, interest, a legally permitted account structure, or a misposted disposition. Identify the resident and transaction, determine which record is wrong, and document any jurisdictional review before changing custody or liability records.

Use reason codes such as scope, cutoff, field meaning, sign, duplication, missing source, unsupported target, identity match, pending settlement, and accepted timing item. Every exception needs an amount or affected-record count, consequence, owner, next evidence, due date, correction method, and retest result.

Missing active leases, unexplained resident balances, deposit ownership gaps, material cash differences, and inaccessible source history are strong release blockers. A documented bank item that cleared the next day may be an acceptable timing exception if policy allows it and the clearing evidence is retained. “Close enough” is not a disposition.

Do not review a mixed trial-balance export as one undifferentiated total. Build a schedule for each operational class and include the fields needed to reproduce it. A tenant-receivable schedule needs resident and lease IDs, unit, charge and credit components, net balance, aging date, and source statement. A deposit schedule needs resident ownership, receipt and disposition status, liability amount, and the applicable cash account. A vendor schedule needs invoice, approval, payment state, and due date. These schedules prevent a correct grand total from masking a missing owner.

For every schedule, calculate a source control total and target control total, then explain the difference as a list of identifiable records. Also test population completeness: count active positive balances, credits, zero balances intentionally imported, inactive records with open amounts, and records rejected by the target. A zero-dollar variance does not pass if the target omitted one $500 receivable and one $500 credit. Retain both the value comparison and the population test in the acceptance packet.

The packet should contain the source export, checksums or other integrity records, closing and opening reports, field map, stable-ID crosswalk, bank support, deposit schedule, exception log, approvals, and archive instructions. Test that a second person can retrieve pre-cutover evidence after the old interface is unavailable.

During the first live close, trace at least one real receipt, returned payment, invoice, owner transaction, adjustment, and deposit event through the target. Reconcile opening plus activity to ending balances. A target that held the opening position but loses the first operating events is not yet a reliable system of record.

Key takeaways

Not always. A controlled opening position plus a durable, retrieval-tested archive can be appropriate when full history cannot be migrated reliably. The choice should reflect reporting, tax, legal, dispute, and operational retention needs; do not cancel access before proving retrieval.

A control total alone is not enough for resident operations. Keep tenant-level receivable and credit detail so statements, collections, disputes, and later corrections remain attributable to the correct household.

Use documented consequence-based criteria. Unexplained cash, missing active obligations, wrong resident balances, deposit ownership gaps, or inaccessible source evidence should ordinarily stop release; a supported timing item may be carried only under an explicit policy.

Do not omit the record merely because the tenancy is inactive. Decide whether the supported receivable, credit, deposit, or write-off remains operationally and legally relevant, preserve the former lease identity, and import or archive it under a documented disposition. Test inactive records as a separate population because ordinary active-lease samples will not find them.

Keep reading