jaz-cli 2.0.0 → 2.2.0

package/assets/skills/api/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: api
-version: 2.0.0
+version: 2.2.0
 description: Complete reference for the Jaz/Juan REST API — the accounting platform backend. Use this skill whenever building, modifying, debugging, or extending any code that calls the API — including API clients, integrations, data seeding, test data, or new endpoint work. Contains every field name, response shape, error, gotcha, and edge case discovered through live production testing.
 license: MIT
 compatibility: Requires Jaz/Juan API key (x-jk-api-key header). Works with Claude Code, Claude Cowork, Claude.ai, and any agent that reads markdown.

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

@@ -55,22 +55,20 @@ All GET list endpoints and POST `/search` endpoints use **`limit`/`offset` pagin
 ### GET /api/v1/organization
 
 ```json
-// Response (returns a LIST, not single object):
+// Response (returns a SINGLE OBJECT, not array):
 {
-  "totalElements": 1,
-  "totalPages": 1,
-  "data": [{
+  "data": {
     "resourceId": "31eb050a-...",
     "name": "Jaz Global SG",
     "currency": "SGD",
     "countryCode": "SG",
     "status": "ACTIVE",
     "lockDate": null
-  }]
+  }
 }
 ```
 
-Access org via `data[0]`. Check `lockDate` — don't seed transactions before it.
+Access org via `data` directly (single object). The API previously returned an array but now returns a single object. Use `Array.isArray(data) ? data[0] : data` to handle both formats. Check `lockDate` — don't seed transactions before it.
 
 ---
 

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

@@ -627,13 +627,21 @@ To convert response dates: `new Date(epochMs).toISOString().slice(0, 10)` → `Y
 
 ### 21. POST /api/v1/organization-users/search
 
-See `organization-users.go`. Standard pattern with limit/offset/filter/sort.
+**Filter fields** (`OrganizationUserFilter`): `name`, `email`, `role`, `status`
+
+**Sort fields**: `name`, `email`, `createdAt`
+
+Standard pattern with limit/offset/filter/sort. Rarely used in conversions.
 
 ---
 
 ### 22. POST /api/v1/bank-rules/search
 
-See `bankRule.go`. Standard pattern with limit/offset/filter/sort.
+**Filter fields** (`BankRuleFilter`): `name`, `bankAccountResourceId`, `status`
+
+**Sort fields**: `name`, `createdAt`
+
+Standard pattern with limit/offset/filter/sort. Used for managing bank reconciliation auto-matching rules.
 
 ---
 

package/assets/skills/conversion/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: conversion
-version: 2.0.0
-description: Accounting data conversion skill — migrates customer data from Xero, QuickBooks, Sage, and Excel exports to Jaz. Covers full and quick conversion workflows, Excel parsing, CoA/contact/tax mapping, clearing accounts, TTB, and TB verification.
+version: 2.2.0
+description: Accounting data conversion skill — migrates customer data from Xero, QuickBooks, Sage, MYOB, and Excel exports to Jaz. Covers config, quick, and full conversion workflows, Excel parsing, CoA/contact/tax/items mapping, clearing accounts, TTB, and TB verification.
 ---
 
 # Jaz Conversion Skill
 
-You are performing an **accounting data conversion** — migrating a customer's financial data from their previous accounting software (Xero, QuickBooks, Sage, or Excel-based systems) into Jaz.
+You are performing an **accounting data conversion** — migrating a customer's financial data from their previous accounting software (Xero, QuickBooks, Sage, MYOB, or Excel-based systems) into Jaz.
 
 **This skill provides conversion domain knowledge. For API details (field names, endpoints, gotchas), load the `jaz-api` skill alongside this one.**
 
@@ -19,9 +19,16 @@ You are performing an **accounting data conversion** — migrating a customer's
 - Verifying post-conversion Trial Balance accuracy
 - Troubleshooting TB mismatches after a conversion
 
-## Two Conversion Types
+## Three Conversion Types
 
-Both types use the **same pipeline** — only the scope (which entity types) differs.
+All types use the **same pipeline** — only the scope (which entity types) differs.
+
+### Config Mode (foundation only)
+- **Scope:** CoA, contacts, items, currencies, tax mapping — NO transactions or journal
+- **Creates:** Foundation entities only (Phases 0-1)
+- **When:** Setting up an org before a conversion, or populating a fresh org with the customer's chart of accounts and contacts
+- **Manifest field:** `"conversionType": "config"`
+- **Requires:** At least one of `coa` or `tb` file (no AR/AP needed)
 
 ### Quick Conversion (Option 2 — recommended starting point)
 - **Scope:** Open AR/AP at FYE + TTB opening balances
@@ -99,12 +106,16 @@ Before any API calls, present a summary for human review:
 
 ### Step 6: Execute
 Create records via Jaz API. Follow the dependency order:
-1. Currencies (must exist before CoA with foreign currency)
-2. CoA (must exist before transactions reference accounts)
-3. Contacts (must exist before invoices/bills reference them)
-4. Tax profiles (read-only — just discover and map)
-5. Transactions (invoices, bills, journals)
-6. Payments (must reference existing invoices/bills)
+1. **Phase 0:** Probe (discover existing resources — accounts, contacts, tax profiles)
+2. **Phase 1A:** Currencies → FX Rates (rates must come AFTER currencies are enabled)
+3. **Phase 1B:** CoA via `POST /api/v1/chart-of-accounts/bulk-upsert`
+4. **Phase 1C:** Contacts → Items (items reference accounts + tax profiles)
+5. **Phase 1D:** Cleanup stale conversions (search + delete CONV-INV-*, CONV-BILL-*, etc.)
+6. **Phase 2:** Conversion invoices (AR), bills (AP), customer credit notes, supplier credit notes
+7. **Phase 3:** TTB journal (routes AR/AP through clearing accounts)
+8. **Phase 4:** Lock dates (per-account, at FYE date)
+
+**Rollback:** If Phase 2 or 3 fails, all Phase 2 resources are automatically rolled back.
 
 ### Step 7: Verify
 After execution, pull the Trial Balance from Jaz and compare against the source TB.

package/assets/skills/conversion/references/edge-cases.md

@@ -6,7 +6,7 @@
 Enable currencies and set FYE closing rates before creating any FX transactions:
 
 ```
