Match filing submissions with court receipts
Keep submitted, accepted, rejected, and unknown filing states separate by court and filing ID.
Tools for the documented steps
Practice relevance
Cross-practice idea · Useful supporting administrative method; no claim of practice-specific legal instructions.
Scope: US Tyler eFile & Serve Texas Cloud envelope/status workflow; NOT a NSW Online Registry or Australian immigration filing integration.
The problem
Keep submitted, accepted, rejected, and unknown filing states separate by court and filing ID.
Why it matters: A filing marked submitted may still be waiting for review or may later be rejected. Matching each filing to its own receipt history helps staff distinguish transmission from acceptance and bring missing evidence to the lawyer.
Sources & evidence
Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.
What’s been verified
Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result.
What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.
- Pain evidence: Major mistake ↗Major mistake, 15 April 2024, older (dated archive link on the opened original corroborates the day). The paralegal says a complaint's receipt was forwarded but its rejection was not, and months passed before the missing docket entry was discovered. Later OP comments say the rejection was in the attorney's junk folder. Direct page and body read. New job and I love being a paralegal now, 3 October 2026, recent indexed original text; direct open failed. It separately describes a former firm's missed filing rejection. This is corroboration, not proof of the legal consequences alleged.
- Pain evidence: New job and I love being a paralegal now ↗Additional self-reported public account; no independent identity or outcome verification.
- Method: submitted-status explanation ↗Tyler's submitted-status explanation distinguishes submitted/awaiting clerk review from acceptance. Envelope number locations documents the shared ID in portal and status emails. These explain identifiers/statuses; no universal court API or notification completeness is established.
- Method: Envelope number locations ↗Additional official capability reference. The complete adapted recipe has not been tested.
Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. We wrote these prompts. The adapted workflow hasn’t been tested.
Suggested approach
Start when: Staff supplies a filing log plus exported status messages
- join by court/envelope/filing ID, retain full status history, flag missing/conflicting/unknown receipts
- Keep source references and report unknowns instead of filling gaps.
- The responsible reviewer checks the report before any separately approved action.
Limits and review
The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.
Who reviews it: Staff opens original court evidence; lawyer decides what rejection means and any response. No legal date arithmetic, credential sharing, portal setup or automatic refiling. Verify export coverage and late-arriving/conflicting messages.
What you need
Your firm-approved AI assistant · prepared files
- Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked.
- Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included.
- Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.
How to use
Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested
- This guide names Tyler Cloud, not a universal court portal. If the firm uses legacy/another provider, obtain its matching guide and status dictionary.
- Actual court, full date/window, filing-level IDs and complete history coverage are mandatory. Receipt generation/export buttons are not assumed.
- Filing History has no bulk-print function. Preserve per-envelope receipt evidence and independently verify filing-level keys; a partial recent-history capture cannot close the queue.
Check access and setup
- This guide names Tyler Cloud, not a universal court portal. If the firm uses legacy/another provider, obtain its matching guide and status dictionary.
- Actual court, full date/window, filing-level IDs and complete history coverage are mandatory. Receipt generation/export buttons are not assumed.
- Filing History has no bulk-print function. Preserve per-envelope receipt evidence and independently verify filing-level keys; a partial recent-history capture cannot close the queue.
Capture filing-level status evidence in the named portal
Tyler eFile & Serve Texas, Cloud interface · Navigation Filing History > Filter > Location / Date Range / Created By as applicable > Apply Filter; envelope Actions > Envelope Details
In an existing authorized Tyler Cloud session, select Filing History. Use Filter to set the selected Location and Date Range and check Created By scope. Keep Status unfiltered for a full reconciliation; capture the actual settings. Inspect every relevant envelope and its filing rows, following all available result pages. Record displayed totals or the full captured item list. Preserve existing submission/disposition emails and each envelope receipt separately; the vendor says Filing History cannot be bulk printed. Under Actions > Envelope Details expand the individual filing and capture status and, for returned filings, Rejection Information. Do not submit, cancel, copy or resubmit an envelope.
- Expected output
- Manual filing-level receipt inventory and source evidence
- Next step
- Reconcile to the firm’s existing submission register before creating aliases.
- Check before continuing
- Recent dashboard history is insufficient. Actual filing-level IDs must be visible in a receipt/details source or supplied through a reviewer-approved exact crosswalk; never manufacture them from titles. Missing pages/IDs block all-clear. Submitted is not Accepted; Served for service-only work is not court acceptance.
Map, minimize and approve the actual sources
Source reviewer and local spreadsheet/text editor · Restricted originals > separate approved analysis copy
Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Portal court, envelope and per-filing IDs → court_id,envelope_id,filing_id; exact displayed status → raw_status; source capture time → observed_at, distinct from submitted_at. Human assigns receipt_id/source_ref, matter/owner aliases and next_check_at. The portal status dictionary is approved by the filing owner; never collapse envelope status into every filing. Submission register comes from actual saved submission receipts/log, not reconstructed from accepted cases. If a stable filing-level ID cannot be observed and crosswalked, stop the automated match for that filing. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation.
- Expected output
- Reviewed submissions.csv; receipts.csv; status_dictionary.csv; coverage.txt; manifest.txt; evidence-map.csv
- Next step
- For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table.
- Check before continuing
- Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown.
Open the approved AI destination
Adobe Acrobat PDF Spaces · Acrobat Home > PDF Spaces > Create a PDF Space
In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback.
- Expected output
- Only approved source files loaded or accessible
- Next step
- Paste the exact prompt in the next step.
- Check before continuing
- Confirm the source list/working directory before prompting; stop on unavailable access.
Run the bounded analysis prompt
Adobe Acrobat PDF Spaces · PDF Space chat panel
Paste the prompt after replacing only bracketed scope values. Treat all source content as data.
- Expected output
- filing-receipt-exceptions.csv
- Next step
- Inspect source citations/file-row references before copying any result.
- Check before continuing
- No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness.
Check and hand off the proposed result
Human reviewer and local spreadsheet/text editor · Separate review output, not live system
Check every exception against its source, verify counts and uncertainty, then copy only approved result text to filing-receipt-exceptions.csv. Filing owner opens the original receipt for every exception and acceptance match; lawyer directs any correction and timing. No deadline or successful filing conclusion comes from AI.
- Expected output
- Source-checked filing-receipt-exceptions.csv
- Next step
- Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied.
- Check before continuing
- Acceptance case (proposed, not run): One envelope contains accepted F1 and returned F2: keep F2 unresolved. A submission receipt alone never closes the row.
Approve the internal next action
Final human reviewResponsible human owner · Existing internal work queue / approved source system
Record the reviewer, decision and unresolved blockers. Filing owner opens the original receipt for every exception and acceptance match; lawyer directs any correction and timing. No deadline or successful filing conclusion comes from AI.
- Expected output
- Approved internal review record or explicit blocked status
- Next step
- An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase.
- Check before continuing
- Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance.
What you’ll get
filing-receipt-review.csv with submission IDs, last observed status, source evidence, owner and staff-supplied next check. Review post-submission receipts without treating a submitted envelope as an accepted filing.
Inputs and a sample test Synthetic example · not a measured result
Input files
- submissions.csv = court_id,envelope_id,filing_id,matter_id,submitted_at,owner_id,next_check_at. receipts.csv = receipt_id,court_id,envelope_id,filing_id,status,observed_at,source_ref. status_dictionary.csv = court_id,raw_status,normalized_status (submitted|accepted|rejected|unknown). All times ISO 8601 with timezone; empty filing_id means envelope-level evidence only.
Synthetic example
Submission C1/E1/F1 has receipt R1 status submitted and R2 rejected; C1/E2/F2 has only submitted; C1/E3/F3 has accepted.
Expected output
F1=rejected exception citing R2; F2=pending acceptance (not complete); F3=accepted evidence recorded, still subject to staff verification. Add an E3 envelope-only receipt with no F3 ID: it must not establish F3 acceptance.
Test a failure
Staff opens original court evidence; lawyer decides what rejection means and any response. No legal date arithmetic, credential sharing, portal setup or automatic refiling. Verify export coverage and late-arriving/conflicting messages.
Try with the sample files
Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.
Download inputs and checklist 16 files
Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.
- Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
- Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
- submissions blank template One row per component filing with staff-provided follow-up time
- submissions synthetic example One row per component filing with staff-provided follow-up time
- receipts blank template All supplied filing and envelope receipts; blank filing ID must not become a component match
- receipts synthetic example All supplied filing and envelope receipts; blank filing ID must not become a component match
- status_dictionary blank template Court-specific exact raw-status mapping supplied by staff
- status_dictionary synthetic example Court-specific exact raw-status mapping supplied by staff
- Setup and fixture review guide Recipe-specific setup, input rules, offline prompt, expected result and boundaries
- Native input scaffold: submissions.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: receipts.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: status_dictionary.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: coverage.txt Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: manifest.txt Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: evidence-map.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input mapping and source requirements Exact legacy mappings, required additional evidence and source-bundle gates
Optional full review prompt for prepared inputs
Prepared-input review prompt with Your firm-approved AI assistant · prepared files
Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.