Technical implementation guide for Polish KSeF e-invoicing, FA(3) schemas, and API onboarding. Use when: Map ERP invoice data to the mandatory FA(3) structured XML format; Design API authentication flows for test and production KSeF environments; Implement the offline24 procedure with required QR code generation logic.
62%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/nex-einvoice-pl/SKILL.mdFree skill by Nex AI. This file is the public guide from Agensi. Scripts, extension source, and templates from the original package are not in this folder.
Integrating Polish KSeF (Krajowy System e-Faktur) is more than just XML mapping. Developers must manage a clearing model where invoices only legally exist once assigned a central KSeF number, requiring specific authentication flows and offline contingency logic.
KSeF 2.0 API, FA(3) XML Schema, MCU module (Moduł Certyfikatów i Uprawnień), and ZAW-FA filing protocols.
Generic LLMs often confuse KSeF clearing with Peppol exchange models. This skill enforces the specific FA(3) hierarchy, legal issuance dates based on transmission, and the technical requirements for Type 2 certificates needed for offline QR codes.
Requires a KSeF certificate for offline24 modes. Commercial attachments like PDFs must be sent out-of-band as the Zalacznik node is restricted to structured tax data.
Request
Provide the FA(3) field mapping for a correction invoice (korekta) where the error was present from the start.
Result
Set RodzajFaktury to 'KOR'. Under the Naglowek node, use WariantFormularza 3. In the Fa node, set TypKorekty to 'A' (error from start) and provide the mandatory PrzyczynaKorekty. You must include the DaneFaKorygowanej section referencing the original invoice's KSeF number.
This skill provides a structured implementation roadmap specifically for the Polish FA(3) schema, including API onboarding workflows, authentication logic, and offline24 contingency procedures that generic AI models often misinterpret.
The skill is designed to work with any major LLM (such as GPT-4, Claude 3.5, or Gemini) that supports technical documentation analysis and XML structure generation.
You will receive the complete technical logic package, including FA(3) field mapping guides, API environment onboarding protocols, and specific compliance checklists for the 2026/2027 deadlines.
Yes, the skill includes the mandatory procedures for 'offline24' mode, detailing how to generate compliant QR codes and the specific submission windows required by Polish tax law during system failures.
The skill is updated to reflect the latest KSeF 2.0 API specifications and FA(3) schemas; buyers will receive notifications when updates are released to reflect changes in Polish Ministry of Finance requirements.
This skill focuses on the technical integration and data mapping; you will still need to acquire a qualified certificate or seal from a certified provider to authenticate with the KSeF production environment.
Built by Nex AI. More skills, including the paid catalog: https://www.agensi.io/creators/ch1n4-g3nd4x
NexaiGuy/nex-ai-skills
4034c84
Also appears in
since Nov 6, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.