jaz-clio 5.58.5 → 5.58.7

package/assets/skills/api/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-api
-version: 5.58.5
+version: 5.58.7
 description: >-
   Use this skill whenever you call, debug, or review code that touches the Jaz
   REST API. Covers field names, response shapes, 159 production gotchas, error
@@ -70,7 +70,7 @@ The rest of this skill — field names, gotchas, error catalog, dependency order
 13. **Invoice/bill number is `reference`** — not `referenceNumber`.
 
 ### Transaction Creation
-14. **`saveAsDraft` has OPPOSITE defaults on the two surfaces.** Raw REST: omitting it creates a FINALIZED transaction (`false`). MCP/CLI tools: creates for invoices, bills, both credit notes, journals, sale quotes, purchase requests/orders, and the order-conversions inject `true` — omitting it creates a DRAFT; pass `saveAsDraft: false` to post immediately. When the landing state matters, pass the field explicitly and read `status` off the create response rather than assuming either default. (Cash entries and cash transfers are currently unreliable around this flag — pass it explicitly and verify `status`.)
+14. **`saveAsDraft` has OPPOSITE defaults on the two surfaces.** Raw REST: omitting it creates a FINALIZED transaction (`false`). MCP/CLI tools: creates for invoices, bills, both credit notes, journals, sale quotes, purchase requests/orders, and the order-conversions inject `true` — omitting it creates a DRAFT; pass `saveAsDraft: false` to post immediately. When the landing state matters, pass the field explicitly and read `status` off the create response rather than assuming either default. Cash entries and cash transfers are the exception on both surfaces: they have no draft state, so `saveAsDraft: true` is refused with a 422 and the tools do not offer the field at all.
 15. **If `saveAsDraft: false`** (or omitted on the raw REST surface — see Rule 14), every lineItem MUST have `accountResourceId`.
 16. **Phones MUST be E.164** — `+65XXXXXXXX` (SG), `+63XXXXXXXXXX` (PH). No spaces.
 

package/assets/skills/api/references/errors.md

@@ -682,13 +682,18 @@ Journals support a top-level `currency` object to create entries in a foreign cu
 
 ## Cash Entry Errors
 
-### Missing saveAsDraft field (422)
-**Cause**: Omitting `saveAsDraft` from `POST /cash-in-entries` or `POST /cash-out-entries`.
-**Fix**: `saveAsDraft` is required on cash journal endpoints. Always include it:
+### saveAsDraft: true on a cash endpoint (422)
+```
+Cash entries are always recorded as active and cannot be saved as a draft
+Cash transfers are always recorded as active and cannot be saved as a draft
+```
+**Cause**: Sending `saveAsDraft: true` to `POST /cash-in-entries`, `POST /cash-out-entries` or `POST /cash-transfers`. The accounting service records every direct cash journal ACTIVE, so the flag cannot be honoured; the API refuses it rather than dropping it and handing back a posted entry.
+**Fix**: Send `false`, or omit it (the endpoint defaults to `false`). There is no draft to finalize later.
 ```json
 { "saveAsDraft": false, "reference": "CI-001", "valueDate": "2026-02-08",
   "accountResourceId": "uuid-bank", "lines": [...] }
 ```
+The same applies on update: `PUT /cash-in-entries/:id` with `saveAsDraft: true` returns 422 `Journal is not draft`, because the stored entry never is one.
 
 ### Wrong structure — flat fields vs lines
 **Cause**: Using flat structure with `amount`, `bankAccountResourceId`, `description` fields.

package/assets/skills/api/references/field-map.md

