E-Invoice Finder
Menu
Countries Compare software Deadlines Guides Checker Check obligation
ENFRDEPLNL
Poland · treasury and ERP controls for 2027

KSeF payment-reference and collective-identifier ERP test pack

Prepare ERP and treasury flows for KSeF numbers, collective identifiers and MPP payment references from 1 January 2027.

Quick verdict:
  • Scope first: taxpayer status, invoice mode and reference-capable payment method determine the route.
  • The costliest control failure is paying a mixed-seller group under one collective identifier.
  • Begin by tracing one accepted invoice from UPO evidence through the rendered bank instruction.
Get Poland readiness reportOfficial sources
Last checked: 9 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

Quick scope decision: one invoice, several invoices or out of scope?

Start with three questions: is the payer an active VAT taxpayer, is the payee another active VAT taxpayer, and does the payment method permit a transfer reference? From 1 January 2027, the official rule requires the KSeF number or a KSeF collective identifier when those conditions apply to payment for structured invoices and relevant Offline24 or KSeF-unavailability invoices. For one invoice, place its KSeF number in the transfer reference. For two or more eligible invoices from the same seller, use a collective identifier generated by KSeF. Do not generalise this to every taxpayer, every payment or cash and card flows without checking the statutory conditions. Have Polish tax advisers approve the scope logic; system warnings and release blocks are recommendations. Example: three accepted invoices from Supplier A may use one collective identifier, while an invoice from Supplier B needs a separate payment/reference decision.

Guide

Identifier anatomy and a data model that prevents substitution

The KSeF number uniquely identifies an invoice accepted by KSeF and is returned in the UPO. It is not a field in the invoice XML and is not the seller’s commercial invoice number held in FA(3) field P_2. Store these as separate, labelled values: seller_invoice_number, ksef_number, upo_reference or artefact, collective_identifier, bank_batch_id and erp_document_id. Never use one as fallback for another. The collective identifier has 35 characters: the generator’s authentication-context NIP, the marker IZ, generation year and month, a unique 12-character string and two check digits. An official-format example is 9999999999-IZ202602-FFFFFFFFFFFF-FF. Validate format without assuming that a syntactically valid value is authentic or belongs to the invoices being paid. Preserve the generator, timestamp, invoice list, seller NIP and KSeF evidence; warn if P_2 is pasted into the KSeF-reference field.

Guide

AP-to-treasury workflow from invoice receipt to released payment

Accounts payable should ingest the structured invoice, its seller P_2 number and, after KSeF acceptance, the distinct KSeF number evidenced through the UPO or trusted KSeF-connected process. AP validates supplier, VAT status, amount and payment route, then records whether the duty applies. A proposed payment containing one invoice carries that invoice’s KSeF number. A proposal containing several invoices branches to collective-identifier generation only after confirming the same seller and a complete list of KSeF numbers. Treasury reviews the value passed into the bank reference, not merely the ERP screen, and releases only after the exported bank file is compared with the approved proposal. Reconciliation should link the bank transaction, paid invoices, KSeF numbers and collective identifier. AP owns matching, tax owns interpretation, treasury owns release and IT owns interfaces; this RACI is a recommendation.

Guide

Generate and decode collective identifiers without crossing sellers

A collective identifier aggregates at least two structured invoices issued by the same seller. Generation requires declaring the list of KSeF numbers. The issuer or recipient can generate it through the KSeF Taxpayer Application or connected commercial accounting software. KSeF can decode the identifier to the invoice numbers it contains and can show which collective identifiers include a specified KSeF number. It cannot group different suppliers. Example: invoices A-101 and A-102 from seller NIP X can be declared together; invoice B-201 from NIP Y must not enter that identifier. Before release, decode or otherwise verify the generated value against the approved invoice set, seller, currency and total. Reverify the set after any addition or removal. If software cannot produce or decode the identifier with current, evidenced KSeF support, use the official Taxpayer Application process while assessing a controlled integration.

Guide

MPP, direct debit, third-party payers and offline edge cases

