fakturownia-invoice-ksef-tax-id-kinds

Set buyer and seller tax identifier kinds in fakturownia invoice payloads for KSeF compliance.

Updated Apr 14, 2026

Search Tags:#invoice #vat #fakturownia #ksef #tax-id #foreign-buyer

Ready to run

npx skills add https://github.com/sixers/fakturownia-cli --skill fakturownia-invoice-ksef-tax-id-kinds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fakturownia-invoice-ksef-tax-id-kinds
Source: https://github.com/sixers/fakturownia-cli/tree/main/skills/fakturownia/recipes/invoice-ksef-tax-id-kinds
Command: npx skills add https://github.com/sixers/fakturownia-cli --skill fakturownia-invoice-ksef-tax-id-kinds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This recipe standardizes and prepares buyer and seller tax identifier fields so invoice payloads meet KSeF (Poland's e-invoicing) semantics, avoiding rejected submissions due to ambiguous tax identifier kinds.

Core Features & Use Cases

Explicit tax identifier mapping: Maps API-native fields buyer_tax_no_kind and seller_tax_no_kind to the curated enum values expected by KSeF-aware endpoints.
Foreign buyer support: Handles cases where buyers are non-Polish entities and require country-specific identifier kinds such as NIP UE.
CLI integration: Intended for use with fakturownia invoice create/update commands to ensure payloads are accepted by KSeF validation.

Quick Start

Prepare an invoice payload by setting buyer_tax_no_kind and seller_tax_no_kind to the appropriate enum values from the fakturownia schema before running the invoice create or update command.

Frequently Asked Questions about fakturownia-invoice-ksef-tax-id-kinds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I normalize tax IDs for KSeF invoices in fakturownia?▼

To normalize tax IDs for KSeF invoices, set the buyer_tax_no_kind and seller_tax_no_kind fields to the curated enum values from the fakturownia schema before creating or updating your invoice payload. This standardizes identifiers to meet KSeF semantics and avoids rejected submissions.

Why do my KSeF invoice submissions get rejected due to ambiguous tax identifier kinds?▼

KSeF invoice submissions are rejected due to ambiguous tax identifier kinds because the payload lacks explicit tax identifier mapping. Setting buyer_tax_no_kind and seller_tax_no_kind to curated enum values resolves this formatting validation issue.

How do I handle foreign buyer VAT numbers for KSeF e-invoicing?▼

To handle foreign buyer VAT numbers for KSeF e-invoicing, apply country-specific identifier kinds like NIP UE to the buyer_tax_no_kind field. This validates formats against country-specific rules for non-Polish entities.

What tax identifier kinds are required for EU VAT scenarios in KSeF?▼

EU VAT scenarios in KSeF require explicit tax identifier kinds mapped to curated enum values. You must populate buyer_tax_no_kind and seller_tax_no_kind with the specific schema values to satisfy KSeF-aware endpoints.

Do I need to set tax identifier kinds when updating invoices in fakturownia for KSeF?▼

Yes, you need to set tax identifier kinds when updating invoices in fakturownia for KSeF. Applying buyer_tax_no_kind and seller_tax_no_kind ensures the updated payload passes KSeF validation during create or update operations.

Can I use this tax ID normalization for non-Polish entities in fakturownia?▼

Yes, you can use tax ID normalization for non-Polish entities in fakturownia. It handles foreign buyers by applying country-specific identifier kinds and validating formats against the respective country-specific rules.