Lease and rent-roll to ledger reconciliation research

This brief asks how to reconcile an approved lease and rent-roll population to tenant accounting, cash, deposit custody, and the general ledger. The conclusion is an operating design: move through the records in a traceable chain, preserve gross transaction types, and assign every difference to a decision owner. A two-total comparison is insufficient because equal totals can conceal missing units, offsetting tenant errors, incorrect periods, or an unsupported journal.

The brief does not set a universal revenue policy. FASB Topic 842, IFRS 16, US federal tax guidance, lease terms, and local landlord law answer different questions. The entity's reporting framework and jurisdiction must be established before a reviewer decides accounting treatment or deposit disposition.

This hierarchy prevents a common category error: using a tax publication to decide book presentation, an accounting standard to decide whether deposit cash may be commingled, or one state's statute as a national operating rule.

Start with the property and lease population, not the ledger balance. For each cycle, record:

• legal entity, property, building, unit, tenant, and lease IDs;
• reconciliation period, contractual charge period, common cutoff, currency, and time zone;
• lease and amendment version, source location, approval status, start and end dates, and occupancy status;
• property-system report name, filters, extraction timestamp, row count, and control total;
• tenant-ledger report name, transaction-status filter, extraction timestamp, row count, and total;
• general-ledger company, property dimension, account set, period status, report timestamp, and trial-balance total;
• receipt source, bank account, deposit batch, settlement date, bank-posting date, and amount;
• preparer, reviewer, open-period status, and links to the prior approved reconciliation.

Save untouched exports. A later report rerun may include backdated charges or corrections and is not the same population. Record later activity in a change tab or subsequent-events section instead of replacing the file that was originally reviewed.

Completeness requires both directions. Trace active leases and occupied units forward into expected charges, and scan posted charges backward for a valid lease and unit. A lease-only test misses unauthorized charges; a ledger-only test misses units that were never billed.

Create one expected-charge row for each lease, charge code, and service period. Recommended evidence fields are:

• property, unit, tenant, lease, and charge IDs;
• lease source citation and amendment or notice reference;
• service-period start and end, due date, and effective date;
• base rent, recurring fee, approved concession, subsidy or tenant split where applicable, tax, and expected billed amount;
• proration basis stated in policy, with the input dates preserved;
• deposit requirement shown separately from rent;
• source currency, ledger currency, and approved exchange-rate reference if relevant;
• approval ID for nonstandard terms or manual overrides; and
• expected tenant-ledger code and general-ledger mapping version.

Do not fill an unclear lease term by copying last month's posting. Prior billing is comparison evidence, not authority for the current period. Send ambiguity to the property or legal owner and preserve the disputed text and affected amount.

The expected schedule should make gross components visible. A concession that is netted into base rent may reproduce the amount due while hiding its expiry date. A security deposit labeled as rent may reproduce cash while misstating both rental activity and the deposit obligation.

The recommended bridge has separate stages.

Approved lease terms to tenant charges

For each expected row, match property, unit, tenant, lease, charge code, service period, amount, and effective date to the tenant ledger. Classify differences as missing, duplicate, wrong amount, wrong period, wrong tenant, wrong code, or unsupported charge. Keep approved prorations and concessions as explicit reconciling items.

Tenant subledger to general ledger

Roll the tenant balance using opening receivable, charges, receipts applied, credits, refunds, write-offs, transfers, and closing receivable. Sum by legal entity, property, currency, and mapped control account, then compare with the general ledger at the same cutoff.

A direct journal to the receivable control account should appear as an exception unless the approved procedure explicitly permits it and links the tenant-level effect. Otherwise, the general ledger may tie while the tenant balances do not.

Receipts to bank activity and tenant application

Match receipt ID, payer reference, amount, receipt date, deposit batch, bank posting, and tenant application. Keep these states distinct:

• received and applied;
• received but unapplied;
• applied before bank confirmation;
• returned or reversed;
• deposited in transit at cutoff;
• unidentified; and
• refunded or transferred with authorization.

Timing differences should carry the later clearing reference. An unidentified receipt is not rental income merely because cash reached the bank. A bookkeeper can research the payer and lease references, but ambiguous application, inter-tenant transfer, or refund remains an authorized cash decision.

Security-deposit liability to custody evidence

Maintain a tenant-level rollforward of opening deposit liability, receipts, approved deductions, refunds, transfers, interest where required, and closing liability. Compare that schedule with the general-ledger liability and then with the applicable bank or custody account under the governing rule.

