E-Invoice Finder
Menu
Countries Compare software Deadlines Guides Checker Check obligation
ENFRDEPLNL
Poland · AP and employee-expense controls

KSeF no-PO and employee-purchase exception workflow

Route KSeF invoices without purchase orders and employee purchases using buyer checks, Podmiot3 role 11, matching, approvals and duplicate controls.

Quick verdict:
  • Scope: separate supplier, personal-payment and card transactions before any release.
  • Biggest risk: the same purchase is paid through two operational channels.
  • First action: publish buyer details and appoint an owner for each exception queue.
Get Poland readiness reportOfficial sources
Last checked: 7 August 2026Based on official sourcesClear summaryBusiness guidance, not legal advice
Official sources prioritized
Last-checked dates visible
Free checker, no signup required

What you need to know

Guide

Triage three routes before approval

Create three separate queues. Route a supplier invoice addressed to the company but lacking a purchase order to no-PO AP. Route an employee-paid purchase to expenses for reimbursement review, and a corporate-card purchase to card reconciliation. KSeF officially issues, receives and stores structured invoices; it does not perform internal purchase approval. Recommended control: AP checks the KSeF number, buyer NIP, supplier, amount and route within one business day, then assigns an owner. For example, an unplanned PLN 2,400 repair goes to the facilities budget owner, while a personally paid PLN 180 taxi goes to travel expenses. The major risk is processing one document through AP and expenses or card reconciliation, creating supplier payment and employee reimbursement. Route status should be exclusive and searchable by KSeF number.

Guide

Use FA(3) employee identification without changing the buyer

Official fact: FA(3), applicable from 1 February 2026, allows employee data in Podmiot3 with role 11, “Pracownik”, where the employer is the buyer. This can help find the invoice among incoming KSeF records. It is an identification aid, not KSeF approval, and official guidance does not make role 11 universal for every employee-related invoice. The employer remains the buyer, so its correct name, NIP and buyer data matter. Naming an employee does not turn a consumer purchase into a company invoice, establish business purpose or determine VAT deductibility. Recommended control: give staff a purchasing card with legal buyer details and, where supported, request role 11 plus the company-defined employee identifier. Never infer buyer identity from the employee name alone; refer uncertain VAT, reimbursement and correction questions to accounting or tax advisers.

Guide

Standardise intake and employee instructions

Before purchase, give employees the company legal name and NIP and require a cost centre, business purpose, payment method and permitted employee reference. Afterwards, collect the KSeF number when available, supplier, date, amount, project, proof of personal payment for reimbursement, and relevant travel or receipt evidence. A PDF or emailed copy is not a second invoice; use the KSeF number as the official incoming identity where available. Receipts, approvals and travel records may remain in an expense or DMS system and should be linked, not described as automatically embedded in KSeF. A formal KSeF invoice attachment is different and follows official scope and rules. Recommended service level: employees submit claims within five working days; expenses return incomplete claims within two. Reject a claim with no buyer check rather than converting a retail receipt into business evidence, and preserve every follow-up.

Guide

Approve and match no-PO supplier invoices

A no-PO invoice needs an exception path, not an invented order. AP validates identity, supplier master data, arithmetic, KSeF number and duplicate status. The requester confirms what was ordered; the service owner confirms delivery; the budget owner supplies coding and business purpose; procurement reviews policy breaches; finance releases payment after approval. PO number, cost centre, service receipt and business purpose are recommended internal fields, not statutory KSeF rules. For an emergency repair, retain the call-out request, completion note, asset identifier and manager approval. Set thresholds, such as two approvals above PLN 10,000 and procurement review for every uncontracted supplier, according to policy. KSeF receipt proves neither authorisation nor delivery, correct coding, payability or reimbursement entitlement. Escalate unresolved ownership after three business days and hold payment rather than allowing an inbox to become approval.

Guide

Prevent duplicate employee reimbursement

Match each claim against KSeF and AP using KSeF number first, then supplier NIP, invoice number, amount, date, employee and card line. Require evidence that the employee paid. The expense approver assesses policy and business purpose; accounting assesses buyer identity, posting and tax treatment; treasury reimburses only after a duplicate check. Example: an employee submits a hotel PDF while its structured invoice awaits supplier payment. Mark the case employee-paid or supplier-payable, never both, and retain a cross-reference in the closed route. A receipt or PDF may support a claim but does not prove that the company is the buyer or VAT is deductible. Recommended metric: 100% of reimbursements above the company threshold matched to payment evidence and searched against KSeF and AP before release. Seek professional advice for edge cases.

Guide

Reconcile corporate-card purchases independently

