START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

Q03 - Compare the three trust-reconciliation records read-only

Status: Proposed / not tested

WHAT THIS KIT CONTAINS
Exact input scaffolds and synthetic examples for an offline pilot. Header, JSON-shape and fixture-consistency checks validate these files only; they do not test an assistant, product integration, legal decision, PDF inspection or live workflow.

PREREQUISITES
1. Same account/currency/cutoff date; accountant-approved opening balances and outstanding classifications; complete deidentified ledger exports; spreadsheet formulas or fixed-decimal script; no live bank connection needed.

SETUP
1. Use the separate synthetic example inputs first. Fill a copy of the blank template or input checklist for your own preparation; do not mix fixture information with real records.
2. Preserve JSON keys and nesting. JSON templates use blank strings, null scalars and nested placeholder rows to expose missing preparation. They are valid JSON scaffolds, deliberately incomplete. Fill all required fields and validate against the supplied schema; semantic checks in this guide remain necessary.
3. Give only the selected synthetic input sections/files and the prompt below to an existing firm-approved private workspace, or perform the clerical comparison manually. Keep expected-result notes separate from the input. For planning checklists, leave unknown requirements explicit instead of inventing them.
4. Compare the draft output with the expected fixture result. A reviewer checks original evidence and all exceptions before any separately approved action. Retain the version, scope and source references with the review.

INPUT RULES
Integer cents only; positive signed adjustments add to the bank. Use one account, one currency, one cutoff. A missing approval or source reference makes an adjustment unresolved. Classifications come from the accountant; they are not inferred.

FILES
- reconciliation.template.json: Preserve nested input structure and validate supplied field types
- reconciliation.example.json: Preserve nested input structure and validate supplied field types
- reconciliation.schema.json: Preserve nested input structure and validate supplied field types

COPYABLE OFFLINE PROMPT
Use this synthetic reconciliation.json read-only. Check one account/currency/cutoff and integer amounts. Missing adjustment approval or source references are unresolved and prevent a complete comparison. Adjusted bank = bank_closing_cents + sum(approved signed adjustments). Compare it with firm_ledger_closing_cents and the sum of client_balances. Return all three totals, pairwise differences, adjustment IDs, missing client mappings, duplicate transaction IDs and unresolved rows. Never invent an adjustment, classify a transaction, net different clients/currencies, mark an account reconciled, post entries or move money. Label the result preliminary accountant/lawyer review.

INPUTS
reconciliation.json = {account_id,currency,cutoff_date,bank_closing_cents,firm_ledger_closing_cents,approved_bank_adjustments:[{adjustment_id,signed_cents,source_ref,approved_by}],client_balances:[{client_id,balance_cents,source_ref}],transactions:[{transaction_id,client_id,signed_cents,bank_match_id,classification,source_ref}]}. Amounts integer cents in a single currency; positive approved adjustments add to bank closing. classification is accountant-supplied cleared|outstanding|unresolved.

OUTPUT
A list of balance differences and unresolved transaction IDs. Approved adjustments and source references remain visible for the bookkeeper’s review.

Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing.

EXPECTED SYNTHETIC FIXTURE RESULT
Bank closing=120000 cents; approved outstanding-check adjustment=-20000; firm ledger=100000; clients C1=60000 and C2=39000. Expected adjusted bank=100000, firm=100000, clients=99000; bank/firm difference 0 and both minus clients=1000 cents unresolved. A transaction with blank client_id is also flagged; the tool must not assign the missing 1000 to either client.

LIMITS
- Responsible lawyer and qualified bookkeeper review original statements, timing and jurisdictional rules. Balances or differences alone do not prove misuse. No account access, journal entries, transfers, bill applications or completion of a legal compliance certification.
- Synthetic data only in the delivered files. No credentials, real client records, live-action scripts, API connection or Make blueprint is included.
- Real use requires firm-approved access, confidentiality, processing terms, retention, product access and reviewer authority. Pseudonymous IDs alone do not anonymize real records.