Do not assume that one deposit model applies everywhere. New York section 7-103 uses trust and non-commingling language for covered money. California section 1950.5 says covered security is held for the tenant and establishes permitted claims and disposition requirements, but the cited section should not be restated as New York's bank-segregation rule. For properties within 24 CFR 880.608, the federal regulation expressly requires a segregated, interest-bearing account and an account balance equal to covered deposits from families then in occupancy plus accrued interest.

The reconciliation should therefore include a jurisdiction and program field, the legal or compliance owner's documented rule, bank-account ID, tenant principal, required interest treatment, deductions pending approval, refunds pending, and any shortfall. Never offset a custody-account shortage with operating cash in the workpaper merely to display zero.

General ledger to reporting output

Map reconciled activity to the entity's approved chart of accounts and reporting basis. Keep book, tax, and management-reporting adjustments separately identified. IRS Publication 527's treatment of advance rent and refundable deposits is federal income-tax guidance; it is not a substitute for the accounting policy selected under US GAAP, IFRS, or another valid basis.

The controller or qualified accounting owner decides recognition, classification, impairment, modification, and presentation. The bookkeeper may prepare the bridge and proposed entry support, but should not turn an unreconciled difference into revenue or expense to force agreement.

Every exception should include the property, unit, tenant or payer, lease and transaction IDs, issue type, first-detected date, exact source values, amount if known, affected period, evidence checked, proposed next action, decision owner, due date, current status, and resolution reference.

Article-specific exception categories include:

• occupied unit with no expected charge;
• charge without an active approved lease or outside the approved term;
• incorrect commencement, renewal, increase, concession, or move-out effective date;
• duplicate charge or omitted approved proration;
• receipt applied to the wrong tenant, property, entity, or period;
• cash in bank with no tenant application, or tenant receipt with no bank evidence;
• credit, write-off, refund, or transfer without the required approval;
• tenant-subledger total that does not match the general-ledger control account;
• manual journal posted directly to a control account without tenant detail;
• deposit recorded as rent or deposited into an account inconsistent with the documented rule;
• deposit liability that exceeds applicable custody-account evidence;
• stale refund, disputed deduction, or missing disposition statement;
• cross-property or cross-entity posting; and
• prior-period change introduced after the original export.

Do not assign a made-up universal tolerance or closure time. Management should set materiality, escalation, and review cadence for the entity, while legal deadlines and program rules take precedence where applicable. Zero-dollar data exceptions, trust-account shortfalls, and unauthorized changes may require escalation regardless of amount.

Close an item only when the cited evidence arrives, the authorized decision is recorded, and any resulting entry or system correction can be traced. A comment such as "reviewed" is not resolution evidence.

A reproducible period packet should contain:

1. the frozen lease and unit population;
2. the expected-charge schedule with lease citations;
3. tenant-ledger, receipt, bank, deposit, and general-ledger exports with parameters and timestamps;
4. lease-to-charge, subledger-to-ledger, cash, and deposit rollforwards;
5. mapping tables and the version used;
6. the complete exception register, including open and reopened items;
7. approval records for concessions, credits, write-offs, refunds, transfers, and journals;
8. proposed and posted entry references kept visibly distinct; and
9. preparer and reviewer names, dates, scope, unresolved items, and final sign-off.

The reviewer should reperform selected paths in both directions and inspect all categories management has designated as sensitive, such as deposit custody, direct control-account journals, write-offs, and retroactive lease changes. Selection depth is risk-based and locally approved; the cited sources do not supply a universal sample size.

Remote or offshore staffing does not change these boundaries. Access should be limited to what the assigned preparation task needs, especially for bank and deposit accounts.

This brief synthesizes accounting-framework pages, US federal tax guidance, two state statutes, and a federal housing-program regulation. The reconciliation steps and evidence fields are operating recommendations inferred from the need to connect those separate records. They are not procedures issued by FASB, the IASB, the IRS, New York, California, or HUD.

The sources cover different populations and may change. Publication 527 addresses US federal income tax for residential rental property, not every property type or reporting question. Topic 842 and IFRS 16 apply only under their respective reporting frameworks. The New York, California, and Section 8 deposit provisions are not substitutes for a current review of every state, locality, program, lease, or bank arrangement affecting a property.

A completed reconciliation cannot prove that the lease is enforceable, notices are valid, all units were disclosed, a bank account has the legally required title, or a deposit deduction is permissible. It also does not estimate fraud, error, vacancy, or collection performance. Before use, the responsible accounting, tax, property, treasury, and legal owners should approve the population, mappings, custody model, materiality, deadlines, and escalation rules for the actual portfolio.