Cheque learning: four ways to fill a payee's other cheques

In the 16/10/2026 alpha test, the matcher put each cheque number into the payee pattern, so every cheque had a pattern of its own. When the user chose Cash Account for one SELF-CHQPAID- SARDARCHOWK cheque, the other 8 cheques got only a suggestion and stayed unsaved. The matcher fix leaves the cheque number out of the pattern. Then one choice can fill the payee's other cheques, including rows you have not reached yet, rows in the other step and rows in the other PDF. This page lets you try four ways to show that to the user. Today shows how the app works now.

Sample rows are based on the alpha data for KESARI NANDAN ART (HDFC current account, two PDFs). Person names and account numbers are left out. Amounts and dates are as printed; the balances are made up.

LedgerMapKESARI NANDAN ARTHDFC BANK CA · Apr–Jun.pdf, Jul–Oct.pdf

Sr. no.	Bank	Date	Narration	Reference	Debit	Credit	Balance	Ledger

Keys: ↑↓ HomeEnd move · type or Enter opens the ledger list · Enter chooses (Enter twice takes the suggestion) · Esc back to the row · Ctrl+Enter accepts this suggestion · Ctrl+Shift+Enter accepts all (Suggestions) · Ctrl+[ Ctrl+] step · Alt+Z undo the fill (options 2 and 4)

Try these

The alpha path. On Suggestions, press Ctrl+Shift+Enter. It accepts the two SELF cheques that Miracle history suggests. Then go to Suspense (Ctrl+]) and look at the other SELF cheques.
One choice. On Suspense, row 1 (SELF, 02/04): type cash, then Enter.
A wrong first choice. Choose JAY ART for a SELF cheque, then fix it.

One exception. After a fill, choose PROPRIETOR DRAWINGS for one filled SELF cheque. Look at what happens to the others.
Returned cheques. Choose a ledger for 12/05 CHQ DEPRET-FUNDSINSUFFICIENT. The 29/08 one is another customer's cheque, so it must not fill.
Exported row. 07/05 SELF is already exported with Suspense. No option may change it.

Comparison

	1 · Silent fill	2 · Notice with list and Undo	3 · Ask first (pop-up)	4 · Fill and mark until reached
Who saves the other cheques	The server, immediately	The server, immediately	The user: one `Enter` in the pop-up	The server, immediately
What the user sees	“9 more entries matched to Cash Account.” Each row says “Matched · Same narration as an earlier entry”.	A notice that lists every filled row (date, step, PDF), and every row that lost its ledger, with an Undo button.	The existing “Choose Cash Account for this payee?” pop-up, now with each row's step and PDF. After an accept-all, one pop-up lists every payee.	Filled rows get a thin green bar and “Filled from your choice for 02/04 · not checked yet”. Focus stops on them. The step counts them as left.
Keys	None new	`Alt+Z` undo (or Tab to the Undo button)	`Enter` all · `Space` untick · `Esc` only this one (these keys exist now)	`Alt+Z` undo · `↓` passes a row and marks it checked
Wrong first choice	Fix the first row, and the others follow. But nothing tells you which row was first.	Undo right away. Later, you must find the first row.	Nothing is saved until Enter. Esc keeps only the one row.	The marks show it. Undo, or fix the first row.
Change one filled row	Today's rule: two ledgers for one payee make it unsure, so every other filled row silently loses its ledger.	Same rule, but the notice says which rows lost their ledger.	The others stay. They are your own choices now.	Same rule as 1. The rows go back to open.
Rows in the other step or PDF	They change out of sight.	Listed in the notice.	Listed in the pop-up with their step and PDF.	Marked. You see them when you reach that step.
Exported rows; returned cheques	The same for every option. A matcher guard leaves exported rows alone. Returned cheques (DEPRET, RETURN, INSUFFICIENT) keep the cheque number in the pattern, so one customer's bounce never fills another's.
Next import	The same for every option. After export, the choices teach later imports, and there the cheques save automatically (exact), as other payees do now.
Effort	S: matcher only	M: a new notice state and an undo endpoint (record rejections)	S–M: matcher, plus the in-import cheque pattern only suggests; the pop-up exists, and a grouped version after accept-all is new	L: a new “not checked” state (saved per tab), step counts and a focus rule
Risk of wrong auto-saves	High	Medium	Low	Medium
Key presses for 9 cheques	0	0	1	0, plus a visit to each row

Recommendation

Option 3: ask first. In this import, a cheque payee's other entries are offered in the existing pop-up. One Enter saves all of them. After export, the next import fills them automatically.

Nothing is saved without a key press. A wrong first choice costs Esc, not a hunt for nine rows.
The rows you confirm become your own choices. If you change one later, the others keep their ledger. With options 1, 2 and 4, one exception empties every other filled row, because of the “two ledgers make a payee unsure” rule.
Cheque narrations name less than UPI IDs or account numbers do. SELF cheques, “CHQ PAID-CTSS6-MUMB-…” cut short, and returned cheques share text across real payees, so asking first fits them.
It reuses tested UI and its setting. The steps stay fixed and focus does not jump. No new marks or badges are needed.
What it needs: (a) after Accept all, one pop-up for every payee (the alpha user took this path); (b) the step and PDF shown on each pop-up row; (c) a guard for exported rows.

Second choice: option 2, if you want zero extra keys. It needs an undo, and the “one exception empties the rest” rule should change first.

The matcher change (the same for every option)

On a cheque row, the reference column's number (for example 0000000000000160) leaves patternKey. Today it is also read as a 16-digit “account” in entryIdentifiers, which keeps each cheque in a payee group of its own (payeeGroup), so it leaves those too.
Returned-cheque rows (DEPRET, RETURN, INSUFFICIENT) and narrations with no payee word beyond bank codes keep the number, as now.
For option 3 only: a cheque pattern learned only from this import's choices suggests (green, preselected) and is not saved. A pattern learned from exported choices saves as exact.
Checks: bun run matcheval before and after, and a replay on the 17/10 production copy.