The Hierarchy of a Claim vs the Debtor

Receeve is built with the concept of a claim, and account, and a debtor.

Each one lives independently of each other, but is interconnected. At the end of the day, we see it that the account is the entity that glues it all together.

Now each claim lives its own life running through the process. There are a few reasons for this. There are a mixture of clients who can only handle and only need that each claim is its own living entity. And many of the existing systems we would interact with have this restriction. FICO, for example, has this type of restriction in it.

But, we knew in the long term that we would want to tackle the overall account with multiple claims, while keeping the ability to manage the claims as independent things.

So now there is an account layer or hierarchy that contains the claims in them. Now, we also separated out the debtor as well. The claims come with the data for the person/company, and we get a couple of nice benefits for that. If the address or contact information changes, then that creation of the claim gives us an automatic way to update it. And the old claim keeps a record of the old address. It makes it easier to compare. It gives us the ability to create the claim, and note the conflict for resolution. And, the separation allows us one other thing. There are instances where it could be legally possible to transfer the debt from one party to another.