A corporate-card transaction is not an employee reimbursement and needs its own queue. Import the card line, match it to KSeF where available, and link cardholder, merchant, date, amount, currency, cost centre, business purpose and approver. The cardholder confirms the purchase; the manager confirms policy and benefit; accounting checks buyer data and posting; the card administrator resolves missing evidence or disputes. Use tolerance rules cautiously—for example, exact currency and amount unless a documented foreign-exchange policy applies. Close the AP payment route when the merchant was paid by card, while retaining the KSeF record for accounting. Report unmatched lines after five working days. This matching control is operational, not a KSeF requirement. It addresses the risk that an invoice is paid again because it also appears in the supplier inbox.

Guide

Handle wrong buyer data, corrections and exceptions

If the buyer name or NIP appears wrong, quarantine the invoice from posting, payment and reimbursement. AP records the reason and contacts the supplier; accounting determines buyer identity and whether supplier correction is required. Never edit or delete an accepted KSeF invoice. Preserve its identity and audit trail, link any correction, and follow current official rules plus professional advice. Podmiot3 role 11 cannot repair an incorrect buyer; lacking that role does not automatically invalidate correct buyer details. Use exception codes for wrong buyer, unknown employee, missing purpose, duplicate, personal payment unproven, card-paid, goods not received and suspected fraud. Give each an owner and stop condition. For example, accounting owns wrong-buyer analysis within two business days; AP investigates duplicates before due date; procurement owns unauthorised-supplier follow-up. KSeF acceptance must never override a documented hold.

Guide

Run a realistic acceptance test pack

Test at least eight cases: a no-PO emergency service, personal payment with role 11, a valid invoice without role 11, corporate card, wrong buyer NIP, duplicate PDF and KSeF record, card-paid invoice queued in AP, and an expense lacking delivery evidence. Include AP, expenses, card administrator, requester, budget holder, procurement, accounting and treasury. Retain the KSeF identifier, routing decision, matching fields, approvals, exception history, outcome and timestamps. Target 95% routing within one business day, zero test duplicates released, 100% wrong-buyer cases blocked, and an audit export in under ten minutes. Measure reassignments and aging by queue. A pass means the team can explain who decided what and on which evidence—not merely display an invoice. Re-test permissions, unavailable approvers, corrections and month-end volume before go-live.

Guide

Choose software on controls, then act

Require FA(3) ingestion, visibility of Podmiot3 role 11, KSeF-number deduplication, separate AP, expense and card routes, configurable approvals and holds, correction and evidence links, role separation, audit exports and aging dashboards. Test ERP, DMS, card and expense integrations with failures. Avoid auto-approval, duplicate PDF processing, treating role 11 as decisive, reimbursement without payment proof, fake orders and unsupported claims that evidence sits inside KSeF. Next, map exceptions, publish buyer instructions, nominate owners, configure duplicate keys and test with accounting. Obtain tax or accounting advice on buyer identity, VAT deduction, reimbursement and correction. Select software only after it proves these controls with your records and produces a traceable audit export.

Guide

Practical question summary

For KSeF no-PO and employee-purchase exception workflow: Most KSeF questions are about who must use the system, whether current accounting software is ready, how authentication works, how corrections are handled, whether ecommerce or ERP needs API integration, and how accountants access invoice data. This guide focuses on those operational decisions.

Guide

Decision framework for businesses

For KSeF no-PO and employee-purchase exception workflow: A KSeF-ready workflow should show who creates invoices, who submits them, who monitors status, who handles rejection or correction, how invoices are archived and how the accountant sees the records.

Guide

How to use this guide

Use this guide to decide whether KSeF no-PO and employee-purchase exception workflow affects your Poland workflow and which evidence is still missing. Start with KSeF authentication, structured invoice submission, invoice status handling, then test submit a KSeF invoice and simulate an API rejection before comparing software.

Guide

Data and terms to prepare

For KSeF no-PO and employee-purchase exception workflow, the important terms are KSeF no-PO and employee-purchase exception workflow, Poland, KSeF authentication, structured invoice submission, invoice status handling, corrections and rejections, accounting or ecommerce integration. Clean these fields in customer, supplier, tax and accounting records before rollout; otherwise validation and support issues appear during daily invoicing.

Guide

Software proof to request

For KSeF no-PO and employee-purchase exception workflow, ask vendors to show show KSeF authentication, submission status, corrections, permissions and accounting export using your examples. The demo should cover submit a KSeF invoice, simulate an API rejection, create a correction, verify user permissions and explain who handles errors, corrections, archive access and accountant handoff for KSeF authentication, structured invoice submission, invoice status handling.

Guide

Evidence before rollout

Keep official links, screenshots, test invoices and the decision reason for KSeF no-PO and employee-purchase exception workflow. For KSeF no-PO and employee-purchase exception workflow, the implementation file should prove how KSeF authentication, structured invoice submission, invoice status handling, corrections and rejections were checked, not just that a tool was selected.

