Court Clerk Reconciliation
Overview
Produce structured JSON closeout packets by reconciling local case materials against a Court Operations Portal. Follow a fixed reconciliation hierarchy, use the portal to verify records against current schedules and policies, compute financial totals and payment plans, and flag all unsupported charges for exclusion.
Core Workflow
- Read every local payload file and the answer template.
- Query the portal for each target case, its charges, fee schedules, payment policies, forms, and any jurisdiction/citation/docket records needed to fill the template.
- Apply the reconciliation hierarchy (see reconciliation-rules.md).
- Compute case-level financials, payment plans, and register totals. Apply exclusion rules for unsupported charges (see fee-rules.md).
- Map form fields and use the exact placeholder
"TBD from case file" for any required field the available materials cannot fill (see forms-reference.md).
- Assemble the answer object sorted by case/citation number ascending, with ISO dates and currency to two decimal places. Use only the enum values declared in the answer template.
Reconciliation Hierarchy
When sources conflict, resolve by this priority chain (highest to lowest):
- Courtroom hearing notes / bench statements — judge's oral pronouncements override draft worksheets, legacy screens, and finance queue extracts on disposition, departure status, plea, and sentence terms.
- Clerk audit/corroboration memos — override finance queue records on identity (name spelling, DOB) and counsel classification (appointed-private vs. public defender).
- Current portal records (CMS, fee schedules, payment policies, forms) — override stale or archived amounts, obsolete fee codes, and local worksheet figures.
- Docket entries / minute notes — when a final signed order is missing, the case stays deferred/excluded regardless of what a draft worksheet says.
- Finance queue extracts — lowest authority; use only when no higher source conflicts.
For details and example patterns, see reconciliation-rules.md.
Portal Query Strategy
Query the portal endpoints listed in the task prompt. Typical patterns:
GET /api/cases?case_number=X or /api/citations?citation_number=Y for case identity, status, and party records.
GET /api/charges?case_number=X for offense codes, plea, and charge disposition.
GET /api/docket-entries?case_number=X for signed orders and entry history.
GET /api/fee-schedules?jurisdiction=Z for current fee amounts.
GET /api/payment-policies?jurisdiction=Z for installment rules, account-fee treatment, payment application order.
GET /api/forms?form_id=F for form metadata and field requirements.
GET /api/financial-petitions?petition_id=P when a payment petition is in play.
GET /api/search?q=term for cross-reference lookups.
See portal-query-patterns.md for complete query patterns for each docket type.
Financial Calculation Rules
Every fee posted to a case must be supported by the current fee schedule, the judge's order, or the active payment policy. Do not carry forward fees from stale schedules or draft worksheets. Detailed rules and payment-plan math are in fee-rules.md.
Core principles:
- Court costs are jurisdiction-specific flat amounts (verify from the portal fee schedule; do not assume a fixed number).
- Fines are taken from the sentencing pronouncement or the active fee schedule for traffic violations.
- Drug/crime-lab assessments must be verified against the current schedule.
- Public-defender user fees post only when counsel is classified as public defender, not appointed-private.
- Exclude account-management fees, collection fees, late fees, DMV notice fees, returned-check fees, restitution, and copy/certification fees unless directly supported by the current policy or judge's order.
- For traffic-violation matters, exclude stale schedule amounts and statutory-maximum substitutions when the current schedule provides a specific tier.
Payment Plan Math
For installment agreements, compute the schedule from the total due and the approved monthly amount:
total_installments = ceil(total_due / monthly_payment)
full_payment_count = floor(total_due / monthly_payment)
final_payment_amount = total_due - (full_payment_count * monthly_payment)
final_due_date advances from first_due_date by (total_installments - 1) months.
return_to_court_date is typically 60 days after final_due_date.
When a petition includes a budget: disposable income = monthly_income - total_monthly_obligations. If the requested installment is within the policy band and does not exceed disposable income, classify as supportable or supported_by_budget.
Placeholder Convention
For any required template or form field that cannot be completed from the portal, case file, or local materials, use the exact string "TBD from case file". Never invent names, identifiers, addresses, phone numbers, license numbers, probation-officer names, or office locations. See forms-reference.md for a complete field mapping.
Answer Assembly
- Sort all lists by case_number or citation_number ascending, unless the template specifies a different order.
- Use ISO YYYY-MM-DD dates and YYYY-MM-DDTHH:MM:SS datetimes.
- All currency values are numeric and rounded to two decimal places.
- Use enum string values exactly as declared in the answer template; do not replace them with narrative prose.
- Return a single JSON object matching the template structure. Do not wrap in markdown code fences unless the task prompt explicitly asks for them.
1---2name: court-clerk-reconciliation-33description: "Court-clerk reconciliation and financial closeout workflow for criminal, traffic, and post-sentencing dockets. Use when a deputy clerk task requires: (1) cross-referencing local hearing notes, audit memos, finance worksheets, petition summaries, or form excerpts against a Court Operations Portal REST API, (2) resolving identity/counsel/fee/status/departure conflicts across conflicting sources, (3) computing per-case financial totals (fines, costs, assessments, user fees, surcharges), (4) structuring approved post-disposition payment plans with installment math, (5) preparing CC-1375 probation referrals, CC-1379 license-suspension/installment orders, or local payment-plan forms, (6) identifying unsupported or stale charges for exclusion, or (7) assembling docket-register entries with batch totals from a multi-case closeout batch."4license: MIT5compatibility: designed for deepagents-code6metadata:7 source: https://skillmd.com/skills/prism-shadow/court-clerk-reconciliation-38---910# Court Clerk Reconciliation1112## Overview1314Produce structured JSON closeout packets by reconciling local case materials against a Court Operations Portal. Follow a fixed reconciliation hierarchy, use the portal to verify records against current schedules and policies, compute financial totals and payment plans, and flag all unsupported charges for exclusion.1516## Core Workflow17181. Read every local payload file and the answer template.192. Query the portal for each target case, its charges, fee schedules, payment policies, forms, and any jurisdiction/citation/docket records needed to fill the template.203. Apply the reconciliation hierarchy (see [reconciliation-rules.md](references/reconciliation-rules.md)).214. Compute case-level financials, payment plans, and register totals. Apply exclusion rules for unsupported charges (see [fee-rules.md](references/fee-rules.md)).225. Map form fields and use the exact placeholder `"TBD from case file"` for any required field the available materials cannot fill (see [forms-reference.md](references/forms-reference.md)).236. Assemble the answer object sorted by case/citation number ascending, with ISO dates and currency to two decimal places. Use only the enum values declared in the answer template.2425## Reconciliation Hierarchy2627When sources conflict, resolve by this priority chain (highest to lowest):28291. **Courtroom hearing notes / bench statements** — judge's oral pronouncements override draft worksheets, legacy screens, and finance queue extracts on disposition, departure status, plea, and sentence terms.302. **Clerk audit/corroboration memos** — override finance queue records on identity (name spelling, DOB) and counsel classification (appointed-private vs. public defender).313. **Current portal records** (CMS, fee schedules, payment policies, forms) — override stale or archived amounts, obsolete fee codes, and local worksheet figures.324. **Docket entries / minute notes** — when a final signed order is missing, the case stays deferred/excluded regardless of what a draft worksheet says.335. **Finance queue extracts** — lowest authority; use only when no higher source conflicts.3435For details and example patterns, see [reconciliation-rules.md](references/reconciliation-rules.md).3637## Portal Query Strategy3839Query the portal endpoints listed in the task prompt. Typical patterns:4041- `GET /api/cases?case_number=X` or `/api/citations?citation_number=Y` for case identity, status, and party records.42- `GET /api/charges?case_number=X` for offense codes, plea, and charge disposition.43- `GET /api/docket-entries?case_number=X` for signed orders and entry history.44- `GET /api/fee-schedules?jurisdiction=Z` for current fee amounts.45- `GET /api/payment-policies?jurisdiction=Z` for installment rules, account-fee treatment, payment application order.46- `GET /api/forms?form_id=F` for form metadata and field requirements.47- `GET /api/financial-petitions?petition_id=P` when a payment petition is in play.48- `GET /api/search?q=term` for cross-reference lookups.4950See [portal-query-patterns.md](references/portal-query-patterns.md) for complete query patterns for each docket type.5152## Financial Calculation Rules5354Every fee posted to a case must be supported by the current fee schedule, the judge's order, or the active payment policy. Do not carry forward fees from stale schedules or draft worksheets. Detailed rules and payment-plan math are in [fee-rules.md](references/fee-rules.md).5556Core principles:5758- Court costs are jurisdiction-specific flat amounts (verify from the portal fee schedule; do not assume a fixed number).59- Fines are taken from the sentencing pronouncement or the active fee schedule for traffic violations.60- Drug/crime-lab assessments must be verified against the current schedule.61- Public-defender user fees post only when counsel is classified as public defender, not appointed-private.62- Exclude account-management fees, collection fees, late fees, DMV notice fees, returned-check fees, restitution, and copy/certification fees unless directly supported by the current policy or judge's order.63- For traffic-violation matters, exclude stale schedule amounts and statutory-maximum substitutions when the current schedule provides a specific tier.6465## Payment Plan Math6667For installment agreements, compute the schedule from the total due and the approved monthly amount:6869- `total_installments = ceil(total_due / monthly_payment)`70- `full_payment_count = floor(total_due / monthly_payment)`71- `final_payment_amount = total_due - (full_payment_count * monthly_payment)`72- `final_due_date` advances from `first_due_date` by `(total_installments - 1)` months.73- `return_to_court_date` is typically 60 days after `final_due_date`.7475When a petition includes a budget: disposable income = monthly_income - total_monthly_obligations. If the requested installment is within the policy band and does not exceed disposable income, classify as `supportable` or `supported_by_budget`.7677## Placeholder Convention7879For any required template or form field that cannot be completed from the portal, case file, or local materials, use the exact string `"TBD from case file"`. Never invent names, identifiers, addresses, phone numbers, license numbers, probation-officer names, or office locations. See [forms-reference.md](references/forms-reference.md) for a complete field mapping.8081## Answer Assembly8283- Sort all lists by case_number or citation_number ascending, unless the template specifies a different order.84- Use ISO YYYY-MM-DD dates and YYYY-MM-DDTHH:MM:SS datetimes.85- All currency values are numeric and rounded to two decimal places.86- Use enum string values exactly as declared in the answer template; do not replace them with narrative prose.87- Return a single JSON object matching the template structure. Do not wrap in markdown code fences unless the task prompt explicitly asks for them.