Certified billing software with hash-chained, tamper-evident records.
The open source tax stack.
Not just a directory — a map. What open source covers in tax, organized by the problems tax teams actually face: mandates to meet, AI to deploy without data leaving the building, tax to compute, returns to file, and law to understand.
I lead a tax function
Your next board question is on this page: the compliance calendar, and an AI plan that keeps data in-house.
I advise clients
What's filable with open tools today, what each mandate changes, and how to judge a tool before relying on it.
I build software
Engines with inspectable rules, law as data, and the compliance plumbing you'd rather not write twice.
The compliance calendar
The mandates redrawing tax operations, and where each one stands. Every entry links to the open tooling for that jurisdiction.
All B2B invoices clear through the national KSeF platform.
Quarterly digital records and filing through recognised software.
Structured invoices via accredited platforms (PDP), Factur-X among the formats.
B2B structured invoicing (XRechnung/ZUGFeRD); receiving is already mandatory.
The largest consumption-tax rewrite in decades, on top of NF-e rails.
EN 16931 e-invoicing and digital reporting across all member states.
Meet a mandate
Governments are rewiring tax compliance around real-time, structured data — e-invoicing clearance, digital reporting, certified billing software. This is the decade's compliance story, and much of the plumbing that meets it is open: invoice format libraries, VAT validation, and reporting standards you can read, audit, and embed.
Open source fits the format and transmission layer — the mandate logic itself. It won't give you the surrounding workflow, archiving, or liability cover a vendor contracts for.
Compliant invoices: Peppol, UBL, ZUGFeRD/Factur-X, and clearance.
Indirect tax: rates, number validation, calculation, and returns.
Regulatory filings and standards: SAF-T, CbC, DAC7, FATCA/CRS.
Put AI to work — without shipping your data away
Every tax leader is being asked for an AI plan. The open-source answer has a structural advantage the vendors can't match: tools your team runs on infrastructure you control, so client data and filings never leave the building. MCP servers give AI agents governed access to tax systems; skills and local models make the workflows portable and private.
Open source fits experimentation and data-sensitive deployment. It doesn't fit teams with nobody to run it — hosted AI with a data-processing agreement may serve them better.
Full tax AI assistants, copilots, and workpaper workbenches.
Skill packs, plugins, and portable workflows for AI agents.
Model Context Protocol servers exposing tax data and tools.
Models, pipelines, and applications for tax language.
Embeddings, retrieval pipelines, and RAG over tax corpora.
AI that runs on your own machine. No cloud, no data leaving the building.
Compute it right
Tax logic in a spreadsheet is a liability; tax logic in a black-box SaaS is a dependency. The middle path is tax law as inspectable code — engines and rules-as-code frameworks where every rate, threshold, and rule is visible, versioned, and testable. Several national administrations already work this way.
Open source fits when correctness must be auditable — you can read the rule that produced the number. It doesn't fit if nobody owns keeping the rules current when the law changes.
Libraries and engines that compute tax, embeddable anywhere.
Tax law as executable code: statutes and benefit rules you can run.
Payroll taxes, social contributions, and withholding calculation.
File and prepare
The most visible layer, and the most uneven. The United States has the IRS's own Direct File in the open; crypto cost-basis tooling is genuinely strong everywhere; but in much of Europe consumer filing stops at closed government APIs. What exists is here — including the accounting layer underneath it.
Open source fits preparation, calculation, and crypto reporting today. Actual submission depends on the jurisdiction — where filing channels are closed, no license can open them.
Preparing and e-filing individual and business tax returns.
Crypto tax, portfolio accounting, and capital gains calculators.
Ledgers, ERPs, and bookkeeping tools with tax features built in.
Understand and shape the law
Tax law as data: statute corpora, rate scrapers, microsimulation models that score reform proposals, and the benchmarks that measure whether AI actually understands any of it. This is where policy teams, researchers, and the serious end of tax AI meet.
Open source fits research and policy analysis outright — the transparency is the point. Treat community-maintained legal corpora as a starting point, not as advice.
Scrapers, APIs, and corpora of tax law, rulings, rates, and forms.
Tax-benefit microsimulation and policy analysis models.
Cross-border taxation, treaties, and transfer pricing tooling.
Evaluation suites and datasets for tax-domain systems.
Awesome lists and landscape maps of the tax tech ecosystem.
How to evaluate open-source tax software
Four questions before you rely on anything in this index — each one answerable from signals shown on every listing.
License
Every listing shows its license. Permissive (MIT, Apache-2.0) embeds anywhere; copyleft (GPL, AGPL) obliges you to share changes — fine for internal use, a real decision for products.
Maintenance
The colored pill on every card reads the repository's pulse: Active (pushed within a month), Maintained (six months), Quiet, Stale. Tax tools live on annual cycles — Quiet isn't dead, but Stale code meets this year's law at your risk.
Coverage
Tax software doesn't travel. Check the jurisdiction and tax-subject tags before anything else — a brilliant German ELSTER library is worth nothing in Madrid.
Who maintains it
A tax authority (IRS, Polish Ministry of Finance), a company with a business on top, or a lone maintainer — each is a different risk profile. Claimed projects here are verifiably run by their maintainers.