Guide

Decision checkpoint

Do not close KSeF no-PO and employee-purchase exception workflow until someone can explain KSeF no-PO and employee-purchase exception workflow in Poland, name the workflow owner, show one tested invoice scenario and describe how the team avoids choosing software for Poland before proving the real KSeF no-PO and employee-purchase exception workflow workflow.

Checklist

Publish the company legal name, NIP and approved employee-reference instructions.

Create exclusive queues for no-PO, personal-payment and corporate-card cases.

Use the KSeF number as the primary incoming-invoice identity when available.

Assign AP, expense, card, procurement, accounting and budget-owner responsibilities.

Match claims against KSeF, AP, card and reimbursement records before release.

Require proof of personal payment for every employee reimbursement request.

Block wrong-buyer and duplicate cases pending documented accounting review.

Link receipts, delivery evidence and approvals without claiming KSeF embedding.

Measure routing time, exception aging, duplicate prevention and audit completeness.

Test corrections, absent approvers, integration failures and month-end volumes.

FAQ

Can an employee receive a company KSeF invoice?

The employer can be the buyer while employee information is included in FA(3) Podmiot3 with role 11, “Pracownik”, helping identify the invoice. The company’s correct buyer name and NIP remain essential. The employee reference does not authorise the purchase, prove business purpose or determine reimbursement or VAT treatment.

Is Podmiot3 role 11 mandatory for every employee purchase?

The official FA(3) structure provides role 11 for employee identification, but it should not be presented as universally mandatory. A missing role 11 does not automatically decide invoice validity, while its presence does not cure wrong buyer data. Ask accounting or a tax adviser about the specific transaction.

What should happen when a KSeF invoice has no purchase order?

Route it to a defined no-PO exception queue. AP checks identity and duplicates, the requester and service owner confirm the purchase and receipt, the budget holder approves coding and funding, and procurement reviews policy exceptions. Keep it on hold until the company’s required evidence and approvals are complete.

Can a receipt or PDF be reimbursed?

It may support a claim under company policy, but it is not automatically a company invoice or proof of VAT deductibility. Check buyer identity, business purpose and personal payment. Where a KSeF invoice exists, link the visual copy and claim to its KSeF number and obtain advice for uncertain tax treatment.

Who approves an employee-related KSeF invoice?

KSeF does not approve purchases internally. A recommended model separates the manager’s policy and business-purpose approval, the goods or service owner’s receipt confirmation, accounting’s buyer and posting review, and treasury’s release. Thresholds and substitutes should be documented in the company’s own authority matrix.

How do we avoid paying a supplier and reimbursing an employee twice?

Search by KSeF number and also compare supplier NIP, invoice number, amount, date, employee and card line. Make AP, expense and card routes mutually exclusive, cross-reference the closed route, and run the duplicate check again immediately before supplier payment or reimbursement release.

What if the buyer data is wrong?

Place the invoice on hold and ask accounting to assess buyer identity. Contact the supplier where a correction is needed, preserve the accepted invoice and link the correction. Do not edit or delete an accepted KSeF invoice, and do not assume an employee entry can repair an incorrect company NIP.

Are supporting documents stored inside KSeF?

Do not assume so. Receipts, travel records, approvals and service evidence may live in an expense platform or DMS and be linked to the accounting record. A formal KSeF invoice attachment has its own official scope and rules; it is distinct from arbitrary internal evidence files.

What do businesses usually ask about KSeF?

For KSeF no-PO and employee-purchase exception workflow: They ask about software readiness, API integration, authentication, corrections, accountant access and ecommerce workflows.

What is the most practical KSeF risk?

For KSeF no-PO and employee-purchase exception workflow: The practical risk is late discovery that permissions, corrections or invoice status handling do not match the business process.

What should I test first for KSeF no-PO and employee-purchase exception workflow?

For KSeF no-PO and employee-purchase exception workflow, start with submit a KSeF invoice, simulate an API rejection, create a correction because those scenarios reveal whether the workflow is practical.

What is the main risk for KSeF no-PO and employee-purchase exception workflow?

The main risk is choosing software for Poland before proving the real KSeF no-PO and employee-purchase exception workflow workflow.

Key regulations, formats and terms

PolandKSeFKrajowy System e-FakturPolish Ministry of Financepodatki.gov.plstructured invoiceAPI authenticationinvoice correctionsaccounting softwareVATSMEecommerceEuropean CommissioneInvoicingEN 16931Directive 2014/55/EUstructured electronic invoiceVAT automationcross-border tradeKSeF no-PO and employee-purchase exception workflow

Poland — Country hub

Poland

Open country hub →

Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.

Continue reading

Official sources

We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.