OWNER WORKFLOW GUIDE
3-Way Bank Reconciliation for Commercial Property Managers
Bank reconciliation for property managers gets harder when the PM system, bank statement, and ledger drift apart — here's what a live, matched feed changes.
Bank reconciliation for property managers is supposed to confirm that the property-management system, the bank statement, and the general ledger agree on the same money — a 3-way reconciliation, in the term property-accounting firms actually use for it. In practice the three legs are built by different people on different schedules, so the harder problem usually isn't whether the totals match — it's tracing one anonymous bank line back to the specific tenant, vendor, or work order it belongs to.
1. The three legs of a 3-way reconciliation, and where they actually drift
A 3-way reconciliation compares three separate records of the same money: what the property-management system (PM system) says happened — rent charged, CAM billed, a work order paid — what the bank statement says actually moved, and what the general ledger says was posted. In a small commercial portfolio, each leg is usually built by a different process on a different schedule. The PM system updates the moment a payment is logged, the bank statement is a monthly or on-demand pull, and the GL is whatever an accountant or bookkeeper last posted, sometimes weeks behind either of the other two.
Most of the drift isn't fraud or error — it's timing and labeling. Anyone trying to reconcile a rental property's bank account by hand runs into the same handful of patterns, and none of them show up until someone sits down to compare all three records line by line.
- Payment confirmed in the PM system before it settles at the bank, or the reverse for a returned ACH
- Multiple tenants' payments batched into a single deposit line by a payment processor or lockbox
- A GL entry posted from a paper invoice that never touched the connected bank account
- A bank fee, NSF charge, or interest credit with no PM-system counterpart at all
2. Why matching totals isn't the same as matching money: a $4,180 example
Suite 210's November rent is $4,000 base plus a $180 CAM estimate — $4,180 total, due on the 1st. When the tenant's payment lands in the property's checking account, the bank statement shows an ACH credit for $4,180 with a routing number and a counterparty name, and nothing else: no suite number, no lease reference, no indication it's rent rather than a security deposit or a vendor refund. A traditional monthly tie-out can post that $4,180 line to "Income" and call the totals reconciled, because the totals do agree.
The reconciliation isn't actually finished at that point. It's finished once that specific bank line is matched back to a specific tenant, unit, and billing period — Suite 210, November, rent plus CAM — not just to a GL bucket labeled income.
- $4,000 base rent — Suite 210's November lease charge
- $180 CAM estimate — November, per the lease's CAM schedule
- $4,180 total ACH credit, unlabeled on the bank statement itself
- Match target: the specific invoice the payment applies to, not the "Rental Income" account
3. What a live, matched bank feed actually changes
This is the piece a monthly export can't do, and it's where a live feed changes the actual mechanics of commercial property bank reconciliation software. TenantPoint connects to the property's real bank account through Plaid, once, from the Banking screen. After that, transactions sync automatically instead of arriving as a monthly file, and each new line is checked against open tenant charges, vendor records, work orders, and CAM periods as it appears — not batched for a month-end pass.
An incoming $4,180 ACH credit is compared against open tenant charges, and an amount match alone is never enough on its own to match it automatically. It takes a second, corroborating signal — the tenant's name appearing in the transaction description, or a historical pattern matching a prior deposit from that same tenant — agreeing with the amount before a match is applied without review. Anything less certain than that, including two tenants who both plausibly owe close to $4,180 that month, is held for a person to confirm instead of guessed.
- Deposits are checked against open tenant charges as they arrive, not once a month
- A single unambiguous match is applied automatically; anything with more than one plausible answer is queued for review
- The same feed surfaces outgoing debits for vendor and work-order matching, not just tenant income
- This is read-only bank connectivity — TenantPoint doesn't move money or process a tenant's rent payment
4. From "did the three totals agree" to "what's still unmatched"
With three static ledgers, the monthly question is binary: do the totals on the PM system, the bank statement, and the GL agree? With a live, continuously matched feed, most of that work has already happened by the time month-end arrives, so the real monthly question gets narrower: what's still unmatched, and why? A work order paid by check instead of the connected account, a bank fee with no PM-system record, an ACH that bounced and needs to be traced back to the tenant it belonged to — those are the items that actually need a person's judgment, because everything else already tied out as it happened.
The general ledger leg updates the same way. Once a rent invoice is generated, a payment is confirmed, or a work-order expense is reconciled and tagged to a vendor, TenantPoint pushes that record into QuickBooks — an Invoice, a Payment applied against it, or a Purchase for the paid expense. It's a one-way push; TenantPoint never reads QuickBooks' ledger back into its own records, and if an accountant later edits that same transaction directly in QuickBooks, TenantPoint detects the mismatch and flags it as a conflict for a person to resolve rather than silently overwriting either side.
- Unmatched deposits and debits become the exception queue, not the whole reconciliation
- Reconciled events push once into QuickBooks as Invoice, Payment, or Purchase records
- An accountant's direct QuickBooks edit is flagged as a conflict, never overwritten automatically
- Only two conflict resolutions exist: accept QuickBooks' current value, or ignore it
5. What still needs a human, and what a live feed doesn't fix by itself
A live feed removes the busywork of retyping three ledgers into agreement, but it doesn't remove judgment from the categories that were always judgment calls. A bank debit only becomes a work-order expense once someone reconciles that specific transaction and tags it to the work order it paid for — TenantPoint never guesses that a $340 debit to a plumbing company was for a specific unit's leak repair. A work order with more than one vendor attached is held for a person to assign rather than assigned to whichever vendor happens to be listed first.
None of this requires starting from a clean slate. A property that's been reconciling by spreadsheet, or hasn't reconciled in months, can connect its bank account and let the feed populate transaction history first. Some bookkeeping firms sell exactly that kind of backlog cleanup as a standalone catch-up service, but it's the same matching process applied to older transactions instead of new ones — and once a bank account is connected, staying current uses that same process going forward.
- Work-order expenses push only after a person reconciles the bank line and tags the work order — never auto-matched
- A work order with more than one vendor is flagged for a person to assign, not guessed
- Catching up on months of unreconciled transactions uses the same matching logic as staying current
- A live feed narrows the review queue to real exceptions; it doesn't remove the need to resolve them
Frequently asked questions
What makes a reconciliation "3-way" instead of a standard bank reconciliation?
A standard bank reconciliation compares the bank statement to one set of books. A 3-way reconciliation adds a third, independent record — typically the property-management system's own charge and payment history — so a match has to hold across all three, which is what property-accounting firms mean by 3-way reconciliation in property management.
Does connecting a bank account mean TenantPoint can move money or accept rent payments?
No. The bank connection is read-only, through Plaid. It syncs transaction data for matching and reconciliation — it doesn't initiate payments, transfers, or rent collection.
What happens when a bank transaction can't be matched automatically?
It's held as an exception for manual review instead of assigned to the closest guess — the same rule applies whether the ambiguity is between two tenants, two vendors, or a work order with more than one vendor attached.
Will a live bank feed change how often I need to close the books?
That's set by your own accounting cadence, not by the bank feed. A live feed shrinks the review queue to real exceptions, but the general ledger still closes on whatever schedule your accountant or your invoice sync policy uses.
USE THIS WITH ONE REAL PROPERTY
Stop rebuilding the operating record every month.
Start a 15-day trial, add one property, and bring the lease, rent, CAM, and tenant communication into the same workspace.