fakturownia-invoice-ksef-tax-id-kinds

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.

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.

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.

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.

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.

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.