How to Reconcile UPI and Bank Payments by UTR
Payments recorded in the field never get checked against the bank
Collectors write down UPI and bank transfers in the field. Weeks later the owner finds a payment in the book that never reached the bank, or a transfer in the bank that nobody wrote down.
The same UTR gets written twice, once by the collector and once by the office, and the client looks like they paid double.
Full bank reconciliation is more than a small services firm wants to run every day. They need a light tick that says this one is in the bank.
Why this happens
- Non-cash payments are saved without a reference to match.
- Duplicate references are not flagged.
- There is no per-payment tick for seen in bank or cash handed over.
- Nobody is told when a payment has gone unchecked for too long.
Biznsbook addresses this through UTR or reference on non-cash payments, duplicate reference warning, Seen in bank and Cash handed over ticks when Service Billing & Collections is licensed. Clients are the parties you already keep, and collectors record what they received without seeing the fee or the outstanding.
Services firms lose money in the gap between the work done and the payment recorded. Keeping the fee on the job, the payment against the job, and the collector away from the numbers closes that gap without turning the firm into an accounting office.
Step-by-step: Reconcile UPI and Bank Payments by UTR
Built for owners of services firms and the staff who collect client payments in Biznsbook Collections.
- Require a reference for non-cash payments. In Collections Settings, keep Require a UTR or reference for payments that are not cash turned on. It is on by default. Collectors then must enter the UTR for UPI, bank transfer, cheque, card, and other modes.
- Choose how long a payment may wait. Settings chooses how many days an unticked payment waits before the dashboard counts it as not reconciled. The default is 7 days.
- Record payments with the UTR. On Record a payment, the collector enters the UTR and can attach a photo of the payment screen. They never see the fee or the outstanding.
- Let duplicates warn the collector. If the reference was already used, the collector sees only: This reference has already been used — please check. The owner’s payment list and payment detail name the other payment, the client, and the amount.
- Match references in Payments. Filter Payments by date, mode, or reference. Compare each UTR with your bank or UPI statement.
- Tick Seen in bank or Cash handed over. Each row has a Seen in bank pill for non-cash payments and a Cash handed over pill for cash. Ticking it does not change the amount.
- Clear the not reconciled list. The dashboard counts payments not ticked after the days you set. Its chip opens Payments already filtered to Not reconciled.
Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen names in this guide match Collections in the product: Record a payment, My entries, Dashboard, Jobs, Payments, Payment links, Corrections, Service types, Settings, and Guide. Every screen has a ? help button.
Common mistakes to avoid
- Mistake 1: Non-cash payments are saved without a reference to match. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
- Mistake 2: Duplicate references are not flagged. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
- Mistake 3: There is no per-payment tick for seen in bank or cash handed over. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
- Mistake 4: Nobody is told when a payment has gone unchecked for too long. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
Note each recurring gap in the weekly review; each should map to a step in this guide.
Best practices that hold up as you scale
- Require a reference for non-cash payments — In Collections Settings, keep Require a UTR or reference for payments that are not cash turned on.
- Choose how long a payment may wait — Settings chooses how many days an unticked payment waits before the dashboard counts it as not reconciled.
- Record payments with the UTR — On Record a payment, the collector enters the UTR and can attach a photo of the payment screen.
- Let duplicates warn the collector — If the reference was already used, the collector sees only: This reference has already been used — please check.
- Match references in Payments — Filter Payments by date, mode, or reference.
Firms that keep the fee on the job, let Collections compute outstanding, and correct by reversal instead of editing a row keep their period totals and their trail intact.
How Biznsbook supports this workflow
UTR or reference on non-cash payments is part of Biznsbook Service Billing & Collections. Each client is a party you already keep, each job holds its fee, and each payment keeps who entered it, when, and how the client paid.
duplicate reference warning is part of Biznsbook Service Billing & Collections. Each client is a party you already keep, each job holds its fee, and each payment keeps who entered it, when, and how the client paid.
Seen in bank and Cash handed over ticks is part of Biznsbook Service Billing & Collections. Each client is a party you already keep, each job holds its fee, and each payment keeps who entered it, when, and how the client paid.
Ledger posting is off until Collections settings turn it on, and only when Accounting or Finance is licensed. Outstanding is the fee plus any tax, minus the payments on the job. Collectors do not see fees, outstanding, other people’s entries, the dashboard, statements, the correction queue, or a journal.
Suggested implementation timeline
- Week 1: Add your service types, check that clients exist as parties, and open jobs with fees.
- Week 2: Start UTR or reference on non-cash payments with one collector and a handful of clients.
- Week 3: Add the rest of the collectors and clear the dashboard attention items daily.
- Week 4: Review billed, collected, and outstanding by age with the client statements.
- Ongoing: Weekly review using light reconciliation, not a full bank rec and the dashboard.
Why the warning hides the other payment
A collector who learns that a UTR belongs to another client also learns that client’s amount. The warning therefore says only that the reference was already used. The owner, who already sees every payment, gets the full match in the payment list and the payment detail.
The payment is still saved, so a genuine coincidence does not block the collector. The owner decides whether it is a duplicate and, if so, a correction with a reason reverses one of them.
A daily routine that takes minutes
Each evening, open Payments filtered to today and to UPI or bank transfer. Read down the bank app and tick Seen in bank for every match. Tick Cash handed over as cash comes in.
Once a week, open the dashboard. The not reconciled count shows what is older than the days you set. Its chip opens the filtered list, so nothing old slips past.
Payments listed in the company currency make it easy to read straight from the bank app.
Metrics to track monthly
- Billed for the date range
- Collected for the date range
- Outstanding, and outstanding older than 90 days
- Collections by payment mode
- Payments not yet reconciled
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheets and notebooks vs Biznsbook Collections
Compare running this on spreadsheets with Biznsbook UTR or reference on non-cash payments and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Reference on a transfer | ❌ Optional, often missing | ✅ Required for non-cash by default |
| Same UTR twice | ❌ Found at year end | ✅ Warned at the moment it is typed |
| Collector sees | ❌ The other client and amount | ✅ A warning that names neither |
| Checking the bank | ❌ A separate spreadsheet | ✅ A Seen in bank tick per payment |
| Cash in hand | ❌ Trust | ✅ A Cash handed over tick per payment |
| Forgotten items | ❌ Nobody notices | ✅ Not reconciled count after the days you set |
Light reconciliation, not a full bank rec
The ticks are deliberately light: a reference, a duplicate warning, and a tick per payment. Firms that want full bank reconciliation can license Finance Management. Collections stays usable for a firm that only wants to know every payment reached the bank.
Write this into your weekly owner routine and revisit it when you add collectors or new services.
Frequently asked questions
Is a UTR required for every payment?
For payments that are not cash, by default yes. Settings can turn the requirement off. Cash never needs a reference.
What does a collector see when a UTR is reused?
This reference has already been used — please check. It does not say which client or how much. The owner sees the full match.
Does ticking Seen in bank change the payment?
No. Seen in bank and Cash handed over are owner ticks. They do not change the amount or the allocation.
When does a payment count as not reconciled?
When it is still unticked after the number of days set in Settings. The default is 7 days.
How this differs by industry
Retail
A clinic with three front-desk staff records UPI fees all day and ticks Seen in bank each evening from the bank app.
Wholesale & distribution
A consultancy catches a bank transfer that the office and the field collector both recorded, because the second entry warned on the reused UTR.
Manufacturing
A service workshop ticks Cash handed over when each technician hands in the day’s cash, and the dashboard shows what is still out.