LedgerMap · Ledger matching review · 16/10/2026

Clear names were landing in Suspense.
Now every clue is a suggestion.

You moved many ASMARK ENGINEERS entries out of Suspense by hand, though the narration named the ledger. This page shows why that happened, what changed, and the effect on your real entries.

Data: ASMARK ENGINEERS · production, read-only Entries replayed: 837 · with a known ledger: 392 Commits efebbd4, c54ac97, cb5106b · not deployed yet

On your entries, as a first import

The 392 entries whose ledger is known (your choices and the matches they made), replayed with no earlier choices — the worst case.

Right ledger, saved or suggested
178→388
+210 entries ready with Enter or already done
Right ledger, but sent to Suspense
145→0
These were the “17% likely” entries
Nothing suggested at all
66→0
Every entry now gets at least one suggestion
Wrong first suggestion
3→4
ATM fee (3) fixed; now LOANCHARGES (3) → BANK CHARGES, and ROHIT (1) with your ledger second

Where the 392 entries end up

Each bar splits the same 392 entries by outcome. Hover or Tab onto a segment for its count.

Show as a table
OutcomeBeforeAfter

Problem 1 — the 40% bar decided the step

A suggestion under 40% likely was hidden as “Possible” and the entry waited in Suspense. Now the first suggestion always fills the box, and its “% likely” stays visible in the list.

Before Routing

Clue ≥ 40% likely
→
Suggestions step
Clue under 40% (e.g. “MOLIYA DHANANJAY · 17%”)
→
Suspense step, box empty
No clue
→
Suspense step

Now Routing

Any clue, any %
→
Suggestions step, box filled, % shown
Miracle history clue more likely than the server’s
→
Becomes the suggestion
No clue at all
→
Suspense step

The server now sends preselect: true for every suggested entry, so installed apps follow the new rule as soon as the server is deployed.

Why a full name showed “17% likely”

The % comes from a replay against older Miracle books. For “ledger name found in the narration”, most of its “wrong” rows were not wrong names:

What made it 13%

  • 16 rows: the company’s own name (MARUTI ENERGY) printed on its own receipts. Now the own name is never suggested.
  • 7 rows: MOLIYA DHANANJAY / SUSHIL — the old books posted them to LABOUR WAGES EXP.; you now use their own ledgers.
  • 6 rows: INTEX CAD/CAM — two real ledgers (creditor and unsecured loan).

Measured again

9 of 69 right before → 103 of 129 right now (more rows, because glued names are now read).

  • MOLIYA, GAFAR, INTEX, R P, J P, UCAM: 17% → 80%
  • Alphatech (name cut short): 83% · Priyankkumar (cut): 95%

Problem 2 — names the matcher could not read

These narrations name the ledger, but the old reader missed them completely.

NarrationWhat blocked itNow suggests
168033ALPHATECH ENTERPRIS ICICICheque number glued to the nameAlphatech Enterprise
Part of the name · 83%
168037MULTITECH ENTERPRIS KOTAK…Cheque number glued to the nameMULTITECH ENTERPRISE
168039ARGUS CARBIDE PRIVA KOTAK…Cheque number glued; PRIVATE cut shortArgus Carbide Private Limited
168042J P INDUSTRIES H D F C BANK LTDCheque number glued to an initialJ.P. INDUSTRIES
RTGSOSKO VALVES PRIVATERTGS glued to the nameOsko Valves Private Limited
Now saved by itself
NEFT OSKO VALVES PRIVAT“PRIVAT” not read as PRIVATEOsko Valves Private Limited
Now saved by itself
NEFT UCAM PVT LTDOne-word name too short to searchUCAM PVT. LTD.
Only when PVT / LTD follows · 80%
RTGSPRIYANKKUMAR POPATBHKKBKR52026091700871825Cut name glued to Kotak’s RTGS reference (KKBK + R + number)Priyankkumar Popatbhai Bhuva (Capital Acc.)
Name cut short · 95%
NEFT ROHIT CHOTHABHAI BOnly the father’s name matches, spelled CHOTHABHAI; surname is just “B”CHOTHABHAI BIJALBHAI BHUNIDYA (ADVANCE), then CHOTABHAI BHUNDIYA
One name of the ledger · as written first · ~38% likely
LOANCHARGES · CASHWITHDRAWCHR · INSPECTIONCHARGERECOVERYCharge word glued to othersBANK CHARGES
0000000/DR: ATM ANNUAL FEEATM read as cashBANK CHARGES
Was wrongly Cash Account
Paid to SELFNo rule for a cheque to SELFCash Account
A NEFT/UPI to SELF is not cash

Every entry, before and after

Your 392 entries grouped by narration (reference numbers shown as #). “Before” and “Now” show the step the entry lands in on a first import.

RowsNarrationYour ledgerBeforeNow

Check against Miracle books (10 companies, 1,611 rows)

The replay test compares matching with what the books show. “Fresh” is a first import; “prior” and “full” learn from earlier choices.

Outcomefresh: beforenowprior: beforenowfull: beforenow
Saved by itself, right196220 (+24)497516 (+19)632646 (+14)
Saved by itself, WRONG00 11 11
First suggestion right417624 (+207)396441 (+45)563585 (+22)
Right ledger only in Suspense1600 (-160)530 (-53)170 (-17)
No suggestion at all697584 (-113)566523 (-43)330302 (-28)
First suggestion wrong141183 (+42)98130 (+32)6877 (+9)
Decisions left for you998767 (-231)718654 (-64)416380 (-36)

Read it like this

  • Wrong automatic saves did not move (0 / 1 / 1).
  • 231 more entries are right on a first import; 231 fewer decisions.
  • No entry that was right before is wrong now. Each new wrong first suggestion was, before, a weak guess hidden in Suspense or no guess at all.

Why “First suggestion wrong” still rises

Showing every guess means weak guesses can be wrong in plain sight. After the first fix it rose 141 → 297 (fresh). Tracing those rows found two causes, now fixed:

  • 114 rows: “Interest” suggested Miracle’s built-in Interest Expense A/c.(Default) first, with INTEREST ON TERM LOAN second. Built-in “(Default)” ledgers now come last. Your Interest rows: 2% → 80%.
  • 4 rows (full): a UPI ID used only for money in suggested GOODS SALES on a payment. Sales, purchase, income and expense ledgers are no longer suggested against their direction.

What is left (+42 fresh, +9 full) is mostly salary rows with several salary ledgers, people who share a first name with a ledger, and old bookings.

Your decision and next steps

Decide: bulk accept

Ctrl+Shift+Enter accepts every suggestion shown — now including weak guesses such as “Looks like a loan payment · 2% likely”. Keep it, or skip suggestions under some % in the bulk accept?

To reach the app

  • Say “file the PR”: OpenQodex review, PR, squash-merge.
  • Then, when you ask: server deploy (routing changes for installed apps at once).
  • Then a desktop release for the Miracle history change.