How to structure a tax knowledge base for sellers

Why a tax knowledge base

An e-commerce seller trading in Europe quickly accumulates a considerable amount of tax information: rates by country, filing deadlines, onboarding procedures for new marketplaces, operational instructions for the accountant. Without a structure, this information scatters across emails, spreadsheets and messy desktop folders.

A well-structured tax knowledge base helps you:

• avoid re-explaining the same things to your accountant every quarter;
• reduce operational errors (missed deadlines, wrong rates);
• speed up onboarding when adding a new channel or marketplace;
• have a single point of reference in case of a tax audit.

The three levels of a tax knowledge base

An effective structure is organised across three distinct levels:

Level 1 — Regulatory references Stable documents that rarely change: EU VAT rates by country, OSS thresholds, rules on foreign VAT numbers, document retention periods. These need updating once a year or when new regulations come out.

Level 2 — Operational procedures Step-by-step instructions for recurring tasks: how to import the VAT Transaction Report from Amazon, how to aggregate data for the quarterly OSS return, how to prepare the folder for your accountant. These procedures are the heart of the knowledge base.

Level 3 — Log and historical decisions A record of choices made over time: why you decided not to register in Poland, when you first crossed the OSS threshold, what agreements you have with your accountant. This level is valuable in case of an audit years later.

Recommended minimal structure

Even a simple knowledge base, maintained with discipline, is worth more than an elaborate system abandoned after two weeks. A functional minimal structure:

/tax
  /references
    eu-vat-rates-[year].pdf
    oss-thresholds-[year].md
    foreign-vat-numbers.md
  /procedures
    import-amazon-vat-report.md
    quarterly-oss-aggregation.md
    accountant-handover.md
  /log
    tax-decisions.md
    historical-deadlines.md
  /archive
    /2024
    /2025
    /2026

Every procedure file should include: purpose, frequency, ordered steps, expected output and links to the tools used.

What to include in operational procedures

A useful operational procedure answers these questions:

• Who carries it out (you, your accountant, a collaborator)?
• When is it carried out (end of month, end of quarter, once a year)?
• What is needed as input (files, credentials, data)?
• What steps, in order?
• What’s the expected output (file, report, email)?
• What to do if something goes wrong (missing file, import error)?

Without answering these questions, a procedure is just a title with no operational value.

Maintenance and updates

A knowledge base ages quickly if it isn’t maintained. The minimum rules to keep it alive:

• Annual review of regulatory references: rates, thresholds, deadlines change;
• Immediate update of procedures when a tool or process changes (e.g. Amazon changes the VAT Report format);
• Decision log updated every time you make a relevant tax choice;
• Last-modified date visible on every document, so you can tell at a glance what’s up to date.

How VATManager fits into this workflow

VATManager doesn’t replace the knowledge base: it feeds it. The reports generated by the platform become documented outputs of the operational procedures. Per-country aggregations, import logs and accountant reports can be archived directly into the /archive/[year] structure, with clear traceability of what was declared and when.

The knowledge base provides the context; VATManager provides the processed data. Together they make the tax process repeatable and verifiable.

📎 Learn more: E-commerce VAT software — 2025 comparison — VATManager onboarding checklist for new sellers — How to prepare your accountant for the OSS return