Business Process Consultant, Poland

How national e-invoicing reshapes the purchasing process

Purchase invoices in Poland long followed a familiar path: invoices arrived by email or post, someone checked them against an order, and a wrong invoice went back to the supplier. With KSeF, structured invoices are issued into a national system, and the buyer retrieves them from there. The rollout has been reshaped more than once, so applicability to your business is something to settle with your tax advisor.

The process questions are concrete:

• Who retrieves incoming invoices, and how often?
• How is each invoice assigned to the right person or cost center when it no longer arrives in their inbox?
• What happens when an invoice is wrong? Since a document in the national system cannot simply be sent back, the route is usually a request to the supplier for a correcting invoice, tracked until it arrives.
• How are invoices from suppliers outside the system, such as foreign vendors, handled alongside?

I map today's process from real documents, then design the future one with owners for retrieval, assignment, matching, disputes and approval. The point is not the technology; it is making sure nobody assumes someone else is watching. My wider business process consulting service explains the mapping method in full.

White-list checks and split payment inside the payment run

Polish payment processes carry checks that many foreign parents do not expect. Before paying a supplier, companies commonly verify that the bank account appears on the official list of VAT taxpayers, since paying to an account not on that list can have tax consequences above certain amounts. Some invoices also require, or benefit from, payment through the split payment mechanism. The rules come from your tax advisor; the process exists so they are applied on every run.

The payment run I design follows a fixed order:

1. Approved invoices are selected for payment by due date and cash plan.
2. Each supplier account is checked against the list, and the result is recorded.
3. Invoices that need split payment are flagged with the right data.
4. Exceptions, such as an account not on the list, go to a named person with a defined set of options.
5. The payment file is prepared by one person and released by others with the right authority.

Changed supplier bank details get their own step: confirmation through a known contact and approval by someone other than the requester. Payments in foreign currency and to foreign suppliers are mapped as variants, since the list check applies differently. Translating these controls into specification lines for software is handled under my Polish ERP business analyst service.

Board representation, approval limits and sales

Polish companies define in their articles and the commercial register who may represent them, and joint representation by board members is common. Representation and internal sign-off are separate things, and mixing them up breeds either queues or holes in control. A procurement manager may need to approve routine orders without being a board member, while a significant contract still needs the signatures the articles require.

I write the approval matrix to sit alongside those rules: limits by amount, cost center and entity, deputies for absences and a clear escalation for anything above the limits. Your legal advisor confirms the representation side; I make sure the daily process respects it.

On the sales side, the order-to-cash map follows the order from quotation to collection:

• Customer data checked against public registers when the account is opened.
• Orders confirmed, delivered and invoiced, with the invoice issued through the national system where applicable.
• Payments matched, including split payments landing on the VAT account.
• Reminders and decisions on credit holds assigned to named people.

Design choices for routing sign-offs are discussed at length under ERP approval workflows.

JPK, the local close and the group

Many companies in Poland belong to foreign groups or run shared service centers serving entities abroad. Their record-to-report process has two audiences: Polish statutory and tax obligations, and the group's reporting calendar. The two often compete for the same people in the same days.

I map the close so both are visible. Which reconciliations happen first, how exchange rates are applied in line with your accountant's guidance, how intercompany balances are agreed, which group reports are due and how the JPK files are reviewed before submission. Since JPK quality depends on postings and master data throughout the month, I also mark the upstream steps that feed it, such as correct tax codes on purchase invoices, and give each one an owner.

Hire to pay usually involves an outside payroll provider or a local accounting office. I chart how starters, leavers, contract amendments, sick leave and bonuses travel to that provider and how the posting file returns. Personal data passes through these steps, so the map marks where it goes and who sees it, giving your data protection advisor a concrete basis for a review under GDPR and Polish law.

For multi-entity designs, my multi-company ERP page covers the options.

From agreed process to system decisions

Polish subsidiaries often face a specific question: should they run the parent's ERP template, a Polish system or a mix? Answering it without an agreed process tends to turn into a debate about software. With process maps in hand, the conversation changes. The group can see which steps are standard, which local steps the law requires and which local habits could simply be dropped.

The handover pack holds both sets of maps, a prioritized problem list, the sign-off thresholds, the ordered payment checks, the supplier dispute path, agreements with outside advisors and role-by-role instructions. Everything is in editable form and stays with you. The engagement runs in English, and keeping the Polish instructions aligned with the English reference is a job for your staff or a partner in Poland.

Then software returns to the agenda. Sometimes better setup of the current system is enough. In other cases they feed a formal platform comparison through my Polish ERP selection service, with the Poland ERP consultant page describing the wider advisory role. Steps that turn out to be repetitive and rule-based lead into my Polish business automation work. The Poland hub lists the remaining services.