jaz-clio 5.46.14 → 5.47.1

package/assets/skills/api/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-api
-version: 5.46.14
+version: 5.47.1
 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
@@ -115,7 +115,7 @@ The rest of this skill — field names, gotchas, error catalog, dependency order
 28. **CN refunds use the same Payment shape** as invoice/bill payments — `paymentAmount`, `transactionAmount`, `accountResourceId`, `paymentMethod`, `valueDate`, `reference`. The API also accepts aliases `refundAmount`/`refundMethod` (see Rule 53) but prefer canonical `paymentAmount`/`paymentMethod` for consistency.
 
 ### Inventory Items
-29. **Inventory items require**: `unit` (e.g., `"pcs"`), `costingMethod` (`"FIXED"` or `"WAC"`), `cogsResourceId`, `blockInsufficientDeductions`, `inventoryAccountResourceId`. `purchaseAccountResourceId` MUST be Inventory-type CoA.
+29. **Inventory items** (`POST /inventory-items`, verified live 2026-09-02): required are `itemCode`, `name`, `unit` (e.g. `"pcs"` — a blank unit returns `ITEM_UNIT_EMPTY_ERROR`), `costingMethod` (`"FIXED"` or `"WAC"`), `cogsResourceId` and `blockInsufficientDeductions` (send `false` explicitly — omitting it 422s, it is not defaulted server-side). Send `name`: the endpoint declares no `name` property and marks `internalName` required, but the API populates `internalName` from the `name` you send. The two account links are TYPE-constrained and the errors name the type: `cogsResourceId` must be **Direct Costs** (`INVALID_ACCOUNT_TYPE_DIRECT_COST`), `purchaseAccountResourceId` must be **Inventory** (`INVALID_ACCOUNT_TYPE_INVENTORY`) — an inventory purchase debits the asset, and COGS is recognised on sale. The API reports `purchaseAccountResourceId`, `saleAccountResourceId`, `appliesToSale` and `appliesToPurchase` as "required if [cogsResourceId] is present" — but `cogsResourceId` is itself always required, so all four are unconditional too. `appliesToSale` and `appliesToPurchase` must both be **`true`**, not merely present: `false` returns `APPLIES_TO_SALE_ERROR` / `APPLIES_TO_PURCHASE_ERROR` ("must be true when cogs selected"), so an inventory-tracked item with COGS is necessarily both sale- and purchase-applicable. There is no `inventoryAccountResourceId` — it appears in no request schema and a create succeeds without it.
 30. **Delete inventory items via `DELETE /items/:id`** — not `/inventory-items/:id`.
 
 ### Cash Transfers

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

@@ -882,7 +882,7 @@ Always wrap in `{ payments: [...] }` even for single payment.
 **CRITICAL notes from live testing**:
 - POST uses `name`, GET returns both `customFieldName` and `name`
 - Valid `type` values: `"TEXT"`, `"DATE"`, `"DROPDOWN"` (UPPERCASE)
-- `printOnDocuments` is REQUIRED — omitting it causes 400
+- `printOnDocuments` is REQUIRED and is not defaulted server-side — omitting it returns 422 `printOnDocuments is a required field` (probed 2026-09-02; recorded as a 400 before that). `create_custom_field` sends `false` when you omit it.
 - Do NOT send `appliesTo` field — causes "Invalid request body"
 - Only send: `name`, `type`, `printOnDocuments` (and `options` for DROPDOWN)
 - For DROPDOWN type, `options` array works (without `appliesTo`)
@@ -949,7 +949,7 @@ Returns full custom field definition including `applyToSales`, `applyToPurchase`
 ```json
 // Request:
 {
-  "internalName": "Widget A",
+  "name": "Widget A",
   "itemCode": "WDG-A",
   "unit": "pcs",
   "appliesToSale": true,
@@ -964,8 +964,7 @@ Returns full custom field definition including `applyToSales`, `applyToPurchase`
   "purchaseTaxProfileResourceId": "uuid-tax",
   "costingMethod": "WAC",
   "cogsResourceId": "uuid-direct-costs",
-  "blockInsufficientDeductions": false,
-  "inventoryAccountResourceId": "uuid-inventory-account"
+  "blockInsufficientDeductions": false
 }
 
 // Response:
@@ -973,10 +972,15 @@ Returns full custom field definition including `applyToSales`, `applyToPurchase`
 ```
 
 **CRITICAL notes from live testing**:
+- Send `name`, not `internalName`. The endpoint declares no `name` property and marks `internalName` required, but the API populates `internalName` from the `name` you send (verified by readback 2026-09-02)
 - `unit` is REQUIRED (e.g., `"pcs"`, `"box"`, `"kg"`) — omitting causes ITEM_UNIT_EMPTY_ERROR
+- `blockInsufficientDeductions` is REQUIRED and is NOT defaulted server-side — omitting it fails with "blockInsufficientDeductions is a required field"
 - `costingMethod` must be `"FIXED"` or `"WAC"` (NOT `"FIXED_COST"`)
