The White List and Split Payment — When MPP Is Mandatory, and When to Use It More Widely

Two rules decide how a Polish company pays an invoice over 15,000 zł. They share that number and nothing else. Treat them as one rule and you end up perfectly compliant with the wrong one.

The first asks who you are paying: is the bank account on the register of VAT taxpayers on the day the transfer leaves your bank. The second asks what you bought: is there anything from załącznik nr 15 on the invoice, because then the payment has to be split.

They touch at exactly one point, and that point is why I am writing this. Paying in split payment also kills the white-list penalty. Which makes MPP the cheapest insurance in the Polish payment process — and it still is not free, for reasons that have nothing to do with tax and everything to do with cash.

The two conditions, and why both matter

Mandatory split payment needs both of these true at the same time:

• the invoice total is 15,000 zł gross or more, and
• at least one line comes from załącznik nr 15 to the VAT Act.

The annex is a long PKWiU list. In practice it clusters into groups worth knowing by name: steel and metal products, fuel, coal, electronics — phones, laptops, processors, consoles, hard drives — car parts, waste and scrap, and most construction and installation services. Check the annex against your own PKWiU codes rather than trusting anyone's summary. Mine included.

Then the mechanical conditions: both parties are businesses, the payment is in PLN, and it runs through a Polish settlement account with its attached VAT account. A euro transfer to a German supplier sits outside the regime completely, whatever the invoice says.

Now look at what the threshold is measured on. The whole invoice, not the annex-15 line. A 15,400 zł invoice with one 300 zł item from the annex is a mandatory-MPP invoice. The split itself covers the VAT on the annex items, but the trigger is the total. This is the case firms get wrong again and again, because the annex item is trivial and nobody reads past it.

The overlap almost nobody uses deliberately

Here is the connection that turns two chores into one decision.

Pay an invoice of 15,000 zł or more into an account that is not on the register and two things follow. That payment stops being a deductible cost, and you become jointly liable for the VAT your supplier does not pay. I put numbers on it in the post on when a contractor check actually counts — around 21,000 zł of exposure on a single 61,500 zł transfer.

Settle that same payment through split payment and both consequences disappear.

Sit with that for a second. The white-list obligation has two escape hatches, not one. ZAW-NR works after the fact and gives you seven days to spot a problem you did not know you had. Split payment works at the moment of transfer and needs nobody to spot anything.

One is a fire extinguisher. The other is not leaving the pan on the hob.

What MPP will not do: turn a fake contractor into a real one, replace due diligence, or help you with foreign-currency payments and foreign accounts. It protects one payment against one specific pair of consequences. That is the whole of it — and it is enough to change how you build the payment run.

The cost nobody puts in the pitch

If split payment removed risk for free, this article would end here. It does not.

Pay in MPP and the VAT portion lands on your supplier's VAT account instead of their operating one. Get paid in MPP and the same happens to you. Money sitting on a VAT account is yours, but you can spend it on a short list of tax obligations — not on rent, salaries or stock.

To move it to your current account you file an application with the tax office, and the decision can take up to 60 days. Nothing goes wrong in that process. It is just slow, and slow is a liquidity cost.

So the honest version of "just pay everything in MPP" goes like this. For a firm with a cash buffer it is close to free and removes a real risk. For a firm paying wages out of receivables, a growing balance on the VAT account is a problem arriving quietly. That is a treasury decision, not a compliance one — which is why I do not hand the advice out in bulk.

The seller's half, which is where the errors start

Everything above is the buyer's side. The seller carries a separate duty on the same transaction: an invoice meeting both conditions must carry the annotation mechanizm podzielonej płatności. Miss it and there is an additional tax liability calculated on the VAT of the annex-15 items — which falls away if the buyer settled in split payment anyway.

Two things follow. Both are worth putting on a wall.

First, on the sales side, someone is making a per-invoice classification decision while issuing the document, usually at speed. The wholesaler selling both car parts and cleaning supplies has annex and non-annex items in the same order. The trigger depends on the total and on one line item's PKWiU.

Second, on the purchase side: a missing annotation is not your defence. If the invoice meets both conditions, the payment goes out split whether or not your supplier marked it. So the check has to live in your payment process, not in how carefully somebody reads a supplier's invoice layout.

What can be automated, and what the agent actually watches

Almost none of this is judgement. It is matching data that already sits in the ERP against a list, on a schedule nobody keeps reliably at month-end.

A document agent working on an enova365, Optima or Symfonia setup can do all of this, as drafts and alerts:

• Tag annex-15 items in the product catalogue once, then flag every incoming and outgoing invoice where an annex line meets the total threshold.
• Build the payment run with both checks done on the same day — register status for the account, MPP flag for the invoice — so the two rules stop being handled by two people a fortnight apart.
• Catch unmarked purchase invoices that should have been marked. Before the transfer, not during a tax audit.
• Watch the VAT account balance and warn when locked cash crosses a level you set. This is what turns "MPP on everything" from a slogan into a policy somebody actually manages.
• Run the seven-day ZAW-NR clock when a payment did go to an off-register account.

Same rule as with every agent I build for accounting offices: it prepares and warns, a named person decides. On the reconciliation side it slots into the work I described in automating bank statement posting, because a split payment arrives as a transaction with two amounts and matches badly if nobody taught the matcher about it.

What stays with a person

Classifying a borderline PKWiU item. Deciding whether to pay voluntarily in MPP when liquidity is tight. Applying for the release of VAT-account funds and judging whether the wait is worth it. Telling a supplier their invoice is marked wrongly. Choosing not to pay at all.

Any agent sold to you as handling one of those five is being sold dishonestly.

When to build nothing

If you never buy or sell anything from the annex and your over-threshold transfers are rare, buy nothing. Set voluntary split payment as the default for PLN transfers over 15,000 zł, check the VAT account balance once a month, and you have removed most of the exposure in this article for the price of one decision.

Need occasional register checks with the evidence stored? KsięgoAI does that per NIP for 39 zł per 30 checks, no integration project. The volume at which a built agent starts to pay for itself is the arithmetic in what an accounting AI agent costs — document count, not enthusiasm. Split payment handling is not a project on its own. It is a module you bolt onto an intake or reconciliation agent that is already running, and there it costs next to nothing extra.

One number to measure this week: take last month's PLN payments over 15,000 zł and work out what share went out as split payment. Then look at today's VAT account balance. The first number tells you how much risk you are carrying for free. The second tells you what protecting yourself further would cost. Most firms have never seen the two side by side, and the decision makes itself once they do.

Want to know how this would attach to your ERP, and how much of your payment run it would cover? Get in touch — scoping is free and takes half an hour.