jaz-clio 5.44.0 → 5.45.0

package/assets/skills/api/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-api
-version: 5.44.0
+version: 5.45.0
 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
@@ -396,7 +396,7 @@ Bills, invoices, and credit notes share identical mandatory field specs. Adding
 
 121. **Intra-batch reference dedup is MERGE, not REJECT** — Two rows in the same bulk-upsert call sharing the same natural key (`invoiceReference`/`billReference`/etc.) are MERGED by the API (last row wins). If the user wants strict-uniqueness, dedup client-side first.
 
-122. **Fixed asset bulk upsert — date fields are inconsistent** — the bulk-upsert REQUEST has TWO different date conventions: `valueDate` is `YYYY-MM-DD` (string); `depreciationStartDate` is **epoch milliseconds** (number). Sending YYYY-MM-DD for `depreciationStartDate` returns generic 400 "Invalid request body" with no detail. The GET RESPONSE uses `purchaseDate` (different field from request `valueDate`). Sending `purchaseDate` in the request → same generic 400. Other fields: `cost` and `purchaseAmount` are synonyms; `effectiveLife` and `usefulLifeMonths` are synonyms. Required: `reference`, `registrationType` ("NEW" | "TRANSFER"). Recommended: `typeCode` (e.g. `FURNITURE_AND_FIXTURE`), `typeName`, `category` ("TANGIBLE" | "INTANGIBLE"), `cost`/`purchaseAmount`, `valueDate` (YYYY-MM-DD), `effectiveLife`/`usefulLifeMonths`, `depreciationMethod` (`STRAIGHT_LINE` | `NO_DEPRECIATION`), `purchaseAssetAccountResourceId` (UUIDv4), `depreciationExpenseAccountResourceId` (UUIDv4), `accumulatedDepreciationAccountResourceId`. To set `depreciationStartDate`: pass epoch ms OR omit (defaults to valueDate).
+122. **Fixed asset bulk upsert — dates are EPOCH MILLISECONDS** — the bulk-upsert REQUEST takes `purchaseDate` and `depreciationStartDate` as **epoch milliseconds** (numbers), unlike every other bulk-upsert (which takes `YYYY-MM-DD`). A date string returns a generic 400 "Invalid request body" with no detail. There is no `valueDate`, `cost`, `usefulLifeMonths`, `currencyCode`, `tags` or `resourceId` field on this endpoint — those are silently discarded; the wire names are `purchaseDate`, `purchaseAmount` and `effectiveLife`, and the natural key is `reference`. Required: `reference`, `registrationType` ("NEW" | "TRANSFER"). `NEW` also requires `purchaseBusinessTransactionType` ("PURCHASE" | "SALE" | "JOURNAL_MANUAL") + `purchaseBusinessTransactionResourceId` (the purchase LINE ITEM, not the bill/journal id); `TRANSFER` instead takes `accumulatedDepreciationAtTransferDate` + `bookValueAtTransferDate`. Recommended: `typeCode` (e.g. `FURNITURE_AND_FIXTURE`), `typeName`, `category` ("TANGIBLE" | "INTANGIBLE"), `purchaseAmount`, `purchaseDate`, `effectiveLife`, `depreciationMethod` (`STRAIGHT_LINE` | `NO_DEPRECIATION`), `purchaseAssetAccountResourceId` (UUIDv4), `depreciationExpenseAccountResourceId` (UUIDv4), `accumulatedDepreciationAccountResourceId`. Omit `depreciationStartDate` to default it to `purchaseDate`.
 
 ### Reconciliation actions (write-side)
 

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

@@ -82,7 +82,7 @@ All GET list endpoints and POST `/search` endpoints use **`limit`/`offset` pagin
     "resourceId": "31eb050a-...",
     "name": "Jaz Global SG",
     "currency": "SGD",
-    "countryCode": "SG",
+    "country": "SG",
     "status": "ACTIVE",
     "lockDate": null
   }

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

