Why It Matters
Most expense leaks aren't fraud. They're friction, habit, and inattention.
A vendor quietly raises prices 8% over six months. A receipt gets submitted twice in the same pay period. A card gets used at a merchant category that's out of policy. None of these are dramatic — but all of them compound.
SpendGuard is designed to surface these patterns while they're still correctable. Not at year-end. Not at audit. While there's still time to act.
"Outputs are structured for advisor review — not automated accusations. Your advisory team sees the exceptions. They decide what to do with them."
In one case, a contractor was purchasing materials from their usual supplier when SpendGuard identified the same materials were available elsewhere for significantly less.
Illustrative example. Client details are not published.
Capabilities
What SpendGuard analyzes
Receipt parsing
Extract merchant, items, quantities, taxes, and tips from submitted receipts. Structured data, not scanned images sitting in a folder.
Duplicate detection
Flag the same receipt or charge submitted twice — including split-tender anomalies that would pass a manual review.
Unauthorized transactions
Surface card misuse patterns and merchant category exceptions. Know when a card is used outside its intended scope.
Better local pricing
Compare common supplies against known local and online benchmarks when available. Overpaying for the same items, repeatedly, is a pattern — not a one-time event.
Vendor drift
Detect creeping price increases by vendor over time. A 3% increase every quarter compounds quietly until it's a material margin problem.
Policy enforcement
Flag out-of-policy purchases by category, limit, timing, or approver. Policy violations caught in week one don't become month-end surprises.
Exception-ready reporting
Clean summaries advisors can review with clients and share with lenders. Structured for conversation, not just compliance.
What We've Found
Real cases. Real outcomes.
All cases are anonymized. Client details are not published.
Retail
Cash runway: 2.8 → 1.9 months
Caught in Week 1
Inventory double-order went undetected — until it nearly collapsed the cash runway
An inventory control employee ordered double the normal inventory amounts. The CEO had no visibility because the transaction hadn't appeared in the monthly report yet. By the time it would have surfaced through normal reporting, the company's cash runway had already dropped from 2.8 months to 1.9 months — a level that would have created a serious cash shortage by the time the quarterly report arrived.
FinTel flagged the anomaly in Week 1 of service. The order was caught in time to correct the position before the cash shortage became a crisis.
Why it mattered
Monthly reporting would have surfaced this 3–4 weeks too late to prevent the cash shortage.
Construction
Embezzlement spanning multiple years
Pattern identified, investigation confirmed
Project payment split into two checks — one deposited, one cashed, proceeds returned 10 days later
A construction company employee was receiving project payments as two checks instead of one. The first check was deposited normally. The second was cashed — and the cash was deposited 10 days later, obscuring the transaction pattern from routine review.
FinTel identified the double-check pattern and the delayed deposit of the second half, and recommended investigation. The employee confessed to having used the same method a significant number of times over multiple years. The funds had been "borrowed" and returned — a pattern that had never triggered a flag in traditional reporting.
Why it mattered
The short-term return of funds made this invisible to standard reconciliation. Only continuous transaction-level monitoring could detect the timing pattern.
Kitchen Renovation
$450 flagged in Month 2 — years of history found
Receipt-level analysis
Personal items mixed into supply runs — undetected for years
In Month 2 of service, SpendGuard flagged a receipt where an employee had included personal items in a company card purchase during a supply run. The unauthorized amount was $450 — small enough to pass unnoticed in any aggregate review.
FinTel advisors recommended investigation. The review revealed the same employee had been mixing personal purchases into company supply trips for years — a pattern that had never been caught because no one was reviewing receipts at the line-item level.
Why it mattered
Individual transactions were too small to trigger any threshold-based alert. Only receipt-level parsing could surface the pattern.
