Skip to main content

Tax Managers

Compliance software for corporate tax managers: which returns each entity owes, who files them, where each period stands, and what evidence sits behind it.

Capabilities

What Lextree tracks for Tax Managers

  • Keep one register of every tax obligation the group's entities carry — what each entity owes, in which jurisdiction, how often, and which of those are the tax team's to file rather than someone else's
  • Record who is accountable for each obligation and who actually prepared a given period's return, so filing responsibility lives on the obligation itself instead of in one person's memory
  • See where every period stands in one pass — filed, accepted, rejected, or not yet filed — across the whole book of work a single tax manager answers for
  • Show what sits behind any filed period on the date someone asks: the entity, the jurisdiction, the period, who filed it, and the confirmation stored with the record
  • Hand an incoming preparer the current state of each obligation and the last period filed against it, instead of rebuilding that picture from folders and email threads at the start of an engagement
  • Add entities, jurisdictions, and tax types as the group grows, with every new obligation hanging off the legal entity that holds it rather than a new tab in a shared file

Answerable for Returns Someone Else Files

A corporate tax manager is answerable for the returns of nineteen entities filing in eleven jurisdictions. Two outside firms prepare most of them. One person is asked, in February, which of those returns are already out the door.

The honest answer usually lives in three places: an engagement letter, a controller’s close file, and an inbox thread from months ago naming who was supposed to follow up — none of which shows the whole book at a glance. The gap shows up at the worst moment: a lender’s diligence request, a new controller’s first week, a manager’s own return from leave, each one asking what the group owes and where each return stands. Rebuilding that picture from three sources costs a week nobody budgeted for.

Lextree is compliance software for corporate tax managers: one register for the obligation, the responsible filer, and the period status, so the answer never depends on who remembers what a particular engagement letter said.

The Department’s Book of Work

The department’s own inventory differs from a preparer’s engagement list or a controller’s close checklist. It counts standing obligations — a tax the group owes, in a jurisdiction, on a cadence, whether or not this period’s return has been touched — not filings currently in motion. No one outside the department counts it this way, so no one outside it knows the number.

A short exercise makes the gap concrete: counting the obligations a group actually carries, before assigning a single one to a preparer, usually turns up more standing obligations than the department’s own working list shows.

Prepared Outside, Owned Inside

Most descriptions of this problem miss the split: the firm preparing a return and the person accountable for it are not the same person. A firm can draft, review, and file a return and still not answer for whether it happened — that sits with the tax manager, regardless of who holds the pen.

Treating responsibility as a fact recorded against the obligation, not a note in an engagement letter, is what lets the tax manager answer for work performed somewhere else.

Questions From Outside Tax

Auditors, lenders, prospective buyers, and the company’s CFO ask questions with nothing to do with the mechanics of a return: is this entity current, who is responsible for it, and when did its status last change. None require reopening a filed return — they answer from responsibility and period status, once those live as recorded facts rather than being reassembled from memory.

That is also the records a diligence reviewer asks a tax manager for — not the return itself, but who owned what and when it changed.

Which Entity Owes What

A tax filing obligation is a standing fact about a legal entity: a tax type it owes, in a jurisdiction, on a recurring frequency, whether or not the current period’s return has been filed. Tax filing responsibility across entities usually rests with one person — the tax manager — who is accountable for knowing the obligation exists at all.

Obligations, Entity by Entity

Every obligation hangs off the legal entity that holds it, entity by entity rather than one undifferentiated pile of returns. Entity tax registration tracking belongs in that same record, beside the entity record each obligation hangs off, rather than in a separate system. The result is a register queryable by entity, jurisdiction, or tax type, rather than a stack of engagement letters sorted by year: where each tax obligation and its returns are tracked.

Naming the Responsible Filer

Who files each entity’s tax returns is a staffing fact, not a footnote in a shared drive. An internal team member, an outside firm, a payroll provider, or another service provider can each hold responsibility for a different obligation on the same entity — recorded like the obligation itself, answerable without a call to whoever set up the engagement.

When the Group Changes

An entity formed, newly qualified in a state, dissolved, or sold partway through the year opens or closes obligations on a timeline that rarely reaches the tax department first — the manager usually learns of it from a bank statement or a stray invoice.

Obligation count tends to track how filing volume grows with each subsidiary more directly than headcount — three new subsidiaries in a year can add more than three new obligations. A team with no system yet can start with a starter Excel workbook for teams without a system yet before outgrowing a shared file.

Where Each Period Stands