@@ -285,7 +285,7 @@ Uses `purchaseAmount` + `purchaseDate` + `effectiveLife` + `purchaseAssetAccount
 | `description` | NOT USED | Cash entries do not have a flat `description` field |
 | `bankAccount` | `accountResourceId` (top level) | Same as above |
 | offset account | `lines[].accountResourceId` | The offsetting account goes in `lines` |
-| (omit saveAsDraft) | `saveAsDraft` | **REQUIRED** — must be included on cash-in and cash-out entries |
+| (omit saveAsDraft) | `saveAsDraft` | Send `false` or omit. `true` is refused with a 422 — cash entries have no draft state |
 
 ## Cash Entries (LIST/GET response shape — DIFFERENT from CREATE!)
 

package/assets/skills/cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-cli
-version: 5.58.5
+version: 5.58.7
 description: >-
   Use this skill when running Clio CLI commands, building shell scripts with
   Clio, debugging auth issues, understanding --json output, paginating results,
@@ -380,7 +380,7 @@ clio ct loan --principal 100000 --rate 5 --term 60 --start-date 2026-01-01 \
 1. **Pipe JSON to jq**: `clio invoices list --json | jq '.data[] | {ref: .reference, amount: .totalAmount}'`
 2. **Export to CSV**: `clio contacts list --all --format csv > contacts.csv`
 3. **Multi-org scripts**: `clio invoices list --org acme-sg --json && clio invoices list --org acme-ph --json`
-4. **Draft-then-finalize**: The CLI defaults to saving as draft (overrides the API default of `saveAsDraft: false`). Use `--finalize` to create a finalized transaction immediately. Note: cash entries (`cash-in`, `cash-out`) do NOT override — they follow the API default (`saveAsDraft: false`, i.e. finalized).
+4. **Draft-then-finalize**: The CLI defaults to saving as draft (overrides the API default of `saveAsDraft: false`). Use `--finalize` to create a finalized transaction immediately. Note: `cash-in`, `cash-out` and `cash-transfer` have no draft state and so take no `--finalize` — they always post ACTIVE.
 5. **Idempotent creates**: Use `--input` with the same JSON to get consistent results. The API dedup guards catch duplicate contacts, items, and accounts.
 6. **Check before bulk ops**: Always preview with `--json | jq length` before piping IDs into `quick-fix`.
 7. **Offline calculators for exploration**: `clio calc` commands need no auth -- use them to explore scenarios before committing with `clio ct`.

package/assets/skills/cli/references/agent-gotchas.md

@@ -5,7 +5,7 @@
 
 ---
 
-1. **Cash entries finalize immediately.** `clio cash-in` and `clio cash-out` default to `saveAsDraft: false` (API default). Unlike invoices/bills/journals which the CLI overrides to draft. Use `--finalize` on invoices to finalize; cash entries are already final.
+1. **Cash entries and transfers post ACTIVE and take no `--finalize`.** `clio cash-in`, `clio cash-out` and `clio cash-transfer` have no draft state at all — the API refuses `saveAsDraft: true` with a 422 — so there is no flag to pass and nothing to finalize afterwards. Invoices, bills and journals are the ones the CLI saves as draft and `--finalize` posts.
 
 2. **Line-item account resolution is NOT fuzzy.** The `accountResourceId` field inside `--lines` JSON arrays requires a UUID or exact account name. Fuzzy matching only works for top-level flags (`--contact`, `--account`). Always resolve accounts first: `clio accounts list --json | jq '.data[] | {name, id: .resourceId}'`.
 

package/assets/skills/cli/references/field-guide.md

@@ -68,7 +68,7 @@ Use in search: `clio invoices search --status UNPAID --json`
 
 1. **Create returns minimal response** — only `{ "resourceId": "uuid" }`. Run `clio invoices get <id> --json` for full data.
 2. **Line-item accounts don't fuzzy-resolve** — `--lines` JSON requires exact account name or UUID. Top-level `--account` fuzzy-resolves.
-3. **Transaction creates default to draft** — invoices, bills, journals, cash entries, credit notes and orders. Use `--finalize` to create as finalized (UNPAID for invoices, ACTIVE for journals). Master data has no draft state: contacts, items, accounts, tags, tax profiles and the rest are created live, and accept no `--finalize`.
+3. **Transaction creates default to draft** — invoices, bills, journals, credit notes and orders. Use `--finalize` to create as finalized (UNPAID for invoices, ACTIVE for journals). Cash entries and cash transfers are the exception: they post ACTIVE and accept no `--finalize`. Master data has no draft state either: contacts, items, accounts, tags, tax profiles and the rest are created live.
 4. **`--offset` is page number (0-indexed)** — not row skip count. offset=0 + limit=100 = page 1.
 5. **`customer` is boolean** — `--customer true`, not `--customer "Acme"`.
 6. **Dates are YYYY-MM-DD** — org-local timezone. API returns epoch ms but CLI formats them.

package/assets/skills/conversion/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-conversion
-version: 5.58.5
+version: 5.58.7
 description: >-
   Use this skill when migrating accounting data into Jaz — importing from Xero,
   QuickBooks, Sage, MYOB, or Excel exports. Covers the full conversion pipeline:

package/assets/skills/jaz-kit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-kit
-version: 5.58.5
+version: 5.58.7
 description: >-
   Use this skill when an accountant, bookkeeper, or owner is running real books
   in Jaz across one or more organizations from the terminal — setting up a

package/assets/skills/jaz-pseudo-sql/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-pseudo-sql
-version: 5.58.5
+version: 5.58.7
 description: >-
   Use this skill when answering ad-hoc data questions that aren't covered by
   download_export (canonical reports — anomaly, audit, aging, P&L, BS, GL,

package/assets/skills/jobs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-jobs
-version: 5.58.5
+version: 5.58.7
 description: >-
   Use this skill for recurring accounting workflows — month/quarter/year-end
   close, bank reconciliation, GST/VAT filing, payment runs, credit control,

package/assets/skills/transaction-recipes/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-recipes
-version: 5.58.5
+version: 5.58.7
 description: >-
   Use this skill when modeling complex multi-step accounting transactions —
   anything that spans multiple periods, involves changing amounts, or requires

package/assets/skills/transaction-recipes/references/fixed-deposit.md

@@ -100,10 +100,10 @@ Verify after finalize:
 - Assert: `balance['Interest Income'] (period MTD) == schedule[periodIndex].accrualAmount`.
 - `balance['Fixed Deposit Receivable']` stays at `100,000` until maturity.
 
-At maturity (month 12), finalize the maturity cash-in:
+At maturity (month 12), the maturity cash-in needs no finalize step — a cash entry is recorded ACTIVE the moment it is created and has no draft state. Edit it only if the amounts changed:
 ```
 **STOP — not selectable by filter.** Journals carry no capsule or fixed-asset link in either direction (`JournalFilter` declares neither; a journal row has no such field even at `view: 'full'`; `GET /capsules/{id}` returns only a `totalTransactions` count — measured 2026-09-07). A date+status search returns every matching DRAFT in the org, so it must never feed `bulk_update_journals` or `delete_journal`. Surface the capsule and its expected count to the practitioner and let them identify the journals.
