A Nashville Airbnb can host the same guests across December 31 and still produce several different year-end totals. The reservation was created on one date, the nights occurred on others, the platform sent money later, and the bank recorded a deposit after that. Before comparing the property's December results with January, decide which question each report answers.
For a buyer, the useful deliverable is a cutoff schedule: one record of the stays crossing the reporting boundary, connected to the related payments and later adjustments. It explains a difference between periods without automatically labeling that difference growth, missing revenue or a tax error.
Define three views before comparing a total
A stay-date view asks which nights the home provided lodging. A platform-payment view asks which transactions were sent or remained upcoming under that system's reporting definition. A bank view asks when money reached the receiving account. Preserve all three date fields, even when two happen to match.
Airbnb's earnings-download guidance describes reports by listing and date range, with gross earnings, deductions and net pay. Export the source records and retain the selected filters. Check the actual field definitions in the report; do not assume that every dashboard or CSV groups a reservation by the same date.
The platform's earnings dashboard guidance also separates upcoming and paid transactions and notes that payouts for multiple listings can appear together. A paid row therefore needs its underlying reservation detail before you assign the whole amount to one Nashville property.
Build a boundary file for the exact unit
Start with the unit, channels, currency, reporting window and the date the records were exported. For year-end analysis, pull enough surrounding activity to find the stays and settlements crossing the boundary. The required lookback and follow-up depend on the transactions; an arbitrary seven-day window can leave a longer outstanding item unexplained.
Use reservation references, check-in and check-out dates, nightly accommodation amounts, adjustments, platform transaction references and bank posting dates. Keep guest names, contact information and access codes out of the buyer's working packet. Retain the original exports separately from your classifications.
Our broader revenue and cash-flow overview addresses the difference between receipts and owner cash. The cutoff schedule adds a specific test: whether a change in the reporting date moved an amount between periods without changing the underlying stay.
A four-night example across December 31
The following is an invented illustration, not an actual Nashville reservation, an observed nightly rate or a forecast for the coming New Year. Assume one stay checks in December 30, 2026 and checks out January 3, 2027. Its four occupied nights carry the accommodation charges below. Cleaning, taxes, platform deductions and other charges are excluded so the date allocation stays visible.
Night beginning | Assumed accommodation charge | Stay-date year |
|---|---|---|
December 30 | $300 | 2026 |
December 31 | $600 | 2026 |
January 1 | $400 | 2027 |
January 2 | $300 | 2027 |
Total: four nights | $1,600 | $900 / $700 |
In this explicitly defined stay-date analysis, December receives $900 and January receives $700. Dividing the $1,600 equally by four nights would instead assign $800 to each year. That shortcut preserves the combined total but moves $100 out of December and into January. Use the documented nightly charges when available; disclose an allocation assumption when they are missing.
Now assume, solely for the example, that one $1,600 settlement is sent December 31 and posted by the bank January 4. The payment-date view puts the settlement in December; the bank-posting view puts it in January. Neither view changes the four nights or their $900/$700 analytical allocation. These assumed dates are not Airbnb processing promises.
Reconcile the opening and closing items
For each period, list the earlier stays whose receipts arrived during the period, the in-period stays with receipts still outstanding, and any later refunds or adjustments connected to those stays. Match the references and amounts rather than forcing an unexplained difference into a generic miscellaneous line.
The four-night example can be checked across the combined December–January window: $900 plus $700 equals the same $1,600 settlement and bank receipt. That agreement is only a check of this simplified example. A real file also needs its deductions, split payments, other channels and unresolved items reconciled.
Do not add the platform settlement and bank deposit together as two receipts. They are two pieces of evidence for the same transfer. Likewise, a reservation appearing in both Airbnb and a property-management system remains one stay. Resolve the channel mapping before using either report to compare months.
Keep later adjustments attached to the original stay
A refund issued after the reporting boundary needs both its transaction date and the reservation it relates to. Preserve the dated source record. Then show how your chosen analytical presentation treats the adjustment and whether the earlier period has been revised. Do not silently mix an updated December stay schedule with an unrevised January payment report.
For a purchase review, deliver a short exception list alongside the totals: unmatched settlement, combined-listing payout, missing nightly detail, unresolved refund or amount routed to another recipient. Give each item a supporting record and resolution status. An outstanding receipt is a question to investigate, not proof that the seller has lost the money.
Compare performance only after the dates agree
Use the same unit, revenue definition and stay-date convention when comparing December with another December. Keep future reservations separate from completed activity. An earlier payout, a different export setting or an extra listing inside a report can change a headline total without proving stronger lodging demand.
This schedule is an investment-analysis tool. It does not determine taxable income, a 1099-K amount or the accounting method the owner should use. Ask the property's accountant to reconcile the tax records under the applicable rules; a nightly analytical allocation should not quietly become a tax filing instruction.
Place the cutoff schedule in the income section of the turnkey STR due-diligence file. For broader reservation and operating context, the companion site's Nashville Airbnb revenue-analysis guide provides a separate starting point.
If you are evaluating a Nashville rental with income spanning a reporting boundary, The Costigan Group's STR advisory team can help organize the property-specific questions before you rely on the annual total. Bring the export settings, boundary schedule and unresolved items to the discussion.
Written by Jack Costigan, The Costigan Group. Platform guidance checked October 20, 2026. All reservation amounts and settlement dates above are illustrative. Cover: an AI-generated Nashville-style rental interior, not an actual listing or business record.
