jaz-cli 2.7.0 → 2.8.0

package/assets/skills/jobs/references/building-blocks.md

@@ -0,0 +1,135 @@
+# Building Blocks for Accounting Jobs
+
+Shared concepts that all jobs rely on. Read this first.
+
+---
+
+## Accounting Periods
+
+Jaz uses a **financial year** (FY) that may not match the calendar year. The org's FY start date determines period boundaries.
+
+**Period formats used in jobs:**
+- Month: `YYYY-MM` (e.g., `2025-01` = January 2025)
+- Quarter: `YYYY-QN` (e.g., `2025-Q1` = Jan–Mar 2025 for calendar-year orgs)
+- Year: `YYYY` (e.g., `2025` = full FY 2025)
+
+**Period boundaries matter for:**
+- Search filters (`valueDate between`) — determines which transactions are "in period"
+- Report snapshots (`startDate`, `endDate`, `primarySnapshotDate`) — determines what the reports cover
+- Lock dates — determines what can no longer be edited
+
+---
+
+## Lock Dates
+
+Lock dates prevent backdated entries. Two levels:
+
+| Level | What it locks | When to set |
+|-------|--------------|-------------|
+| **Org-wide** | All transactions before this date | After month/quarter/year-end close |
+| **Per-account** | Specific CoA account locked before date | For bank accounts after recon, or controlled accounts |
+
+**Setting lock dates via API:**
+- Org lock date: managed through organization settings
+- Per-account lock date: `lockDate` field on CoA account
+
+**Best practice for SMBs:**
+- Set org lock date after completing each month-end close
+- Move it forward each month: Jan close → lock to 2025-01-31, Feb close → lock to 2025-02-28
+- Only move lock date forward, never backward (unless correcting errors — requires admin)
+
+---
+
+## Period Verification Pattern
+
+Every job ends with a verification phase. The universal pattern:
+
+### 1. Trial Balance Check
+```
+POST /generate-reports/trial-balance
+{ "startDate": "YYYY-MM-01", "endDate": "YYYY-MM-DD" }
+```
+- Total debits MUST equal total credits
+- No unexpected account balances (e.g., negative cash, negative inventory)
+- Compare to prior period — flag significant variances
+
+### 2. P&L Review
+```
+POST /generate-reports/profit-and-loss
+{ "primarySnapshotDate": "YYYY-MM-DD", "secondarySnapshotDate": "YYYY-MM-01" }
+```
+- Revenue and expense trends should make sense
+- One-off entries (accruals, adjustments) should be explainable
+
+### 3. Balance Sheet Review
+```
+POST /generate-reports/balance-sheet
+{ "primarySnapshotDate": "YYYY-MM-DD" }
+```
+- Assets = Liabilities + Equity (always, by definition)
+- Bank balances match bank statements
+- AR/AP aging ties to balance sheet control accounts
+
+### 4. Bank Balance Reconciliation
+```
+POST /generate-reports/bank-balance-summary
+{ "primarySnapshotDate": "YYYY-MM-DD" }
+```
+- Book balance per Jaz should match bank statement closing balance
+- Differences = timing items (outstanding cheques, deposits in transit)
+
+---
+
+## Scheduler Verification
+
+Many month-end steps are automated via schedulers. Before closing, verify:
+
+1. **Schedulers fired** — Check that recurring journals were created for the period
+   - `POST /journals/search` with capsule filter + valueDate in period
+2. **Amounts correct** — Fixed schedulers should produce consistent amounts
+3. **No duplicates** — If you manually posted a journal AND the scheduler fired, you'll double-count
+
+**Common issue for SMBs:** Scheduler was set up mid-period or end date already passed. Always check before assuming automation handled it.
+
+---
+
+## Capsule Conventions for Jobs
+
+Jobs reference capsules from transaction recipes. Standard capsule types:
+
+| Capsule Type | Used By |
+|-------------|---------|
+| Prepaid Expenses | Prepaid amortization steps |
+| Deferred Revenue | Revenue recognition steps |
+| Accrued Expenses | Accrued expense steps |
+| Loan Repayment | Loan interest accrual steps |
+| Lease Accounting | IFRS 16 lease steps |
+| Depreciation | Non-standard depreciation steps |
+| FX Revaluation | Period-end FX revaluation |
+| ECL Provision | Bad debt provision steps |
+| Employee Benefits | Leave and bonus accrual steps |
+
+**Verification shortcut:** Group the General Ledger by capsule to see the complete lifecycle of each multi-step workflow in one view.
+
+---
+
+## Report API Quick Reference
+
+Jobs frequently generate reports. The key endpoints and their required fields:
+
+| Report | Endpoint | Required Fields |
+|--------|----------|----------------|
+| Trial Balance | `POST /generate-reports/trial-balance` | `startDate`, `endDate` |
+| P&L | `POST /generate-reports/profit-and-loss` | `primarySnapshotDate`, `secondarySnapshotDate` |
+| Balance Sheet | `POST /generate-reports/balance-sheet` | `primarySnapshotDate` |
+| General Ledger | `POST /generate-reports/general-ledger` | `startDate`, `endDate`, `groupBy: "ACCOUNT"` |
+| AR Aging | `POST /generate-reports/ar-report` | `endDate` |
+| AP Aging | `POST /generate-reports/ap-report` | `endDate` |
+| Cash Balance | `POST /generate-reports/cash-balance` | `reportDate` |
+| Cashflow | `POST /generate-reports/cashflow` | `primaryStartDate`, `primaryEndDate` |
+| Bank Balance | `POST /generate-reports/bank-balance-summary` | `primarySnapshotDate` |
+| Tax Ledger | `POST /generate-reports/vat-ledger` | `startDate`, `endDate` |
+| FA Register | `POST /generate-reports/fixed-assets-summary` | (check endpoint) |
+| Equity Movement | `POST /generate-reports/equity-movement` | `primarySnapshotStartDate`, `primarySnapshotEndDate` |
+
+**Data exports** (Excel/CSV) use `/data-exports/` with the same report names but simpler field names (e.g., P&L export uses `startDate`/`endDate` instead of snapshot dates).