-update_cash_in(resourceId: <cash-in id>, saveAsDraft: false)
+update_cash_in(resourceId: <cash-in id>, lines: [...])   # only to correct it
 ```
 
 Verify after maturity:

package/assets/skills/transaction-recipes/references/provisions.md

@@ -118,12 +118,12 @@ This is in `year-end-close.md` Y5.
 ### Step 7 — Settlement (final period)
 
 When settlement date arrives:
-- Finalize the settlement cash-out: `update_cash_in(resourceId: <settlement id>, saveAsDraft: false)`.
+- The settlement cash-out needs no finalize step — a cash entry is recorded ACTIVE on creation and has no draft state.
 - Verify: `balance['Provision for Warranties'] == 0`; `balance['Cash']` reduced by 500,000.
 - Close capsule: a manual `update_capsule(title: '<original> [CLOSED]')` (the API has no `status` field for capsules — closure is informational only).
 
 If actual settlement amount differs from estimated $500,000 (highly likely for warranty / decommissioning):
-- Edit the settlement cash-out before finalizing: `update_cash_out_entry(resourceId: <id>, lines: [{accountResourceId: <Provision>, amount: <actual>}, ...])`.
+- Edit the settlement cash-out to the actual amount: `update_cash_out(resourceId: <id>, lines: [{accountResourceId: <Provision>, amount: <actual>}, ...])`.
 - Post a true-up journal for the difference: Dr/Cr Warranty Expense for the over/under-provision. (If under-provided: Dr Warranty Expense / Cr Cash for the shortfall. If over-provided: Dr Provision / Cr Warranty Expense for the reversal.)
 
 ---
@@ -137,7 +137,7 @@ If actual settlement amount differs from estimated $500,000 (highly likely for w
 | `plan_recipe` | 422 `rate_invalid` | Discount rate must be > 0. Per IAS 37.47, use a pre-tax rate reflecting current market + obligation-specific risks. SG: typically gov't bond rate + risk premium. |
 | `execute_recipe` | 422 `account_not_found` for `Finance Cost` | Step 3 incomplete. Create via `create_account(accountType: 'Finance Cost', name: 'Finance Cost')`. Note `Finance Cost` is both a valid account TYPE and the account NAME here — the error refers to the missing account, not a bad type. |
 | Step 6 remeasurement | Recipe doesn't natively support mid-life remeasurement | Manual journal + delete remaining DRAFT unwinding journals + re-execute recipe for remaining term. |
-| Step 7 actual settlement ≠ estimated | (always, for real-world provisions) | Edit settlement cash-out via `update_cash_out_entry` before finalizing, post true-up journal for the delta. |
+| Step 7 actual settlement ≠ estimated | (always, for real-world provisions) | Edit settlement cash-out via `update_cash_out`, post true-up journal for the delta. |
 | Provision presented as Operating Expense vs Finance Cost confusion | (presentation) | Per IAS 37.84, the unwinding charge is presented in P&L as a Finance Cost (separate from the recognition expense which is Operating Expense). Practitioner judgment if jurisdiction disagrees. |
 
 ---