ReconAI

CFO operations platform

How card spend is processed

1 · Policy checks2 · Auto-code spend3 · Review & approve

When a card expense is ingested, the orchestrator runs these steps in order. Each step is audited with a run_id you can replay in transaction detail.

1
Policy checks
Every card expense is evaluated against your rules — receipt thresholds, spend caps, banned categories.
Example AWS over $75 → receipt required before auto-code can proceed.
Policy admin →
2
Auto-code spend
The tagging agent assigns a GL code using vendor rules, similar past expenses (RAG), and one structured LLM call when needed.
Example Slack with a saved vendor rule → high confidence, LLM skipped.
Auto-coded
Add transaction →
3
Review & approve
When the system will not guess, an accountant reviews, overrides GL, and teaches a vendor rule for next time.
Example Unknown vendor or low confidence → queue or refuse — never silent wrong GL.
Needs reviewUnclassified
Review queue →

Tri-state decisions (tagging outcomes)

Auto-codedConfident enough to auto-code (vendor rule or strong evidence + policy allows).
Needs reviewNew vendor, receipt gate, or mid confidence — accountant decides.
UnclassifiedUnknown merchant or invalid GL — we refuse rather than miscoding silently.

Try all three on Add transaction

Loading company metrics…

Review queue

Transactions that need an accountant — see why each was flagged and apply an override.

AP inbox

Incoming invoices, recommended pay dates, and duplicate detection — recommendations only, no payments executed.

Policy admin

Receipt requirements, spend caps, and category rules that can block auto-coding.

Add transaction

Submit a card expense — try common scenarios like receipt required, new vendor, or unknown merchant.

Settings

Company preferences, API access, and system health.