Nex Einvoice pl

    1

    Technical implementation guide for Polish KSeF e-invoicing, FA(3) schemas, and API onboarding.

    Secure checkout via Stripe

    0 installsSecurity scanned

    Works with the AI tools you already use

    CClaude CodeCCursorCCodex CLIGGitHub CopilotGGemini CLIVVS CodeWWindsurfMManus+14 more

    See it in action

    You say

    Provide the FA(3) field mapping for a correction invoice (korekta) where the error was present from the start.

    Your agent does

    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.

    What you get

    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.Audit taxpayer readiness based on 2026 sales thresholds and VAT status.

    About this skill

    The problem

    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.

    What it does

    • Generates readiness checklists based on taxpayer category, gross sales, and VAT status.
    • Provides FA(3) schema field structures for standard, correction (korekta), and advance (zaliczkowa) invoices.
    • Outlines onboarding workflows for KSeF 2.0 API environments across test, demo, and production.
    • Defines offline24 contingency procedures, including mandatory QR code rules and submission windows.
    • Flags critical 2026 deadlines for penalty grace periods and token expiration.

    Frameworks & tools

    KSeF 2.0 API, FA(3) XML Schema, MCU module (Moduł Certyfikatów i Uprawnień), and ZAW-FA filing protocols.

    Why this beats prompting it yourself

    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.

    Use cases

    • Map legacy ERP data fields to the mandatory FA(3) XML structure.
    • Build a recovery workflow for the offline24 mode and system failures.
    • Determine the exact compliance deadline for a specific Polish entity or branch.
    • Configure authentication using KSeF certificates, seals, or tokens before the 2027 cutoff.

    Known limitations

    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.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    Listedtoday

    Frequently Asked Questions