Zenfinance

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Replacement category slug from get_user_context.orgs[].categories[].name (e.g. 'restaurants'); UUIDs also accepted. Must match income/expense kind. Omit/null to keep current."
+}

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Replacement category UUID from get_user_context.orgs[].categories[].id. Must match income/expense kind. Omit/null to keep current."
-}

Previous value: -"Replacement ISO 8601 date/time. Omit/null to keep current."New value: +"Replacement ISO 8601 timestamp, e.g. '2026-05-03T00:00:00-03:00'. Sent without an offset, the household's jurisdiction timezone is applied. Omit/null to keep current."

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Replacement tag UUIDs from get_user_context.transaction_tags[].id. Null=no change; []=clear all tags; list=replace all tags."
-}

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Replacement tag names from get_user_context.transaction_tags[].name (UUIDs also accepted). Null=no change; []=clear all tags; list=replace all tags."
+}

Previous value: -"Exclusive ISO 8601 end date. Defaults to now if omitted."New value: +"Exclusive ISO 8601 end timestamp. Sent without an offset, the household's jurisdiction timezone is applied. Defaults to now if omitted."

Previous value: -"Inclusive ISO 8601 start date. Defaults to start of current month if omitted."New value: +"Inclusive ISO 8601 start timestamp, e.g. '2026-05-01T00:00:00-03:00'. Sent without an offset, the household's jurisdiction timezone is applied. Defaults to start of current month if omitted."

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 500,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ALWAYS set this to the number of transaction rows you intend to send. If the server receives a different number (the client truncated your payload), it saves NOTHING and tells you how to resend safely."
+}

Previous value: -"ISO date or timestamp for the operation. Drives which month the batch shows up in on monthly cashflow reports; the per-transaction date stays the actual purchase date. Rules: for a single transaction or a same-period batch, set to the transaction date so a late-recorded purchase does not drift into today's month. For a credit card invoice: if the payment date falls in a different month than the invoice period (e.g. April invoice paid in May), use the close date — this keeps the batch in the correct spending month, not the payment month; if the payment date falls within the same month as the invoice period, use the payment date (actual cashflow, no misattribution). Leave null only when truly uncertain; the server defaults to now()."New value: +"ISO 8601 timestamp for the operation, e.g. '2026-05-31T00:00:00-03:00'. Include the UTC offset when known; sent without an offset, the household's jurisdiction timezone is applied (e.g. BR → America/Sao_Paulo). Drives which month the batch shows up in on monthly cashflow reports; the per-transaction date stays the actual purchase date. Rules: for a single transaction or a same-period batch, set to the transaction date so a late-recorded purchase does not drift into today's month. For a credit card invoice: if the payment date falls in a different month than the invoice period (e.g. April invoice paid in May), use the close date — this keeps the batch in the correct spending month, not the payment month; if the payment date falls within the same month as the invoice period, use the payment date (actual cashflow, no misattribution). Leave null only when truly uncertain; the server defaults to now()."

Previous value: -"Org UUID from get_user_context.orgs[].id."New value: +"Org UUID from get_user_context.orgs[].id (the org name also works)."

Previous value: -"Transaction lines to save under one Zen operation. Each item must include direction ('income' or 'expense'), amount, and category_id from get_user_context. When a user provides many files or a full year, process them without forcing one-file-at-a-time back-and-forth; group saves by source file or statement/bill period when useful for metadata and review. Omit account_id to use the Phase 1 default account. For credit-card bills, exclude previous-bill payment/total lines, save only installments present on this bill, fold clearly linked per-item taxes/fees into the purchase amount when supported by the statement/jurisdiction, skip fee/reimbursement ONLY when BOTH the original charge AND its refund for the same amount appear on the same bill (a true pair) — a standalone credit, estorno, or reimbursement that has no matching charge on this bill must be saved as income, not skipped, and do not invent FX rates; preserve original currency/amount in notes when not normalized. Optional fields: date, account_id, description, counterparty, statement_line_id."New value: +"Transaction lines to save under one Zen operation. Each item must include direction ('income' or 'expense'), amount, and category (slug like 'groceries' from get_user_context). Send the full statement in ONE call (up to 500 rows) and set expected_count so payload truncation is detected. When a user provides many files or a full year, process them without forcing one-file-at-a-time back-and-forth; group saves by source file or statement/bill period when useful for metadata and review. Omit account_id to use the Phase 1 default account. For credit-card bills, exclude previous-bill payment/total lines, save only installments present on this bill, fold clearly linked per-item taxes/fees into the purchase amount when supported by the statement/jurisdiction, skip fee/reimbursement ONLY when BOTH the original charge AND its refund for the same amount appear on the same bill (a true pair) — a standalone credit, estorno, or reimbursement that has no matching charge on this bill must be saved as income, not skipped, and do not invent FX rates; preserve original currency/amount in notes when not normalized. Optional fields: date, account_id, description, counterparty, statement_line_id, tags."