@@ -83,7 +83,7 @@ These aliases are applied by middleware on POST/PUT endpoints. The alias is only
 | `apiKey` header | `x-jk-api-key` | Custom header (not Authorization: Bearer) |
 | `org.id` | `data[0].resourceId` | Org endpoint returns a LIST |
 | `org.baseCurrency` | `data[0].currency` | Not `baseCurrency` |
-| `org.country` | `data[0].countryCode` | ISO 2-letter code |
+| `org.country` | `data[0].country` | ISO 2-letter code. NOT `countryCode` — that name is a deprecated alias, is optional, and may be absent from the response |
 
 ---
 
@@ -247,7 +247,7 @@ DIFFERENT shape from single create — easier to confuse.
 
 ### Bulk upsert (`POST /fixed-assets/bulk-upsert`) — REQUEST shape
 
-⚠️ **Date field is `valueDate`, NOT `purchaseDate`.** The GET response uses `purchaseDate`; the bulk-upsert REQUEST uses `valueDate`. Sending `purchaseDate` returns generic 400 "Invalid request body" with no detail. Most painful field-name asymmetry in the API.
+⚠️ **Both dates are EPOCH MILLISECONDS, not `YYYY-MM-DD`.** `purchaseDate` and `depreciationStartDate` are integers on this endpoint (every other bulk-upsert takes `YYYY-MM-DD`). A date string returns a generic 400 "Invalid request body" with no detail. There is no `valueDate`, `cost`, `usefulLifeMonths`, `currencyCode`, `tags` or `resourceId` field here — they are silently discarded.
 
 | Field | Required? | Notes |
 |-------|-----------|-------|
@@ -257,19 +257,22 @@ DIFFERENT shape from single create — easier to confuse.
 | `typeCode` | recommended | e.g. `FURNITURE_AND_FIXTURE`, `COMPUTER_AND_ELECTRONIC` |
 | `typeName` | recommended | Human label, e.g. `"Furniture and Fixtures"` |
 | `category` | recommended | `"TANGIBLE"` or `"INTANGIBLE"` |
-| `cost` OR `purchaseAmount` | recommended | Synonyms — both accepted |
-| `valueDate` | recommended | Acquisition date YYYY-MM-DD (NOT `purchaseDate`!) |
-| `currencyCode` | recommended | `"SGD"` flat string |
-| `depreciationStartDate` | optional | **EPOCH MILLISECONDS** (number, NOT YYYY-MM-DD — inconsistent with `valueDate` on the same endpoint). Sending YYYY-MM-DD → generic 400. Omit to default to `valueDate`. |
-| `effectiveLife` OR `usefulLifeMonths` | recommended | Months — synonyms |
+| `purchaseAmount` | recommended | Acquisition cost (there is no `cost` alias) |
+| `purchaseDate` | recommended | Acquisition date, **epoch milliseconds** |
+| `depreciationStartDate` | optional | **Epoch milliseconds.** Omit to default to `purchaseDate` |
+| `effectiveLife` | recommended | Months (there is no `usefulLifeMonths` alias) |
 | `depreciationMethod` | recommended | `"STRAIGHT_LINE"` or `"NO_DEPRECIATION"` |
 | `purchaseAssetAccountResourceId` | recommended | Asset account UUIDv4 |
 | `depreciationExpenseAccountResourceId` | recommended | Depreciation expense account UUIDv4 |
 | `accumulatedDepreciationAccountResourceId` | recommended | Accum dep account UUIDv4 |
+| `purchaseBusinessTransactionType` | required for `NEW` | `"PURCHASE"` \| `"SALE"` \| `"JOURNAL_MANUAL"` |
+| `purchaseBusinessTransactionResourceId` | required for `NEW` | Purchase LINE ITEM resourceId, must be UNLINKED |
+| `accumulatedDepreciationAtTransferDate` | `TRANSFER` only | Depreciation already booked in the source system |
+| `bookValueAtTransferDate` | `TRANSFER` only | Remaining undepreciated value |
 
 ### Single create (`POST /fixed-assets`)
 