The payment-reference obligation also applies to split-payment mechanism (MPP) payments from 1 January 2027. For one invoice, use its KSeF number; for selected multiple invoices, use the KSeF-generated collective identifier instead of the period normally used for the multi-invoice MPP message. Direct debit creates a duty for the invoice issuer, so the process owner must not assume the bank’s collection flow removes the reference requirement. Third-party payers are also covered when the statutory conditions are met; retain a clear link between payer, buyer, seller and invoices. For Offline24 or KSeF-unavailability invoices, capture when the invoice entered KSeF and when its KSeF number became available before payment-file creation. Official guidance notes an exception where such invoices were not entered into KSeF because of an announced outage. Preserve the outage announcement and transaction facts before invoking it. Use tax-approved decision tables; blocking thresholds and retention periods are recommendations.

Guide

ERP and bank-file architecture: pass the right value end to end

Use a dedicated payment_reference_type with values such as KSEF_NUMBER, COLLECTIVE_IDENTIFIER, DOCUMENTED_EXCEPTION and NOT_APPLICABLE, plus the reference value and decision evidence. A payment-group service should reject mixed seller NIPs before requesting or importing a collective identifier. The treasury interface should map the approved value into the bank format’s actual transfer-reference field, detect truncation or unsupported characters, and show the final rendered output for approval. Keep bank batch IDs separate because they identify execution batches, not KSeF invoices. Use duplicate-payment controls, separate test and production credentials, restrict generation roles and alert on changed references. Those architectural safeguards are recommendations. Confirm character limits and field behaviour with each bank, and verify KSeF integration behaviour in the current official environment rather than relying on screenshots or vendor claims.

Guide

Eight-scenario acceptance test pack with owners and evidence

Run eight end-to-end tests: (1) AP pays one accepted structured invoice—owner AP; retain KSeF number, UPO evidence and bank preview. (2) Treasury pays three invoices from one seller—owner treasury; retain declared list, collective identifier, decoded list and export. (3) A batch mixes two sellers—owner IT; prove generation or release is blocked. (4) P_2 is entered as the payment reference—owner AP systems; prove validation rejects substitution. (5) Selected invoices are paid under MPP—owner tax; prove the collective identifier replaces the period and appears in the final message. (6) Direct debit is initiated—owner receivables; retain the issuer’s reference decision and mandate/payment evidence. (7) A third party pays—owner tax/AP; retain payer-buyer-seller linkage and applicable reference. (8) Offline24 or unavailability is followed by an announced outage—owner tax; prove the correct KSeF-number timing or documented exception. Retain inputs, approvals, interface logs, bank rendering, expected result and defect disposition; an ERP screenshot alone is insufficient.

Guide

Reconciliation, incidents and measurable operating criteria

Reconcile daily from bank statement back to transfer reference, collective identifier, included KSeF numbers and ERP invoices. Flag a payment if the amount or supplier differs from the approved set, an invoice appears in two paid batches, decoding produces a different list, the bank truncates the value, or the reference was edited after approval. A practical pilot gate could require 100% correct reference rendering across all eight scenarios, zero mixed-seller collective identifiers, zero P_2 substitutions, 100% traceability from settled transaction to invoice list, and documented resolution of every exception before production. These percentages are recommended acceptance criteria, not legal thresholds. Classify incidents consistently. Freeze unreleased files when integrity is uncertain; for executed payments, preserve evidence and assess corrective action with advisers. Track defects and decoding mismatches, then rerun tests after system changes.

Guide

Software and vendor decision criteria, common mistakes and next actions

Ask vendors to demonstrate current generation and decoding with your authorised environment, a same-seller multi-invoice case, reverse lookup of collective identifiers for a KSeF number, MPP output, bank-field rendering, audit export and outage handling. Official guidance says API-connected systems will support generation and decoding, but an issue opened in the official CIRFMF repository on 1 April 2026 still asked when that implementation would be available and showed no public milestone in the fetched issue. Verify the current official API specification and environment plus vendor evidence; do not accept invented endpoint names or a promise that API functions are live. Score proven coverage, identifier controls, reconciliation, bank compatibility and audit export. Common mistakes are mixing sellers, treating P_2 or a bank batch ID as the KSeF number, viewing the UPO itself as the payment reference, and trusting format checks without decoding. Next, approve the scope matrix, run all eight tests, close defects and obtain dated tax sign-off. This is practical information, not legal or tax advice.

Guide

Practical question summary

