Active …
मराठी A
Open the money desk → every credit and every payment screenshot side by side — tie, untie, split or set aside with one tap
Today · 56 credits heard, ₹16,86,885 — 35 on their case · 13 waiting for you → · 8 set aside
Yesterday · 73 credits heard, ₹30,84,726 — 49 on their case · 11 waiting for you → · 13 set aside
Money to confirmWhy it is not automaticEvery message

Why it is not automatic

1248 payments verified · 2100 still waiting
Of the 1248 that came in, 100% matched themselves — 1243 with nobody pressing anything, 5 by a person. That share is of the money ALREADY IN, not of all 3348 cases.
Of those 1243: 804 certain — a receipt named the case (the UTR, the exact paise, or the screenshot's own minute), which cannot be another case's money. 439 on the amount alone, through the guards.
78 of the 1243 were undone or moved to another case — 0 by a person (Not this case), 78 by EzDocs itself (the second look, a stronger screenshot, the rule for a finished case).
the ones to check — 439 matched on the amount alone
No receipt named the case: no UTR, no exact paise, no screenshot minute. The guards let them through on the figure. These are the only ones that could sit on the wrong case — open a few and see.
NOI-2026-01903 ₹18,410.12 · NOI-2026-01537 ₹11,130.39 · NOI-2026-03535 ₹14,070.74 · NOI-2026-01410 ₹7,630 · NOI-2026-01334 ₹30,790 · NOI-2026-01526 ₹26,140.36 · NOI-2026-01883 ₹26,730.93 · NOI-2026-03178 ₹14,070.56 · NOI-2026-03479 ₹26,060.15 · NOI-2026-02852 ₹14,430.27 · NOI-2026-01932 ₹5,280.70 · NOI-2026-01866 ₹18,180.87 · NOI-2026-02269 ₹18,510.71 · NOI-2026-01953 ₹32,810.75 · NOI-2026-02203 ₹11,910.18 · NOI-2026-03255 ₹32,280.22 · NOI-2026-01144 ₹5,990 · NOI-2026-01262 ₹26,640 · NOI-2026-03381 ₹14,180.42 · NOI-2026-01995 ₹24,470.52 · NOI-2026-02389 ₹14,070.58 · NOI-2026-02831 ₹25,270.72 · NOI-2026-03147 ₹44,510.04 · NOI-2026-01449 ₹27,740 · NOI-2026-03401 ₹35,910.02 · NOI-2026-03073 ₹18,640.16 · NOI-2026-03244 ₹16,000.38 · NOI-2026-03400 ₹9,730.70 · NOI-2026-03486 ₹23,680.66 · NOI-2026-02727 ₹46,760.94 · NOI-2026-03263 ₹44,820.62 · NOI-2026-01328 ₹29,650 · NOI-2026-02063 ₹10,130.83 · NOI-2026-03328 ₹26,060.63 · NOI-2026-02019 ₹28,760.42 · NOI-2026-03062 ₹15,150.10 · NOI-2026-02045 ₹18,070.83 · NOI-2026-02898 ₹18,070.80 · NOI-2026-01268 ₹25,360 · NOI-2026-02820 ₹31,900.86 · NOI-2026-03146 ₹19,600.44 · NOI-2026-02030 ₹10,870.88 · NOI-2026-01383 ₹26,660 · NOI-2026-01472 ₹43,460 · NOI-2026-01057 ₹26,960 · NOI-2026-00075 ₹24,020 · NOI-2026-01272 ₹16,660 · NOI-2026-02483 ₹26,160.19 · NOI-2026-01516 ₹26,020.16 · NOI-2026-01931 ₹28,800.83 · NOI-2026-02475 ₹8,560.68 · NOI-2026-02277 ₹29,220.59 · NOI-2026-01503 ₹28,760.73 · NOI-2026-01522 ₹37,330.24 · NOI-2026-02892 ₹17,250.49 · NOI-2026-03589 ₹1,62,560.03 · NOI-2026-02882 ₹14,070.15 · NOI-2026-02526 ₹26,740.60 · NOI-2026-02301 ₹15,570.96 · NOI-2026-01498 ₹24,470.43
Nobody has pressed “Not this case” on an engine match yet — so no match is known to have been wrong. That is not proof they are all right.
400 times EzDocs took a tie back by itself — 24 credits
The second look (the case's own screenshot shows another payment), a stronger screenshot on another case, the rule for a finished case. Put right without anyone pressing anything — not a person finding a wrong match. 8 credits were tied again after being taken back, and taken back again — EzDocs now remembers its own take-back and leaves such a credit for a person, with the reason.
NOI-2026-00665 ₹10,450 192 times — amount-only match onto a case past the challan, the credit days after the case's last branch mail
NOI-2026-03131 ₹8,752 168 times — amount-only match onto a case past the challan, on the other channel
NOI-2026-03095 ₹22,800 6 times — amount-only match onto a case past the challan, the credit days after the case's last branch mail, on the other channel
NOI-2026-00028 ₹18,380 5 times — HDFC sent two messages for this one payment and both were tied — to NOI-2026-03538 and NOI-2026-00028; the case whose own papers name the payment keep
NOI-2026-03308 ₹31,240 4 times — amount-only match onto a case past the challan, on the other channel
NOI-2026-03164 ₹31,240 4 times — amount-only match onto a case past the challan, on the other channel
NOI-2026-01933 ₹8,100 3 times — amount-only match onto a case past the challan, the credit days after the case's last branch mail, on the other channel
NOI-2026-03095 ₹22,780 2 times — amount-only match onto a case past the challan, the credit days after the case's last branch mail, on the other channel
NOI-2026-03094 ₹28,485 — NOI-2026-03598's own payment screenshot carries this credit's transaction number (066780909884); NOI-2026-03094 had it on the amount alone (a little o
NOI-2026-03256 ₹26,400 — this case's screenshot shows the same amount with another transaction id (628036637893) — another payment; NOI-2026-03605 names this payment
NOI-2026-00192 ₹15,664 — a stronger claim: NOI-2026-03596's screenshot names ₹15,664 on this road (screenshot_amount_time); NOI-2026-00192 had it on the amount alone
NOI-2026-03570 ₹33,795 — a stronger claim: NOI-2026-03594's screenshot names ₹33,795 on this road (screenshot_amount_time); NOI-2026-03570 had it on the amount alone
NOI-2026-03472 ₹18,050 — this case's screenshot shows ₹16,050 — another payment; NOI-2026-03574 names this payment
NOI-2026-01697 ₹24,850 — this case's screenshot shows ₹24,812 — another payment; NOI-2026-02574 names this payment
NOI-2026-03262 ₹29,051 — this case's screenshot shows the same amount paid at another time — another payment; NOI-2026-03489 names this payment
NOI-2026-03472 ₹18,050 — HDFC sent two messages for this one payment and both were tied — to NOI-2026-03472 and NOI-2026-03471; the case whose own papers name the payment keep
NOI-2026-03489 ₹29,050 — HDFC sent two messages for this one payment and both were tied — to NOI-2026-03489 and NOI-2026-03464; the case whose own papers name the payment keep
NOI-2026-03252 ₹18,702 — this case's screenshot shows the same amount paid at another time — another payment; NOI-2026-03484 names this payment
NOI-2026-03450 ₹26,141 — HDFC sent two messages for this one payment and both were tied — to NOI-2026-03450 and NOI-2026-03501; the case whose own papers name the payment keep
NOI-2026-03468 ₹23,650 — this case's screenshot shows the same amount paid at another time — another payment; NOI-2026-03507 names this payment
GPay: Google is still BATCHING. 137 GPay alerts came in the last 14 days but only 80 settlement credits followed them. One credit for several payments has no case's exact figure in it, so those cannot match themselves. Instant settlement is what fixes this. 22 alerts are still waiting for their money.
Is every phone hearing every app?
A phone can forward the bank’s SMS perfectly while its GPay or Vyapar alerts are switched off. The road split judges the phone; this judges each app on it.
the Vivo (EZDOCS)
HDFC-VYAPARheard 54 min agoworking
JD-PNBSMS-Sheard 1 h agoworking
VA-PNBSMS-Sheard 3 h agoworking
GPAY-BIZheard 3 h agoworking
JK-PNBSMS-Sheard 4 h agoslow
BP-HDFCBK-Sheard 5 h agoslow
VM-HDFCBK-Theard 6 h agoslow
AD-HDFCBK-Sheard 6 h agoslow
VM-HDFCBK-Sheard 7 h agoslow
VD-HDFCBK-Sheard 26 h agogone quiet
AD-HDFCBK-Theard 8 days agogone quiet
JX-PNBSMS-Sheard 9 days agogone quiet
This phone is plainly alive — other apps on it are reaching us — but VD-HDFCBK-S, AD-HDFCBK-T, JX-PNBSMS-S has said nothing for most of a working day. That is a switch on the phone, not a quiet night: check notification access for that app, its battery setting, and that the app’s own alerts are on.
the Samsung (ThinkBigz)
HDFC-VYAPARheard 48 min agoworking
BP-HDFCBN-Sheard 48 min agoworking
JK-PNBSMS-Sheard 1 h agoworking
VM-HDFCBK-Sheard 1 h agoworking
VD-HDFCBN-Sheard 1 h agoworking
JD-PNBSMS-Sheard 2 h agoworking
VM-HDFCBN-Sheard 2 h agoworking
BP-HDFCBK-Sheard 4 h agoslow
VM-HDFCBK-Theard 4 h agoslow
VD-HDFCBK-Sheard 24 h agogone quiet
AD-HDFCBK-Theard 33 h agogone quiet
GPAY-BIZheard 2 days agogone quiet
AD-HDFCBK-Sheard 3 days agogone quiet
JM-HDFCBK-Sheard 8 days agogone quiet
JM-HDFCBN-Sheard 8 days agogone quiet
JD-HDFCBN-Sheard 8 days agogone quiet
JX-PNBSMS-Sheard 9 days agogone quiet
AD-HDFCBN-Sheard 10 days agogone quiet
This phone is plainly alive — other apps on it are reaching us — but VD-HDFCBK-S, AD-HDFCBK-T, GPAY-BIZ, AD-HDFCBK-S, JM-HDFCBK-S, JM-HDFCBN-S, JD-HDFCBN-S, JX-PNBSMS-S, AD-HDFCBN-S has said nothing for most of a working day. That is a switch on the phone, not a quiet night: check notification access for that app, its battery setting, and that the app’s own alerts are on.
Which senders are reaching us — 30 in the last 14 days
Every sender the phones have forwarded. A sender you expect and cannot see here is not being forwarded — that is a setting on the phone, not in the app. A Vyapar alert carries no account number and both companies use the same sender, so the phone is what says whose money it is.
AD-HDFCBK-S, AD-HDFCBK-T, BP-HDFCBK-S, GPAY-BIZ, HDFC-VYAPAR, JD-PNBSMS-S, JK-PNBSMS-S, JX-PNBSMS-S, VD-HDFCBK-S, VM-HDFCBK-S, VM-HDFCBK-T is arriving from more than one phone. Both companies use the same sender, so only the phone can say whose money it is — check that each phone carries its own &ear=.
GPAY-BIZ103 message(s)last 16:38phone: EZDOCSEZDOCS
HDFC-VYAPAR85 message(s)last 19:48phone: THINKBIGZTHINKBIGZ
BP-HDFCBN-S67 message(s)last 19:48phone: THINKBIGZTHINKBIGZ
GPAY-BIZ57 message(s)last 13 Oct 08:24phone: THINKBIGZTHINKBIGZ
VD-HDFCBN-S55 message(s)last 18:44phone: THINKBIGZTHINKBIGZ
VM-HDFCBN-S43 message(s)last 18:11phone: THINKBIGZTHINKBIGZ
JK-PNBSMS-S39 message(s)last 16:02phone: EZDOCSEZDOCS
JK-PNBSMS-S39 message(s)last 19:18phone: THINKBIGZTHINKBIGZ
HDFC-VYAPAR36 message(s)last 19:37phone: EZDOCSEZDOCS
JD-PNBSMS-S31 message(s)last 18:35phone: THINKBIGZTHINKBIGZ
JD-PNBSMS-S31 message(s)last 19:15phone: EZDOCSEZDOCS
JM-HDFCBN-S25 message(s)last 7 Oct 18:08phone: THINKBIGZTHINKBIGZ
VA-PNBSMS-S14 message(s)last 17:20phone: EZDOCSEZDOCS
VM-HDFCBK-S11 message(s)last 19:18phone: THINKBIGZTHINKBIGZ
AD-HDFCBK-S9 message(s)last 14:01phone: EZDOCSEZDOCS
VM-HDFCBK-S8 message(s)last 13:01phone: EZDOCSEZDOCS
JX-PNBSMS-S6 message(s)last 6 Oct 18:09phone: THINKBIGZTHINKBIGZ
AD-HDFCBK-S6 message(s)last 12 Oct 17:55phone: THINKBIGZTHINKBIGZ
VD-HDFCBK-S6 message(s)last 14 Oct 18:07phone: EZDOCSEZDOCS
JD-HDFCBN-S6 message(s)last 7 Oct 11:53phone: THINKBIGZTHINKBIGZ
VM-HDFCBK-T4 message(s)last 16:22phone: THINKBIGZTHINKBIGZ
BP-HDFCBK-S4 message(s)last 14:50phone: EZDOCSEZDOCS
AD-HDFCBK-T3 message(s)last 14 Oct 11:16phone: THINKBIGZTHINKBIGZ
JX-PNBSMS-S3 message(s)last 6 Oct 13:01phone: EZDOCSEZDOCS
BP-HDFCBK-S3 message(s)last 16:27phone: THINKBIGZTHINKBIGZ
VM-HDFCBK-T3 message(s)last 14:31phone: EZDOCSEZDOCS
AD-HDFCBN-S2 message(s)last 5 Oct 15:18phone: THINKBIGZTHINKBIGZ
AD-HDFCBK-T2 message(s)last 7 Oct 16:26phone: EZDOCSEZDOCS
JM-HDFCBK-S2 message(s)last 7 Oct 19:12phone: THINKBIGZTHINKBIGZ
VD-HDFCBK-S2 message(s)last 14 Oct 19:41phone: THINKBIGZTHINKBIGZ

Every case still waiting for its fee, sorted by the reason it could not verify itself. This is where the automation leaks — fix the biggest number first.

EzDocs matches the way a person does: the UTR, the payer's name (this case's own screenshot, and the payer book), and the screenshot's printed minute against the credit's. That last one currently allows 12 minutes either way (CLAIM_TIME_WINDOW_MIN on EzDocs) — widen it and cases move from “nothing tied it” into matched by themselves.

This is the newest 1500 only. There are more waiting behind them — the counts below are a floor, not the whole pile.
216The branch has not said it paid
no screenshot and no UTR on the case — nothing has gone wrong, the money simply has not come yet. Not a leak.
0Our own mail asked for a different figure
the loan the fee is worked out on changed after the mail went. The branch is holding our old figure, so what it pays is not short. Send a fresh ask for the difference, or keep the figure they already have.
2The amount we recorded is round — and no fee mail has gone yet
nothing has reached the branch, so this one is SAFE to fix: give the ask its paise tag before the mail goes and the credit will name its own case.
Every bank has the paise tag on. These asks were made before that, and they keep their round figures — the branch is holding our old mail and will pay THAT, so the figures must not be changed now.
0The branch already holds a round figure
our fee mail went out with a round amount, so no credit can name its own case. Do NOT change the figure now — they will pay what they were asked. This one matches by UTR, by the screenshot's minute, or by hand.
Every bank has the paise tag on. These asks were made before that, and they keep their round figures — the branch is holding our old mail and will pay THAT, so the figures must not be changed now.
25The branch paid its own figure
it says it paid an amount we did not ask for. When their own mail STATED that figure EzDocs already matches it (bank_own_total) — these are the ones where they never said what they would pay. The pay link and the QR carry the exact amount and end the question.
1128The credit is here — nothing tied it
a credit that could settle this ask is sitting unplaced in our own ear. Nothing is missing: the matcher was too strict. This is the reason with a DIAL on it — the screenshot's minute must fall within CLAIM_TIME_WINDOW_MIN of the credit.
51Its own payment is counted on another case
the screenshot on this case carries the transaction number of a credit tied to another case on weaker evidence. EzDocs moves it here by itself when the other tie was only a figure; when that case is past its challan, or a person tied it there, the money desk shows it with one tap that moves it here.
53Paid before the phones listened — or an old screenshot
the screenshot is dated before the office phones began forwarding the bank's messages, or months before it reached us. No phone could have heard this money: find it once on the bank statement and press where you saw it. Not a leak in the ear.
25We never heard the credit
the branch says it paid, the figure is plausible, and nothing in our ear comes near it. The money is in the account and the app was never told. Fix in the ear — the forwarder phone, the bank's own alerts, the statement paste.
Which road that money took, and whether its ear is alive — a big number on one road is one phone, not many problems.
11the Google Pay Business account · the Vivo (EZDOCS)that ear is working — these alerts never fired
5the receipt does not say which road
4the advocate’s own accountno phone hears this, ever
3the HDFC Vyapar QR · the Samsung (ThinkBigz)that ear is working — these alerts never fired
1the Google Pay Business account · the Samsung (ThinkBigz)DEAD — not forwarding, 60 h without a word. Every payment on this road is invisible until it speaks.
1the HDFC Vyapar QR
rendered in 3.89 s · 18 queries · this page refreshes by itself when something on it changes (never while you type) · release v530 · build 0f000022