For an accountant, searching merchants by chat is a quick way to pull every payment to one vendor, spot the name variants that split it into pieces, and prepare questions for the client. Use it read-only, treat the totals as leads to verify against invoices, and apply any fixes yourself in the app.
What problem does it solve?
A single vendor often appears under several names in a client's records: the full trading name, a short form, a payment company's label. If you add up only one spelling, the vendor looks smaller than it is, and the invoice trail looks incomplete. A merchant search by name, plus a follow-up for variants, shows the whole picture in minutes.
How do I run a vendor tie-out?
- Connect the assistant with read-only access, after checking that your engagement and the client's consent allow it.
- Ask for all payments matching the vendor's name in the period, with count and total.
- Ask for similar or abbreviated names and list them separately.
- Add the totals of the variants to get the combined figure.
- Compare with the vendor's invoices or statement of account, and note the difference.
Say 'Sharma Traders' shows 5 payments of ₹48,500 in total, and a variant 'SHARMA TRDRS' shows 2 payments of ₹12,200. Combined, that is 48,500 + 12,200 = ₹60,700 across 7 payments. If the vendor's own statement says ₹65,200, you are ₹4,500 apart (65,200 - 60,700), and you have a specific question for the client: was there a cash payment, or a payment from another account?
| Step | Output | Next action |
|---|---|---|
| Search exact name | 5 payments, ₹48,500 | Note and keep |
| Search variant | 2 payments, ₹12,200 | Combine with the first |
| Combined total | 7 payments, ₹60,700 | Match to invoices |
| Vendor statement | ₹65,200 | Query the ₹4,500 gap with the client |
How do I make the variants stick?
Once you know two names are one vendor, record that in the app. SpendixAI lets you add merchant aliases, and corrections become history that later categorisation draws on. That spares you the same search next month.
Be careful of looking-alike names. Two different vendors may share a word, so check amounts and dates before you merge them.
What are the limits?
- A search finds what is recorded; payments from another account or in cash will not appear unless added.
- The assistant can miscount; verify totals against the report, not against its own earlier answer.
- Search results sit in the chat, so keep questions narrow and follow your confidentiality duties.
- Estimates in reports, including GST, need checking against invoices, and rules and limits change, so confirm the current position with the official source.
What goes in my working papers?
Note the date of the search, the name variants used, the totals and the document you compared them with. If the numbers feed a Tally or other export, produce that from the app's export area after your fixes, not from chat output.
How does this fit a month-end routine?
Run the search for your top vendors after the statements are in and before you finalise categories. A vendor with a split name often shows up as two small totals that look unremarkable, until combined. Doing this early means the oddities are questions for the client while the month is still fresh, instead of audit points months later.
A closing checklist
- Consent confirmed, read-only chosen.
- Exact name and variants searched.
- Combined total compared with the vendor's document.
- Aliases added for confirmed variants.
- Differences listed as questions for the client.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