-Uses `purchaseAmount` + `purchaseDate` + `effectiveLife` + `purchaseAssetAccountResourceId` + `depreciationExpenseAccountResourceId`. CLI command `clio fixed-assets create` mirrors this. **Different date field from bulk-upsert** — see warning above.
+Uses `purchaseAmount` + `purchaseDate` + `effectiveLife` + `purchaseAssetAccountResourceId` + `depreciationExpenseAccountResourceId`. CLI command `clio fixed-assets create` mirrors this. Same field names as bulk-upsert, but dates here are `YYYY-MM-DD` strings — see warning above.
 
 ---
 

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

@@ -813,7 +813,12 @@ single-create siblings do — the alias middleware rewrites the top-level body o
 these routes the aliased keys sit inside the `cashEntries[]` / `cashTransfers[]` rows. Send
 `valueDate` on bulk rows.
 
-### Record-list option pickers (4) — 2026-08-12
+### Record-list option pickers (4) — NOT WRAPPED
+
+These four exist in the REST API but this client has **no wrapper for them and no
+tool exposes them**, so they cannot be called from here. They are listed only so
+that looking for them and finding nothing is not mistaken for the catalog being
+incomplete. Reaching them needs a raw HTTP call.
 
 | Method | Path | Description |
 |--------|------|-------------|

package/assets/skills/api/references/search-enums.md

@@ -370,9 +370,12 @@ No enum fields on the top level. String filters: `resourceId`, `type`.
 | Field | Valid Values |
 |-------|-------------|
 | `status` | `ACTIVE`, `INACTIVE` |
-| `role` | `ADMIN`, `CUSTOM_USER` |
+| `userType` | `ADMIN`, `CUSTOM_USER` |
 
-**String fields**: `name`, `email`
+**String fields**: `email`, `resourceId`, `userResourceId`
+**Nested** (`user`): `user.firstName`, `user.lastName`, `user.email`, `user.status`, `user.phoneRegistered`
+
+There is no `name` or `role` field on this filter.
 
 ---
 

package/assets/skills/api/references/search-reference.md

