Receipt-to-Transaction Matching with AI agents

An agent can watch your card feed for new transactions and automatically match each one to the receipt an employee submitted, flag the transactions that don't have a matching receipt yet, and nudge the employee directly instead of Finance manually cross-referencing two separate systems every month. The value is catching missing receipts while they're still fresh — a nudge sent the same week beats a mass email at month-end asking forty people to remember what they bought three weeks ago.

How it works today vs. with Neotask

Expense reconciliation is a slow grind because card transactions and submitted receipts live in two different systems that don't talk to each other automatically. Someone in Finance has to open the card feed, open the expense tool, and manually eyeball which transactions have a matching receipt and which don't — and with a few hundred transactions a month, that's real hours spent every close cycle. The transactions that slip through are the expensive part: by the time a missing receipt is caught at month-end, the employee often can't remember what it was for, and Finance either has to write it off as unsubstantiated spend or chase down a paper trail that's gone cold. Categorization is its own manual step on top of matching — someone still has to decide which GL code a matched expense belongs to, transaction by transaction. An agent matches transactions to receipts continuously as both land, not in a monthly batch, so a missing receipt gets flagged and chased while the employee still remembers the context.

The agent flow

Ingest the card transaction feed

The agent watches for new transactions as they post to the corporate card feed.

Integration: brex

Match against submitted receipts

Each transaction is matched to a submitted receipt by amount, merchant, and date, handling near-matches like a slightly different merchant name gracefully.

Integration: ramp

Flag unmatched transactions

Any transaction without a matching receipt after a short grace period is flagged clearly rather than silently carried forward to the next reconciliation cycle.

Nudge the employee

The employee gets a direct, specific reminder — this transaction, this amount, this date — rather than a generic "submit your receipts" blast.

Integration: slack

Categorize matched expenses

Once matched, the agent applies the correct GL category based on merchant type and prior categorization patterns, ready for the accounting system.

Integration: quickbooks

Escalate aged unmatched items

Transactions still unmatched after the escalation threshold get routed to the employee's manager, since Finance shouldn't have to write off spend nobody explained.

Variations

• High-frequency travelers get a batched daily digest of unmatched transactions instead of individual nudges for every single one.
• Transactions under a small threshold (e.g., under $25) can skip the receipt requirement entirely per policy, matched automatically without a nudge.
• International transactions get currency-normalized before matching so a receipt in a foreign currency still reconciles against the card statement correctly.

Frequently asked questions

What counts as a "match" if the merchant name is slightly different on the receipt vs. the card statement?

The agent uses fuzzy matching on merchant name, amount, and date, and only auto-matches when confidence is high — ambiguous cases are flagged for a human to confirm rather than guessed.

How long before an unmatched transaction gets escalated to a manager?

That's configurable, but a typical policy is one nudge to the employee, then escalation after 14 days of no response.

Does the agent decide the GL category on its own?

It proposes a category based on merchant type and historical patterns, but Finance can override the categorization rule set at any time.

Plans

Continue