@spaceinvoices/js-sdk 14.9.0 → 14.10.0

package/dist/generated/model/vatReturnPreview.d.cts

@@ -15,6 +15,8 @@ export interface VatReturnPreview {
     vat_period_setting: VatReturnPreviewVatPeriodSetting;
     period_matches_setting: boolean;
     deadline: VatReturnDeadline;
+    /** True when the monthly period owes the recapitulative statement (RP-O), so the DDV-O deadline is the 20th of the next month. The deadline and cut-off use the same answer. */
+    rpo_required?: boolean;
     boxes: DdvOBoxes;
     record_counts: VatReturnRecordCounts;
     warnings: string[];

package/dist/generated/model/vatReturnPreview.d.ts

@@ -15,6 +15,8 @@ export interface VatReturnPreview {
     vat_period_setting: VatReturnPreviewVatPeriodSetting;
     period_matches_setting: boolean;
     deadline: VatReturnDeadline;
+    /** True when the monthly period owes the recapitulative statement (RP-O), so the DDV-O deadline is the 20th of the next month. The deadline and cut-off use the same answer. */
+    rpo_required?: boolean;
     boxes: DdvOBoxes;
     record_counts: VatReturnRecordCounts;
     warnings: string[];

package/dist/generated/tax-reports/tax-reports.d.cts

@@ -692,13 +692,14 @@ when a period has no applicable records, as required for a joint eDavki submissi
 
 **Important:**
 - KIR/KPR is available only to entities whose country code is `SI`
-- Draft, voided, and deleted documents are excluded
+- Draft and deleted documents and voided credit notes are excluded. A voided invoice is excluded together with the credit note created when it was voided if both fall in the same period. If that credit note falls in another period, the invoice is reported in its own period and the credit note in its own. A voided invoice without such a credit note is excluded
 - Domestic outgoing advances are included as separate KIR rows and their allocated net/VAT amounts are subtracted from the linked final invoice. For intra-EU B2B supplies, goods prepayments are omitted and not deducted; only the classified service component is reported in P10 and deducted from the final invoice. A fully prepaid reportable service still emits the final reconciliation row with P10 empty/zero
 - Third-country outgoing documents use the persisted item tax treatment: bases with an explicit 0% tax row map to P7, while no-tax net amounts (including unrated summary bases) map to P27. Mixed documents are split between both fields. Product/service classification and customer geography are not substitutes for tax treatment; the legacy `export` transaction type remains an explicit goods-export marker and maps to P7
 - Domestic and intra-EU B2C outgoing documents fail closed when any net base is 0%, no-tax, unrated, or does not reconcile to the explicit tax summaries; an exemption semantic is required before those amounts can be placed safely
 - The selected month or quarter includes the complete final calendar day
 - Customer identity fields P5/P6/P6DS are omitted for end consumers
-- KIR uses the issued-document date for period selection and P2/P4. KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
+- KIR P2/P4 are the issued-document date. An invoice issued before 2026-11-01 is selected by its issue date. An invoice issued from 2026-11-01 is selected by its VAT tax point: the end of the service period (`date_service_to`, else `date_service`, else `date`), or the payment date when one payment received before the service covers the whole total. A part prepayment keeps the default tax point and is returned as a warning by the VAT return preview. An invoice issued after the KIR cut-off of its tax-point period is selected by its issue date, and the preview warns when it charges VAT. Credit notes and advance invoices are selected by their issue date
+- KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
 - An included AP document must have its own supplier-document date for KPR P5; receipt date is never substituted into P5
 - Reportable intra-EU AP purchases require both the supplier VAT number and an EU supplier country code so KPR P7/P7DS can be emitted together
 - P6/P6DS (KIR) and P7/P7DS (KPR) are reported as a pair. The country is the address country; an EU VAT ID prefix that differs from it takes precedence, and P6DS/P7DS is the ID without its prefix. A third-country VAT ID is reported whole in P6DS/P7DS with the country field empty. Greek `EL` prefixes are normalized to FURS country code `GR`
@@ -712,6 +713,7 @@ when a period has no applicable records, as required for a joint eDavki submissi
 - Cross-border supplier-charged foreign VAT is excluded. Mixing it with Slovenian-reportable reverse-charge VAT is rejected as ambiguous
 - Customs imports and fixed-asset KPR columns P12/P13/P15/P16 are not currently supported; the exporter does not infer either treatment from supplier geography, item descriptions, or financial categories
 - Ambiguous domestic outgoing 0% supplies, unknown transaction types, unsupported tax rates, missing EUR conversions, and amounts outside the FURS XSD bounds are rejected with HTTP 422 instead of producing an unsafe filing
+- A 422 caused by document data lists the affected documents in `cause.documents` (`number`, `type`, `reason`), up to 100, with the full count in `cause.total_documents`
 - Entity must have a valid 8-digit Slovenian tax number (SI prefix is automatically removed)
 
  * @summary Generate combined KIR/KPR VAT ledgers

package/dist/generated/tax-reports/tax-reports.d.ts

@@ -692,13 +692,14 @@ when a period has no applicable records, as required for a joint eDavki submissi
 
 **Important:**
 - KIR/KPR is available only to entities whose country code is `SI`
-- Draft, voided, and deleted documents are excluded
+- Draft and deleted documents and voided credit notes are excluded. A voided invoice is excluded together with the credit note created when it was voided if both fall in the same period. If that credit note falls in another period, the invoice is reported in its own period and the credit note in its own. A voided invoice without such a credit note is excluded
 - Domestic outgoing advances are included as separate KIR rows and their allocated net/VAT amounts are subtracted from the linked final invoice. For intra-EU B2B supplies, goods prepayments are omitted and not deducted; only the classified service component is reported in P10 and deducted from the final invoice. A fully prepaid reportable service still emits the final reconciliation row with P10 empty/zero
 - Third-country outgoing documents use the persisted item tax treatment: bases with an explicit 0% tax row map to P7, while no-tax net amounts (including unrated summary bases) map to P27. Mixed documents are split between both fields. Product/service classification and customer geography are not substitutes for tax treatment; the legacy `export` transaction type remains an explicit goods-export marker and maps to P7
 - Domestic and intra-EU B2C outgoing documents fail closed when any net base is 0%, no-tax, unrated, or does not reconcile to the explicit tax summaries; an exemption semantic is required before those amounts can be placed safely
 - The selected month or quarter includes the complete final calendar day
 - Customer identity fields P5/P6/P6DS are omitted for end consumers
-- KIR uses the issued-document date for period selection and P2/P4. KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
+- KIR P2/P4 are the issued-document date. An invoice issued before 2026-11-01 is selected by its issue date. An invoice issued from 2026-11-01 is selected by its VAT tax point: the end of the service period (`date_service_to`, else `date_service`, else `date`), or the payment date when one payment received before the service covers the whole total. A part prepayment keeps the default tax point and is returned as a warning by the VAT return preview. An invoice issued after the KIR cut-off of its tax-point period is selected by its issue date, and the preview warns when it charges VAT. Credit notes and advance invoices are selected by their issue date
+- KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
 - An included AP document must have its own supplier-document date for KPR P5; receipt date is never substituted into P5
 - Reportable intra-EU AP purchases require both the supplier VAT number and an EU supplier country code so KPR P7/P7DS can be emitted together
 - P6/P6DS (KIR) and P7/P7DS (KPR) are reported as a pair. The country is the address country; an EU VAT ID prefix that differs from it takes precedence, and P6DS/P7DS is the ID without its prefix. A third-country VAT ID is reported whole in P6DS/P7DS with the country field empty. Greek `EL` prefixes are normalized to FURS country code `GR`
@@ -712,6 +713,7 @@ when a period has no applicable records, as required for a joint eDavki submissi
 - Cross-border supplier-charged foreign VAT is excluded. Mixing it with Slovenian-reportable reverse-charge VAT is rejected as ambiguous
 - Customs imports and fixed-asset KPR columns P12/P13/P15/P16 are not currently supported; the exporter does not infer either treatment from supplier geography, item descriptions, or financial categories
 - Ambiguous domestic outgoing 0% supplies, unknown transaction types, unsupported tax rates, missing EUR conversions, and amounts outside the FURS XSD bounds are rejected with HTTP 422 instead of producing an unsafe filing
+- A 422 caused by document data lists the affected documents in `cause.documents` (`number`, `type`, `reason`), up to 100, with the full count in `cause.total_documents`
 - Entity must have a valid 8-digit Slovenian tax number (SI prefix is automatically removed)
 
  * @summary Generate combined KIR/KPR VAT ledgers

package/dist/generated-zod/tax-reports/tax-reports.d.cts

@@ -926,13 +926,14 @@ when a period has no applicable records, as required for a joint eDavki submissi
 
 **Important:**
 - KIR/KPR is available only to entities whose country code is `SI`
-- Draft, voided, and deleted documents are excluded
+- Draft and deleted documents and voided credit notes are excluded. A voided invoice is excluded together with the credit note created when it was voided if both fall in the same period. If that credit note falls in another period, the invoice is reported in its own period and the credit note in its own. A voided invoice without such a credit note is excluded
 - Domestic outgoing advances are included as separate KIR rows and their allocated net/VAT amounts are subtracted from the linked final invoice. For intra-EU B2B supplies, goods prepayments are omitted and not deducted; only the classified service component is reported in P10 and deducted from the final invoice. A fully prepaid reportable service still emits the final reconciliation row with P10 empty/zero
 - Third-country outgoing documents use the persisted item tax treatment: bases with an explicit 0% tax row map to P7, while no-tax net amounts (including unrated summary bases) map to P27. Mixed documents are split between both fields. Product/service classification and customer geography are not substitutes for tax treatment; the legacy `export` transaction type remains an explicit goods-export marker and maps to P7
 - Domestic and intra-EU B2C outgoing documents fail closed when any net base is 0%, no-tax, unrated, or does not reconcile to the explicit tax summaries; an exemption semantic is required before those amounts can be placed safely
 - The selected month or quarter includes the complete final calendar day
 - Customer identity fields P5/P6/P6DS are omitted for end consumers
-- KIR uses the issued-document date for period selection and P2/P4. KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
+- KIR P2/P4 are the issued-document date. An invoice issued before 2026-11-01 is selected by its issue date. An invoice issued from 2026-11-01 is selected by its VAT tax point: the end of the service period (`date_service_to`, else `date_service`, else `date`), or the payment date when one payment received before the service covers the whole total. A part prepayment keeps the default tax point and is returned as a warning by the VAT return preview. An invoice issued after the KIR cut-off of its tax-point period is selected by its issue date, and the preview warns when it charges VAT. Credit notes and advance invoices are selected by their issue date
+- KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
 - An included AP document must have its own supplier-document date for KPR P5; receipt date is never substituted into P5
 - Reportable intra-EU AP purchases require both the supplier VAT number and an EU supplier country code so KPR P7/P7DS can be emitted together
 - P6/P6DS (KIR) and P7/P7DS (KPR) are reported as a pair. The country is the address country; an EU VAT ID prefix that differs from it takes precedence, and P6DS/P7DS is the ID without its prefix. A third-country VAT ID is reported whole in P6DS/P7DS with the country field empty. Greek `EL` prefixes are normalized to FURS country code `GR`
@@ -946,6 +947,7 @@ when a period has no applicable records, as required for a joint eDavki submissi
 - Cross-border supplier-charged foreign VAT is excluded. Mixing it with Slovenian-reportable reverse-charge VAT is rejected as ambiguous
 - Customs imports and fixed-asset KPR columns P12/P13/P15/P16 are not currently supported; the exporter does not infer either treatment from supplier geography, item descriptions, or financial categories
 - Ambiguous domestic outgoing 0% supplies, unknown transaction types, unsupported tax rates, missing EUR conversions, and amounts outside the FURS XSD bounds are rejected with HTTP 422 instead of producing an unsafe filing
+- A 422 caused by document data lists the affected documents in `cause.documents` (`number`, `type`, `reason`), up to 100, with the full count in `cause.total_documents`
 - Entity must have a valid 8-digit Slovenian tax number (SI prefix is automatically removed)
 
  * @summary Generate combined KIR/KPR VAT ledgers
@@ -1521,6 +1523,7 @@ export declare const PreviewVatReturnResponse: zod.ZodObject<{
         due_date: zod.ZodString;
         kir_kpr_prefill_cutoff: zod.ZodString;
     }, zod.z.core.$strip>;
+    rpo_required: zod.ZodOptional<zod.ZodBoolean>;
     boxes: zod.ZodObject<{
         "11": zod.ZodString;
         "12": zod.ZodString;

package/dist/generated-zod/tax-reports/tax-reports.d.ts

@@ -926,13 +926,14 @@ when a period has no applicable records, as required for a joint eDavki submissi
 
 **Important:**
 - KIR/KPR is available only to entities whose country code is `SI`
-- Draft, voided, and deleted documents are excluded
+- Draft and deleted documents and voided credit notes are excluded. A voided invoice is excluded together with the credit note created when it was voided if both fall in the same period. If that credit note falls in another period, the invoice is reported in its own period and the credit note in its own. A voided invoice without such a credit note is excluded
 - Domestic outgoing advances are included as separate KIR rows and their allocated net/VAT amounts are subtracted from the linked final invoice. For intra-EU B2B supplies, goods prepayments are omitted and not deducted; only the classified service component is reported in P10 and deducted from the final invoice. A fully prepaid reportable service still emits the final reconciliation row with P10 empty/zero
 - Third-country outgoing documents use the persisted item tax treatment: bases with an explicit 0% tax row map to P7, while no-tax net amounts (including unrated summary bases) map to P27. Mixed documents are split between both fields. Product/service classification and customer geography are not substitutes for tax treatment; the legacy `export` transaction type remains an explicit goods-export marker and maps to P7
 - Domestic and intra-EU B2C outgoing documents fail closed when any net base is 0%, no-tax, unrated, or does not reconcile to the explicit tax summaries; an exemption semantic is required before those amounts can be placed safely
 - The selected month or quarter includes the complete final calendar day
 - Customer identity fields P5/P6/P6DS are omitted for end consumers
-- KIR uses the issued-document date for period selection and P2/P4. KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
+- KIR P2/P4 are the issued-document date. An invoice issued before 2026-11-01 is selected by its issue date. An invoice issued from 2026-11-01 is selected by its VAT tax point: the end of the service period (`date_service_to`, else `date_service`, else `date`), or the payment date when one payment received before the service covers the whole total. A part prepayment keeps the default tax point and is returned as a warning by the VAT return preview. An invoice issued after the KIR cut-off of its tax-point period is selected by its issue date, and the preview warns when it charges VAT. Credit notes and advance invoices are selected by their issue date
+- KPR uses the receipt date (falling back to supplier-document date) for period selection and P2/P4, while P5 remains the supplier-document date. Dedicated reporting state and post-export locking are deferred
 - An included AP document must have its own supplier-document date for KPR P5; receipt date is never substituted into P5
 - Reportable intra-EU AP purchases require both the supplier VAT number and an EU supplier country code so KPR P7/P7DS can be emitted together
 - P6/P6DS (KIR) and P7/P7DS (KPR) are reported as a pair. The country is the address country; an EU VAT ID prefix that differs from it takes precedence, and P6DS/P7DS is the ID without its prefix. A third-country VAT ID is reported whole in P6DS/P7DS with the country field empty. Greek `EL` prefixes are normalized to FURS country code `GR`
@@ -946,6 +947,7 @@ when a period has no applicable records, as required for a joint eDavki submissi
 - Cross-border supplier-charged foreign VAT is excluded. Mixing it with Slovenian-reportable reverse-charge VAT is rejected as ambiguous
 - Customs imports and fixed-asset KPR columns P12/P13/P15/P16 are not currently supported; the exporter does not infer either treatment from supplier geography, item descriptions, or financial categories
 - Ambiguous domestic outgoing 0% supplies, unknown transaction types, unsupported tax rates, missing EUR conversions, and amounts outside the FURS XSD bounds are rejected with HTTP 422 instead of producing an unsafe filing
+- A 422 caused by document data lists the affected documents in `cause.documents` (`number`, `type`, `reason`), up to 100, with the full count in `cause.total_documents`
 - Entity must have a valid 8-digit Slovenian tax number (SI prefix is automatically removed)
 
  * @summary Generate combined KIR/KPR VAT ledgers
@@ -1521,6 +1523,7 @@ export declare const PreviewVatReturnResponse: zod.ZodObject<{
         due_date: zod.ZodString;
         kir_kpr_prefill_cutoff: zod.ZodString;
     }, zod.z.core.$strip>;
+    rpo_required: zod.ZodOptional<zod.ZodBoolean>;
     boxes: zod.ZodObject<{
         "11": zod.ZodString;
         "12": zod.ZodString;