The same event appears twice on one side.

Conclusion

Concluded by ruleset-v2 in run c2f01047, as of 2026-07-02 17:48 UTC.

What matching tried

1. Duplicate sweepTwo Ledger entries cite the same reference `ch_mercadia_0028`, identical amount — the later one appears twice.broke here
2. Resolution ruleEarlier-landed entry kept as primary; this later entry flagged as the duplicate.broke here

The transaction

identity

ledger / mercadia:operating / LED-2026-0028-DUP

type

payment

amount

$85.99

occurred

2026-05-02 19:43 UTC

observed

2026-07-02 17:48 UTC

version

v1 · current

normalized by

ledger-v1

The raw record

{
  "type": "payment",
  "amount": "85.99",
  "status": "posted",
  "account": "mercadia:operating",
  "entryId": "LED-2026-0028-DUP",
  "bookedAt": "2026-05-02T19:43:00.000Z",
  "currency": "USD",
  "reference": "ch_mercadia_0028",
  "valueDate": "2026-05-02",
  "description": "Customer payment — order #1027 (posted twice in error)"
}

The ingestion batch

source

ledger

idempotency key

ledger:file:eee96b5921b04c75a871c7525830c871cbabec9edb4642efbe0a616c1deeb144

landed

2026-07-02 17:48 UTC

status

normalized