When the IRS and the City Disagree: Reconciling Schedule E Income With Local Registration Records

Most hosts think of "getting caught" as one event, an audit, a notice, an inspection. In reality, there are two entirely separate records of your STR income that rarely talk to each other, and a mismatch between them is one of the quieter ways hosts end up under review from a direction they never anticipated.

The Short Version

Your federal tax return reports rental income on Schedule E, based on your 1099-K and your own books. Your local tax office has its own separate record, built from your registration filings and, increasingly, from third-party monitoring software that tracks live listings against permit and tax databases. These two records were never designed to match automatically, and when they don't, either side can be the one that flags it.

How the Two Records Actually Diverge

The IRS side runs on income matching. Platforms issue Form 1099-K reporting gross booking revenue, and the IRS runs that figure against what you report on Schedule E. If the numbers don't reconcile, commonly because the 1099-K reflects gross revenue while your books reflect the net payout after platform fees and cleaning charges were deducted, the mismatch can trigger an automated CP2000 notice. This isn't usually about STR-specific rules; it's the same income-matching system the IRS runs on any 1099. The fix is procedural: report the gross figure on Schedule E and deduct platform fees separately as an expense, rather than only reporting what actually hit your bank account.

The local side runs differently, and it's less forgiving of a mismatch. Many cities and counties now use third-party STR monitoring platforms tools built specifically to scrape live listings, cross-reference the address against permit and tax registration records, and flag any property that's operating without matching paperwork on file. These systems don't need your tax return to notice a discrepancy; they compare what's publicly advertised against what's registered, and gaps between the two are exactly what they're designed to surface. One municipality using this kind of system reported a multi-million-dollar increase in collected lodging tax revenue in its first year, largely by closing the gap between listings that existed and taxes that were actually being filed.

Here's where the two systems can actually cross paths: a rental license or registration is a public or semi-public record in most jurisdictions. If a taxing authority, such as federal, state, or local authority has reason to believe a property is operating and generating income, the existence of a local permit or registration is itself a data point. An investor holding a visible STR license with no matching income reported anywhere is a mismatch that doesn't require an audit to notice; it's a pattern automated systems are increasingly built to catch on their own.

Where Hosts Usually Go Wrong

• Reporting net payouts instead of gross revenue on Schedule EL: The 1099-K shows gross; your Schedule E needs to show the same gross figure, with platform fees deducted as a separate expense line, and not simply the number that landed in your account.
• Assuming local registration and federal filing are reconciled automatically: They aren't connected systems. Keeping one current says nothing about the other.
• Not realizing local governments actively cross-reference listings against registrations: Monitoring software doesn't wait for a complaint, it's built to compare public listing data against registration databases continuously.
• Treating a clean Schedule E as proof nothing else needs attention: An accurate federal filing is only one half of the record; the local registration and lodging tax side is tracked entirely separately.
• Registering locally but underreporting federally, or vice versa: Either direction of mismatch creates exposure and a visible local permit with no matching federal income, or federal income with no corresponding local registration, are both patterns that draw scrutiny from their respective side.

Your Action Checklist

• Confirm your Schedule E reports gross 1099-K revenue, with platform fees and commissions deducted separately as expenses
• Cross-check that every jurisdiction where you're registered locally matches a property you're also reporting income for federally
• Check whether your city or county uses third-party STR monitoring software, and if so, confirm your listing address matches your registration exactly
• Reconcile 1099-K totals against your own booking records before filing, rather than after a CP2000 notice arrives
• Keep documentation, permits, tax filings, and income records, organized by property and by year, so a mismatch on either side can be explained quickly
• If you hold a license in a jurisdiction where you're not actively renting, confirm whether it needs to be closed out rather than left dormant and visible

Federal reconciliation and local registration are two different jobs, and most hosts are only actively managing one of them at a time. Lodge Compliance handles the local side of registrations, filings, and keeping your record clean against what monitoring software will find, so it's never the side of the mismatch that catches you off guard.

Reach out to a property compliance expert at lodgecompliance.com to prevent fines and other reporting surprises.

Neither system is watching for you specifically, but neither one needs to, when the mismatch is sitting in public records for anyone to cross-reference.

This article is for general informational purposes and isn't legal, tax, or financial advice. Reporting requirements and enforcement practices vary by jurisdiction and change over time — confirm current rules with the IRS, your local tax authority, or a qualified professional before relying on them