Case · Unexpected fee · tieout

Overview Runs Breaks Exceptions Quarantine

Overview Runs Breaks Exceptions Quarantine

Reading the record…

Mercadia demo · synthetic data · resets nightly

Tieout observes and explains. It never moves money, never edits your books, and never guesses.

Case · Unexpected fee · tieout

run c2f01047 · as of 2026-07-02 17:48 UTC · ruleset-v2

Unexpected feeopen

−$8.50txn_fee_radar_0001

seen in 1 run · opened by system

The case, append-only

Openedby run c2f010472026-07-02 17:48 UTC

AcknowledgeResolve

Resolving never edits financial data. If the next run disagrees, this case reopens.

Read-only demo — enforced server-side, not just here.

The evidence

This run’s finding, embedded — not a copy, the same record.

Conclusion
Unexpected feeThe source charged a fee your books never anticipated.
Concluded by ruleset-v2 in run c2f01047, as of 2026-07-02 17:48 UTC.
2
What matching tried
1. Duplicate sweepSurvived — no other Stripe record shares this id or reference.passed
2. Fee schedule checkNo fee schedule entry anticipates this charge for the period.broke here
3. Exact-reference passNo ledger entry references it.broke here
4. Settlement-lag windowPast its settlement-lag window → break.broke here
The transaction
identity
stripe / acct_mercadia / txn_fee_radar_0001
type
fee
amount
−$8.50
occurred
2026-05-15 03:00 UTC
observed
2026-07-02 17:48 UTC
version
v1 · current
normalized by
stripe-v1

4

The raw record

{
  "id": "txn_fee_radar_0001",
  "fee": 0,
  "net": -850,
  "type": "stripe_fee",
  "amount": -850,
  "object": "balance_transaction",
  "source": null,
  "status": "available",
  "created": 1778814000,
  "currency": "usd",
  "description": "Radar for Fraud Teams — May",
  "fee_details": [],
  "available_on": 1778976000,
  "reporting_category": "fee"
}

exactly as receivedcontent hash 3ca34f5f…

The ingestion batch
source
stripe
idempotency key
stripe:acct_mercadia:222471279ce675758f90bb872bb8bd978c013794250c23777e66777cda700b6c
landed
2026-07-02 17:48 UTC
status
normalized

Open the full evidence chain →

Investigate

Clara · assistant · suggests, never resolves

Suggested by Claude · never blocks, never edits

amount_mismatch

A Stripe fee transaction of 850 cents was recorded with no corresponding ledger-side entry or reference to tie it to a parent transaction, suggesting an unexpected or unrecorded fee rather than a duplicate or timing issue.

Next: Check Stripe's fee schedule and the associated payout/charge for this account to confirm the fee is legitimate, then post a matching fee entry to the internal ledger.

claude-sonnet-5 · triage-v2 · confidence medium

No one has investigated this case yet. Ask Clara to trace it through the record — she cites what she reads, and the thread is shared with every operator on the case.

You’re viewing as a read-only demo visitor. Sign in as an operator to ask Clara — the thread and its citations are fully readable either way.