@spaceinvoices/js-sdk 13.9.0 → 13.10.0

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

@@ -782,8 +782,12 @@ export type updateExpenseResponse = (updateExpenseResponseSuccess | updateExpens
 export declare const getUpdateExpenseUrl: (id: string) => string;
 export declare const updateExpense: (id: string, updateExpenseBody: UpdateExpenseBody, options?: RequestInit) => Promise<updateExpenseResponse>;
 /**
- * Only draft expenses can be deleted; posted expenses must be voided instead. The request fails with 409 while automatic recognition of the draft's document is queued or processing.
- * @summary Delete draft expense
+ * 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).
+
+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
  */
 export type deleteExpenseResponse204 = {
     data: void;
@@ -809,6 +813,10 @@ export type deleteExpenseResponse409 = {
     data: IdempotencyError;
     status: 409;
 };
+export type deleteExpenseResponse422 = {
+    data: Error;
+    status: 422;
+};
 export type deleteExpenseResponse500 = {
     data: Error;
     status: 500;
@@ -820,7 +828,7 @@ export type deleteExpenseResponse503 = {
 export type deleteExpenseResponseSuccess = (deleteExpenseResponse204) & {
     headers: Headers;
 };
-export type deleteExpenseResponseError = (deleteExpenseResponse400 | deleteExpenseResponse401 | deleteExpenseResponse403 | deleteExpenseResponse404 | deleteExpenseResponse409 | deleteExpenseResponse500 | deleteExpenseResponse503) & {
+export type deleteExpenseResponseError = (deleteExpenseResponse400 | deleteExpenseResponse401 | deleteExpenseResponse403 | deleteExpenseResponse404 | deleteExpenseResponse409 | deleteExpenseResponse422 | deleteExpenseResponse500 | deleteExpenseResponse503) & {
     headers: Headers;
 };
 export type deleteExpenseResponse = (deleteExpenseResponseSuccess | deleteExpenseResponseError);

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

@@ -782,8 +782,12 @@ export type updateExpenseResponse = (updateExpenseResponseSuccess | updateExpens
 export declare const getUpdateExpenseUrl: (id: string) => string;
 export declare const updateExpense: (id: string, updateExpenseBody: UpdateExpenseBody, options?: RequestInit) => Promise<updateExpenseResponse>;
 /**
- * Only draft expenses can be deleted; posted expenses must be voided instead. The request fails with 409 while automatic recognition of the draft's document is queued or processing.
- * @summary Delete draft expense
+ * 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).
+
+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
  */
 export type deleteExpenseResponse204 = {
     data: void;
@@ -809,6 +813,10 @@ export type deleteExpenseResponse409 = {
     data: IdempotencyError;
     status: 409;
 };
+export type deleteExpenseResponse422 = {
+    data: Error;
+    status: 422;
+};
 export type deleteExpenseResponse500 = {
     data: Error;
     status: 500;
@@ -820,7 +828,7 @@ export type deleteExpenseResponse503 = {
 export type deleteExpenseResponseSuccess = (deleteExpenseResponse204) & {
     headers: Headers;
 };
-export type deleteExpenseResponseError = (deleteExpenseResponse400 | deleteExpenseResponse401 | deleteExpenseResponse403 | deleteExpenseResponse404 | deleteExpenseResponse409 | deleteExpenseResponse500 | deleteExpenseResponse503) & {
+export type deleteExpenseResponseError = (deleteExpenseResponse400 | deleteExpenseResponse401 | deleteExpenseResponse403 | deleteExpenseResponse404 | deleteExpenseResponse409 | deleteExpenseResponse422 | deleteExpenseResponse500 | deleteExpenseResponse503) & {
     headers: Headers;
 };
 export type deleteExpenseResponse = (deleteExpenseResponseSuccess | deleteExpenseResponseError);

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

@@ -2293,8 +2293,12 @@ export declare const UpdateExpenseResponse: zod.ZodObject<{
     has_attachment: zod.ZodBoolean;
 }, zod.z.core.$strip>;
 /**
- * Only draft expenses can be deleted; posted expenses must be voided instead. The request fails with 409 while automatic recognition of the draft's document is queued or processing.
- * @summary Delete draft expense
+ * 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).
+
+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
  */
 export declare const deleteExpensePathIdRegExp: RegExp;
 export declare const DeleteExpenseParams: zod.ZodObject<{

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

@@ -2293,8 +2293,12 @@ export declare const UpdateExpenseResponse: zod.ZodObject<{
     has_attachment: zod.ZodBoolean;
 }, zod.z.core.$strip>;
 /**
- * Only draft expenses can be deleted; posted expenses must be voided instead. The request fails with 409 while automatic recognition of the draft's document is queued or processing.
- * @summary Delete draft expense
+ * 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).
+
+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
  */
 export declare const deleteExpensePathIdRegExp: RegExp;
 export declare const DeleteExpenseParams: zod.ZodObject<{

package/package.json

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