A tax manager needs one pass across the whole book: which periods are filed, which are accepted, which came back rejected, and which have no return recorded yet. That is the module those obligations and returns sit in, with the filed return and its confirmation held against the period record rather than a separate folder — so “do we have the confirmation for that one” has an answer without an inbox search. The Timeline records when each status changed, so a period’s history needs no asking whoever last touched it.

The returns themselves are still prepared where they have always been prepared — in the firm’s own return software or the department’s own workpapers. What Lextree holds is the obligation, the period, the responsible filer, and the confirmation that came back once a return was filed. Rules differ by jurisdiction and tax type; confirm each one with the tax authority. This page is general information, not legal or tax advice.

Two situations extend the same record rather than requiring a new one. An extended period is still an open period — it has picked up a later date. An examination notice on the tax manager’s desk lands on an entity and period that already exist in the record, not a file started from scratch. Both are handoffs made elsewhere: filings owed to agencies other than the tax authority sit alongside the same entities, and turning those obligations into dated work keeps either from surprising anyone.

What Changes Hands

Two handoffs mark the role: what an incoming preparer needs at engagement start, and what finance and legal need the rest of the year.

Onboarding an Outside Preparer

A new firm coming onto an engagement needs to know what already exists: the current state of each obligation, and the last period filed against it. Handing that over from memory means the new firm spends its first weeks rebuilding a picture the tax manager already had. How the obligation and the period record stay separate turns the handoff into handing over a record, not reconstructing one.

The controller needs to know, at close, which tax positions are settled and which are open — the finance side of the same obligations the tax manager already tracks, checked against the period’s own prepared statements rather than a carried-over number.

Legal needs to know when the entity record legal opens and closes creates or retires a tax obligation, since a dissolution or new qualification changes what the department owes. A separate register tracks renewals the entity owes to stay in good standing — adjacent to tax, owned by someone else, touching the same entity — and once a return is filed, the payment that settles it moves through the bank accounts and signatories treasury already tracks, a handoff the tax manager notes rather than runs. Each is a one-line handoff, not a module the tax manager runs.

One System the Tax Team Runs

Fragmentation costs the tax manager more than duplicate data entry: the one person answerable for the whole book is the last to learn something in it changed — an entity dissolved, a preparer swapped, a period gone quiet.

Start with the obligation register and the filing responsibility behind it — the two facts any tax obligation tracking software has to get right, and the two that answer what the group owes and who is filing it, without a round of emails. Expand into entity records, treasury, and financial statements as the group grows and the same tax manager answers for more of it.

The role rarely stands alone. The outside CPA firm doing this across client entities answers a version of the same question for every client at once, and a CFO who wants tax as one line in a wider view of exposure is asking the tax manager for exactly the status this register keeps. One system, run by the person already answerable for it — not rebuilt from three sources every time someone asks in February.

Trusted by

An established platform, not a new bet

15 years
In market
118 jurisdictions
Where customers operate

Built secure

The record auditors trust. Protected the way they expect.

Lextree is built for the people who lose sleep over compliance, so security isn’t optional.

  • Encrypted in transit and at rest

    Every byte that moves through Lextree travels over TLS 1.2 or higher, and the managed infrastructure it runs on encrypts stored data with AES-256.

  • Hosted in audited, SOC 2 facilities

    Lextree runs on infrastructure certified to SOC 2 Type II, hosted in ISO 27001 data centers.

  • Role-based access, scoped to your data

    Users see only what their role allows, and Lextree subscribers never see each other's data.

  • An automatic trail of every change

    Every create, update, and delete is logged automatically — in the same database transaction — with the user who made it, a timestamp, and the fields that changed.

  • Daily backups, point-in-time recovery

    Your data is backed up on managed infrastructure, with point-in-time recovery to roll back to a moment before a mistake.

  • Passwordless sign-in, SSO, and MFA

    Sign in without passwords — Lextree never stores one to be stolen — with multi-factor authentication available and SAML or OIDC single sign-on on Enterprise plans.

Read the full security overview →
Pricing

Every plan includes all 21 modules

Tiers add user limits, granular permissions, and enterprise controls. Modules stay constant.

  • Pro

    $75/ mo

    Includes 5 seats, then $15 / seat

    For teams moving off spreadsheets and scattered files.

    Start free trial →
  • Business

    $550/ mo

    Includes 5 seats, then $10 / seat

    For businesses that need collaboration, workflows, and reporting.

    Start free trial →
  • Enterprise

    $950/ mo

    Includes 5 seats, then $5 / seat

    For organizations with security, governance, and scale needs.

    Start free trial →

Stop managing compliance from memory.

Search