When does KSeF actually become mandatory, and for whom?
KSeF has been announced as a mandatory system for B2B invoices in Poland. The Polish government has moved the exact start date several times; the latest plan is a phased mandate from 2026 for large taxpayers, followed by the rest of the SME sector. We keep an eye on the roadmap and plan your integration so that it is working in the sandbox well before your deadline. It's important to realise that once the mandate takes effect, the tax authority no longer accepts a paper or PDF invoice as a valid tax document. Anything you send outside KSeF formally doesn't count: your customer can't reclaim the VAT, and you effectively have no recognised invoice.
What is FA(3) and why is the schema so strict?
FA(3) is the XML schema that KSeF prescribes for electronic invoices: a detailed XSD with mandatory fields for parties, invoice lines, VAT codes and corrections. It is strict because the Polish tax authority can validate the content directly and only accepts the invoice after schema validation. Alongside pure schema checks, business rules also apply: certain combinations of VAT rates and invoice types are not allowed, NIP numbers must validate against the Polish register, and correction invoices must reference the original invoice via UUID. We run this validation on our side too, before submission, so rejections become rare.
How do you connect SAP IDoc INVOIC to KSeF?
With a middleware layer between SAP and KSeF. The IDoc is picked up (via RFC, a file port or an EDI broker), transformed into FA(3) XML, signed with the qualified certificate and submitted to KSeF. We write the confirmation of receipt or the rejection back to SAP, as an IDoc status, a custom Z-table or an email notification, depending on what your SAP team prefers. We explicitly keep your SAP system clean: no Z-development inside SAP and no changes to standard IDoc segments. All KSeF-specific logic sits outside SAP, in a separate service that we manage or that you run yourself after handover.
Can we test safely in a sandbox first?
Yes. KSeF has a separate sandbox environment that is identical to production in terms of API and schema. We build against it first and run a full end-to-end test with real invoice data. Only once the signature flow, submission, callback and error paths all work do we switch to production. The switch itself is a config change, not a code change. In the sandbox we also deliberately simulate failure scenarios: a wrong VAT rate, a missing NIP, a timeout on the KSeF side, a revoked signature. We only go live once those paths are handled cleanly.
How do we connect Exact Online or AFAS to KSeF?
For Exact Online we build the integration on the Exact Online API; for AFAS we deliver via Profit connectors or GetConnectors. The integration layer between your accounting software and KSeF lives as a separate service, so an upgrade of Exact or AFAS doesn't break the KSeF integration. See also our
Exact Online integration page for the Exact side. For AFAS we typically use a GetConnector to extract invoice data, an UpdateConnector to write the KSeF status back, and a separate service for the KSeF submission itself. That keeps the AFAS environment within your AFAS consultant's scope and the KSeF layer within ours.
Does this work alongside Peppol for other EU countries?
Yes. Peppol is emerging as a universal e-invoicing network for the EU, while Poland has its own mandatory system in KSeF. Many multinationals run into this parallel world. We build routing logic that chooses between Peppol, KSeF or another mandate (for example SDI in Italy or FacturaE in Spain) based on the recipient's country and VAT position. One platform, multiple channels, one shared audit log. That makes a huge difference to management: one integration team, one set of monitoring dashboards, and one place where the finance controller checks rejected invoices.
What about archiving and the retention obligation?
Polish tax legislation requires invoice data to be archived for the long term, typically ten years. We set up encrypted storage in your cloud or ours, with immutable (write-once) logging and an audit trail showing who viewed or exported which invoice, and when. Access runs through your IdP (Azure AD, Okta, Google Workspace), so it falls within your existing security policy. Alongside the FA(3) XML, we also store the corresponding KSeF UUID, the acceptance timestamp and, where relevant, the original source IDoc or API response, so you can produce the full trail during an audit.
What if KSeF rejects our invoice: who corrects what?
Rejections come in all shapes: schema errors (a field that doesn't match), business-rule errors (invalid NIP, wrong VAT rate), or technical errors on the KSeF side (timeouts, maintenance). We separate these paths in code: schema errors go back to your finance team with a readable explanation, business-rule errors trigger a manual review, and technical errors are retried automatically with exponential backoff. Nothing disappears into a log file that nobody looks at: everything appears in the ops dashboard with an action button.
What does a KSeF integration cost?
That depends heavily on the scope: a single ERP and a single entity is a short project, while a multi-entity setup with SAP IDoc flows and Peppol overlap is a larger one. In the first conversation we walk through the scope and then come back to you with a sprint budget. No open-ended hours; fixed budgets per sprint. We also explicitly name which risks fall outside the scope for now (for example, new FA versions that Poland only publishes later) and how we handle them under maintenance without the project running on indefinitely.