The 2 AM text that found a $2,340 double charge

A founder texts an accounting agent at 2:07 AM: "did we pay the vendors??"

The reply comes back in seconds: "Yes. Also, you were double-charged $2,340. Refund already requested."

That 8-second exchange is the whole pitch for agentic accounting, so here is what has to be true behind it.

The workflow behind the text

1. Ingest payments continuously. Bank feeds and card transactions land in one ledger instead of living in exports.
2. Match vendor bills to payments. Every payment is paired with the invoice it settles.
3. Flag anomalies. Two charges, same vendor, same amount, close dates: duplicate candidate.
4. Act, then report. The agent drafts the refund request and tells you after, with the evidence attached for review.

Nothing exotic. It is the reconciliation a bookkeeper does at month-end, run every night instead.

Why legacy tools miss it

Legacy software makes you export, re-enter and reconcile by hand. A duplicate charge sits in a CSV until someone has the hour to scan it. By then the refund window may be closing.

Where MCP fits

Portali supports MCP integration, so the agent reads and acts on the ledger through a standard interface rather than screen scraping. The workflow comes first; MCP is just how the agent gets safe access to your data.

Meet Tali, the AI assistant on the other end of that text, and see the reconciliation workflow: portali.tech