Reconcile filing submissions with acceptance or rejection receipts
Get the source data and prepare the review

Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested

WHAT WAS CHECKED
Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed.

BEFORE YOU START
- 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.

DATA ACQUISITION LIMITS
- 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.

MAP THE ACTUAL SOURCE TO THE REVIEW INPUT
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 no stable filing-level ID is exposed, record an explicit identity blocker rather than treating envelope ID as every filing ID.

INPUTS THE ASSISTANT MAY READ
submissions.csv; receipts.csv; status_dictionary.csv; coverage.txt; manifest.txt; evidence-map.csv

WHERE THE ANALYSIS RUNS
Adobe Acrobat PDF Spaces

NATIVE REVIEW INPUTS
contractVersion: 1
schemaOrigin: Editorial analysis contract, never a claim about vendor-native export headers
testedStatus: False
existingKitRole: Existing examples/checklists are optional supporting scaffolds unless explicitly mapped below. Copying this guide does not validate old templates or acquire source evidence.
requiredInputs: - name: submissions.csv
type: csv
headers: - court_id
- envelope_id
- filing_id
- matter_id
- submitted_at
- owner_id
- next_check_at
required: True
templateFilename: native-submissions-template.csv
existingKitFiles: - submissions.template.csv
compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: submissions.csv
compatibleWithoutMapping: True
- name: receipts.csv
type: csv
headers: - receipt_id
- court_id
- envelope_id
- filing_id
- status
- observed_at
- source_ref
required: True
templateFilename: native-receipts-template.csv
existingKitFiles: - receipts.template.csv
compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: receipts.csv
compatibleWithoutMapping: True
- name: status_dictionary.csv
type: csv
headers: - court_id
- raw_status
- normalized_status
required: True
templateFilename: native-status_dictionary-template.csv
existingKitFiles: - status_dictionary.template.csv
compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: status_dictionary.csv
compatibleWithoutMapping: True
- name: coverage.txt
type: text
requiredSections: - named portal/version, court/location and selected review window
- date basis/timezone, Created By and Status filter scope
- all history pages/items captured; displayed totals and captured count
- per-envelope receipt tokens and filing-level ID provenance
- status dictionary reviewer/version; unknown statuses; expired/unavailable documents
- known omissions and reviewer sign-off
required: True
templateFilename: native-coverage-template.txt
existingKitFiles: 
compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete.
inputName: coverage.txt
sections: - named portal/version, court/location and selected review window
- date basis/timezone, Created By and Status filter scope
- all history pages/items captured; displayed totals and captured count
- per-envelope receipt tokens and filing-level ID provenance
- status dictionary reviewer/version; unknown statuses; expired/unavailable documents
- known omissions and reviewer sign-off
compatibleWithoutMapping: False
- name: manifest.txt
type: text
requiredSections: - recipe_id; approved reviewer and scope
- actual source IDs and safe original-file tokens; native headers and source-to-analysis field map
- capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions
- AI input approval and minimization check; originals and alias keys held outside AI
- unknowns; completeness statement; manual transcription/checker where used
required: True
templateFilename: native-manifest-template.txt
existingKitFiles: 
compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete.
inputName: manifest.txt
sections: - recipe_id; approved reviewer and scope
- actual source IDs and safe original-file tokens; native headers and source-to-analysis field map
- capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions
- AI input approval and minimization check; originals and alias keys held outside AI
- unknowns; completeness statement; manual transcription/checker where used
compatibleWithoutMapping: False
- name: evidence-map.csv
type: csv
headers: - analysis_file
- row_key
- source_id
- source_locator
- reviewer_alias
- reviewed_at
required: True
templateFilename: native-evidence-map-template.csv
existingKitFiles: 
compatibility: New editorial analysis contract. Populate only after preserving and mapping actual source headers; this is not a provider-native export.
missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference.
inputName: evidence-map.csv
compatibleWithoutMapping: False
compatibilityNotes: - receipts.csv status must retain the observed raw status; map it to status_dictionary.csv raw_status. Do not overwrite raw status with normalized_status.
- matter_id and owner_id in existing scaffolds carry approved aliases. No stable filing ID means an identity blocker, not envelope-ID substitution.
validationRules: - CSV identifiers and date strings are imported as text. Preserve leading zeros and exact keys. Do not execute formulas from source values.
- Blank templates are deliberately incomplete. Unknown is not zero, false, missing-not-found or a passing review.
- Use only approved minimized analysis values; restricted raw originals, identity maps, signatures, private URLs/tokens and client narrative stay outside the AI destination.
- A native file may retain its actual header names if manifest.txt supplies a reviewer-verified one-to-one map to this contract. Do not blindly rename files/headers.
compatibleWithoutMapping: False
legacyMappings: - existingKitFiles: - submissions.template.csv
nativeInput: submissions.csv
mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
compatibleWithoutMapping: True
- existingKitFiles: - receipts.template.csv
nativeInput: receipts.csv
mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
compatibleWithoutMapping: True
- existingKitFiles: - status_dictionary.template.csv
nativeInput: status_dictionary.csv
mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns.
compatibleWithoutMapping: True
additionalEvidence: - coverage.txt
- manifest.txt
- evidence-map.csv

