<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Taxes on Lextree AI</title><link>https://lextree.ai/resources/topics/taxes/</link><description>Recent content in Taxes on Lextree AI</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 20 Sep 2026 20:29:21 -0700</lastBuildDate><atom:link href="https://lextree.ai/resources/topics/taxes/index.xml" rel="self" type="application/rss+xml"/><item><title>Tracking Tax Filings Across Multiple Entities and Jurisdictions</title><link>https://lextree.ai/resources/tax-filing-evidence-tracker/</link><pubDate>Sun, 20 Sep 2026 20:29:21 -0700</pubDate><guid>https://lextree.ai/resources/tax-filing-evidence-tracker/</guid><description>&lt;h2 id="what-stays-true-between-periods"&gt;What stays true between periods&lt;/h2&gt;&#10;&lt;p&gt;Tracking tax filings across multiple entities and jurisdictions rests on three records: a recurring obligation for each entity, jurisdiction, and tax type; a return record for what was filed each period; and payment evidence for what was paid. Multi-entity tax filing records work when those three stay separate and joined by a shared reference.&lt;/p&gt;&#10;&lt;h3 id="what-the-obligation-record-holds"&gt;What the obligation record holds&lt;/h3&gt;&#10;&lt;p&gt;An obligation row is keyed to the entity, the jurisdiction, and the tax type — not to the entity alone. A group of three entities can still produce four obligation rows. An entity filing both an income tax and a payroll tax in the same jurisdiction needs two rows, not one. Collapsing them into an entity-level row is the miscount that breaks most trackers before they start.&lt;/p&gt;</description></item></channel></rss>