← BriefcaseCONTENT HISTORY

Update to Briefcase

Snapshot Oct 2, 2026 · 00:28 UTC · version 1.1.1

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "manual-journals",
  "description": "Post a manual journal to a Briefcase Ledger client, such as a correction, reclassification, capital introduction or one-off period-end adjustment, with the accounts checked, the lock date respected and a preview agreed before anything posts. Use when the user asks to post, book or record a journal, move a balance between accounts, or correct a posting.",
  "included_files": [],
  "skill_md_contents": "---\nname: manual-journals\ndescription: Post a manual journal to a Briefcase Ledger client, such as a correction, reclassification, capital introduction or one-off period-end adjustment, with the accounts checked, the lock date respected and a preview agreed before anything posts. Use when the user asks to post, book or record a journal, move a balance between accounts, or correct a posting.\n---\n\n# Manual journals in Briefcase\n\nA posted journal changes the client's accounts immediately and can only be reversed in the Briefcase app. Treat every journal as irreversible from here. Manual journals only exist for Briefcase Ledger clients (Xero and QuickBooks clients return `UNSUPPORTED_CAPABILITY`) and need the Ledger post permission.\n\n## Before drafting\n\n- Check whether a journal is the right tool. Recurring prepayments, accruals, deferred income and depreciation belong in the close tools (see the financial close review skill), and a miscoded bill should be fixed on the transaction, not journalled over.\n- `briefcase_get_client` gives `general_ledger_lock_date`. Entries must be dated after it.\n- `briefcase_get_reference_data` with `kind: accounts` for account ids (narrow with `account_class`, for example `EXPENSE`, or `search_term`), and `kind: tax_rates` when a line carries VAT. Quote each account's name and code back to the user.\n- To correct something already posted, read it first with `briefcase_list_journals` (filter by `account_id` and dates) and `briefcase_get_journal`.\n\n## Draft and preview\n\nCall `briefcase_create_manual_journal` with `mode: preview`:\n\n- `entry_date`, `description` and a `reference` the user will recognise later.\n- `lines`: each has an `account_id` and either a `debit` or a `credit` (never both), as gross amounts in major units. A `tax_rate_id` splits the VAT to the VAT account automatically; revenue and expense lines need one.\n- `business_id` (and `property_id` with it) when the entry belongs to one business or property.\n\nShow the user the lines as a small debit and credit table with the totals, then explain any blocker:\n\n- `PERIOD_LOCKED`: the date is on or before the lock date. Move the date or ask the user to move the lock date in the app.\n- `UNBALANCED`: debits and credits differ. Never add a balancing line the user did not ask for.\n- `RESERVED_ACCOUNT`: control accounts such as accounts receivable and payable cannot take manual journals; the fix belongs on the invoice or bill.\n- Deleted or unknown accounts, invalid lines, and accounts spanning businesses or properties.\n\n## Post\n\nOnly after the user explicitly approves the preview, call again with `mode: execute`, the `preview_id` and a fresh `idempotency_key`. Return the `web_url`, then show the effect: `briefcase_get_balance_sheet` or `briefcase_get_profit_and_loss` for the affected period.\n\nIf a call fails with a network error, retry with the same `idempotency_key`; Briefcase will not post the journal twice. Never retry with a new key to get round an error.\n"
}

SHA-256: ad36c3e4fd967d2c431dac889008000d21fbcc3d23222f7d87a24d17ca67aadf