Inter-Company Reconciliation
Compare the due-to / due-from balances and transactions between your entities, let AI match by reference and amount and flag everything that doesn't agree on both sides, then let the group accountant assign a cause, approve the agreed balance, and export a reconciled schedule plus the elimination entry.
A web tool where you import each entity's inter-company subledger, AI matches the two sides by reference and amount, flags one-sided items and amount differences, and shows a due-to vs due-from matrix that should net to zero. The group accountant assigns a cause and owner to each mismatch and approves the agreed balance, and the tool exports a reconciled inter-company schedule and a ready-to-post elimination entry.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- Each entity's inter-company subledger export (CSV is fine: counterparty, transaction, amount, date, reference)
- Claude Code or any AI coding agent
The problem this kills
It's close week in a multi-entity group, and the inter-company accounts won't behave. Entity A says it's owed 50,000 from Entity B. Entity B's books show 47,500. Somewhere between them sits a payment in transit, a timing difference, an invoice booked at the wrong rate, or a charge one side never recorded at all. Until you find it, the due-to and due-from accounts don't net to zero — and consolidation can't go out the door with a hole in it.
So you do it by hand. You pull each entity's inter-company subledger into a spreadsheet, sort both sides by reference, and eyeball your way down two columns looking for what matches and what doesn't. With two entities it's tedious. With five entities and ten counterparty pairs it's a half-day of squinting, and the failure mode is quiet: miss a one-sided item and the elimination is wrong, post the wrong agreed balance and the consolidated numbers are off — and you get to explain why at the audit.
This is exactly the kind of rules-based, high-stakes matching a small internal tool does better than a spreadsheet — and you don't need to be a developer to build it.
What you'll build
A simple internal web tool for your close. You import each entity's inter-company subledger — counterparty, transaction, amount, date, reference. The tool pairs up the two sides of every counterparty relationship, matches transactions by reference and amount, and works out three buckets: items that agree on both sides, items only one side recorded, and items both sides recorded but at different amounts. It shows you a due-to vs due-from matrix across all entities that should net to zero, with every out-of-balance pair lit up.
The group accountant reviews the flagged mismatches on one screen, assigns each a cause (timing, FX, missing entry, error) and an owner, and clicks Approve on the agreed inter-company balance for each pair. Only then does the tool produce a reconciled inter-company schedule and a ready-to-post elimination entry, and carry any still-open items forward to next period.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your business — which entities and currencies you run, how each subledger labels the counterparty, what your reference/voucher convention is, your matching tolerance, your timing-difference and in-transit rules, and your nastiest edge cases — and then tailors the data model, the matching logic, and every later step to your answers. This is a build shaped around your group, not a generic template.
From there it walks the agent through the database schema, the per-entity CSV imports with their duplicate guards, the two-sided matching engine, the netting matrix, the group accountant's review-assign-and-approve screen, and the export of the reconciled schedule and the elimination entry. Every step ends with a ready-to-copy prompt. Because the whole thing runs on CSV in and a clean schedule and journal CSV out, you can build and use it this weekend even if you have no direct connection to your consolidation system.
The governance it includes (this is the point)
This feeds consolidation, so it's built like it matters: login so only your finance team can use it, row-level security so you only ever see your own group's data, and a complete audit trail of every import, match, cause assignment, approval, and export — who did what, and when. Nothing is agreed automatically: the matched balance is a draft until the group accountant approves it, and approval is the hard human-in-the-loop gate before any elimination entry is produced. Duplicate guards on the reference — and on each imported file — mean the same inter-company transaction can't be matched twice and the same balance can't be agreed twice.
Who it's for
Group accountants, consolidation accountants, and controllers in multi-entity groups who reconcile due-to / due-from accounts every close and want it fast, defensible, and the same every period. If you can explain how you decide that two sides agree, you can build this.
You've got this — open the plan, paste the first prompt, and let it interview you about your group.