FINAHQ · Munshi
Munshi runs your close. Your team approves it.
Munshi is the close agent inside FINAHQ that chases people for what the close needs, so your team only reviews and approves.
Intercompany reconciliation
Read the transcript
The problem: every company books the same intercompany deal its own way. Invoice numbers keyed differently on each side. GST the buyer can't claim stays with the buyer. Cut-off booked in the last week by one side only. Natures booked under another nature by the buyer. Munshi pulls every company's SAP G/L lines and open AR/AP items through FINAHQ — 17 companies, one table. One company keeps its own vendor and customer codes. They sit on their own rows, counted in that company's books only. Eliminate on an ICO control or a lead entity. GST the buyer can't claim stays as group cost. Leave a party out of a run. 100 intercompany pairs, matched invoice by invoice. 47 sit outside tolerance — and Munshi says why. Recon sheets are live SUMIFS on the tagged base data, quarter by quarter. You enter the stock still held and the seller's margin % — ₹10 Cr × 10%. Change it any time; every change is logged. Three draft journals — P&L, balances and hybrid — at L3/L4, in the lead entity's books. Every journal balances. Narrations name the pair, the recon and the reason for any difference. Nothing posts to the books until you approve. Send it back and the step runs again.
Year-end close
Chapters
- 0:00 Good Group, year-end disclosures, prepared by Munshi
- 0:18 Open Good 1, its close, step by step
- 1:00 The statements prove themselves, 7a to 7d
- 1:54 Your team only reviews and approves
- 2:12 Ready for the auditors
- 2:24 All three companies done
Read the transcript
Munshi by FINAHQ. Good Group, year-end disclosures, prepared by Munshi. Three companies, year ended 31 March 2026, amounts in rupee lakh. Munshi prepared the year-end close for three companies. Across the whole group, just one thing needs your team: an approval. Open Good 1: its close, step by step. Each figure ties back to the ledger, and the checks prove it. The statements prove themselves: 7a, the Balance Sheet foots, both years. 7b, the Profit and Loss ties to the ledger, both years. 7c, equity closes to the Balance Sheet. 7d, the cash flow closes to cash. Your team only reviews and approves. Approved: every step of Good 1 is done. Ready for the auditors: draft statements downloaded, PDF and Excel. The group's year-end close: all three companies done.
What it does
What Munshi takes off your team
No close plan to build
Munshi reads what the group already publishes and drafts the plan. You approve it instead of building it.
No chasing people
Munshi asks each owner directly for what's needed, collects it and confirms — the chasing stops being your job.
Nothing missing for the auditor
Every request, confirmation and approval is logged automatically, so the trail is already there when they ask.
Next quarter starts itself
The roster, decisions and dates carry forward on their own — nothing rebuilt from scratch each quarter.
Nothing new to learn
Reachable over MCP, the standard AI tools use to connect, so your team runs it from the tools they already use.
How a close runs
The plan. Munshi reads what your group already publishes, like the annual report, and drafts the close plan: every step with an owner, a date and an approver — so nobody starts the quarter from a blank plan. You fix what is wrong and approve it.
The trial balances. FINAHQ pulls each company’s trial balance, read-only, from Tally, SAP, Oracle or QuickBooks, and maps it to your group chart of accounts. Fix a mapping once and it sticks.
| Entity | Source | Q1 | Q2 | Q3 | Q4 |
|---|---|---|---|---|---|
| Good Industries | Tally Prime | Loaded | Loaded | Loaded | Loaded |
| Good Components | Tally Prime | Loaded | Loaded | Loaded | Loaded |
| Good Polymers | SAP S/4HANA | Loaded | Loaded | Loaded | Loaded |
| Good Logistics | Oracle Fusion | Loaded | Loaded | Loaded | Loaded |
| Good FZE | Oracle Fusion | Loaded | Loaded | Loaded | Not loaded |
| Good Services | Tally Prime | Loaded | Loaded | Loaded | Loaded |
A period that is not loaded is shown as not loaded. Asked about it, the product says so rather than estimating.
The asking. Munshi emails the owner behind every gap on that grid. They reply with the schedule attached. No login, no portal, and the follow-ups go out on their own.
What does not agree. When an intercompany pair is off, Munshi writes to both people with the same reference, so your two teams argue from one list instead of each chasing their own.
The judgements. Provisions and estimates go in as top-side adjustments, with who raised and who approved each one — an answer ready the moment an auditor asks for it, not reconstructed afterward.
The statements. Consolidation runs on the mapped data, and the statements come out in your approved statutory templates, ready to review rather than built from a blank workbook.
| Line | Good Industries | Good Components | Good Polymers | Good Logistics | Good FZE | Good Services | Sum | Eliminations | Consolidated |
|---|---|---|---|---|---|---|---|---|---|
| Revenue from operations | 48,200 | 12,400 | 9,650 | 5,180 | 7,320 | 2,140 | 84,890 | (6,450) | 78,440 |
| Other income | 640 | 85 | 120 | 45 | 210 | 30 | 1,130 | (380) | 750 |
| Total income | 48,840 | 12,485 | 9,770 | 5,225 | 7,530 | 2,170 | 86,020 | (6,830) | 79,190 |
| Cost of materials consumed | 29,150 | 7,880 | 5,940 | 1,120 | 4,260 | 0 | 48,350 | (6,450) | 41,900 |
| Employee benefits expense | 6,420 | 1,690 | 1,310 | 1,540 | 980 | 1,180 | 13,120 | — | 13,120 |
| Finance costs | 1,180 | 310 | 240 | 160 | 95 | 20 | 2,005 | (380) | 1,625 |
| Depreciation and amortisation | 2,240 | 640 | 510 | 420 | 330 | 60 | 4,200 | — | 4,200 |
| Other expenses | 5,610 | 1,240 | 980 | 860 | 720 | 460 | 9,870 | — | 9,870 |
| Total expenses | 44,600 | 11,760 | 8,980 | 4,100 | 6,385 | 1,720 | 77,545 | (6,830) | 70,715 |
| Profit before tax | 4,240 | 725 | 790 | 1,125 | 1,145 | 450 | 8,475 | — | 8,475 |
| Current tax | — | — | — | — | — | — | — | — | 2,180 |
| Deferred tax | — | — | — | — | — | — | — | — | 145 |
| Profit for the year | — | — | — | — | — | — | — | — | 6,150 |
| Attributable to owners of the parent | — | — | — | — | — | — | — | — | 5,945 |
| Attributable to non-controlling interests | — | — | — | — | — | — | — | — | 205 |
Next quarter. The roster, the decisions and the dates carry forward, so the next close starts from the one you just finished.
You don't pay for a process. You pay for a finished close.
An answer isn't a closed book
FINAHQ already works over MCP, the standard AI tools use to connect, so your team can ask it anything from their own tools — tie the statements, check which figures were plugged. What that gets you is an answer to one question at a time. Munshi is what gets you the finished, approved close, without your team running that question every step of the way.
FINAHQ · MCP Called from your own toolsget_tb(entity="vppl", period="FY 2025-26")- Trial balance loaded · 6 entities now held for FY 2025-26
run_recon(scope="intercompany")- 3 trading pairs matched · eliminations proposed, none posted
fs_tie()- Balance sheet ties · profit and loss ties · consolidation agrees to the sum of its parts
query_statutory_scope(provenance="plug_number")- Every figure that was plugged rather than computed, by entity and period — with the cell it came from
post_reclass(...)- Proposed, not posted. Nothing is written without an explicit approval
Real calls. Illustrative figures from a fictional group. One SOP, and every close comes out the same way
A close is the same procedure every period. So we write your SOP (standard operating procedure) with you, once. After that it isn't a procedure your team runs — it's a close plan Munshi executes and your team approves. Every row stays yours to change.
Munshi · Close plan FY 2025-26 · SEBI (LODR) Regulation 33 — audited annual results, 60 days from year endEvery step of the close with its owner, approver, due date and status Step Owner Approver Due Status Trial balances loaded from each ERP 6 of 6 entities Entity controller Group financial controller 10 Apr Approved Intercompany balances matched and agreed 6 of 6 entities Entity controller Group financial controller 18 Apr Approved Fixed asset register reconciled to the ledger 4 of 6 entities Entity controller Group financial controller 24 Apr Waiting Closing rate confirmed for the overseas entity Munshi Group financial controller 24 Apr Confirming Eliminations posted and the consolidation run Group financial controller Chief financial officer 2 May To do Schedule III notes drafted from the consolidated figures Group financial controller Chief financial officer 12 May To do Auditor questions answered and the board pack issued Chief financial officer Audit committee 26 May To do Illustrative figures from a fictional group. A finished schedule, not an open thread
Each month your people send the files they already make. Where a question needs a person, Munshi asks it once, in your words. What comes back to you is the completed, reconciled schedule — not a thread you still have to chase.
Munshi · Waiting on 3 open · 22 April 2026Outstanding requests by entity, with when each was asked and how many reminders have been sent Entity Waiting for With Asked Reminders Good Polymers Fixed asset additions for the fourth quarter Entity controller 14 Apr 2 Good Logistics Fixed asset additions for the fourth quarter Entity controller 14 Apr 1 Good FZE Confirmation of the closing rate Munshi fetched Group financial controller 21 Apr 0 Illustrative figures from a fictional group. The close gets easier, not harder, every quarter
We keep looking for ways to make FINAHQ easier to use. Seshadri Subbaraman, CFO at SNR, said it before we did: “they are consistently on the lookout to keep improving the tool”.
For your auditor
The approval log
Who approved what, and when. Every figure also links back to the journal entry it came from.
| Entity | Request | Approved by | When |
|---|---|---|---|
| Good Polymers | Trial balance for the quarter released for group reporting | Finance owner | |
| Good Components | Intercompany trade balance with the parent, 1,340: confirmed | Finance owner | |
| Good FZE | Closing rate for the period, and the translation basis | Finance controller | |
| Good Industries | Elimination schedule approved for posting | Group controller |
Questions
Commonly asked
Does Munshi make accounting decisions?
No. It asks the person who owns the answer, records what they say and logs the approval. The judgement stays with your team. Munshi takes away the chasing.
Do our line owners have to log into another system?
No. Munshi emails each owner, and they reply with the schedule attached. No account to create and no password to reset.
What if nobody replies?
The item stays open and visible, Munshi sends its own follow-ups, and the close plan shows it as outstanding. Nothing counts as resolved because nobody replied.
How does an auditor check a figure without us in the room?
Every figure links back to the journal entry it came from. Adjustments are approved entries, never typed over a figure, and the approval log shows who approved what and when.
Can it run inside our own infrastructure?
Yes, including on-premise. The trust page sets out the deployment options and the controls that come with each.
Munshi's AI usage is not part of any estimate. It is borne by the customer at actual cost and varies with how Munshi is used.
FINAHQ, Munshi and FINK are all offered by Ananta Technology Services LLP.