@spaceinvoices/js-sdk 11.0.1 → 11.1.0

package/dist/generated/entity-stats/entity-stats.d.cts

@@ -11,7 +11,7 @@ import type { Error, StatsQueryBatchRequest, StatsQueryBatchResponse, Validation
 
 Send an array of 1-25 queries. Queries share one read-only database snapshot and results are returned in the same order.
 
-**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes
+**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes, expenses
 
 **Metric types**: count, sum, avg, min, max
 
@@ -26,6 +26,7 @@ Send an array of 1-25 queries. Queries share one read-only database snapshot and
 - Include a sum of `financial_conversion_missing` in every financial query. A positive result means the aggregate is incomplete and must be shown as unavailable, rather than treating omitted conversion values as zero. For limited rankings, check missing conversions across the whole eligible population in a separate query before presenting the ranking. Historical copied foreign amounts without conversion evidence are not treated as valid 1:1 conversions.
 - Group invoice sales by `customer_key` and `customer_display_name` to keep linked customers stable across name changes; unlinked snapshots use a normalized-name fallback.
 - Date filters are inclusive calendar dates. Invoice overdue fields use the entity timezone; callers should construct reporting periods in that same timezone.
+- Expenses use the same `financial_eligible`, `financial_gross_converted`, `financial_conversion_missing`, `total_due_converted` and `overdue_bucket` fields as invoices, by expense date; `supplier_key`/`supplier_display_name` group by stable supplier identity.
 
 **Virtual fields for group_by**:
 - `day` - Calendar day (YYYY-MM-DD)

package/dist/generated/entity-stats/entity-stats.d.ts

@@ -11,7 +11,7 @@ import type { Error, StatsQueryBatchRequest, StatsQueryBatchResponse, Validation
 
 Send an array of 1-25 queries. Queries share one read-only database snapshot and results are returned in the same order.
 
-**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes
+**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes, expenses
 
 **Metric types**: count, sum, avg, min, max
 
@@ -26,6 +26,7 @@ Send an array of 1-25 queries. Queries share one read-only database snapshot and
 - Include a sum of `financial_conversion_missing` in every financial query. A positive result means the aggregate is incomplete and must be shown as unavailable, rather than treating omitted conversion values as zero. For limited rankings, check missing conversions across the whole eligible population in a separate query before presenting the ranking. Historical copied foreign amounts without conversion evidence are not treated as valid 1:1 conversions.
 - Group invoice sales by `customer_key` and `customer_display_name` to keep linked customers stable across name changes; unlinked snapshots use a normalized-name fallback.
 - Date filters are inclusive calendar dates. Invoice overdue fields use the entity timezone; callers should construct reporting periods in that same timezone.
+- Expenses use the same `financial_eligible`, `financial_gross_converted`, `financial_conversion_missing`, `total_due_converted` and `overdue_bucket` fields as invoices, by expense date; `supplier_key`/`supplier_display_name` group by stable supplier identity.
 
 **Virtual fields for group_by**:
 - `day` - Calendar day (YYYY-MM-DD)

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

@@ -19,4 +19,5 @@ export declare const StatsQueryRequestTable: {
     readonly items: "items";
     readonly invoice_taxes: "invoice_taxes";
     readonly credit_note_taxes: "credit_note_taxes";
+    readonly expenses: "expenses";
 };

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

@@ -19,4 +19,5 @@ export declare const StatsQueryRequestTable: {
     readonly items: "items";
     readonly invoice_taxes: "invoice_taxes";
     readonly credit_note_taxes: "credit_note_taxes";
+    readonly expenses: "expenses";
 };

package/dist/generated-zod/entity-stats/entity-stats.d.cts

@@ -11,7 +11,7 @@ import * as zod from "zod";
 
 Send an array of 1-25 queries. Queries share one read-only database snapshot and results are returned in the same order.
 
-**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes
+**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes, expenses
 
 **Metric types**: count, sum, avg, min, max
 
@@ -26,6 +26,7 @@ Send an array of 1-25 queries. Queries share one read-only database snapshot and
 - Include a sum of `financial_conversion_missing` in every financial query. A positive result means the aggregate is incomplete and must be shown as unavailable, rather than treating omitted conversion values as zero. For limited rankings, check missing conversions across the whole eligible population in a separate query before presenting the ranking. Historical copied foreign amounts without conversion evidence are not treated as valid 1:1 conversions.
 - Group invoice sales by `customer_key` and `customer_display_name` to keep linked customers stable across name changes; unlinked snapshots use a normalized-name fallback.
 - Date filters are inclusive calendar dates. Invoice overdue fields use the entity timezone; callers should construct reporting periods in that same timezone.
+- Expenses use the same `financial_eligible`, `financial_gross_converted`, `financial_conversion_missing`, `total_due_converted` and `overdue_bucket` fields as invoices, by expense date; `supplier_key`/`supplier_display_name` group by stable supplier identity.
 
 **Virtual fields for group_by**:
 - `day` - Calendar day (YYYY-MM-DD)
@@ -85,6 +86,7 @@ export declare const QueryEntityStatsBodyItem: zod.ZodObject<{
         items: "items";
         invoice_taxes: "invoice_taxes";
         credit_note_taxes: "credit_note_taxes";
+        expenses: "expenses";
     }>;
     date_from: zod.ZodOptional<zod.ZodString>;
     date_to: zod.ZodOptional<zod.ZodString>;
@@ -121,6 +123,7 @@ export declare const QueryEntityStatsBody: zod.ZodArray<zod.ZodObject<{
         items: "items";
         invoice_taxes: "invoice_taxes";
         credit_note_taxes: "credit_note_taxes";
+        expenses: "expenses";
     }>;
     date_from: zod.ZodOptional<zod.ZodString>;
     date_to: zod.ZodOptional<zod.ZodString>;

package/dist/generated-zod/entity-stats/entity-stats.d.ts

@@ -11,7 +11,7 @@ import * as zod from "zod";
 
 Send an array of 1-25 queries. Queries share one read-only database snapshot and results are returned in the same order.
 
-**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes
+**Available tables**: invoices, estimates, credit_notes, advance_invoices, payments, customers, items, invoice_taxes, credit_note_taxes, expenses
 
 **Metric types**: count, sum, avg, min, max
 
@@ -26,6 +26,7 @@ Send an array of 1-25 queries. Queries share one read-only database snapshot and
 - Include a sum of `financial_conversion_missing` in every financial query. A positive result means the aggregate is incomplete and must be shown as unavailable, rather than treating omitted conversion values as zero. For limited rankings, check missing conversions across the whole eligible population in a separate query before presenting the ranking. Historical copied foreign amounts without conversion evidence are not treated as valid 1:1 conversions.
 - Group invoice sales by `customer_key` and `customer_display_name` to keep linked customers stable across name changes; unlinked snapshots use a normalized-name fallback.
 - Date filters are inclusive calendar dates. Invoice overdue fields use the entity timezone; callers should construct reporting periods in that same timezone.
+- Expenses use the same `financial_eligible`, `financial_gross_converted`, `financial_conversion_missing`, `total_due_converted` and `overdue_bucket` fields as invoices, by expense date; `supplier_key`/`supplier_display_name` group by stable supplier identity.
 
 **Virtual fields for group_by**:
 - `day` - Calendar day (YYYY-MM-DD)
@@ -85,6 +86,7 @@ export declare const QueryEntityStatsBodyItem: zod.ZodObject<{
         items: "items";
         invoice_taxes: "invoice_taxes";
         credit_note_taxes: "credit_note_taxes";
+        expenses: "expenses";
     }>;
     date_from: zod.ZodOptional<zod.ZodString>;
     date_to: zod.ZodOptional<zod.ZodString>;
@@ -121,6 +123,7 @@ export declare const QueryEntityStatsBody: zod.ZodArray<zod.ZodObject<{
         items: "items";
         invoice_taxes: "invoice_taxes";
         credit_note_taxes: "credit_note_taxes";
+        expenses: "expenses";
     }>;
     date_from: zod.ZodOptional<zod.ZodString>;
     date_to: zod.ZodOptional<zod.ZodString>;