Transaction categorisation · comparison
Uncat vs FeeGuard: categorising the unexplained vs eliminating causes
Reconciliation compares what you recorded against what settled. The Connect leak this page is about produces no record to compare — the reversal that should have happened simply did not, so nothing mismatches. Uncat is strong at the first job; here is an honest map of where the second one begins.
What Uncat does
a lightweight tool helping accountants categorise uncategorised transactions quickly inside their existing bookkeeping flows. Source: https://uncat.com.
That is real capability in its lane — and the lanes below show precisely where it ends.
Everything said here about Uncat is summarised from its own public materials at the link above, never from private knowledge of how it works inside. Products change; if any line has gone out of date, tell us at feeguard@teamveristria.com and we will correct the page rather than argue about it.
Side by side: FeeGuard vs Uncat
Eight capabilities a Connect platform needs. No empty cells — every row states what each product actually does.
| Capability | FeeGuard | Uncat |
|---|---|---|
| Unreversed-transfer detection | Yes — computed on every `charge.refunded` event: proportional expectation, rounding tolerance, ratio clamping | No — cleanup UX for symptoms; causes untouched. |
| Application-fee leak detection | Yes — application fees tested against reversals via Net Platform Margin; zero- and three-decimal currencies handled | No — fee mysteries categorised, not prevented. |
| Dispute-loss clawback support | Yes — recoverable figure computed on `dispute.closed` (transfer remainder, fee excluded); early warning on `created`; gated automation | No — dispute oddities sorted, not resolved. |
| Cross-border FX monitoring | Yes — realised rates measured against same-day currency-pair baselines; directional loss flagging beyond 0.8% | No — fX deltas labelled, never measured. |
| Runs on your live Stripe Connect account today | Yes — read-only restricted key, roughly ten minutes to first findings, revocable anytime | Depends on deployment |
| Performs recovery actions | One-click manual reversals (free tier); risk-gated automation with idempotency keys on Monitor Pro | Varies by product |
| Evidence & audit trail | Append-only trail on every action; finding-level evidence ids exportable as CSV | Varies by product |
| Pricing model | Detection and the 90-day lookback free · monitoring is a subscription from $49/mo · success fee only when eligible funds are recovered | See vendor site |
Where Uncat genuinely wins
- — Focused, delightful tool earning genuine affection from bookkeepers.
- — Zero-learning-curve fit into existing workflows.
Why platforms choose FeeGuard over Uncat
- Absence, not mismatch. Reconciliation finds rows that disagree with each other; these detectors find the row that was never written.
- All four vectors, natively. Unreversed transfers, kept fees, uncovered dispute losses and FX drag are separate detectors with separate arithmetic, not one heuristic wearing four labels.
- Free before you pay anyone. Detection and the 90-day lookback cost nothing — measure your stranded dollars before committing to any vendor, including us.
- Ten-minute, read-only setup. One restricted key you create and revoke; no migration, no seller re-onboarding, no payment-path changes.
- Recovery is billed on results. The success fee applies only to dollars actually recovered and confirmed in Stripe — if nothing recovers, nothing bills.
- Evidence-grade trail. Append-only logs with finding-level arithmetic — ready for controllers, auditors and diligence teams.
Bottom line
Every uncategorised Stripe oddity is a question. Half our findings are answers. If your problem lives in transaction categorisation, Uncat deserves its reputation. If your problem is a platform balance lower than your ledger predicts — refunds succeeding while transfers never come home — that problem has exactly one purpose-built answer, and you are reading it. Run the free audit; the number settles the debate faster than any comparison page can.
Common questions
Does Uncat explain why transactions look weird?
It categorises them efficiently; root-causing Connect anomalies is our lane.
Is FeeGuard a better choice than Uncat?
For transaction categorisation, Uncat is the specialist and we say so plainly. For detecting and recovering silent Stripe Connect losses — the four vectors above — FeeGuard is purpose-built and Uncat does not perform that function. Most platforms comparing the two are feeling the second problem.
Can we run Uncat and FeeGuard together?
Yes, commonly. They operate on different objects and different events; neither conflicts with the other’s workflow.
What does switching cost us?
Nothing upfront: read-only key, ten-minute setup, free detection. Recovery carries a success fee only on confirmed dollars — so trying FeeGuard risks no budget at all.