Schedule E is the simplest tax form short-term rental hosts will meet — but it's the one where the most money is left on the table. Not because the lines are tricky, but because the categorization upstream is messy. Get that right and the form fills itself.

In this guide we'll walk Lines 1 through 26 with concrete examples drawn from a real Hudson Valley host. We'll flag the four mistakes we see in nearly every file — mixed-use math, depreciation timing, supplies vs. repairs, and the cleaning fee that ends up in two places.

1. Rents received: what counts, what doesn't

Cleaning fees billed to guests are rental income, not pass-through. Cancellation fees retained are too. Refunds you issued are not — they should reduce gross rents, not show up as an expense.

The “small details” of Schedule E are not actually small — they are usually the difference between a $42,000 net and a $39,000 net.

2. Repairs vs. improvements

A new water heater is a repair if it replaces a broken one of similar quality; an improvement if it upgrades capacity. The first deducts this year. The second depreciates over 27.5 years. Hosteero proposes the right bucket from the receipt — and you can override it inline.

3. The cleaning fee problem

Most hosts double-count cleaning: once as rental income because guests paid for it on top of the nightly rate, and again as the bill they pay their cleaner. Those are two separate lines on Schedule E. Hosteero flags this in the inbox the day bookings sync.

Most hosts do not need more bookkeeping discipline. They need a smaller loop. Ninety seconds a day beats three hours on Sunday because the context is still fresh: the cleaner texted yesterday, the Home Depot run was obvious, and the guest refund is not a mystery yet.

The daily review is simple: open the inbox, approve the obvious transactions, flag anything that needs a receipt, and move on. The win is not that every line is perfect today. The win is that nothing sits long enough to become archeology.

Start with the auto-matches

Hosteero learns from prior approvals. If Lowe's was maintenance for Marigold Cottage last month, the next Lowe's charge should arrive with that suggestion already made. Approve the batch first. You get momentum and keep your attention for the weird stuff.

Then triage exceptions, not every transaction

Exceptions are the whole game: unknown merchants, split purchases, reimbursements, missing receipts, and expenses that belong to a different property than usual. Those get flagged, not solved under pressure.

A clean ledger is not built by one heroic catch-up. It is built by refusing to let small decisions pile up.

End by creating one rule

If you made the same decision twice, make it a rule. Merchant, account, property, and category are enough for Hosteero to handle the next one. The app gets quieter as your operation gets more predictable.

Occupancy is an operations metric. Rental-use percentage is a tax metric. They look similar enough to confuse people, and that is exactly where mistakes happen. A property can be 80% occupied and still only have 73% rental use once owner nights and personal holds are counted correctly.

This matters because some expenses may need allocation. Mortgage interest, insurance, utilities, supplies, and maintenance can all be affected depending on how the property was used during the year.

Separate available, booked, and personal days

A booked guest night is not the same as an available night, and neither is the same as a personal stay. Hosteero keeps those buckets visible so you can explain the math later instead of reconstructing it from calendar screenshots.

Owner holds deserve labels

A blocked weekend for repairs should not be treated like Thanksgiving with family. The calendar should know the difference. Labeling owner holds makes the year-end export less fragile.

The tax question is not “was it booked?” It is “what kind of use happened on that day?”

Make the ratio auditable

Your accountant does not need every operational detail. They need the ratio, the source, and the confidence that personal days were not quietly ignored. A clean Schedule E handoff includes all three.

Hosts already trust enough systems: booking platforms, cleaners, banks, locks, insurance, guests. Your bookkeeping app should not become another surface that can move money. Hosteero uses Plaid to read transactions, balances, and account metadata. That is enough.

We do not need transfer permissions to categorize a Home Depot charge. We do not need payment initiation to build a Schedule E preview. We do not need write access to tell you Capital One needs re-authentication.

Read-only keeps the blast radius small

If something goes wrong, the worst outcome should be missing or stale data, not money moving somewhere it should not. That principle shapes how we design banking, accountant access, and audit logs.

Accountants get visibility, not control

Read-only seats are for review, export, and notes. Your CPA can ask for context and inspect categorization history, but they do not need your bank login or payment permissions to do that work.

The safest financial workflow is the one that can explain your money without touching it.

Re-authentication is a feature, not a bug

Banks sometimes require a fresh connection. Hosteero surfaces that plainly instead of pretending sync is magic. If an account needs attention, you should see exactly which one and when it last synced.

Lena started with one carriage house and a spreadsheet named “Airbnb income final v7.” Two years later, there were three properties, two cleaners, one direct booking site, and no version of the spreadsheet that felt final anymore.

The problem was not volume. It was context. A $148 supply run means something different depending on which property needed towels, which cleaner requested them, and whether the purchase was reimbursable.

The portfolio view answered the first question

Before categorizing anything, Lena wanted to know which property needed attention. Hosteero's property cards made that visible: net income, pending reviews, occupancy, and recent activity in one glance.

Rules made repeat work disappear

Once the same cleaner was assigned to the same property twice, the third transaction arrived with a suggestion. Lena still reviewed it, but she stopped rebuilding the decision from scratch.

The dashboard became less about accounting and more about knowing where to look next.

One tab changed the handoff

At tax time, the export was not a folder of screenshots and guesses. It was a property-level ledger with notes, receipts, and the decisions that changed along the way.

Receipts fail when the ritual is too precious. If your system only works at your desk, it will fail in the parking lot, at the hardware store, and during the weekend you promised not to work.

The host-friendly version is fast: snap the receipt, attach it to the transaction, add one note if the purchase is weird, and let the inbox remind you only when proof is missing.

Capture before you categorize

Do not wait until you know the perfect category. A receipt photo is useful even before the bookkeeping decision is final. Categorization can be corrected; missing proof is harder to recover.

Use notes for exceptions only

“Towels for Marigold after guest stain” is worth a note. “Cleaning supplies” is usually not. Notes should explain the thing a future you would otherwise forget.

The best receipt system is boring enough that you actually use it.

Let missing receipts become a queue

Hosteero keeps receipt-needed items visible without turning the whole ledger red. That keeps the daily review calm and makes tax prep less dramatic.

Dark mode for bookkeeping is not just a color inversion. If the contrast is too hard, every number feels like an alarm. If it is too soft, the app becomes mush. We wanted Hosteero to feel like a quiet desk lamp: focused, warm, and easy to keep open.

That meant avoiding pure black, avoiding neon success states, and making sure the same hierarchy worked in both modes. The numbers should still lead. The cards should still breathe. Warnings should still be warnings.

The palette starts with paper

The light app uses warm paper and walnut. The dark app keeps the same family, just deeper: espresso backgrounds, cream text, muted gold accents, and enough border contrast to preserve structure.

States matter more than vibes

Approved, pending, needs receipt, excluded, reimbursable: these states have to be readable before they are pretty. Dark mode forced us to simplify the color system so every status has one job.

Calm software is not empty. It is opinionated about what deserves attention.

System mode should respect the system

Hosts move between desktop, phone, and late-night fixes. If the operating system says dark, Hosteero should follow unless the user explicitly chooses otherwise.