-PUT /api/v1/organization/currencies           // Enable currency
+POST /api/v1/organization/currencies          // Enable currency
 { "currencies": ["USD"] }
 
 POST /api/v1/organization-currencies/USD/rates  // Set FYE rate
@@ -85,6 +85,27 @@ Same logic applies for AP Clearing.
 ### Fix
 Create a small adjustment journal to bring the clearing account to zero. Document the reason (e.g., "FX rounding adjustment — $0.02").
 
+## Idempotency — Stale Conversion Cleanup
+
+The pipeline is safe to re-run. Before creating Phase 2 transactions, it searches for and deletes any existing resources with conversion reference patterns:
+- Invoices matching `CONV-INV-*`
+- Bills matching `CONV-BILL-*`
+- Customer credit notes matching `CONV-CCN-*`
+- Supplier credit notes matching `CONV-SCN-*`
+- Journals matching the TTB reference
+
+This ensures a clean slate before each execution. The search uses `/api/v1/{entity}/search` with `filter: { reference: { contains: "CONV-INV" } }`.
+
+## CoA Bulk-Upsert Batch Rejection
+
+**Gotcha:** `POST /api/v1/chart-of-accounts/bulk-upsert` rejects the **entire batch** if any single account in the batch already exists (returns a `DUPLICATED` error). This is all-or-nothing.
+
+The executor handles this by treating the entire batch as "skipped" and then re-fetching all accounts via `/api/v1/chart-of-accounts/search` to get resource IDs.
+
+If calling manually, either:
+1. Filter out existing accounts before sending the batch
+2. Catch `DUPLICATED` errors and fall through to a search
+
 ## Rounding
 
 ### The $0.01 Problem
@@ -141,9 +162,10 @@ When doing a CoA wipe-and-replace on a fresh org:
 
 ### Discovery
 ```
-GET /api/v1/accounts
+POST /api/v1/chart-of-accounts/search
+{ "limit": 200, "offset": 0 }
 ```