package/assets/skills/jobs/references/credit-control.md

@@ -0,0 +1,273 @@
+# Credit Control / AR Chase
+
+Systematically chase overdue customer invoices, assess collection risk, and manage bad debt exposure. This is not just "send reminders" — it's a structured process to protect your cash flow and recognize when receivables are impaired.
+
+**CLI:** `jaz jobs credit-control [--overdue-days 30] [--json]`
+
+---
+
+## Phase 1: Generate the AR Aging
+
+The aging report is your starting point. Everything flows from this.
+
+### Step 1: Generate AR aging report
+
+```
+POST /api/v1/generate-reports/ar-report
+{ "endDate": "2025-02-28" }
+```
+
+**What you get:** All outstanding customer invoices grouped by aging bucket (current, 1-30 days, 31-60 days, 61-90 days, 91-120 days, 120+ days), with totals per customer and grand totals.
+
+### Step 2: Export for working paper (optional)
+
+```
+POST /api/v1/data-exports/ar-report
+{ "endDate": "2025-02-28" }
+```
+
+---
+
+## Phase 2: Prioritize
+
+### Step 3: Filter by overdue threshold
+
+If `--overdue-days` is specified (e.g., 30), focus on invoices overdue by at least that many days. Otherwise, review all overdue items.
+
+**Priority classification:**
+
+| Priority | Overdue | Action |
+|----------|---------|--------|
+| **Critical** | 90+ days | Escalate to management, consider legal, assess bad debt |
+| **High** | 60-90 days | Direct phone call, formal demand letter |
+| **Medium** | 30-60 days | Follow-up email with statement of account |
+| **Low** | 1-30 days | Gentle reminder, may be processing delay |
+| **Current** | Not yet due | No action needed — monitor only |
+
+### Step 4: Group by customer, sort by largest balance
+
+From the AR aging data, rank customers by total overdue amount (descending). The 80/20 rule applies — a handful of customers typically account for most of your overdue AR.
+
+---
+
+## Phase 3: Detailed Customer Review
+
+For each overdue customer (starting with the largest balances), pull the full picture.
+
+### Step 5: List outstanding invoices for a customer
+
+```
+POST /api/v1/invoices/search
+{
+  "filter": {
+    "contactResourceId": { "eq": "<customer-uuid>" },
+    "status": { "eq": "POSTED" },
+    "balanceAmount": { "gt": 0 }
+  },
+  "sort": { "sortBy": ["dueDate"], "order": "ASC" },
+  "limit": 100
+}
+```
+
+**What to check per invoice:**
+- `dueDate` — How overdue is it?
+- `balanceAmount` — How much is still owed? (Could be partially paid)
+- `reference` — The invoice number for follow-up correspondence
+- `totalAmount` vs `balanceAmount` — Has the customer been making partial payments?
+
+### Step 6: Check for unapplied credit notes
+
+Before chasing, verify there are no unapplied customer credit notes that should reduce the balance:
+
+```
+POST /api/v1/customer-credit-notes/search
+{
+  "filter": {
+    "contactResourceId": { "eq": "<customer-uuid>" },
+    "status": { "eq": "POSTED" }
+  },
+  "sort": { "sortBy": ["valueDate"], "order": "DESC" },
+  "limit": 50
+}
+```
+
+If there are unapplied credit notes, apply them before chasing:
+
+```
+POST /api/v1/invoices/{invoiceResourceId}/credits
+{
+  "credits": [
+    { "creditNoteResourceId": "<credit-note-uuid>", "amountApplied": 500.00 }
+  ]
+}
+```
+
+### Step 7: Generate statement of account
+
+```
+POST /api/v1/statement-of-account-export
+```
+
+The statement of account is what you send to the customer — it shows all invoices, payments, and the running balance. Attach this to follow-up communications.
+
+---
+
+## Phase 4: Follow-Up Priority List
+
+### Step 8: Build the chase list
+
+For each overdue customer, document:
+
+| Customer | Total Overdue | Oldest Invoice | Days Overdue | Priority | Action |
+|----------|--------------|----------------|--------------|----------|--------|
+| Acme Corp | $45,000 | INV-1023 | 95 | Critical | Phone + demand letter |
+| Beta Ltd | $12,500 | INV-1089 | 62 | High | Phone call |
+| Gamma Inc | $3,200 | INV-1134 | 35 | Medium | Email reminder |
+
+**Escalation process (typical SMB):**
+
+1. **Day 1-7 overdue:** Automated or gentle email reminder with invoice attached
+2. **Day 14 overdue:** Second reminder, direct email to AP contact
+3. **Day 30 overdue:** Phone call to AP contact, request payment commitment date
+4. **Day 45 overdue:** Escalate to customer's management, send statement of account
+5. **Day 60 overdue:** Formal demand letter, consider suspending future sales on credit
+6. **Day 90 overdue:** Final demand, engage collections agency or legal counsel
+7. **Day 120+ overdue:** Write off if uncollectable (see Phase 5)
+
+---
+
+## Phase 5: Bad Debt Assessment
+
+**Conditional:** Only if there are material amounts in the 90+ day aging bucket.
+
+### Step 9: Assess bad debt risk
+
+For invoices that appear uncollectable, evaluate using the ECL (Expected Credit Loss) model:
+
+**Calculator:** `jaz calc ecl`
+
+```bash
+jaz calc ecl --current 100000 --30d 50000 --60d 20000 --90d 10000 --120d 5000 --rates 0.5,2,5,10,50
+```
+
+This produces the provision matrix — the estimated total bad debt exposure based on aging buckets and historical loss rates.
+
+**Recipe:** `bad-debt-provision` — see `transaction-recipes/references/bad-debt-provision.md` for the full ECL provision pattern.
+
+### Step 10: Record bad debt write-off (if uncollectable)
+
+When a specific invoice is confirmed uncollectable (customer bankrupt, dissolved, or dispute resolution failed), write it off:
+
+**Option A: Customer credit note + write-off journal**
+
+Create a customer credit note to clear the invoice balance:
+
+```
+POST /api/v1/customer-credit-notes
+{
+  "contactResourceId": "<customer-uuid>",
+  "saveAsDraft": false,
+  "reference": "CN-BADDEBT-001",
+  "valueDate": "2025-02-28",
+  "lineItems": [{
+    "name": "Bad debt write-off — INV-1023",
+    "unitPrice": 45000.00,
+    "quantity": 1,
+    "accountResourceId": "<bad-debt-expense-uuid>"
+  }]
+}
+```
+
+Then apply the credit note to the invoice:
+
+```
+POST /api/v1/invoices/{invoiceResourceId}/credits
+{
+  "credits": [
+    { "creditNoteResourceId": "<credit-note-uuid>", "amountApplied": 45000.00 }
+  ]
+}
+```
+
+**Option B: Use DEBT_WRITE_OFF payment method**
+
+Record as a payment using the special write-off method:
+
+```
+POST /api/v1/invoices/{invoiceResourceId}/payments
+{
+  "payments": [{
+    "paymentAmount": 45000.00,
+    "transactionAmount": 45000.00,
+    "accountResourceId": "<bad-debt-expense-uuid>",
+    "paymentMethod": "DEBT_WRITE_OFF",
+    "reference": "WRITEOFF-INV-1023",
+    "valueDate": "2025-02-28"
+  }]
+}
+```
+
+**Accounting effect:** DR Bad Debt Expense, CR Accounts Receivable — removes the receivable from the books and recognizes the expense.
+
+---
+
+## Phase 6: Verification
+
+### Step 11: Re-run AR aging after actions
+
+```
+POST /api/v1/generate-reports/ar-report
+{ "endDate": "2025-02-28" }
+```
+
+**What to check:**
+- Credit notes have reduced the correct invoice balances
+- Written-off invoices no longer appear in the aging
+- Total AR ties to the Accounts Receivable balance on the trial balance
+
+### Step 12: Review trial balance impact
+
+```
+POST /api/v1/generate-reports/trial-balance
+{ "startDate": "2025-02-01", "endDate": "2025-02-28" }
+```
+
+**What to check:**
+- Accounts Receivable balance reflects all collections, credit notes, and write-offs
+- Bad Debt Expense (if write-offs were made) shows the correct amount
+- Allowance for Doubtful Debts (if using provision method) reflects the ECL calculation
+
+---
+
+## Credit Control Checklist (Quick Reference)
+
+| # | Step | Phase | Conditional |
+|---|------|-------|-------------|
+| 1 | Generate AR aging | Assess | Always |
+| 2 | Export working paper | Assess | Optional |
+| 3 | Filter by overdue threshold | Prioritize | If --overdue-days specified |
+| 4 | Group by customer | Prioritize | Always |
+| 5 | List outstanding invoices | Review | Always |
+| 6 | Check unapplied credit notes | Review | Always |
+| 7 | Generate statement of account | Review | Always |
+| 8 | Build chase list | Follow-up | Always |
+| 9 | Assess bad debt (ECL) | Bad debt | If material 90d+ balances |
+| 10 | Record write-off | Bad debt | If confirmed uncollectable |
+| 11 | Re-run AR aging | Verify | Always |
+| 12 | Review trial balance | Verify | Always |
+
+---
+
+## Tips for SMBs
+
+**Typical credit terms:** Net 30 is standard in Singapore. Some industries use Net 60 or Net 14. Whatever your terms, enforce them consistently — if you let one customer pay at 60 when terms are 30, everyone will.
+
+**Prevention is cheaper than collection.** Before extending credit to a new customer, do a basic credit check (ACRA business profile for SG companies, $5.50). Set a credit limit and stick to it.
+
+**The phone is more effective than email.** After 30 days, email follow-ups have diminishing returns. A 5-minute phone call to the AP department resolves more overdue invoices than 10 emails.
+
+**Document everything.** Keep records of all follow-up attempts (dates, who you spoke to, commitments made). If it goes to legal, you need an evidence trail.
+
+**When to involve legal:** If the amount exceeds $20,000 and the customer is unresponsive after 90 days, consider a letter of demand from a lawyer ($300-500). For amounts under $10,000, the Small Claims Tribunal (SG) is a cost-effective option.
+
+**Bad debt tax deduction (SG):** Bad debts written off are deductible for income tax purposes if you can prove the debt is genuinely irrecoverable and reasonable steps were taken to collect. Keep documentation.

