AI tax preparation in Poland: PIT, VAT and ZUS for sole traders

AI helps prepare taxes for a Polish sole trader by organising records and suggesting how to classify transactions. Accounting software then uses those records and business settings to calculate PIT, VAT and ZUS contributions. You review the inputs and results. Filing returns and making payments are subsequent actions, each with its own confirmation.

The practical benefit comes from moving information between records, ledgers and reports without repeatedly entering it. You still need to answer three questions: where did this amount come from, what is missing, and what remains to be done? This guide follows that process for a Polish sole proprietorship, known as a JDG, with examples from Norman. ZUS covers insurance contributions, which we discuss alongside taxes as a separate obligation.

What does AI tax preparation actually involve?

Preparation includes collecting information, assigning transaction categories, calculating amounts and presenting the results for review. An assistant can help explain individual steps. The final amount should be traceable to business records and applicable rules, with a route back to the entries behind it.

When evaluating AI accounting in Poland, check whether asking “where did this tax advance come from?” leads to revenue, deductible costs, contributions and earlier periods. An explanation without those inputs is insufficient to verify the result. If you are choosing software, start with our AI bookkeeping tests for Polish sole traders.

Automation should shorten the path from records to a reviewed report. Do not assume that a language model performs every step or that every AI response changes the ledger. Establish when you are looking at a suggestion, a recorded entry or a document prepared for submission.

What business information is needed first?

Confirm your income tax regime, VAT status, reporting frequency and ZUS profile. The progressive tax scale, flat income tax and revenue-based ryczałt require different calculations. Settings for a Polish limited company, a sp. z o.o., cannot replace those for a JDG. Your bank balance alone is also insufficient.

In Norman, these details sit under Account → Taxes. They should match your actual business circumstances. Changing a setting in the application does not notify the tax office, CEIDG business register or ZUS. See the tax settings guide for the available options and their effect on reports.

If you move your bookkeeping during the year, check the cumulative figures from previous months. Missing revenue, costs or earlier advances can change the result even when the current month is complete. Identify the figures to carry over and compare them with your previous records. Clarify an unusual insurance situation with an accountant before preparing ZUS documents.

How do records become calculation inputs?

Review transactions for the relevant period before assessing the tax result. Check that revenue is complete, expenses have appropriate categories and paid contributions are recognised. Separate business and personal spending. For an unclear purchase, record its business purpose and establish the treatment instead of accepting a category solely because the software suggested it.

In Norman, unreviewed transactions can already affect a calculation. A warning about transactions awaiting review does not mean their amounts have been excluded. Open the listed entries, correct the data and inspect the report again. The transaction review guide explains where to check categories, VAT treatment and supporting documents.

Do not use the bank balance as the tax base. A receipt of money, taxable revenue and an outstanding customer balance describe different things. Likewise, a payment to the tax office does not become another deductible business expense simply because it reduced the bank balance. Correctly connecting records prevents calculations based on the wrong total.

How is the PIT advance prepared?

Under the progressive scale and flat income tax, revenue and tax-deductible costs are starting inputs. Under ryczałt, ordinary business costs do not reduce taxable revenue, as explained by the Polish Ministry of Finance in its ryczałt guidance. The tax regime must therefore be established before the software uses the collected figures.

Norman prepares the advance using the KPiR income and expense ledger or revenue register, relevant transactions and contributions, and figures from earlier periods. For the progressive scale and flat income tax, review the cumulative calculation from the start of the year and the earlier advances due that it accounts for. Comparing the result with a percentage of last month's revenue is not enough.

Open the PIT advance breakdown and compare its inputs with the records. Resolve missing information before paying. Biznes.gov.pl also explains advances under the progressive tax scale. An advance payment and an annual PIT return are separate parts of income tax compliance.

What does the software prepare for VAT and ZUS?

VAT requires a separate review of sales, purchases and entitlement to deduct input VAT. A deductible cost for PIT does not automatically establish VAT deductibility. For an active VAT taxpayer, JPK_V7 combines VAT records with a declaration component. The Ministry of Finance describes its scope and monthly and quarterly variants.

In Norman, open the JPK_V7 period, prepare current data, resolve flagged issues and review the breakdown. Regenerate the report after correcting transactions. The JPK_V7 approval guide takes you from the underlying data to choosing a filing authorisation method. Approval alone does not send the file.

ZUS depends on your insurance profile and the health contribution rules for your tax regime, among other factors. Do not derive every contribution from one profit figure: ZUS explains differences in the health contribution basis. Norman prepares DRA as a KEDU file. Download it, review it and submit through eZUS or Płatnik, following the ZUS contributions and DRA guide.

Example: from monthly records to a reviewed result

Suppose an example sole trader using the progressive tax scale has PLN 18,000 of taxable revenue and PLN 3,000 of correctly recognised deductible costs in the month under review. These fictional figures illustrate the workflow. Their difference is PLN 15,000 before further calculation elements. This is neither the tax payable nor the complete basis for the year-to-date advance calculation.

First, compare both totals with the ledger entries. Then check earlier months, contributions and other required inputs. Only then assess the calculated advance. Review VAT in its own registers and ZUS against the relevant profile and calculation basis. One revenue-minus-costs figure cannot replace all three calculations.

If the tax amount is higher than last month, begin with changes in revenue, costs and cumulative figures. Record the explanation and any correction needed. After changing a category, make sure you are reviewing the current report rather than an earlier downloaded file. This makes the result traceable without guessing whether AI calculated it correctly.

What happens after the calculation is prepared?

You need separate evidence for each completed stage. The following distinction reflects Norman's public documentation checked on 2 November 2026.

Annual reporting requires an additional review of the full year. Complete monthly summaries do not establish that all reliefs, other income or payments have been accounted for. Check the scope and limitations of annual PIT in Norman.

After filing JPK, check the submission status and UPO acknowledgement. Separately initiate the required transfers using the tax and ZUS payment details. Manually marking an amount as paid organises its application status; look in your bank for confirmation that the transfer was executed.

Start with one reporting period: confirm settings, review transactions, open the calculations, then proceed to filing and payment. This is a practical way to use Norman AI accounting while keeping every amount explainable.