-- `purchaseAccountResourceId` MUST point to an Inventory-type CoA account (NOT Direct Costs) — wrong type causes INVALID_ACCOUNT_TYPE_INVENTORY
-- `inventoryAccountResourceId` also must be Inventory-type
+- `cogsResourceId` is required, and MUST point to a Direct Costs account — wrong type causes INVALID_ACCOUNT_TYPE_DIRECT_COST
+- `purchaseAccountResourceId` MUST point to an Inventory-type CoA account (NOT Direct Costs) — wrong type causes INVALID_ACCOUNT_TYPE_INVENTORY. An inventory purchase debits the asset; COGS is recognised on sale
+- Because `cogsResourceId` is always required, so are `purchaseAccountResourceId`, `saleAccountResourceId`, `appliesToSale` and `appliesToPurchase` — the API reports them as "required if [cogsResourceId] is present", but that condition always holds
+- `appliesToSale` and `appliesToPurchase` must both be `true`, not merely present: `false` returns APPLIES_TO_SALE_ERROR / APPLIES_TO_PURCHASE_ERROR, "must be true when cogs selected". An inventory-tracked item with COGS is necessarily both sale- and purchase-applicable
+- There is no `inventoryAccountResourceId` — it appears in no request schema and a create succeeds without it
 - Delete inventory items via `DELETE /items/:id` (NOT `/inventory-items/:id`)
 - `GET /inventory-item-balance/:id` returns balance per item
 - `GET /inventory-balances/:status` currently returns 500 (known bug)

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

@@ -90,9 +90,10 @@ Or call `list_account_classifications` — authoritative for that organisation.
 
 ## Custom Field Errors
 
-### "Invalid request body" (400) — missing printOnDocuments
-**Cause**: Missing the required `printOnDocuments` field.
-**Fix**: Always include `printOnDocuments: false` (or `true`) in POST body.
+### "printOnDocuments is a required field" (422) — missing printOnDocuments
+**Cause**: Missing the required `printOnDocuments` field. It is not defaulted server-side.
+**Fix**: Always include `printOnDocuments: false` (or `true`) in POST body. `create_custom_field` now sends `false` when you omit it, so this only bites a direct API caller.
+**Note**: recorded here as a 400 "Invalid request body" until 2026-09-02, when a live probe returned `422 validation_error` with the field named. Either the API tightened or the original entry generalised from a different malformed body; the 422 is what it returns today.
 ```json
 { "name": "PO Number", "type": "TEXT", "printOnDocuments": false }
 ```

package/assets/skills/api/references/full-api-surface.md

@@ -259,7 +259,7 @@ Body for all three: `{ items: [{btResourceId: "<uuid>", btType: "SALE|PURCHASE|S
 | DELETE | `/items/:resourceId` | Delete item |
 | POST | `/items/search` | Advanced search with filters |
 | POST | `/items/bulk-upsert` | Bulk create/update items (max 500) |
-| POST | `/inventory-items` | Create inventory item (needs `unit`, `costingMethod`, `cogsResourceId`, `blockInsufficientDeductions`, `inventoryAccountResourceId`) |
+| POST | `/inventory-items` | Create inventory item (needs `name`, `itemCode`, `unit`, `costingMethod`, `cogsResourceId` (Direct Costs), `purchaseAccountResourceId` (Inventory), `saleAccountResourceId`, `blockInsufficientDeductions`) |
 | GET | `/inventory-items` | List inventory items |
 | GET | `/inventory-item-balance/:resourceId` | Get inventory balance |
 | GET | `/inventory-balances/:balanceStatus` | List by status (**known 500 bug**) |

package/assets/skills/cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-cli
-version: 5.46.14
+version: 5.47.1
 description: >-
   Use this skill when running Clio CLI commands, building shell scripts with
   Clio, debugging auth issues, understanding --json output, paginating results,

package/assets/skills/cli/references/command-catalog.md

@@ -362,6 +362,9 @@ Body shape (all 3): `{ items: [{ btResourceId, btType }] }` with `btType ∈ {SA
 |------------|-----------|
 | `items` | `--limit`, `--offset`, `--all`, `--format`, `--json` |
 | `balance <itemId>` | `--json` |
+| `create` | `--item-code`, `--name`, `--unit`, `--costing-method`, `--cogs-account`, `--purchase-account`, `--sale-account`, `--block-insufficient`, `--input` |
+
+All seven of `--item-code`, `--name`, `--unit`, `--costing-method`, `--cogs-account`, `--purchase-account` and `--sale-account` are required. `--cogs-account` must be a Direct Costs account and `--purchase-account` an Inventory account. There are no `--sale`/`--purchase` flags: the API rejects either as false once COGS is set, so both are always sent as `true`.
 
 ---
 

package/assets/skills/conversion/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-conversion
-version: 5.46.14
+version: 5.47.1
 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.46.14
+version: 5.47.1
 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.46.14
+version: 5.47.1
 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.46.14
+version: 5.47.1
 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.46.14
+version: 5.47.1
 description: >-
   Use this skill when modeling complex multi-step accounting transactions —
   anything that spans multiple periods, involves changing amounts, or requires