package/assets/skills/jobs/references/fa-review.md

@@ -0,0 +1,267 @@
+# Fixed Asset Review
+
+Review the fixed asset register for accuracy, identify assets requiring disposal or write-off, process disposals, and reconcile the register to the trial balance. This is a housekeeping job — ensuring the FA register reflects reality.
+
+**CLI:** `jaz jobs fa-review [--json]`
+
+---
+
+## When to Do This
+
+- **Annually (minimum):** As part of year-end close or audit preparation
+- **Quarterly:** For growing businesses that acquire assets frequently
+- **Ad-hoc:** After a major event (office move, equipment upgrade, insurance claim)
+
+---
+
+## Phase 1: Take Stock
+
+### Step 1: List all fixed assets
+
+```
+POST /api/v1/fixed-assets/search
+{
+  "filter": { "status": { "eq": "ACTIVE" } },
+  "sort": { "sortBy": ["purchaseDate"], "order": "ASC" },
+  "limit": 1000
+}
+```
+
+**What you get:** Every active fixed asset with `name`, `purchaseDate`, `purchaseAmount`, `bookValueAmount`, `depreciationMethod`, `typeName`, and `status`.
+
+### Step 2: List fixed asset types
+
+```
+POST /api/v1/fixed-assets-types/search
+{
+  "filter": {},
+  "sort": { "sortBy": ["typeName"], "order": "ASC" },
+  "limit": 100
+}
+```
+
+Asset types define the default depreciation method and useful life. Common types for SMBs:
+
+| Type | Typical Useful Life | Depreciation | Examples |
+|------|-------------------|--------------|----------|
+| **Office Equipment** | 5-7 years | Straight-line | Desks, chairs, shelving |
+| **Computer Equipment** | 3-5 years | Straight-line or DDB | Laptops, servers, monitors |
+| **Motor Vehicles** | 5-8 years | Straight-line | Delivery vans, company cars |
+| **Furniture & Fittings** | 7-10 years | Straight-line | Reception area, meeting rooms |
+| **Leasehold Improvements** | Lease term | Straight-line | Renovation, fit-out |
+| **Plant & Machinery** | 5-15 years | Straight-line or DDB | Production equipment |
+| **Software** | 3-5 years | Straight-line | Licensed software, ERP |
+
+---
+
+## Phase 2: Review
+
+Work through the asset list and classify each asset.
+
+### Step 3: Identify fully depreciated assets still in use
+
+Search for assets where book value equals zero (or equals salvage value):
+
+```
+POST /api/v1/fixed-assets/search
+{
+  "filter": {
+    "status": { "eq": "ACTIVE" },
+    "bookValueAmount": { "eq": 0 }
+  },
+  "sort": { "sortBy": ["purchaseDate"], "order": "ASC" },
+  "limit": 1000
+}
+```
+
+**What to do:**
+- If the asset is still in use → no action required. It stays on the register at zero NBV. No further depreciation is posted.
+- If the asset is no longer in use → dispose (Phase 3)
+
+**Note:** Fully depreciated assets still in use should be reviewed for impairment reversal under IAS 36 if their recoverable amount is significantly higher than carrying amount (zero). In practice, most SMBs don't reverse — the asset just sits at zero until disposal.
+
+### Step 4: Identify assets no longer in use
+
+This is a physical verification step — walk through the office/warehouse and compare the register to reality. Common findings:
+
+- **Thrown away but not written off:** Old laptops, broken equipment disposed of without updating the register
+- **Lost or stolen:** Equipment that can't be located
+- **Returned under warranty:** Asset was replaced but the old entry wasn't removed
+- **Sold informally:** Asset was sold (e.g., to an employee) but the sale wasn't recorded
+
+**Flag these for disposal in Phase 3.**
+
+### Step 5: Review depreciation methods
+
+```
+POST /api/v1/fixed-assets/search
+{
+  "filter": { "status": { "eq": "ACTIVE" } },
+  "sort": { "sortBy": ["typeName"], "order": "ASC" },
+  "limit": 1000
+}
+```
+
+Group by asset type and verify:
+- All assets of the same type use the same depreciation method (consistency principle)
+- Useful lives are reasonable for the asset type
+- No assets have an obviously wrong method (e.g., a building on 3-year straight-line)
+
+**Conditional:** Only act on this if you find inconsistencies. Changing depreciation method mid-life is a change in accounting estimate (IAS 8) — apply prospectively, not retrospectively.
+
+---
+
+## Phase 3: Disposals
+
+### Step 6: Sale disposals
+
+When an asset is sold, record the disposal. The calculator computes accumulated depreciation to disposal date, net book value, and gain/loss.
+
+**Calculator:** `jaz calc asset-disposal`
+
+```bash
+jaz calc asset-disposal --cost 50000 --salvage 5000 --life 5 --acquired 2022-01-01 --disposed 2025-06-15 --proceeds 12000
+```
+
+**Recipe:** `asset-disposal` — see `transaction-recipes/references/asset-disposal.md` for the full journal pattern.
+
+Record the disposal journal:
+
+```
+POST /api/v1/journals
+{
+  "saveAsDraft": false,
+  "reference": "FA-DISP-001",
+  "valueDate": "2025-06-15",
+  "journalEntries": [
+    { "accountResourceId": "<bank-account-uuid>", "amount": 12000.00, "type": "DEBIT", "name": "Proceeds from sale of Delivery Van VH-1234" },
+    { "accountResourceId": "<accumulated-depreciation-uuid>", "amount": 31500.00, "type": "DEBIT", "name": "Clear accumulated depreciation — Delivery Van VH-1234" },
+    { "accountResourceId": "<loss-on-disposal-uuid>", "amount": 6500.00, "type": "DEBIT", "name": "Loss on disposal — Delivery Van VH-1234" },
+    { "accountResourceId": "<fixed-asset-cost-uuid>", "amount": 50000.00, "type": "CREDIT", "name": "Remove cost — Delivery Van VH-1234" }
+  ]
+}
+```
+
+Then mark the asset as sold in the FA register:
+
+```
+POST /api/v1/mark-as-sold/fixed-assets
+```
+
+### Step 7: Scrap / write-off disposals
+
+When an asset is scrapped (no sale proceeds), the full NBV becomes a loss.
+
+**Calculator:**
+
+```bash
+jaz calc asset-disposal --cost 50000 --salvage 5000 --life 5 --acquired 2022-01-01 --disposed 2025-06-15 --proceeds 0
+```
+
+Record the write-off journal:
+
+```
+POST /api/v1/journals
+{
+  "saveAsDraft": false,
+  "reference": "FA-WRITEOFF-001",
+  "valueDate": "2025-06-15",
+  "journalEntries": [
+    { "accountResourceId": "<accumulated-depreciation-uuid>", "amount": 31500.00, "type": "DEBIT", "name": "Clear accumulated depreciation — Old Server Rack" },
+    { "accountResourceId": "<loss-on-disposal-uuid>", "amount": 18500.00, "type": "DEBIT", "name": "Write-off loss — Old Server Rack" },
+    { "accountResourceId": "<fixed-asset-cost-uuid>", "amount": 50000.00, "type": "CREDIT", "name": "Remove cost — Old Server Rack" }
+  ]
+}
+```
+
+Then mark the asset as discarded:
+
+```
+POST /api/v1/discard-fixed-assets/{assetResourceId}
+```
+
+---
+
+## Phase 4: Verification
+
+### Step 8: FA register reconciliation
+
+```
+POST /api/v1/generate-reports/fixed-assets-summary
+```
+
+```
+POST /api/v1/generate-reports/fixed-assets-recon-summary
+```
+
+The reconciliation report shows:
+
+```
+Opening NBV (start of period)
++ Additions (new assets acquired)
+- Disposals (sold or scrapped)
+- Depreciation (period charge)
+= Closing NBV (end of period)
+```
+
+### Step 9: Reconcile to trial balance
+
+```
+POST /api/v1/generate-reports/trial-balance
+{ "startDate": "2025-01-01", "endDate": "2025-12-31" }
+```
+
+**What must tie:**
+
+| FA Register | Trial Balance Account |
+|------------|----------------------|
+| Total cost (all active assets) | Fixed Assets (at cost) — total of all FA cost accounts |
+| Total accumulated depreciation | Accumulated Depreciation — total of all accum. dep. accounts |
+| Closing NBV | Cost minus Accumulated Depreciation = Net Book Value |
+| Period depreciation charge | Depreciation Expense on P&L |
+| Gain/Loss on disposal | Other Income / Other Expense on P&L |
+
+If the register and trial balance don't tie, investigate:
+- Manual journal entries to FA accounts that bypassed the register
+- FA register entries that didn't generate journals (system issue)
+- Disposed assets not yet removed from the register
+
+---
+
+## FA Review Checklist (Quick Reference)
+
+| # | Step | Phase | What |
+|---|------|-------|------|
+| 1 | List all fixed assets | Take stock | Search active assets |
+| 2 | List asset types | Take stock | Review type definitions |
+| 3 | Fully depreciated assets | Review | Identify NBV = 0 assets |
+| 4 | Assets no longer in use | Review | Physical verification |
+| 5 | Depreciation methods | Review | Consistency check |
+| 6 | Sale disposals | Dispose | Calculator + journal + mark as sold |
+| 7 | Scrap / write-off | Dispose | Calculator + journal + discard |
+| 8 | FA register report | Verify | Reconciliation summary |
+| 9 | Reconcile to trial balance | Verify | FA register = TB accounts |
+
+---
+
+## Tips for SMBs
+
+**Keep a low-value asset threshold.** Items under $1,000 (or your chosen threshold) should be expensed immediately, not capitalized as fixed assets. This reduces register clutter and depreciation complexity. Common SG practice is $1,000-$5,000 depending on company size.
+
+**Tag your assets.** Use physical asset tags (numbered stickers) and record the tag number as the asset reference in Jaz. This makes physical verification much faster.
+
+**Review useful lives annually.** If your "3-year laptop" is still going strong at year 5, the useful life estimate was wrong. Adjust prospectively (IAS 8) — extend the remaining life and recalculate monthly depreciation.
+
+**Depreciation for tax (SG-specific):**
+- IRAS allows 1-year write-off for assets costing <= S$5,000 (Section 19A(10A))
+- IRAS allows 3-year accelerated write-off for all other assets (Section 19A)
+- Book depreciation (straight-line over useful life) and tax depreciation (accelerated) can differ — track the deferred tax difference
+
+**Insurance coverage check.** While reviewing assets, verify that your business insurance covers the replacement cost of active assets. Fully depreciated assets may still have significant replacement value — a 5-year-old server at $0 NBV still costs $15,000 to replace.
+
+**Common FA accounts in Jaz:**
+- Fixed Assets (at cost) — typically one sub-account per asset type
+- Accumulated Depreciation — mirror sub-accounts for each asset type
+- Depreciation Expense — on P&L, may be split by asset type for reporting
+- Gain on Disposal — Other Income
+- Loss on Disposal — Other Expense