Added value: +{
+  "description": "Category slug from get_user_context.orgs[].categories[].name (e.g. 'groceries', 'salary'). Slugs are preferred — they are short and cannot be corrupted in transit. Category UUIDs are also accepted. The category's kind must match direction (income vs expense).",
+  "type": "string"
+}

Removed value: -{
-  "description": "Category tag UUID from get_user_context.orgs[].categories[].id.",
-  "type": "string"
-}

Previous value: -"Optional ISO 8601 transaction date/time. Defaults to the operation date. For card installments, use the actual purchase date as shown on the statement; operation_date handles monthly attribution separately."New value: +"Optional ISO 8601 transaction timestamp, e.g. '2026-05-03T00:00:00-03:00'. Include the UTC offset when known; if sent without an offset, the household's jurisdiction timezone is applied. Defaults to the operation date. For card installments, use the actual purchase date as shown on the statement; operation_date handles monthly attribution separately."

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Optional list of system tag UUIDs from get_user_context.transaction_tags[].id. Apply 'subscription' tag to any recurring fixed-period charge (streaming, SaaS, gym, apps, news). Apply 'tax_deductible' tag to expenses that may be deductible from personal income tax in the org's jurisdiction (e.g. Brazil IRPF: medical/health, education, pension contributions, qualifying donations, dependents expenses). A transaction may carry both tags. Omit or pass null to save without tags."
-}

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional list of system tag names from get_user_context.transaction_tags[].name (UUIDs also accepted). Apply 'subscription' to any recurring fixed-period charge (streaming, SaaS, gym, apps, news). Apply 'tax_deductible' to expenses that may be deductible from personal income tax in the org's jurisdiction (e.g. Brazil IRPF: medical/health, education, pension contributions, qualifying donations, dependents expenses). A transaction may carry both tags. Omit or pass null to save without tags."
+}

Previous value: -[
-  "direction",
-  "amount",
-  "category_id"
-]New value: +[
+  "direction",
+  "amount",
+  "category"
+]

Previous value: -"Budget entries to set or update. Each item must include category_id and amount. enabled defaults to true. Use amount=0 with enabled=false to disable a category budget."New value: +"Budget entries to set or update. Each item must include category (slug like 'groceries'; UUID also accepted) and amount. enabled defaults to true. Use amount=0 with enabled=false to disable a category budget."

Added value: +{
+  "description": "Category slug from get_user_context.orgs[].categories[].name (e.g. 'groceries'); UUIDs also accepted.",
+  "type": "string"
+}

Removed value: -{
-  "description": "Category tag UUID from get_user_context.orgs[].categories[].id.",
-  "type": "string"
-}

Previous value: -[
-  "category_id",
-  "amount"
-]New value: +[
+  "category",
+  "amount"
+]

Added value: +"Org purpose: household, personal, business, or other."

Added value: +"Category kind: income, expense, or transfer."

Added value: +"Product area this feedback relates to: onboarding, mcp_setup, household_setup, transactions, imports, categorization, budgets, monthly_summary, privacy_trust, pricing, performance, or other."

Added value: +"Feedback type: issue, suggestion, praise, question, rating, or observation."

Added value: +"Overall sentiment: positive, neutral, negative, or mixed."

Added value: +"Issue severity: low, medium, high, or critical."

Added value: +"'accept' to join the org as a member, or 'deny' to decline."