Finance workflows automated, and tested on real, messy data.
TRISOLUTIONS builds automated finance workflows. In 30 days, 8 connected automations were built and verified covering GST reconciliation, accounts payable, receivables, cash-flow forecasting and management reporting. The full month-close sequence ran in about 15 minutes.
| Invoice | Books | GSTR-2B | Result |
|---|
Headline results
The 15-minute run time was directly measured. The "before" figures are industry benchmarks this roadmap was scoped against, not personally re-timed manual work.
The eight automations
Each one was checked against known, deliberately flawed test data before it was trusted. Open any row for the before, the after and what broke along the way.
GSTR-2B Reconciliation Agent
Compares the purchase ledger against GSTR-2B filing data.
Before
Manual line-by-line comparison across two spreadsheets. Industry benchmark: about 40 hours per entity.
After
Exact-match comparison with AI classification. It found all 4 planted error types: a duplicate entry, a timing difference, an amount mismatch and an invoice missing from the books.
Impact
Catches what a manual review tends to miss, such as a ₹40 discrepancy on a single invoice.
In practice: what you give, receive and do
- You give
- Drop the Tally purchase ledger and the GSTR-2B download into two shared sheets (same layout every month).
- You receive
- An email listing every mismatch, each labelled duplicate entry, timing difference, amount mismatch or missing in books, with a one-line suggested action.
- You do
- Review the flagged invoices and correct them in Tally. Matching invoices need no action.
- How often
- Monthly, or whenever you upload new data.
Fixed along the way: a column-name collision that silently overwrote one dataset with the other, and a missing JSON.stringify that sent the AI a broken placeholder instead of real data.
Accounts Payable Invoice Pipeline
Reads PDF and image invoices and checks mandatory fields.
Before
Manual data entry from each vendor invoice. Industry benchmark: about 10 hours per week.
After
Automatic extraction with a validation check. Invoices missing a GSTIN, invoice number or total are blocked from posting and trigger an automatic warning email.
Impact
A sales invoice was once fed in where a purchase invoice belonged. The extraction was accurate but the document was wrong, so a validation rule now catches this.
In practice: what you give, receive and do
- You give
- Save the vendor invoice (PDF or image) into the 'AP Invoices' Drive folder.
- You receive
- A new row in the 'AP Draft Entries' sheet with vendor, invoice number, GSTIN, amounts and due date, marked 'Ready for Tally entry'. If the GSTIN, invoice number or total is missing, a warning email instead.
- You do
- Check the draft row and post it in Tally. For warnings, get the missing detail from the vendor.
- How often
- Whenever a new invoice arrives.
Fixed along the way: a .docx test file that AI vision cannot read (converted to PDF), and GSTIN truncation that became a permanent 15-character rule.
Automated MIS Generation
Pulls monthly P&L and drafts board-ready commentary.
Before
Commentary written by hand every month. Industry benchmark: about 2 days.
After
Scheduled generation that identifies margin compression, names likely causes and flags forward risk. It arrives as a draft emailed to the owner and is not sent to anyone else automatically.
Impact
A filter bug once pulled the wrong month, and the AI filled the gap with a believable but invented story. Every output is now checked against known figures.
In practice: what you give, receive and do
- You give
- Keep the monthly P&L figures sheet updated (current and previous month).
- You receive
- A DRAFT management commentary emailed to you, the owner, on the set date. It is not sent to anyone else automatically.
- You do
- Read it, edit if needed, then forward it to partners or the board.
- How often
- Monthly.
Fixed along the way: a case-sensitive sheet filter that returned zero rows, then the wrong month, and currency that defaulted to USD instead of ₹ with lakh-style grouping.
Compliance Calendar Agent
Alerts you when a GST, TDS or ROC deadline is within 7 days.
Before
Manual deadline tracking, prone to missed filings and late fees.
After
A daily check against a filing calendar. It fires only inside the warning window and stays silent otherwise. Tested in both directions.
Impact
A missed deadline carries direct penalties. This removes the manual tracking entirely.
In practice: what you give, receive and do
- You give
- Fill the filing calendar once (filing name, due date, form, status) and mark filings Done.
- You receive
- An email alert only when a deadline is within 7 days. No email means nothing is due soon.
- You do
- File the return and update the status in the sheet.
- How often
- A daily check, silent unless something is due.
Fixed along the way: silent failures parsing the DD-Mon-YYYY dates used in Indian filings, a zero-indexed month error and two field-name casing mismatches.
Bank Reconciliation Agent
Matches ledger invoices to bank payments by amount and date.
Before
Manual statement-to-ledger matching every week.
After
Each invoice is marked Paid, Unpaid or Check Manually (an automatic flag for ambiguous matches). It caught a ₹100 short payment and a genuinely unpaid invoice.
Impact
When two invoices share the same amount, it automatically flags them as Check Manually instead of guessing which payment belongs to which.
In practice: what you give, receive and do
- You give
- Upload the bank statement and the purchase ledger to the shared sheets.
- You receive
- An email listing only invoices that are Unpaid or Check Manually, with a suggested action. Short payments (for example ₹100 less than invoiced) are flagged.
- You do
- Chase unpaid invoices and manually confirm the Check Manually ones (for example two invoices with the same amount).
- How often
- Weekly.
Fixed along the way: a race condition between parallel branches (solved with a Merge node) and an execution-mode mismatch that duplicated rows 12 times.
Receivables Follow-Up Agent
Ages unpaid invoices and escalates the reminder tone in 3 stages.
Before
Manual tracking and hand-written follow-ups, with the tone depending on who wrote them that day.
After
Reminders in three escalating tones: gentle (up to 14 days overdue), firm (up to 44 days) and a final notice beyond that. Verified on test invoices at 5, 42 and 82 days overdue. Recommended setup: reminders come to you for approval first, not straight to your customers.
Known limitation
It re-sends a reminder every day it runs, because it does not yet track what was already sent. That is the next iteration, and it is documented rather than hidden.
In practice: what you give, receive and do
- You give
- Keep the receivables sheet current (customer, invoice, due date, amount, status Paid or Unpaid).
- You receive
- Reminder emails in three escalating tones: gentle (up to 14 days overdue), firm (up to 44) and a final notice beyond that. Recommended: they come to you for approval first, not straight to your customers.
- You do
- Approve or edit the reminder, and mark invoices Paid when payment arrives.
- How often
- Daily, once the 'already reminded' fix is in.
Fixed along the way: a Switch node with overlapping thresholds, replaced by a pre-computed stage value for unambiguous routing.
Payable Approval Agent
3-way match across Purchase Order, Goods Receipt and Invoice.
Before
Manual cross-checking of three documents, if it was done at all.
After
Matching orders are marked Approved. A deliberate mismatch (invoice for 50 units, only 45 received) triggered a Payment Hold email stating the exact reason. A person then decides whether it is a data-entry error or a real shortfall.
Impact
Stops payment for goods that were never delivered, a control small teams rarely have time to run by hand.
In practice: what you give, receive and do
- You give
- Fill the Purchase Order, Goods Receipt and Vendor Invoice sheets.
- You receive
- For each order, either Approved, or a Payment Hold email stating the exact reason (for example, invoice bills 50 units, only 45 received).
- You do
- Approved: proceed to pay. Hold: a person decides whether it is a data-entry error or a real shortfall. This is a deliberate human gate.
- How often
- Whenever a new invoice is entered.
Fixed along the way: a stray quote character in a node name that broke cross-node references, and an IF-branch wiring error that sent the approval email for every invoice.
Cash-Flow Forecast Agent
A 13-week (90-day) rolling forecast of your cash position.
Before
No routine forecast existed.
After
A 13-week rolling forecast email built from receivables (adjusted for real collection lag), approved payables and fixed costs, with plain-language commentary and the tightest week highlighted. It flagged a projected shortfall of -₹8,50,500 in week 9. If upstream checks show unresolved issues, you get a Forecast Blocked notice instead.
Impact
It will not run if reconciliation or payables approval still has unresolved issues, because a forecast on unverified numbers misleads.
In practice: what you give, receive and do
- You give
- Maintain the Receivables, Payables Summary (approved payables) and Recurring Costs sheets.
- You receive
- A 13-week rolling forecast email with plain-language commentary and the tightest week highlighted. If upstream checks show unresolved issues, a 'Forecast Blocked' notice instead.
- You do
- Act on any projected shortfall. On a Blocked notice, clear the flagged issues first and the forecast will run.
- How often
- Weekly.
Fixed along the way: comma-formatted amounts in Google Sheets read as text, which silently broke the calculation, and a cross-workflow race condition that read stale status data.
How the agents work together
The month-close sequence (reconciliation, payables approval, receivables follow-up and management commentary) ran in about 15 minutes on a live test.
Reconcile
GSTR-2B data is compared against the purchase ledger.
Match payables
A 3-way match checks the Purchase Order, Goods Receipt and Invoice.
Chase receivables
Overdue invoices get reminders that escalate in three stages.
Forecast cash
A 90-day forecast, built only on resolved reconciliation and payables data.
Report
A draft commentary is generated from the P&L and emailed to the owner.
Common questions
What can you automate?
GST reconciliation, AP invoice extraction, bank reconciliation, receivables follow-up, payable approval, cash-flow forecasting, MIS reporting and compliance deadline alerts.
Is it safe for financial data?
Every automation includes built-in validation rules (such as GSTIN checks, 3-way matching and a forecast that refuses to run on unresolved data) and was tested against known figures before use.
How fast is it?
The full month-close sequence (reconciliation, payables approval, receivables follow-up and commentary) ran in about 15 minutes on a live test.
Does it work with Indian compliance requirements?
Yes. It handles GSTR-2B, GSTIN validation, TDS and ROC deadlines, and ₹ amounts with lakh-style formatting.
How do I get started?
Book a free discovery call using the contact form below, or message TRISOLUTIONS on WhatsApp.
About
TRISOLUTIONS is run by its founder, Trilochan M Hattikar. We build finance and accounting workflow automations covering GST reconciliation, payables, receivables, forecasting and MIS reporting. Every build is tested on real, deliberately imperfect data before it is trusted.
Book a free discovery call
Tell us what you want to automate and Trilochan M Hattikar will reply with next steps.
- FounderTrilochan M Hattikar
- Emailtrilochanmhattikar297@gmail.com
- Phone / WhatsApp