@@ -683,9 +683,12 @@ To convert response dates: `new Date(epochMs).toISOString().slice(0, 10)` → `Y
 
 ### 21. POST /api/v1/organization-users/search
 
-**Filter fields** (`OrganizationUserFilter`): `name`, `email`, `role`, `status`
+**Filter fields** (`OrganizationUserFilter`): `resourceId`, `userResourceId`, `userType`, `status`, `email`, `and`, `or`
+**Nested**: `user` (`user.firstName`, `user.lastName`, `user.email`, `user.phoneRegistered`, `user.status`, `user.resourceId`, `user.deleted`)
 
-**Sort fields**: `name`, `email`, `createdAt`
+**Sort fields** (max 9): `resourceId`, `status`, `userResourceId`, `userType`, `user.FirstName`, `user.LastName`, `user.Email`, `user.PhoneRegistered`, `user.Status`
+
+There is no top-level `name` or `role` on this filter, and the nested sort keys are capitalised while the nested filter keys are not — `user.firstName` filters, `user.FirstName` sorts. Anything else in `sort.sortBy` is a 422. `query` is rejected on this endpoint; use the filter.
 
 Standard pattern with limit/offset/filter/sort. Rarely used in conversions.
 
@@ -707,6 +710,8 @@ Standard pattern with limit/offset/filter/sort. Used for managing bank reconcili
 
 **Sort fields** (max 13): `resourceId`, `name`, `reference`, `currencyCode`, `status`, `valueDate`, `totalItemAmount`, `description`
 
+`query` is rejected on this endpoint ("The query field is not supported for this entity") despite being declared on `SearchPurchaseItemRequest`. Use the filter.
+
 ---
 
 ### 24. POST /api/v1/sale-orders/search

package/assets/skills/api/references/search-syntax.md

@@ -58,9 +58,12 @@ Prefix with any currency symbol or type a numeric range.
 |-------|---------|
 | `$500` | amount = 500 |
 | `$-500` | amount = -500 (negative) |
+| `-$500` | same as above (negative before currency) |
 | `$100-500` | amount between 100 and 500 |
 | `$100 to 500` | same as above |
+| `$500 to $1000` | range with currency on both sides |
 | `$-500 to -100` | negative range |
+| `-$4000 to -$6000` | negative range with currency |
 | `$-100 - -500` | negative range (space-hyphen-space) |
 | `$500+` | amount >= 500 |
 | `$<200` | amount < 200 |
@@ -69,6 +72,34 @@ Prefix with any currency symbol or type a numeric range.
 | `>500` | amount > 500 (no symbol needed for comparisons) |
 | `500+` | amount >= 500 (no symbol needed) |
 
+### Magnitude Suffixes
+
+Use shorthand for large numbers. Case-insensitive.
+
+| Suffix | Aliases | Multiplier | Example |
+|--------|---------|-----------|---------|
+| `k` | k | 1,000 | `$5k` = 5,000 |
+| `m` | m, mn, mm, mil | 1,000,000 | `4.5m` = 4,500,000 |
+| `b` | b, bn, bil | 1,000,000,000 | `$1b` = 1,000,000,000 |
+| `t` | t, tn, trn | 1,000,000,000,000 | `1trn` = 1,000,000,000,000 |
+
+Works everywhere: `$5k`, `5k+`, `>2m`, `4k-5k`, `$4k to $5k`, `amount:5k+`, `amount:>2m`
+
+### Field:Value Amount Syntax
+
+Use `amount:` prefix for explicit field targeting. Supports currency, suffixes, and `to` ranges.
+
+| Input | Meaning |
+|-------|---------|
+| `amount:500` | amount = 500 |
+| `amount:$500` | same (currency stripped) |
+| `amount:-$80000` | amount = -80000 |
+| `amount:100-500` | amount between 100 and 500 |
+| `amount:4k-5k` | amount between 4000 and 5000 |
+| `amount:-4000 to -6000` | amount between -6000 and -4000 |
+| `amount:5k+` | amount >= 5000 |
+| `amount:>2m` | amount > 2,000,000 |
+
 Supported currency symbols: `$` `€` `£` `¥` `₱` `₹` `₩` `฿` `₫` `₺` `R$` `RM` `Rp` `kr` `Fr` `zł` `R`
 
 Also works with ISO codes: `SGD500`, `PHP1000`, `EUR200-500`
@@ -85,14 +116,20 @@ Prefix with `date:` for invoice/transaction date, or `due:` for due date.
 |-------|---------|
 | `date:today` | today |
 | `date:yesterday` | yesterday |
+| `date:tomorrow` | tomorrow |
+| `date:2 days ago` | 2 days ago |
 | `date:this week` | current week (Mon-Sun) |
 | `date:last week` | previous week |
+| `date:next week` | next week |
 | `date:this month` | current month |
 | `date:last month` | previous month |
+| `date:next month` | next month |
 | `date:this quarter` | current quarter |
 | `date:last quarter` | previous quarter |
+| `date:next quarter` | next quarter |
 | `date:this year` | current year |
 | `date:last year` | previous year |
+| `date:next year` | next year |
 | `date:jan 2025` | January 2025 |
 | `date:jan-mar 2025` | Jan 1 to Mar 31, 2025 |
 | `date:jan to mar 2025` | same as above |
@@ -105,8 +142,26 @@ Prefix with `date:` for invoice/transaction date, or `due:` for due date.
 | `date:-3m` | last 3 months |
 | `date:last 30 days` | same as -30d |
 | `date:last 2 weeks` | same as -2w |
+| `date:next 7 days` | next 7 days from today |
+| `date:next 30 days` | next 30 days from today |
+
+### Due Date Semantics
+
+| Input | Meaning |
+|-------|---------|
+| `due:overdue` | due date before today (past due) |
+| `due:past` | same as overdue |
+| `due:upcoming` | due in the next 30 days |
+| `due:tomorrow` | due tomorrow |
+| `due:next 7 days` | due within next 7 days |
+| `due:next 30 days` | due within next 30 days |
+| `due:this week` | due this week |
 
-Date field aliases: `due:` (due date), `created:` (created date), `submitted:` (submitted date), `approved:` (approved date), `lastpayment:` (last payment date)
+### Commas in Amounts
+
+Commas are stripped from amounts: `$1,000` = 1000, `$1,000,000` = 1000000, `$1,000+` = gte 1000
+
+Date field aliases: `due:` (due date), `created:` (created date), `updated:` / `modified:` (updated date), `submitted:` (submitted date), `approved:` (approved date), `lastpayment:` (last payment date)
 
 ---
 
@@ -156,6 +211,38 @@ Comma-separated values search for any match.
 
 ---
 
+## Boolean Search
+
+Some fields accept yes/no values (e.g. `hasattachment`, `customer`, `supplier`).
+
+| Input | Meaning |
+|-------|---------|
+| `hasattachment:yes` | has attachments |
+| `hasattachment:no` | no attachments |
+| `!hasattachment:yes` | no attachments (negated) |
+| `attachmentfilename:report` | attachment file name contains "report" |
+
+Accepted truthy values: `yes`, `true`, `y`, `1`. Accepted falsy values: `no`, `false`, `n`, `0`.
+
+---
+
+## Absolute Value Search
+
+Filter by amount magnitude regardless of sign. Useful for cashflow, bank records, and journals with mixed debit/credit amounts.
+
+| Input | Meaning |
+|-------|---------|
+| `abs:500` | amount = 500 OR amount = -500 |
+| `abs:>=500` | amount >= 500 OR amount <= -500 |
+| `abs:500+` | same as above |
+| `abs:>500` | amount > 500 OR amount < -500 |
+| `abs:<100` | amount < 100 OR amount > -100 |
+| `abs:100-500` | amount between 100-500 OR between -500 and -100 |
+| `abs:$5k+` | currency symbols and suffixes work |
+| `!abs:500` | amount != 500 AND amount != -500 |
+
+---
+
 ## Blank / Empty Checks
 
 | Input | Meaning |
@@ -240,31 +327,200 @@ NOT (status:paid OR status:void)
 ## Available Fields by Entity
 
 ### Sales / Invoices
-`customer` `ref` `status` `approval` `currency` `tag` `id` `amount` `balance` `paid` `date` `duedate` `created` `lastpayment` `submitted` `approved` `updated` `paymentrecorded` `creditapplied` `taxid` `regid` `submittedby` `approvedby` `terms`
+`customer` `ref` `status` `approval` `currency` `tag` `id` `amount` `balance` `paid` `date` `duedate` `createdat` `lastpayment` `submitted` `approved` `updatedat` `paymentrecorded` `creditapplied` `taxid` `regid` `submittedby` `approvedby` `terms` `hasattachment` `attachmentfilename` `saleorderresourceid` `saleresourceid` `lastemail` `changesrequested`
+
+Status values: `unpaid` `paid` `partial` `void` `draft` `overdue`
+Approval values: `pending` `approved`
+Aliases: `invoicedate:` = `date:`, `billref:` / `invoiceref:` = `ref:`
+
+### Sale Line Items
+`amount` `price` `qty` `currency` `name` `desc` `sku` `id` `discount` `taxrate` `account` `accountcode` `customer` `status` `ref` `date` `createdat`
 
 ### Purchases / Bills
-`supplier` `ref` `status` `approval` `currency` `tag` `id` `amount` `balance` `paid` `date` `duedate` `created` `lastpayment` `submitted` `approved` `updated` `paymentrecorded` `creditapplied` `taxid` `regid` `submittedby` `approvedby` `terms`
+`supplier` `ref` `status` `approval` `currency` `tag` `id` `amount` `balance` `paid` `date` `duedate` `createdat` `lastpayment` `submitted` `approved` `updatedat` `paymentrecorded` `creditapplied` `taxid` `regid` `submittedby` `approvedby` `terms` `hasattachment` `attachmentfilename` `purchaseorderresourceid` `purchaseresourceid` `changesrequested`
+
+Status values: `unpaid` `paid` `partial` `void` `draft` `overdue`
+Aliases: `billdate:` = `date:`, `vendor:` = `supplier:`
+
+### Purchase Line Items
+`amount` `price` `qty` `currency` `name` `desc` `sku` `id` `discount` `taxrate` `account` `accountcode` `supplier` `status` `ref` `date` `createdat`
+
+### Billable Items
+`id` `status` `item` `desc` `amount` `currency` `assigned` `billed` `account` `accountcode` `customer` `createdat` `supplier` `ref` `date`
 
 ### Credit Notes (Sale)
-`customer` `ref` `status` `approval` `currency` `tag` `id` `amount` `balance` `paid` `date` `created` `submitted` `approved` `lastpayment` `taxid`
+`customer` `ref` `status` `approval` `currency` `tag` `id` `amount` `paid` `date` `createdat` `submitted` `approved` `lastpayment` `taxid` `hasattachment` `lastemail` `changesrequested`
+
+Status values: `unpaid` `paid` `partial` `void` `draft`
 
 ### Credit Notes (Purchase)
-`supplier` `ref` `status` `approval` `currency` `tag` `id` `amount` `balance` `date` `created` `submitted` `approved` `lastpayment` `taxid`
+`supplier` `ref` `status` `approval` `currency` `tag` `id` `amount` `paid` `date` `createdat` `submitted` `approved` `lastpayment` `taxid` `hasattachment` `changesrequested`
+
+Status values: `unpaid` `paid` `partial` `void` `draft`
+
+### Credit Note Line Items (Sale / Purchase)
+`amount` `price` `qty` `currency` `name` `desc` `sku` `id` `discount` `taxrate` `account` `accountcode` `createdat`
 
 ### Payments
-`customer` `ref` `status` `method` `currency` `id` `amount` `date` `created`
+`customer` `ref` `method` `currency` `id` `amount` `date` `createdat` `status` `taxid` `paymentcurrency` `hasattachment`
+
+Sale payments (default). Aliases: `paymentmethod:` = `method:`, `paymentdate:` / `valuedate:` = `date:`, `curr:` = `currency:`, `contact:` = `customer:`
+
+For purchase payments: use `supplier:` / `vendor:` instead of `customer:`.
+For batch payments: use `contact:` (matches `customer:` and `supplier:`); amount field → `totalAmount`.
+
+### Payments Due
+`amount` `ref` `contact` `currency` `date` `createdat` `tag` `type` `status` `total` `taxid`
+
+Aliases: `balance:` = `amount:`, `reference:` = `ref:`, `customer:` / `supplier:` = `contact:`, `curr:` = `currency:`, `valuedate:` = `date:`, `transactiontype:` = `type:`
 
 ### Journals
-`contact` `ref` `type` `status` `tag` `id` `debit` `credit` `date` `created` `notes`
+`contact` `ref` `type` `status` `tag` `id` `debit` `credit` `date` `createdat` `notes`
+
+Status values: `active` `void` `draft`
+Type values: `manual` `system` `recurring`
+Aliases: `journaltype:` = `type:`, `customer:` / `supplier:` = `contact:`, `amount:` = `debit:`, `internalnotes:` = `notes:`
+
+### Journal Entry Lines
+`amount` `currency` `desc` `id` `contact` `ref` `status` `date`
+
+Aliases: `debit:` / `credit:` = `amount:`, `curr:` = `currency:`, `description:` / `notes:` = `desc:`, `customer:` / `supplier:` = `contact:`, `reference:` = `ref:`, `valuedate:` = `date:`
+
+### Cashflow / Bank Records / Bank Entries
+`description` `payee` / `payer` `ref` `status` `review` `id` `amount` `date`
+
+Status values: `unreconciled` `reconciled` `excluded`
+Review values: `reviewed` `unreviewed`
+Aliases: `desc:` = `description:`, `contact:` / `extcontactname:` = `payee:`, `reference:` / `extreference:` = `ref:`, `netamount:` = `amount:`, `valuedate:` = `date:`, `reviewstate:` = `review:`
+
+### Cash Entries
+`status` `ref` `contact` `currency` `amount` `date` `createdat` `id`
+
+Status values: `active` `void`
+Aliases: `reference:` = `ref:`, `payee:` = `contact:`, `curr:` = `currency:`, `balance:` = `amount:`, `valuedate:` = `date:`
 
-### Cashflow / Bank Entries
-`description` `payee` `ref` `status` `review` `id` `amount` `date`
+### Cash Entry Lines
+`amount` `currency` `ref` `type` `contact` `date` `createdat` `tag` `id`
+
+Aliases: `balance:` = `amount:`, `curr:` = `currency:`, `reference:` = `ref:`, `payee:` = `contact:`, `valuedate:` = `date:`
 
 ### Contacts
 `name` `email` `status` `registration` `taxid` `customer` `supplier` `id`
 
+Status values: `active` `inactive`
+Boolean: `customer:yes` / `customer:no`, `supplier:yes` / `supplier:no`
+
 ### Items / Products
-`name` `sku` `status` `type` `id`
+`name` `sku` `status` `id` `costing` `purchasename` `salename` `cogsaccount` `purchaseaccount` `saleaccount`
+
+Status values: `active` `inactive`
+Aliases: `item:` / `product:` = `name:`, `code:` = `sku:`
+
+### Fixed Assets
+`name` `ref` `status` `id` `amount` `date`
+
+Status values: `registered` `disposed` `draft`
+Aliases: `asset:` = `name:`, `reference:` = `ref:`, `price:` / `cost:` = `amount:`, `purchasedate:` = `date:`
+
+### Disposal Assets
+`name` `ref` `status` `id` `amount` `date` `type` `tag` `bookvalue` `gainloss`
+
+Status values: `registered` `disposed` `draft`
+Aliases: `asset:` = `name:`, `reference:` = `ref:`, `price:` / `cost:` = `amount:`, `disposaldate:` = `date:`, `purchasedate:` = purchase date (separate field), `netbook:` = `bookvalue:`, `gain:` / `loss:` = `gainloss:`
+
+### Capsules / Capsule Transactions
+`name` `ref` `status` `id` `date`
+
+Aliases: `capsule:` = `name:`, `reference:` = `ref:`, `valuedate:` = `date:`
+
+### Inventory Balance
+`name` `sku` `id`
+
+Aliases: `item:` = `name:`, `code:` = `sku:`
+
+### Inventory Transactions
+`ref` `type` `date` `id`
+
+Aliases: `reference:` = `ref:`, `valuedate:` = `date:`
+
+### Deposits / Deposit Balances
+`status` `ref` `contact` `id` `amount` `date`
+
+Aliases: `reference:` = `ref:`, `customer:` / `supplier:` = `contact:`, `total:` = `amount:`, `valuedate:` = `date:`
+
+### Bank Accounts
+`name` `code` `status` `currency` `id` `balance`
+
+Status values: `active` `inactive`
+Aliases: `account:` = `name:`, `curr:` = `currency:`, `amount:` = `balance:`
+
+### Match Transactions (Bank Reconciliation)
+`ref` `contact` `id` `amount` `balance` `date`
+
+Aliases: `reference:` = `ref:`, `customer:` / `supplier:` / `payee:` = `contact:`, `total:` = `amount:`, `bal:` = `balance:`, `valuedate:` = `date:`
+
+### Scheduled Transactions (Invoices / Bills / Subscriptions)
+`contact` `customer` `supplier` `ref` `reference` `status` `currency` `curr` `id` `amount` `total` `date` `nextdate` (→ nextScheduleDate)
+
+### Scheduled Journals
+`contact` `customer` `supplier` `ref` `reference` `status` `tag` `tags` `interval` `id` `date` `start` `startdate` (→ startDate) `end` `enddate` `last` `lastdate`
+NOTE: No amount fields — JournalSchedulerFilter has no BigDecimalExpression fields.
+
+Interval values: `daily` `weekly` `monthly` `quarterly` `yearly` `onetime`
+
+### Scheduled Line Items (Invoice / Bill / Subscription)
+`name` `item` `desc` `description` `sku` `itemcode` `code` `contact` `customer` `supplier` `currency` `curr` `status` `ref` `reference` `date` `valuedate` (→ businessTransactionValueDate) `start` `startdate` `end` `enddate` `next` `nextdate`
+
+Status values: `active` `completed` `cancelled`
+
+### Journal Scheduler Line Items
+`contact` `customer` `supplier` `desc` `description` `currency` `curr` `ref` `reference` `status` `date` `start` `startdate` (→ startDate) `end` `enddate` `next` `nextdate` `id`
+
+### Mandate Batches (E-invoicing)
+`name` `desc` `status` `mandate` `provider` `id` `startdate` `enddate` `createdat` `updatedat` `submissions`
+
+Status values: `draft` `submitted` `accepted` `rejected` `cancelled`
+Aliases: `batchname:` = `name:`, `mandatecode:` = `mandate:`, `providercode:` = `provider:`, `periodstart:` = `startdate:`, `periodend:` = `enddate:`, `count:` = `submissions:`
+
+### Mandate Submissions (E-invoicing)
+`ref` `contact` `type` `doctype` `direction` `status` `response` `id` `btid` `submittedat` `responseat` `workflowupdated` `mandate`
+
+Direction values: `supply` `purchase`
+Status values: `draft` `queued` `submitted` `accepted` `completed` `rejected` `cancelled` `failed`
+Aliases: `bttype:` = `type:`, `documenttype:` = `doctype:`, `workflowstatus:` = `status:`, `responsestatus:` = `response:`, `btresourceid:` = `btid:`, `workflowupdatedat:` = `workflowupdated:`, `mandatecode:` = `mandate:`
+
+### Sale Orders
+`id` `ref` `date` `due` `approved` `currency` `amount` `customer` `regid` `taxid` `tag` `created` `status` `customfields`
+
+### Sale Order Line Items
+`id` `name` `currency` `amount` `customer` `status` `ref` `date`
+
+### Sale Quotes
+`id` `ref` `date` `due` `currency` `amount` `customer` `regid` `taxid` `tag` `created` `status` `customfields` `signing` `changesrequested`
+
+### Sale Quote Line Items
+`id` `name` `currency` `amount` `customer` `status` `ref` `date`
+
+### Purchase Orders
+`id` `ref` `date` `due` `approved` `currency` `amount` `supplier` `regid` `taxid` `tag` `created` `status` `customfields`
+
+### Purchase Order Line Items
+`id` `name` `currency` `amount` `supplier` `status` `ref` `date`
+
+### Purchase Requests
+`id` `ref` `date` `due` `currency` `amount` `supplier` `regid` `taxid` `tag` `created` `status` `customfields` `signing` `changesrequested`
+
+### Purchase Request Line Items
+`id` `name` `currency` `amount` `supplier` `status` `ref` `date`
+
+### Employees / Directory
+`id` `name` `email` `phone` `currency` `employmenttype` `beneficiary` `paymentmethod` `manager` `claimprofile` `created` `updated`
+
+### Employees / Claims
+`id` `ref` `currency` `date` `created` `amount` `employee` `vendor` `customfields` `hasattachment` `createdby` `changesrequested`
+
+### Employees / Payouts
+`employee` `ref` `type` `valuedate`
 
 ---
 
@@ -289,6 +545,12 @@ NOT status:void sort:amount:desc
 # Find negative journal entries in a date range
 $-1000 to -5000 AND date:feb-mar 2025
 
+# Match transactions between $4k and $5k for reconciliation
+amount:4k to 5k
+
+# Find purchases over $2 million
+supplier:acme AND amount:>2m
+
 # Find all unpaid purchases from a specific supplier in EUR
 supplier:acme AND status:unpaid AND currency:EUR
 
@@ -300,4 +562,22 @@ taxid:T1234567
 
 # Find all transactions with balance > 0 and due before today
 balance:>0 AND duedate:<2026-03-15
+
+# Find unreconciled bank entries above $1,000
+status:unreconciled AND $1000+
+
+# Find manual journals from this month
+type:manual AND date:this month
+
+# Find active items of type service
+status:active AND type:service
+
+# Find registered fixed assets purchased this year
+status:registered AND date:this year
+
+# Find batch e-invoice submissions that were rejected
+status:rejected
+
+# Find capsules with no reference
+ref:blank
 ```

package/assets/skills/cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jaz-cli
-version: 5.44.0
+version: 5.45.0
 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/conversion/SKILL.md

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