Expense reconciliation audit log for finance teams

The moment someone goes looking for this: a finance analyst is preparing month-end close and notices the number in the analytics dashboard doesn't match the number in the expense report export. They spend two hours trying to figure out which one is right, whether the gap is timing, rounding, category mapping, or a bug. They have no way to trace a specific transaction through the system to see why it appears differently in two views. They file a support ticket and wait.

This gap persists because analytics and expense reporting are often built by different teams inside incumbent vendors, pulling from the same database but aggregating differently — different filters, different date-range logic, different handling of pending versus posted transactions. The people who experience the pain are finance analysts; the people who could fix it are engineers who don't see it as broken, just 'technically correct.' The buyer (the finance director) doesn't feel the daily friction — the analyst does but has no purchase authority. Nobody screams loudly enough to get it fixed.

The specific complaint is direct: 'The analytics report differs from the expense report.' That's not vague — that's a reconciliation gap that finance teams in regulated industries cannot tolerate. Another complaint compounds it: the last four digits of the payment method were removed from expense reports, meaning analysts can't even trace which card a transaction came from when investigating discrepancies.

This is a business because the reconciliation problem doesn't go away — it recurs every close cycle, every audit, every time a new expense category or card is added. The cost is concrete: analyst time spent manually reconciling, delayed closes, and audit findings that trace back to unexplained report discrepancies.

What to build

Build a reconciliation audit tool that connects to an expense management system's data export (CSV or API), compares transaction-level data between the analytics output and the expense report output, flags every line where the two disagree, and generates a diff report showing exactly which field — amount, category, date, card identifier — is responsible for the mismatch.

Where to start

Start exclusively with companies running Amadeus Cytric or Amex GBT Egencia, where the analytics-versus-export discrepancy complaint is documented and users are sophisticated enough to pay for audit tooling — target their finance teams directly via LinkedIn outreach with a free reconciliation run as the hook.

The hard part

Every expense tool exports data in a slightly different format with different field names, and building reliable parsers for each one without a proper API is slow, fragile, and doesn't scale — so early on you'll have to pick one or two tools to support and resist the urge to generalize too fast.

How it makes money

Monthly subscription at $299/month per company, covering unlimited reconciliation runs. Offer a one-time free diagnostic report to convert the first conversation into a paying customer.