DR DYNAMICSFA(3)
Poland's EN 16931-based XML schema for B2B invoices, introduced with KSeF 2.0. Every invoice is submitted, validated, and returned with a unique KSeF number and a UPO receipt — the proof that the invoice legally exists.
Poland's KSeF mandate: getting Dynamics 365 F&O compliant
In short
KSeF, Poland’s national e-invoicing system, is live. Since 1 February 2026 every VAT-registered business must be able to receive invoices through KSeF, and large taxpayers — above PLN 200 million of 2024 sales — must issue through it. All other VAT-registered businesses joined on 1 April 2026, and micro-entrepreneurs follow on 1 January 2027. Poland runs a clearance model: the invoice goes to the government platform, which validates it and returns a KSeF number and a UPO receipt. Dr Dynamics makes Microsoft Dynamics 365 Finance & Operations ready.
How engagement works
- ValidateFree — the 34-check data-readiness validator
- ImplementFrom €35,000 — typical pilot live in 6–10 weeks
- Run15% per year — named engineer, SLA, monthly review
KSeF is live, in phases
- 1 Feb 2026Receiving + large taxpayers Every VAT-registered business must receive via KSeF; taxpayers above PLN 200m of 2024 sales must also issue.
- 1 Apr 2026All other taxpayers The remaining VAT-registered businesses must issue through KSeF.
- 1 Jan 2027Micro-entrepreneurs The smallest businesses join, completing the rollout.
A clearance model, not a network
KSeF, the government platform
Where Belgium and Norway use Peppol networks, Poland puts the tax administration in the middle of the flow. You do not send the invoice to your customer: it is cleared through KSeF, and that is where your customer collects it.
VAT reporting moved in step. JPK_V7(3) became mandatory from 1 February 2026 and carries KSeF context on every entry — NrKSeF for the KSeF identifier, plus the OFF, BFK and Dl markers. The D365 application builds, Electronic Reporting versions and Electronic Messages setup that requires are covered in our JPK-V7(3) briefing.
What this means for Dynamics 365 F&O
Generate
FA(3)-compliant invoices out of Dynamics 365 F&O through Electronic Reporting, on master data clean enough to pass KSeF validation on submission.
Clear
Submission to KSeF and handling what comes back. The KSeF number and UPO belong against the source invoice in Dynamics — that number is what proves the invoice exists.
Report
JPK_V7(3) alignment, so the NrKSeF, OFF, BFK and Dl flags on your VAT file match the invoices actually cleared through KSeF.
Platforms
- ecosio — live integration
- Pagero
- EDICOM
- Generix
- Direct KSeF integration
How engagement works: Validate → Implement → Run
Validate Free
Our 34-check data-readiness validator: a code package your engineer drops into D365 Finance, so your team can run the seller, buyer and payment-terms checks on your own master data — and get a plain-Excel report of every problem and its fix.
Implement from €35,000
Full implementation: configuration, KSeF submission and UPO handling, inbound AP, the validation layer, JPK_V7(3) alignment and cutover. Typical pilot live in 6–10 weeks.
Run 15% per year
Post-go-live support with a named engineer, an SLA and a monthly operational review — so the next schema version is a configuration task, not a project.
Start free → Validate the data behind your e-invoices.Our readiness validator runs 34 checks — seller, buyer and payment terms — inside Dynamics 365 Finance, on your own master data, and reports every problem and its fix in a plain Excel list. The actual package, not a demo: email validate@drdynamics.co.uk with subject “READINESS”.
Request the free validatorPoland KSeF FAQ
Is KSeF mandatory now?
Yes, in phases. Since 1 February 2026 every VAT-registered business must be able to receive invoices through KSeF, and taxpayers with more than PLN 200 million of 2024 sales must issue through it. All other VAT-registered businesses followed on 1 April 2026. Micro-entrepreneurs join on 1 January 2027.
What is the FA(3) schema?
FA(3) is Poland's EN 16931-based XML schema for B2B invoices, introduced with KSeF 2.0. Every B2B invoice in scope must be submitted to KSeF in that structure.
What is a UPO and why does it matter?
When KSeF accepts an invoice it validates the submission and returns a unique KSeF number together with a UPO confirmation. That is the evidence the invoice was cleared, so both belong stored against the source invoice in your ERP rather than left in a middleware log.
Are there penalties yet?
No financial penalties apply during the 2026 calendar year — a full-year grace period to work through technical problems. Note the limit of that: ordinary VAT sanctions for incorrect settlements still apply from 1 February 2026, so the grace period covers KSeF process errors, not bad VAT.
How does KSeF affect our JPK_V7 VAT reporting?
Directly. JPK_V7(3) became mandatory from 1 February 2026 specifically to align VAT reporting with KSeF, adding the NrKSeF identifier plus the OFF, BFK and Dl markers. In D365 Finance that means a supported application build, current SAF-T Electronic Reporting configurations and an Electronic Messages setup with schema version 3 as default — our JPK-V7(3) briefing lists the exact versions.
Does Dynamics 365 F&O support KSeF?
Yes. D365 Finance generates the Polish invoice structures through Electronic Reporting and handles JPK_V7 through Electronic Messages. What every project still owns is the KSeF submission loop — clearing the invoice, capturing the KSeF number and UPO against it, and handling rejections — plus the master-data quality that determines whether KSeF accepts the invoice at all.
What language does the engagement run in?
English. Dr Dynamics delivers to Polish entities from the UK, and the project language — meetings, workshops and documentation — is English.
Get your fastest-path plan for Poland
KSeF is live and the penalty grace period runs out at the end of 2026. Bring your Polish entities, your Dynamics version and your current JPK_V7 setup, and we will tell you honestly where you stand.