@spaceinvoices/js-sdk 14.4.0 → 14.5.0

package/dist/generated/expenses/expenses.d.cts

@@ -885,7 +885,7 @@ export declare const updateExpense: (id: string, updateExpenseBody: UpdateExpens
 /**
  * Deletes an expense together with all of its attachments, including the source file of an OCR recognition. Draft expenses can always be deleted. Posted expenses (including voided ones) can be deleted only when they were entered manually (`creation_source=standard`) or created by OCR (`creation_source=ocr`) and did not come from a received e-invoice; expenses created through `/expenses/custom`, legacy-migrated expenses and expenses from received e-invoices can only be voided (422).
 
-An expense with payments cannot be deleted (422): delete the payments first, or void the expense. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
+The expense's payments are deleted with it, and each emits a `payment.deleted` event, exactly like deleting the payment on its own. An expense with credit-note settlements applied to it (or recorded by it) cannot be deleted (422): void it instead. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
 
 Deleting does not change usage: the expense still counts toward the document count of the billing period it was created in, and OCR pages that were scanned stay counted (their usage is kept in the metered usage ledger). Submitting the same document again creates a new expense and a new recognition that is counted again. Stock movements and accounting-recognition entries of the expense are removed.
  * @summary Delete expense

package/dist/generated/expenses/expenses.d.ts

@@ -885,7 +885,7 @@ export declare const updateExpense: (id: string, updateExpenseBody: UpdateExpens
 /**
  * Deletes an expense together with all of its attachments, including the source file of an OCR recognition. Draft expenses can always be deleted. Posted expenses (including voided ones) can be deleted only when they were entered manually (`creation_source=standard`) or created by OCR (`creation_source=ocr`) and did not come from a received e-invoice; expenses created through `/expenses/custom`, legacy-migrated expenses and expenses from received e-invoices can only be voided (422).
 
-An expense with payments cannot be deleted (422): delete the payments first, or void the expense. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
+The expense's payments are deleted with it, and each emits a `payment.deleted` event, exactly like deleting the payment on its own. An expense with credit-note settlements applied to it (or recorded by it) cannot be deleted (422): void it instead. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
 
 Deleting does not change usage: the expense still counts toward the document count of the billing period it was created in, and OCR pages that were scanned stay counted (their usage is kept in the metered usage ledger). Submitting the same document again creates a new expense and a new recognition that is counted again. Stock movements and accounting-recognition entries of the expense are removed.
  * @summary Delete expense

package/dist/generated-zod/expenses/expenses.d.cts

@@ -2790,7 +2790,7 @@ export declare const UpdateExpenseResponse: zod.ZodObject<{
 /**
  * Deletes an expense together with all of its attachments, including the source file of an OCR recognition. Draft expenses can always be deleted. Posted expenses (including voided ones) can be deleted only when they were entered manually (`creation_source=standard`) or created by OCR (`creation_source=ocr`) and did not come from a received e-invoice; expenses created through `/expenses/custom`, legacy-migrated expenses and expenses from received e-invoices can only be voided (422).
 
-An expense with payments cannot be deleted (422): delete the payments first, or void the expense. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
+The expense's payments are deleted with it, and each emits a `payment.deleted` event, exactly like deleting the payment on its own. An expense with credit-note settlements applied to it (or recorded by it) cannot be deleted (422): void it instead. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
 
 Deleting does not change usage: the expense still counts toward the document count of the billing period it was created in, and OCR pages that were scanned stay counted (their usage is kept in the metered usage ledger). Submitting the same document again creates a new expense and a new recognition that is counted again. Stock movements and accounting-recognition entries of the expense are removed.
  * @summary Delete expense

package/dist/generated-zod/expenses/expenses.d.ts

@@ -2790,7 +2790,7 @@ export declare const UpdateExpenseResponse: zod.ZodObject<{
 /**
  * Deletes an expense together with all of its attachments, including the source file of an OCR recognition. Draft expenses can always be deleted. Posted expenses (including voided ones) can be deleted only when they were entered manually (`creation_source=standard`) or created by OCR (`creation_source=ocr`) and did not come from a received e-invoice; expenses created through `/expenses/custom`, legacy-migrated expenses and expenses from received e-invoices can only be voided (422).
 
-An expense with payments cannot be deleted (422): delete the payments first, or void the expense. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
+The expense's payments are deleted with it, and each emits a `payment.deleted` event, exactly like deleting the payment on its own. An expense with credit-note settlements applied to it (or recorded by it) cannot be deleted (422): void it instead. While automatic recognition of the expense's document is still queued or processing, or has finished but its usage is not yet recorded, the request fails with 409 (try again shortly).
 
 Deleting does not change usage: the expense still counts toward the document count of the billing period it was created in, and OCR pages that were scanned stay counted (their usage is kept in the metered usage ledger). Submitting the same document again creates a new expense and a new recognition that is counted again. Stock movements and accounting-recognition entries of the expense are removed.
  * @summary Delete expense

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spaceinvoices/js-sdk",
-  "version": "14.4.0",
+  "version": "14.5.0",
   "description": "Official JavaScript/TypeScript SDK for the Space Invoices API",
   "author": "Space Invoices <support@spaceinvoices.com>",
   "license": "MIT",