[gopher_space]

> a line in a csv about a debt that is easily challenged and hard to document when challenged

From the perspective of someone who's dealt with finance and exports most of their life, CSV files of this nature are more of a gentleman's agreement between engineers (who all died years ago) than a statement of fact. I don't know how you'd convince a judge that your csv file is error-free when the transaction process itself is full of clawbacks due to all the buggy data and creaky code.

[toast0]

In theory, you might be able to use the csv entry as a hook to trace back both the original lender and ask them for their documentation of debt as well as the chain of custody that leads you to be authorized to collect it; but most likely it's going to be default judgements because nobody showed up. Default judgements are more of a punishment for not showing up than a statement of likely results on the merits of the case.

[gopher_space]

> In theory, you might be able to use the csv entry as a hook to trace back both the original lender and ask them for their documentation of debt as well as the chain of custody

In practice, you'll have created a billion-dollar SaaS corporation and helped write legislation. The fundamental issue is that data quality and handling practices mean this information will always be "truthy". At a base level your input comes from an office clerk who's medium-engaged in the process and who's asked for quantity over quality.

The entire financial network (imho, from my perspective, etc etc) is "best effort" and mutual agreements. Nobody involved wants to cast a string to a legal agreement.