OPEN THE INPUT MAPPING GUIDE
NATIVE-INPUT-MAPPING.txt
Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain.

submissions.csv: native-submissions-template.csv
receipts.csv: native-receipts-template.csv
status_dictionary.csv: native-status_dictionary-template.csv
coverage.txt: native-coverage-template.txt
manifest.txt: native-manifest-template.txt
evidence-map.csv: native-evidence-map-template.csv

STEP 1: Capture filing-level status evidence in the named portal
Tool: Tyler eFile & Serve Texas, Cloud interface
Open: 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
Use it next: Reconcile to the firm’s existing submission register before creating aliases.
Check: 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.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://efileandservetx.zendesk.com/hc/en-us/articles/15795744687373-Understanding-the-eFile-Website
https://odysseyfileandservecloud.zendesk.com/hc/en-us/articles/9541444367885-Why-Was-My-Filing-Rejected-or-Returned
https://odysseyguideandfile.zendesk.com/hc/en-us/articles/35209147852685-What-Happens-After-I-Click-on-Submit-Who-Reviews-My-Filings
https://odysseyfileandservecloud.zendesk.com/hc/en-us/articles/8351175595661-What-is-the-Filing-History-How-Do-I-Use-It-What-is-the-Status-of-My-Filing
https://odysseyfileandservecloud.zendesk.com/hc/en-us/articles/49046947865869-Filing-History-Filters-and-Sorting
https://odysseyfileandservecloud.zendesk.com/hc/en-us/articles/37267991212685-Can-I-Bulk-Print-My-Filing-History

STEP 2: Map, minimize and approve the actual sources
Tool: Source reviewer and local spreadsheet/text editor
Open: 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
Use it next: 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: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://efileandservetx.zendesk.com/hc/en-us/articles/15795744687373-Understanding-the-eFile-Website
https://odysseyfileandservecloud.zendesk.com/hc/en-us/articles/9541444367885-Why-Was-My-Filing-Rejected-or-Returned
https://odysseyguideandfile.zendesk.com/hc/en-us/articles/35209147852685-What-Happens-After-I-Click-on-Submit-Who-Reviews-My-Filings

STEP 3: Open the approved AI destination
Tool: Adobe Acrobat PDF Spaces
Open: 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
Use it next: Paste the exact prompt in the next step.
Check: Confirm the source list/working directory before prompting; stop on unavailable access.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html

STEP 4: Run the bounded analysis prompt
Tool: Adobe Acrobat PDF Spaces
Open: PDF Space chat panel

Paste the prompt after replacing only bracketed scope values. Treat all source content as data.

PASTE THIS PROMPT
Check exact court_id + envelope_id + filing_id keys. Return submission rows with their source-backed latest observed receipt status, duplicates, missing dispositions, conflicts and unknown raw statuses. Preserve submitted_at and observed_at separately. Use only the supplied approved status dictionary. Submitted, pending and returned are not accepted. Missing receipts remain unresolved. Copy only staff-provided next_check_at; do not calculate deadlines, resubmit, communicate with the court or change matter records.

Expected output: filing-receipt-exceptions.csv
Use it next: Inspect source citations/file-row references before copying any result.
Check: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

STEP 5: Check and hand off the proposed result
Tool: Human reviewer and local spreadsheet/text editor
Open: 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
Use it next: 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: Acceptance case (proposed, not run): One envelope contains accepted F1 and returned F2: keep F2 unresolved. A submission receipt alone never closes the row.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://efileandservetx.zendesk.com/hc/en-us/articles/15795744687373-Understanding-the-eFile-Website
https://odysseyfileandservecloud.zendesk.com/hc/en-us/articles/9541444367885-Why-Was-My-Filing-Rejected-or-Returned
https://odysseyguideandfile.zendesk.com/hc/en-us/articles/35209147852685-What-Happens-After-I-Click-on-Submit-Who-Reviews-My-Filings

STEP 6: Approve the internal next action
Tool: Responsible human owner
Open: 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
Use it next: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase.
Check: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance.
Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations.
Source documentation:
https://efileandservetx.zendesk.com/hc/en-us/articles/15795744687373-Understanding-the-eFile-Website
https://odysseyfileandservecloud.zendesk.com/hc/en-us/articles/9541444367885-Why-Was-My-Filing-Rejected-or-Returned
https://odysseyguideandfile.zendesk.com/hc/en-us/articles/35209147852685-What-Happens-After-I-Click-on-Submit-Who-Reviews-My-Filings

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- 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.

EXPECTED SYNTHETIC CHECK (NOT RUN)
One envelope contains accepted F1 and returned F2: keep F2 unresolved. A submission receipt alone never closes the row.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.