jaz-clio 5.46.11 → 5.46.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/api/SKILL.md +2 -2
- package/assets/skills/api/references/endpoints.md +7 -4
- package/assets/skills/cli/SKILL.md +1 -1
- package/assets/skills/conversion/SKILL.md +1 -1
- package/assets/skills/jaz-kit/SKILL.md +1 -1
- package/assets/skills/jaz-pseudo-sql/SKILL.md +1 -1
- package/assets/skills/jobs/SKILL.md +1 -1
- package/assets/skills/transaction-recipes/SKILL.md +1 -1
- package/cli.mjs +439 -439
- package/package.json +1 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: jaz-api
|
|
3
|
-
version: 5.46.
|
|
3
|
+
version: 5.46.13
|
|
4
4
|
description: >-
|
|
5
5
|
Use this skill whenever you call, debug, or review code that touches the Jaz
|
|
6
6
|
REST API. Covers field names, response shapes, 159 production gotchas, error
|
|
@@ -363,7 +363,7 @@ Bills, invoices, and credit notes share identical mandatory field specs. Adding
|
|
|
363
363
|
108. **Transfer Trial Balance** (`POST /api/v1/transfer-trial-balance`) creates opening balance entries. Uses `journalEntries` (NOT `lines` — this is a journal type). Always ACTIVE (no draft mode), reference auto-generated as "Transfer Trial Balance", minimum 1 entry, entries cannot have 0 amounts, skips lock date validation. **`valueDate` must be today or in the past** — future dates are rejected with "Opening data cannot be future date". Each entry: `{ accountResourceId, type: "DEBIT"|"CREDIT", amount }`.
|
|
364
364
|
|
|
365
365
|
### Scheduler Dynamic Strings
|
|
366
|
-
109. **Scheduler placeholder strings** — All scheduled transactions (invoices, bills, journals, subscriptions) support dynamic strings in any free text field (`reference`, line item `name`, `notes`). Strings are replaced with values relative to the **transaction date**: `{{Day}}` → day name (Monday), `{{Date}}` → full date (09 Mar 2026), `{{Date+X}}` → date + X days, `{{DateRange:X}}` → date range spanning X days (min 1, max 999), `{{Month}}` → month name (March), `{{Month+X}}` → month + X months, `{{MonthRange:X}}` → month range spanning X months, `{{Year}}` → year (2026), `{{Year+X}}` → year + X years. Example: `reference: "INV-{{Month}}-{{Year}}"` → `"INV-March-2026"` for a March transaction.
|
|
366
|
+
109. **Scheduler placeholder strings** — All scheduled transactions (invoices, bills, journals, subscriptions) support dynamic strings in any free text field (`reference`, line item `name`, `notes`). **Scheduled JOURNALS are the exception**: their line field is `description`, not `name`, and they have no notes field at all — neither `notes` nor `internalNotes` is on the create or update contract. Probed 2026-09-02: both are accepted like any unknown key and never read back, so for journals the only dynamic-string field is `reference`. Strings are replaced with values relative to the **transaction date**: `{{Day}}` → day name (Monday), `{{Date}}` → full date (09 Mar 2026), `{{Date+X}}` → date + X days, `{{DateRange:X}}` → date range spanning X days (min 1, max 999), `{{Month}}` → month name (March), `{{Month+X}}` → month + X months, `{{MonthRange:X}}` → month range spanning X months, `{{Year}}` → year (2026), `{{Year+X}}` → year + X years. Example: `reference: "INV-{{Month}}-{{Year}}"` → `"INV-March-2026"` for a March transaction.
|
|
367
367
|
|
|
368
368
|
### Bank Rule Dynamic Strings
|
|
369
369
|
110. **Bank rule placeholder strings** — Bank reconciliation rules support dynamic strings in any free text field (`name`, `reference`, cash entry description). Strings are replaced with actual **bank record** values during reconciliation: `{{bankReference}}` → bank record reference (e.g., INV-03/01/2025-01), `{{bankPayee}}` → payer/payee name (e.g., Fruit Planet), `{{bankDescription}}` → transaction description (e.g., QR Payment). Example: `reference: "{{bankPayee}} - {{bankReference}}"`.
|
|
@@ -647,7 +647,7 @@ Bills and supplier credit notes support withholding tax per line item:
|
|
|
647
647
|
"reference": "JV-001",
|
|
648
648
|
"valueDate": "2026-02-08",
|
|
649
649
|
"journalEntries": [
|
|
650
|
-
{ "accountResourceId": "uuid", "amount": 500, "type": "DEBIT", "
|
|
650
|
+
{ "accountResourceId": "uuid", "amount": 500, "type": "DEBIT", "description": "Line note" },
|
|
651
651
|
{ "accountResourceId": "uuid", "amount": 500, "type": "CREDIT" }
|
|
652
652
|
]
|
|
653
653
|
}
|
|
@@ -661,7 +661,10 @@ Bills and supplier credit notes support withholding tax per line item:
|
|
|
661
661
|
- Do NOT use `debit`/`credit` as separate number fields — that is WRONG
|
|
662
662
|
- Do NOT include `currency` at top level — causes "Invalid request body"
|
|
663
663
|
- Total DEBIT amounts MUST equal total CREDIT amounts
|
|
664
|
-
- `contactResourceId` is
|
|
664
|
+
- `contactResourceId` is a TOP-LEVEL field, NOT per entry. Probed 2026-09-02: an entry-level
|
|
665
|
+
`contactResourceId` is silently discarded (an int there is accepted like any unknown key, while an
|
|
666
|
+
int on `description` or `taxProfileResourceId` returns 400), and a real contact id on an entry does
|
|
667
|
+
not appear on the created journal. Put it at the top level, where it does land.
|
|
665
668
|
|
|
666
669
|
---
|
|
667
670
|
|
|
@@ -1356,8 +1359,8 @@ Same but with `"bill"` wrapper instead of `"invoice"`.
|
|
|
1356
1359
|
"valueDate": "2026-03-01",
|
|
1357
1360
|
"saveAsDraft": false,
|
|
1358
1361
|
"schedulerEntries": [
|
|
1359
|
-
{ "accountResourceId": "uuid", "amount": 100, "type": "DEBIT", "
|
|
1360
|
-
{ "accountResourceId": "uuid", "amount": 100, "type": "CREDIT", "
|
|
1362
|
+
{ "accountResourceId": "uuid", "amount": 100, "type": "DEBIT", "description": "Monthly accrual" },
|
|
1363
|
+
{ "accountResourceId": "uuid", "amount": 100, "type": "CREDIT", "description": "Monthly accrual" }
|
|
1361
1364
|
],
|
|
1362
1365
|
"repeat": "MONTHLY",
|
|
1363
1366
|
"startDate": "2026-03-01",
|