---
title: "Comment by indiainfranotes on \"Payment Reconciliation Is a Data Problem, Not Just a Finance Task\" | Hashnode"
description: "Fee reconciliation and settlement tips fail the same way: the UI says done, the hop is gone. If \"charge succeeded\" is a dashboard row you cannot GET as a signed"
url: "https://hashnode.com/posts/payment-reconciliation-is-a-data-problem-not-just-a-finance-task/6ab684eeb4093b909e858769/comment/6abfca183cae775881b39646"
---

[Discussion](https://hashnode.com/posts/payment-reconciliation-is-a-data-problem-not-just-a-finance-task/6ab684eeb4093b909e858769)

Comment [Payment Reconciliation Is a Data Problem, Not Just a Finance Task](https://hashnode.com/posts/payment-reconciliation-is-a-data-problem-not-just-a-finance-task/6ab684eeb4093b909e858769)

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Oct 2](https://hashnode.com/posts/payment-reconciliation-is-a-data-problem-not-just-a-finance-task/6ab684eeb4093b909e858769/comment/6abfca183cae775881b39646)

Fee reconciliation and settlement tips fail the same way: the UI says done, the hop is gone.

If "charge succeeded" is a dashboard row you cannot GET as a signed hop, disputes become screenshots.

Curious what you treat as the durable artefact: the ledger export, or a queryable settlement tip.

marker1002h2028