For KSeF payment reference and collective identifier ERP test pack for 2027: 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 payment reference and collective identifier ERP test pack for 2027: 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 payment reference and collective identifier ERP test pack for 2027 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 payment reference and collective identifier ERP test pack for 2027, the important terms are KSeF payment reference and collective identifier ERP test pack for 2027, 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 payment reference and collective identifier ERP test pack for 2027, 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 payment reference and collective identifier ERP test pack for 2027. For KSeF payment reference and collective identifier ERP test pack for 2027, 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 payment reference and collective identifier ERP test pack for 2027 until someone can explain KSeF payment reference and collective identifier ERP test pack for 2027 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 payment reference and collective identifier ERP test pack for 2027 workflow.

Checklist

Confirm payer and payee VAT status, payment instrument and invoice mode before applying the 2027 reference rule.

Store P_2, KSeF number, UPO evidence, collective identifier, ERP ID and bank batch ID in separate fields.

Use one verified KSeF number when a transfer pays one in-scope invoice.

Generate a KSeF collective identifier only for at least two invoices from the same seller.

Decode or verify every collective identifier against the approved invoice list before release.

Test MPP, direct debit, third-party payer, Offline24 and KSeF-unavailability paths with tax-approved rules.

Inspect the final bank-file reference for truncation, character changes and unauthorised edits.

Retain generation, decoding, approval, outage and settlement evidence in the audit trail.

Block mixed-seller groups, P_2 substitutions, duplicate invoices and unresolved reference mismatches.

Recheck the official API specification, live environment and vendor proof before enabling automation.

FAQ

When is a KSeF number required in a bank transfer?

From 1 January 2027, an active VAT taxpayer paying another active VAT taxpayer for covered structured or Offline24/KSeF-unavailability invoices must provide the KSeF number or collective identifier when the payment instrument permits a transfer reference. Check the precise conditions; this does not cover every taxpayer or payment method.

How should a payment for several invoices be referenced?

For selected invoices from one seller, declare their KSeF-number list and use the collective identifier generated by KSeF. Decode or verify it against the approved invoice set before release. Do not substitute an ERP batch number or place several unrelated references in a free-text memo.

Can invoices from different suppliers share one collective identifier?

No. A collective identifier covers invoices issued by the same seller. Each supplier therefore needs a separate grouping and reference decision. Configure the ERP to block mixed seller NIPs and retain evidence that the approved invoice set matches the generated identifier.

Who can generate and decode a collective identifier?

The issuer or recipient can generate it through the KSeF Taxpayer Application or connected commercial accounting software after declaring the KSeF-number list. KSeF can decode the included invoices and show which collective identifiers contain a specified KSeF number. Restrict roles and retain evidence.

What changes for MPP split payments?

The reference duty applies to MPP from 1 January 2027. Use the KSeF number for one invoice. For selected multiple invoices from the same seller, use the KSeF-generated collective identifier instead of the period. Test the final bank message, not only the ERP screen.

How do direct debit and third-party payments work?

Official guidance places a duty on the issuer for direct debit and covers third-party payers when the relevant conditions apply. Preserve the link among payer, buyer, seller, invoices and reference. Have Polish advisers approve the decision table and operational ownership for each flow.

What if an offline invoice has no KSeF number at payment time?

Record when an Offline24 or KSeF-unavailability invoice entered KSeF and when its number became available. Guidance notes an exception where entry did not occur because of an announced outage. Retain the announcement, timestamps and transaction evidence; do not create a number or assume the exception.

Can our ERP use the KSeF API for collective identifiers now?

Do not assume so. Official guidance anticipates API-connected support, but an official repository issue opened on 1 April 2026 still requested an implementation date and showed no public milestone when reviewed. Check the current specification and environment, then require a logged vendor demonstration without invented endpoint names.

What do businesses usually ask about KSeF?

For KSeF payment reference and collective identifier ERP test pack for 2027: They ask about software readiness, API integration, authentication, corrections, accountant access and ecommerce workflows.

What is the most practical KSeF risk?

For KSeF payment reference and collective identifier ERP test pack for 2027: 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 payment reference and collective identifier ERP test pack for 2027?

For KSeF payment reference and collective identifier ERP test pack for 2027, 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 payment reference and collective identifier ERP test pack for 2027?

The main risk is choosing software for Poland before proving the real KSeF payment reference and collective identifier ERP test pack for 2027 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 payment reference and collective identifier ERP test pack for 2027

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.