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.

Q04 - Recheck settlement-sheet arithmetic using approved amounts

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. Approved final amount schedule, single currency, explicit status for every listed item, exact cents and source refs; Excel or decimal-safe script. Lawyer must supply holdbacks, priorities and fee amount; never derive entitlements, lien reductions, taxes or release authorization.

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. Negative controls: add a second draft COST row and require duplicate-ID reporting; change any approved status to unresolved and require an incomplete result. Do not approve an allocation from an arithmetic match.
3. 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.
4. 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.
5. 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
Use integer cents and one currency. Deduction amounts must be nonnegative. category: fee, cost, lien, reserve or other; status: approved or unresolved. Duplicate line IDs are errors, never permission to silently choose a row. Report missing approval/source references independently.

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

COPYABLE OFFLINE PROMPT
Using this synthetic settlement.json, validate integer cents and one currency, required source references and approval IDs. Missing approval/source data is unresolved. Sum approved deductions exactly once by line_id and subtract from gross. Compare each approved line and amount with draft_lines; flag missing, extra or duplicate IDs, amount differences and unresolved items. Return approved deduction sum, calculated net, draft net, difference and source-linked exceptions. Do not choose fees, resolve liens, determine entitlement, infer missing costs, approve disbursement, create payment instructions or change records. If any item is unresolved, label the worksheet incomplete for lawyer review.

INPUTS
settlement.json = {matter_id,currency,gross_cents,approved_lines:[{line_id,category,amount_cents,source_ref,approved_by,status}],draft_lines:[{line_id,amount_cents}],draft_net_cents}. category is fee|cost|lien|reserve|other; status is approved|unresolved. All deduction amounts nonnegative integer cents; gross is approved. Any unresolved item blocks a complete arithmetic report.

OUTPUT
An arithmetic-difference worksheet with source IDs, duplicate or omitted lines and review questions about an already prepared proposed allocation.

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
Gross 10000000 cents; FEE=3000000, COST=100000, LIEN=2000000, RESERVE=50000, all approved. Draft omits RESERVE and shows net 4900000. Expected deductions 5150000; calculated net 4850000; draft net overstates by 50000; missing RESERVE source flagged. Duplicate COST must be separately reported, not silently removed and approved.

LIMITS
- Lawyer confirms completeness, legal allocations, client approval and any required statements; accountant independently checks math. No actual bank details or personal data needed for pilot. No transfers, check requests, payment execution, release decision or legal/financial advice.
- 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.