Reconciliation & the Monthly Close

Recording isn't the finish line — reconciliation is

Entering a transaction records what you think happened; reconciling confirms it against what actually happened. That's the division of labor this domain runs on, picked up from the stage before: recording decomposes each cash event into its true parts, and reconciliation proves you decomposed it completely — by checking your books against external source records that are independent of your own bookkeeping entries: the bank statement, the card statement, and each payout platform's report. The control isn't "the bank is truth"; it's don't verify the books using only the books.

Skip it and the failure is quiet. It's easy to record transactions all month and never reconcile — the books look done, so the gap stays invisible while small errors — a miscategorized charge, a fee never recorded, a duplicated entry — compound for months. Then a lender asks for a clean profit-and-loss statement, or tax season arrives, and nothing ties out. Reconciliation is what keeps "looks done" and "is done" from drifting apart.

(This node teaches the close as a routine; the platform-by-platform and software-specific reconciliation mechanics live in the linked leaves. A note before we go further: this is educational, not legal or tax advice, and the deductibility and tax-line questions are your tax professional's to decide.)

What reconciliation actually is — two jobs, not one

Reconciling means matching your books to independent source records — until they agree, or until you've found and explained why they don't. Reconcile every material cash account and card, plus every material platform or processor source needed to prove your recorded booking activity and its settlement. (A platform with no activity that month, or one already routed through a single integrated source, doesn't need its own separate pass.)

It helps to see that two different jobs both get called "reconciliation," because they aren't the same operation:

• Account reconciliation — a balance-sheet account (a bank or credit-card account) matched to its external statement, with the difference resolved to zero. This is the formal "reconcile" function in software like QuickBooks Online.
• Payout (source-to-books) reconciliation — the STR-specific one: a platform's activity/payout report matched to the gross components you recorded (revenue, the fee, taxes, refunds) and then to the cash that settled. This isn't the same as clicking a bank-reconcile button — you're proving that what you recorded reconstructs what the platform reported and what actually landed. Treating "reconcile Airbnb" as if it were a bank reconciliation is a common confusion; unless you've built a balance-sheet workflow for it, it's a source-to-books check.

That second job is where a clearing or holding account earns its place — the optional Platform/Payment Clearing account from your chart. It should reconcile to zero once a payout has fully settled — or to a supported, fully explained balance for money still in transit at the reporting cutoff. (A guest stays December 30–31, you record the revenue, and the cash doesn't land until January 2: at December 31 the clearing account legitimately holds that in-transit amount.) So the rule isn't "always zero." The rule is: no unexplained balance survives the close. A residual you can't explain is the error signal; a residual you can explain is a reconciling item you carry forward with a note.

The monthly close, in five steps

The close is a short, repeatable routine — the same five steps every month, in the same order:

1. Reconcile. Prove your external balances and activity to the books — match each material bank and card account to its statement, and reconcile each material platform's payout report to the gross components you recorded and to the cash that settled. Clearing accounts land at zero after settlement, or at a supported in-transit balance you can explain.

2. Review. Scan the P&L and balance sheet for figures that are plausible-but-wrong: uncategorized transactions, a cost in the wrong bucket, or a balance that shouldn't be sitting there — a refundable guest-deposit liability that should have been refunded or reclassified based on the underlying outcome, a Capital-Expenditure-Review clearing account that never got cleared, a stale payable.

3. Adjust. Post supported corrections and the period entries the bank feed never shows — owner-paid costs, and accruals or prepaids if you're on an accrual basis. (In the BFC baseline workflow, depreciation is posted from the depreciation schedule through the period/year-end process rather than estimated from the bank feed; more formal book-depreciation workflows may record it more often — and Tax owns tax depreciation.)

4. Lock. Establish change control over the completed period: set a closing date. In systems like QuickBooks Online this warns on, restricts, or requires authorization for later edits to the closed period — it doesn't make the period technically impossible to change, and an admin can move the date, so treat it as a control, not a seal. If a closed period ever has to change, document why and review the software's closing-date / exceptions report.

5. Report. Only after the first four, produce the month's profit-and-loss statement, balance sheet, and cash-position / cash-flow view. Now they mean something, because they're reconciled and locked. (Reading them for decisions is the next stage, P41.)

Reconcile every material source, while it's fresh

Do the close while the records are current — bank feeds up to date, each active platform's monthly payout report downloaded. Reconcile each material source on its own — Airbnb, Vrbo, and a direct-booking processor like Stripe each produce their own report — and any material source not already reconciled through an integrated source needs to be accounted for in the close, because each can carry fees, taxes, and adjustments differently. (The step-by-step mechanics of reconciling a specific processor are covered in the linked leaf.) The discipline is the same across all of them: the parts you recorded must reconstruct what actually arrived.

Cadence: monthly as the baseline

Builders Finance uses a monthly close as the baseline cadence for an owner-operated STR — frequent enough to catch errors while they're small and cheap to fix, rare enough not to become a burden. Higher-volume operations may reconcile some accounts more frequently; that's about how often you do the work, while the formal close still sets the monthly reporting cutoff. Either way the value isn't in any single close; it's in the routine — same steps, same order, from a checklist. A year of clean monthly closes can turn tax season into a handoff rather than a reconstruction, and gives you a P&L you can hand a lender without an apology. Run it from a written checklist rather than memory, and the close becomes confirmation instead of investigation.

Put it to work. The paired STR Monthly Close Workbook turns this routine into a working tool: a Monthly Close Checklist (period, who, date, and the five steps), an Account Reconciliation Register (each account — statement balance vs. book balance, difference, supported reconciling items, adjusted difference, status), a Platform Reconciliation tab (per platform — gross revenue, fees, taxes, refunds, expected settlement vs. actual payout, clearing balance, explanation), and a Close Issues & Adjustments log. It's built around the real rule — zero or explained difference — not zero-at-all-costs.

   RECONCILE BEFORE YOU REPORT  —  the monthly close

   YOUR BOOKS                      EXTERNAL SOURCE RECORDS  (independent of your entries)
   what you recorded        vs.    bank · each card · each material platform report
        │                               │
        └───────────►  RECONCILE  ◄─────┘   account recon: balance ↔ statement
                     (do they agree?)        payout recon: report ↔ recorded gross ↔ cash
                            │                clearing → 0 after settlement, or explained in-transit
             ┌──────────────┴───────────────┐
        they agree                    difference found
             │                              │
             │                    REVIEW → ADJUST  (fix categorization,
             │                              │        post supported period entries)
             └──────────────┬───────────────┘
                            ▼
                    LOCK the period      change control over the closed period —
                            │            warns / restricts later edits, not a seal;
                            ▼            document any exception
             REPORT: P&L · balance sheet · cash-position view

   Same order, every month:   1 Reconcile → 2 Review → 3 Adjust → 4 Lock → 5 Report

Read it in one line: prove the books against independent bank, card, and platform records; explain or fix every difference; put the period under change control; then report. Report first and you're publishing an unproven number.

Right-size it — the close is confirmation, not a research project

A good close is short and repeatable, not elaborate. Once the money is separated (Separate), the chart is built (Structure), and you record on a cadence (Record), the monthly close is mostly confirmation — a routine that gets faster and more predictable the longer you keep it up. If your close keeps turning into a monthly research project, that's a signal the fix is upstream: the accounts weren't cleanly separated, the chart is fighting you, or recording fell behind. Don't build an elaborate close to compensate for a shaky foundation — repair the stage that's actually leaking. The point is a routine you'll run every month, not the most thorough process you can design and then abandon.

Your action plan

1. Reconcile every material account and source. Each material bank and card account to its statement; each active platform/processor's payout report to the gross components you recorded and to the cash that settled — not just checking.
2. Resolve the clearing accounts. Platform/payment clearing and any holding account should reconcile to zero after settlement, or to a supported in-transit balance you can explain — no unexplained balance survives the close.
3. Review the P&L and balance sheet for anomalies. Uncategorized transactions, wrong-bucket costs, a refundable guest-deposit liability that should have been refunded or reclassified, a stale payable, an uncleared Capital-Expenditure-Review account.
4. Make the period-end adjustments. Fix miscategorizations; record owner-paid and other non-bank entries, plus accruals/prepaids if you're on accrual — and post depreciation from the depreciation schedule through the period/year-end process (Tax owns tax depreciation), not from the bank feed.
5. Lock the period. Set a closing date as change control over the closed period; if a closed period must change later, document why and review the software's closing-date / exceptions report.
6. Report, then keep the cadence. Produce the month's statements, and run the same checklist next month — the routine is the point.

The bottom line

Reconciliation is the step that turns recorded data into numbers whose reliability you've actually proven. Match the books to external source records — the bank, the cards, every material platform — until they agree or you've explained why they don't; review for what's plausible-but-wrong; adjust; put the closed period under change control so later edits are caught, not silent; then report. Do it monthly, the same way, from a checklist, and the reports you read — and the tax handoff at year-end — stand on verified ground instead of hope. Reconciliation is also the quiet proof that everything upstream worked: clean separation, a chart that fits, records kept on a cadence. Get those right and the close is confirmation; skip them and it's archaeology. Reconcile before you report.

About the author

Matt Nunn is the founder of Builders Finance. He has spent two decades working with the financial side of real estate businesses, and started Builders Finance to give short-term-rental operators the financial systems, frameworks, and plain-language education that most hosting advice skips over. Builders Finance publishes educational content for STR owners; it is not legal or tax advice, entity and tax rules vary by state and situation, and it is not a substitute for guidance from your own attorney and qualified tax professional.

Continue learning

Educational information only — not individualized tax, legal, or investment advice. The worked example is an illustrative model, not a projection or a recommendation.