Twill Brain

#1115 Merchant Field extractor logic improvements

2 min read

#1115 — Merchant Field extractor logic improvements

Repo: Twill-AI/facade State: open | Status: open Assignee: meliascosta

Created: 2026-03-11 · Updated: 2026-03-20

Description

Caused by b1ed731d-c888-4daf-a2d8-7f64ccb145d8 in prod.

  • MID is written during field extraction. It should be set once and treated as immutable — subsequent steps must not update it.
  • Merchant name extraction is incorrect. Likely caused by multiple source field names mapping to the same target — these should be merged into one canonical value.
  • Bank statement uploads extract the bank’s own corporate information as merchant data. Extraction logic should exclude non-merchant fields when processing bank statements.

The user was blocked from saving a merchant record due to a routing number extracted by the LLM that failed UI validation. The 404 on save gave no indication of which field caused the failure or why. Workaround: manually clearing the routing number field restored save functionality. To reproduce, create a new merchant in staging and upload documents in the same sequence as in prod:

  • LLM should not produce a field value that fails UI validation.
  • Save errors must identify the specific field and reason for failure.

Notes

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets

Graph View