Intercompany Reconciliation Software for Bookkeepers: Who Actually Needs It

Intercompany reconciliation software promises to delete the ugliest day of a bookkeeper's month-end close. We looked hard at building one, compared the eight tools already selling into this space, and killed the idea. Here's the problem, the pricing, and the reasoning.

The oddly specific problem

Three LLCs, one owner, no documentation, and a bookkeeper holding the bag at month-end.

A bookkeeper takes on a new client. The client owns three LLCs: an operating company, a property holding entity, and something that exists mainly because a lawyer suggested it in 2019. Money moves between them constantly. Owner pays a vendor from the wrong account. Management fee gets booked as a loan in one set of books and an expense in the other. Nobody wrote anything down.

If that structure was set up properly and maintained, the monthly cleanup is roughly twenty minutes. Bookkeepers in the r/Bookkeeping thread on this describe exactly that. But if it has been ignored for a year, the same work becomes a full day per entity. Add a third entity, or a client who does their own bookkeeping between visits, and half a day disappears. The repeat offenders are intercompany loans and management fees, because those are the transactions nobody documents consistently and everybody codes differently.

The specific frustration isn't the arithmetic. It is the number of parties. Each entity has its own timing, its own chart of accounts, its own person entering things. Reconciling two clean entities is an hour. Reconciling four messy ones is a project with no defined end.

Wait, is this actually a problem?

Yes, though the evidence is thinner than the vendor internet would have you believe.

The genuine signal is bookkeepers describing the work in their own words: hours to days of manual matching, undocumented intercompany loans, cleanup that "drags on much longer than anticipated." One commenter noted that this is good work to charge a premium for, precisely because plenty of bookkeepers won't touch it. That is a real market observation, and we'll come back to it, because it cuts in an unexpected direction.

There's also a scoping issue. Roughly a third of one bookkeeper's client base had any intercompany activity at all. Of that third, only a slice has enough entities and enough mess to justify a software line item. So the pain is sharp but narrow: it concentrates in bookkeepers serving multi-entity SMB clients, often in the $30M to $80M revenue range, where structures are complex enough to hurt but not big enough for an enterprise finance team.

Intercompany reconciliation software compared: 8 tools and what they cost

All pricing as of research; enterprise figures are estimates because these vendors don't publish rate cards.

The gap in the table is real but narrow: nothing in the SMB tier is deep. Nothing handles undocumented intercompany loans and inconsistent management fee coding with much sophistication. That's the wedge, and it's why we looked at building here.

So why isn't this a slam dunk?

We scored this 3 out of 10 and walked away. Five reasons, in order of how much they mattered.

The gap is already occupied, and the occupants aren't thriving. DueToFrom is purpose-built for exactly this buyer, at exactly this price, with a free tier and a firm-level pricing ladder. Xenett covers the same buyer as a module. The obvious counter is "yes, but they're shallow." Maybe. We couldn't find evidence for it: no churned-customer complaints, no documented feature gaps, no critical reviews. "Shallow" was our assumption, not a finding. The more useful question is the one we kept avoiding: if this problem is real, painful, technically easy, and has a clearly identifiable buyer, why hasn't either product broken out? Neither appears in funding databases. Neither has visible presence beyond its own site. Every plausible explanation for that silence is a reason not to build.

The buyer's incentives point the wrong way. Recall the bookkeeper who noted this is good work to charge a lot for, because most people won't touch it. We initially filed that as demand evidence. It is closer to the opposite. The buyer who genuinely wants that is the firm owner trying to add capacity without hiring, which is a different person, a different pitch, and a much smaller population than 1.5 million bookkeeping clerks.

The TAM is inflated by roughly an order of magnitude. The US has about 1.52 million bookkeeping, accounting and payroll clerks, and around 156,000 self-employed bookkeepers. Neither number is the market. The market is bookkeepers who serve multi-entity clients, have enough of them to justify a subscription, and won't just use spreadsheets or paste a CSV into ChatGPT. Working from the "about a third of clients" observation and filtering for volume, a defensible estimate lands somewhere between 5,000 and 20,000 US firms. Framing 300 customers as "0.2% penetration" implies the other 99.8% are waiting. If two incumbents haven't reached 1% after years in market, low conversion is the finding, not untapped upside.

5,000-20,000 US firms is the defensible market, not 1.5 million clerks.

Usage is episodic, which is a churn machine. Intercompany reconciliation happens at month-end. One to three days of intense use, then the tool sits idle for three weeks. No daily habit, no network effect, no accumulated data that makes leaving painful. And retention is hostage to something outside your control: if a bookkeeper loses two multi-entity clients, the ROI on a $129/mo subscription flips negative and they cancel that week.

There is no channel. Bookkeepers are not concentrated anywhere reachable. There is no single conference, Slack, or newsletter. The available options are SEO against Intuit and Xero and the entire accounting media industry, app marketplace placement where Intuit controls discovery and can change API terms whenever it likes, or cold outreach to a fragmented low-LTV audience. For a product at $59 to $359 per month with structural churn, none of those math out quickly.

One more note, because it's the trap: the engineering here is easy. Deterministic amount-and-date-window matching with tolerance bands, fuzzy string matching on descriptions, standard OAuth integrations with QBO and Xero, low transaction volumes. Two people could ship something credible in six to eight weeks. That feasibility score was the most dangerous number in the analysis.

Easy to build means it is already built.

What we're watching

Three things would change the verdict.

Documented incumbent failure. Not "we think DueToFrom is thin," but bookkeepers publicly describing what they tried, why they stopped, and what they went back to. That evidence would define a real wedge instead of an assumed one.

A repositioning toward firm owners. The version of this that works sells capacity, not convenience: a firm owner taking on multi-entity clients they currently decline because nobody on staff will touch the cleanup. Same software, different buyer, different pricing logic, and it resolves the billable-hours conflict rather than ignoring it.

Native platform moves. Xero already has some intercompany functionality. If Intuit or Xero ships proper multi-entity matching, the SMB tier of this table collapses into a checkbox and the question stops being interesting. If they conspicuously don't over the next couple of years, that's mild evidence the segment is too small for them, which is exactly the segment where a focused tool can live.

If you're a bookkeeper shopping for intercompany reconciliation software right now, the practical answer is unchanged: try DueToFrom's free tier, and if you want the close-workflow wrapper, run Xenett's 60-day trial. Then bill accordingly for the hours you keep.