-Check for `isSystemGenerated: true` or equivalent flag. These must be preserved.
+Check for `isSystemGenerated: true` flag. These must be preserved.
 
 ### Strategy
 1. Map source accounts to system accounts where possible (e.g., source "Retained Earnings" → Jaz's system "Retained Earnings")
@@ -155,8 +177,10 @@ Check for `isSystemGenerated: true` or equivalent flag. These must be preserved.
 If a conversion goes wrong mid-execution:
 
 ### For Invoices/Bills
-- `POST /api/v1/invoices/<id>/void` — voids the document (cannot be undone)
-- `DELETE /api/v1/invoices/<id>` — deletes draft invoices only
+- `DELETE /api/v1/invoices/<id>` — deletes the invoice (conversion invoices can be deleted directly)
+- `DELETE /api/v1/bills/<id>` — deletes the bill
+- `DELETE /api/v1/customer-credit-notes/<id>` — deletes customer CN
+- `DELETE /api/v1/supplier-credit-notes/<id>` — deletes supplier CN
 
 ### For Journals
 - `DELETE /api/v1/journals/<id>` — deletes the journal entry
@@ -166,9 +190,16 @@ If a conversion goes wrong mid-execution:
 - `DELETE /api/v1/items/<id>` — only if no transactions reference them
 
 ### For CoA
-- `DELETE /api/v1/accounts/<id>` — only if no transactions reference them
+- `DELETE /api/v1/chart-of-accounts/<id>` — only if no transactions reference them
+
+### Automatic Rollback (Pipeline)
+The automated pipeline has built-in rollback:
+- **Phase 2 failure:** If any conversion invoice/bill/credit note fails, ALL successfully created Phase 2 resources are automatically deleted, and Phases 3-4 are skipped.
+- **Phase 3 failure:** If the TTB journal fails, ALL Phase 2 resources are automatically rolled back.
+- This ensures the org is left clean — no partial conversions with unbalanced clearing accounts.
 
-### Rollback Strategy
-1. Delete in reverse order of creation (payments → transactions → contacts → CoA)
+### Manual Rollback Strategy
+If rolling back manually:
+1. Delete in reverse order: journal → credit notes → bills → invoices → contacts → CoA
 2. Some entities may be undeletable if they have dependencies
-3. In worst case, voiding is always available for transactions
+3. Clearing accounts MUST net to zero — never leave a partial conversion in place

package/assets/skills/conversion/references/file-types.md

@@ -2,7 +2,7 @@
 
 Comprehensive catalog of all accounting file types encountered across real customer datasets. Use this to identify and classify files during conversion intake (Pipeline Step 1-2).
 
-**Source data:** 76 files across 10 datasets — Sage 300/Accpac, Xero, QuickBooks, and generic Excel workpapers.
+**Source data:** 76 files across 10 datasets — Sage 300/Accpac, Xero, QuickBooks, MYOB, and generic Excel workpapers.
 
 ---
 
@@ -484,6 +484,7 @@ When analyzing an unknown file, look for these system signatures:
 | **Sage 300/Accpac** | 17+ metadata rows before headers. Hundreds of merged cells. Account codes `XXXX-100` (with dept suffix). Report IDs like GLTRLR1. Filter parameters in header block. `T` column (I/N doc type). Dual-currency column sections. Two-row headers. |
 | **Xero** | Clean flat exports. 4-5 metadata rows. Account codes 3-digit. Tax Rate Name column in GL Detail. "Ageing by due date" text. Auto-numbered invoices (INV-XXXX). "Demo Company (Global)" in demo data. |
 | **QuickBooks** | Grouped/indented sub-accounts. "Total <category>" rows. Template files with instructions sheets. Exchange rate matrices. Account numbers optional. |
+| **MYOB** | 3 preamble rows before data. Per-row aging grouping. Filenames often contain "myob". Classification types: asset, bank, fixed asset, liability, equity, income, cost of sales, expense. |
 | **Generic Excel / Manual** | Very few merged cells (<10). No report metadata block. Custom layouts. May have been prepared by accountant/auditor for statutory purposes. Named schedules ("Schedule 8"). |
 | **Jaz Platform** | CSV with snake_case columns. UUIDs. `jaz.ai` email references. `business_transaction_type` enum values. `resource_id` columns. |
 

package/assets/skills/conversion/references/mapping-rules.md

@@ -6,9 +6,9 @@
 
 When the Jaz org has only default system-generated accounts:
 
-1. **Discover system accounts:** `GET /api/v1/accounts` — system-generated accounts have `isSystemGenerated: true` or are marked as controlled. These cannot be deleted.
-2. **Delete non-system accounts** that aren't in the source CoA
-3. **Create source accounts** using `POST /api/v1/accounts` with bulk upsert (`accounts` wrapper)
+1. **Discover system accounts:** `GET /api/v1/chart-of-accounts/search` — system-generated accounts have `isSystemGenerated: true`. These cannot be deleted.
+2. **Skip accounts that already exist** (matched by name or code from probe)
+3. **Bulk-upsert source accounts** using `POST /api/v1/chart-of-accounts/bulk-upsert` with `{ accounts: [...] }` wrapper
 4. **Match by code first, then name** — if a system account has the same code as a source account, map to it
 
 ### Existing Org Strategy (Match)
@@ -30,21 +30,22 @@ Source systems use different classification names. Map to Jaz types:
 | Source (common names) | Jaz `classificationType` |
 |----------------------|-------------------------|
 | Cash, Bank | Bank Accounts |
-| Accounts Receivable, Trade Debtors | Current Assets |
-| Inventory, Stock | Current Assets |
-| Prepaid Expenses | Current Assets |
-| Fixed Assets, Property/Equipment | Non-Current Assets |
-| Accumulated Depreciation | Non-Current Assets |
-| Accounts Payable, Trade Creditors | Current Liabilities |
-| Accrued Liabilities | Current Liabilities |
-| Loans (long-term) | Non-Current Liabilities |
-| Owner's Equity, Share Capital | Equity |
-| Retained Earnings | Equity |
-| Sales, Revenue, Income | Revenue |
-| Cost of Goods Sold, COGS | Cost of Sales |
-| Operating Expenses | Expenses |
+| Accounts Receivable, Trade Debtors | Current Asset |
+| Inventory, Stock | Inventory |
+| Prepaid Expenses | Current Asset |
+| Fixed Assets, Property/Equipment | Fixed Asset |
+| Accumulated Depreciation | Fixed Asset |
+| Accounts Payable, Trade Creditors | Current Liability |
+| Accrued Liabilities | Current Liability |
+| Loans (long-term) | Non-current Liability |
+| Owner's Equity, Share Capital | Shareholders Equity |
+| Retained Earnings | Shareholders Equity |
+| Sales, Revenue, Income | Operating Revenue |
+| Cost of Goods Sold, COGS | Direct Costs |
+| Operating Expenses | Operating Expense |
 | Other Income | Other Revenue |
-| Other Expenses | Other Expenses |
+
+**Valid `classificationType` values (exactly 13):** Bank Accounts, Cash, Current Asset, Fixed Asset, Non-current Asset, Inventory, Current Liability, Non-current Liability, Shareholders Equity, Operating Revenue, Other Revenue, Direct Costs, Operating Expense
 
 ### Clearing Account Creation
 
@@ -54,15 +55,15 @@ For Quick Conversion, create two clearing accounts:
 {
   "accounts": [
     {
-      "accountName": "AR Conversion Clearing",
-      "accountCode": "1299",
-      "classificationType": "Current Assets",
+      "name": "AR Conversion Clearing",
+      "code": "1299",
+      "classificationType": "Current Asset",
       "description": "Contra account for conversion AR balances — should net to zero"
     },
     {
-      "accountName": "AP Conversion Clearing",
-      "accountCode": "2199",
-      "classificationType": "Current Liabilities",
+      "name": "AP Conversion Clearing",
+      "code": "2199",
+      "classificationType": "Current Liability",
       "description": "Contra account for conversion AP balances — should net to zero"
     }
   ]
@@ -79,20 +80,69 @@ Choose codes that don't conflict with existing accounts. Adjust `1299`/`2199` if
 3. **If no match → create new contact**
 
 ### Contact Types
-- Source "Customer" → Jaz `type: "CUSTOMER"`
-- Source "Supplier" / "Vendor" → Jaz `type: "SUPPLIER"`
-- If both (customer AND supplier) → Jaz `type: "CUSTOMER_AND_SUPPLIER"`
+Jaz uses boolean flags, NOT an enum:
+- Source "Customer" → `customer: true, supplier: false`
+- Source "Supplier" / "Vendor" → `customer: false, supplier: true`
+- If both (customer AND supplier) → `customer: true, supplier: true`
 
 ### Required Fields
-- `companyName` — the contact's business name
-- `displayName` — what shows on invoices/bills (often same as companyName)
-- `type` — CUSTOMER, SUPPLIER, or CUSTOMER_AND_SUPPLIER
+- `name` — the contact's business name
+- `billingName` — what shows on invoices/bills (often same as name)
+- `customer` — boolean (true if the contact is a customer)
+- `supplier` — boolean (true if the contact is a supplier)
 
 ### Optional but Recommended
 - `email` — for payment reminders
 - `phone` — **MUST be E.164** if provided (`+65XXXXXXXX` for SG, `+63XXXXXXXXXX` for PH)
 - `currency` — default currency for this contact (for FX contacts)
 
+### Contact API Example
+```json
+POST /api/v1/contacts
+{
+  "name": "Acme Corp",
+  "billingName": "Acme Corp",
+  "customer": true,
+  "supplier": false,
+  "email": "billing@acme.com"
+}
+```
+
+## Items/Products Mapping
+
+### Detection
+The items extractor detects columns for: name, code, description, type (PRODUCT/SERVICE), sale price, sale account, sale tax profile, purchase price, purchase account, purchase tax profile.
+
+### Item Types
+- `PRODUCT` — physical goods (default if type column not present)
+- `SERVICE` — services
+
+### Payload Shape
+```json
+POST /api/v1/items
+{
+  "internalName": "Widget Pro",
+  "itemCode": "WGT-001",
+  "type": "PRODUCT",
+  "appliesToSale": true,
+  "saleItemName": "Widget Pro",
+  "salePrice": 99.00,
+  "saleAccountResourceId": "<revenue account ID>",
+  "saleTaxProfileResourceId": "<SR tax profile ID>",
+  "appliesToPurchase": true,
+  "purchaseItemName": "Widget Pro",
+  "purchasePrice": 65.00,
+  "purchaseAccountResourceId": "<COGS account ID>",
+  "purchaseTaxProfileResourceId": "<TX tax profile ID>"
+}
+```
+
+### Key Rules
+- Items have **two independent sides** — sale and purchase. Each side has its own account and tax profile.
+- Set `appliesToSale: true` if the item has sale pricing/account. Set `appliesToPurchase: true` if it has purchase pricing/account.
+- Account and tax profile references use template strings (`{{account:Revenue}}`, `{{taxProfile:SR}}`) resolved at execution time via the probe.
+- If the source doesn't distinguish sale vs purchase accounts, use the same account for both.
+
 ## Tax Profile Mapping
 
 **Tax profiles are READ-ONLY in Jaz.** They are pre-provisioned per org. You can only discover and map.
@@ -122,6 +172,13 @@ Returns all available tax profiles with `taxTypeCode`, `taxPercentage`, and `des
 | VAT Exempt | VE | 0% |
 | Zero Rated | VZ | 0% |
 
+### Exempt Tax Profile Split (Sales vs Purchase)
+Jaz has separate exempt tax profiles for sales and purchases. Use the correct one:
+- **Invoices / Customer Credit Notes** → exempt profile where `appliesToSale !== false`
+- **Bills / Supplier Credit Notes** → exempt profile where `appliesToPurchase !== false`
+
+The probe discovers both: `exemptSalesTaxProfileId` and `exemptPurchaseTaxProfileId`. Using the wrong one may cause validation errors.
+
 ### Handling "No Tax" / Tax-Free Items
 If a source line item has no tax, omit `taxProfileResourceId` from the line item payload entirely — do NOT set it to a zero-rate profile unless the source explicitly used one.
 
@@ -131,20 +188,22 @@ If a source line item has no tax, omit `taxProfileResourceId` from the line item
 Before creating any FX transactions or CoA entries with foreign currency:
 
 ```
-PUT /api/v1/organization/currencies
+POST /api/v1/organization/currencies
 {
   "currencies": ["USD", "EUR", "JPY"]
 }
 ```
 
+**Note:** This is a POST (not PUT).
+
 ### Set FYE Exchange Rates
-For Quick Conversion, all conversion transactions use the FYE closing rate:
+For Quick Conversion, all conversion transactions use the FYE closing rate. Rates MUST be set AFTER currencies are enabled:
 
 ```
 POST /api/v1/organization-currencies/<code>/rates
 {
   "rate": 1.35,
-  "effectiveDate": "2023-12-31"
+  "rateApplicableFrom": "2023-12-31"
 }
 ```
 
@@ -152,6 +211,8 @@ POST /api/v1/organization-currencies/<code>/rates
 
 **Note:** Rate endpoints use `/organization-currencies` (hyphenated). Enable/disable uses `/organization/currencies` (nested path). These are DIFFERENT endpoints.
 
+**CRITICAL:** The field is `rateApplicableFrom` (NOT `effectiveDate`). Using the wrong field name will silently fail.
+
 ## Confidence Scoring
 
 For each mapping, assign a confidence level:

package/assets/skills/conversion/references/option1-full.md

@@ -1,5 +1,7 @@
 # Full Conversion (Option 1) — Complete Transaction History
 
+> **Note:** Full Conversion automation is NOT yet implemented in the pipeline. The `conversionType: "full"` manifest option is reserved for future use. This document describes the **manual process** — an agent or human must execute these steps individually using the API. For automated conversion, use Quick Conversion (`conversionType: "quick"`).
+
 ## Overview
 
 The Full Conversion transfers **all transaction details** for FY and FY-1 (typically 2 financial years). This preserves the complete audit trail including individual invoices, bills, payments, journals, and more.
@@ -101,8 +103,8 @@ Apply credit notes to invoices/bills if the source shows them as applied.
 
 #### 5.1 Bank Records
 Import bank statements for reconciliation:
-- Via `POST /api/v1/bank-records/import` (multipart form)
-- Or via individual `POST /api/v1/bank-records`
+- Via `POST /api/v1/magic/importBankStatementFromAttachment` (multipart form with fields: `sourceFile`, `accountResourceId`, `businessTransactionType: "BANK_STATEMENT"`, `sourceType: "FILE"`)
+- Or via individual `POST /api/v1/bank-records/:accountResourceId` (JSON)
 
 #### 5.2 Fixed Assets
 Transfer existing assets with accumulated depreciation:

package/assets/skills/conversion/references/option2-quick.md

@@ -34,8 +34,8 @@ Two modes:
 3. Delete non-system accounts that aren't in the source CoA
 4. Create/update accounts to match source CoA
 5. Create two clearing accounts:
-   - **"AR Conversion Clearing"** — type: `Other Current Assets`, `classificationType: "Current Assets"`
-   - **"AP Conversion Clearing"** — type: `Other Current Liabilities`, `classificationType: "Current Liabilities"`
+   - **"AR Conversion Clearing"** — `classificationType: "Current Asset"`, code: `1299`
+   - **"AP Conversion Clearing"** — `classificationType: "Current Liability"`, code: `2199`
 
 **Existing org:**
 1. GET existing CoA from Jaz
@@ -52,6 +52,17 @@ Two modes:
 - Create customer and supplier contacts from source data
 - Ensure each contact has: name, type (customer/supplier/both), currency if FX
 
+### Phase 1D: Cleanup Stale Conversions (Idempotency)
+
+Before creating new conversion transactions, the executor searches for and deletes any existing resources with matching references:
+- `CONV-INV-*` — stale conversion invoices
+- `CONV-BILL-*` — stale conversion bills
+- `CONV-CCN-*` — stale customer credit notes
+- `CONV-SCN-*` — stale supplier credit notes
+- `TTB-*` — stale TTB journals
+
+This makes the pipeline **safe to re-run** — if a previous execution partially completed or needs to be redone, Phase 1D cleans up the old resources first.
+
 ### Phase 2: Conversion Transactions
 
 #### 2.1 Conversion Invoices (AR)
@@ -142,7 +153,14 @@ POST /api/v1/journals
 ### Phase 4: Lock & Verify
 
 #### 4.1 Lock Date
-Set the accounting lock date to the FYE date to prevent accidental edits to the converted data.
+Set the lock date on **each account individually** to the FYE date:
+
+```
+PUT /api/v1/chart-of-accounts/<accountResourceId>
+{ "lockDate": "<FYE date>" }
+```
+
+This is NOT a single org-level call — it requires N API calls (one per account). The lock date prevents accidental edits to the converted data on or before the FYE date.
 
 #### 4.2 Verify
 Pull the Trial Balance from Jaz at the FYE date. Compare against the source TB.

package/assets/skills/conversion/references/verification.md

@@ -7,10 +7,16 @@ After all conversion transactions are created, verify accuracy by comparing the
 ### Step 1: Pull Jaz Trial Balance
 
 ```
-GET /api/v1/reports/trial-balance?asOnDate=<FYE date>
+POST /api/v1/generate-reports/trial-balance
+{
+  "startDate": "<FY start date>",
+  "endDate": "<FYE date>"
+}
 ```
 
-This returns all account balances as at the specified date.
+This returns all account balances for the specified period. The response may be wrapped as `{ data: [...] }` or `{ data: { data: [...] } }` — handle both formats.
+
+**Note:** This is a POST to `/generate-reports/trial-balance` (NOT a GET to `/reports/trial-balance`).
 
 ### Step 2: Parse Source Trial Balance
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jaz-cli",
-  "version": "2.0.0",
+  "version": "2.2.0",
   "description": "CLI to install Jaz AI skills for Claude Code",
   "type": "module",
   "bin": {