Clients and debtors
- Client (id prefix
C.) - a business whose receivables are managed on the Quiddly platform. Quiddly’s customer (for example a bank or a debt-collection agency) onboards and manages its own clients; Quiddly does not manage them. - Debtor (id prefix
D.) - the party who owes money. Can be a person or a company.
Invoices, payment matchings, enforcement actions, and business loans always
sit on the client/debtor axis. Most “list” endpoints accept
clientId and debtorId filters.
Debtor types
Section titled “Debtor types”The same real-world party is represented at a few different levels:
- Client debtor (
Debtor, id prefixD.) - the debtor as registered under a single client, unique per client and customer number. This is the record you look up and update; it holds the client-specific identity, address, and contact data. - System debtor (
SystemDebtor) - the tenant-wide view of a debtor, keyed byidentificationNumberacross all clients. It carries the shared credit/insurance limits, segment, and SNI used for credit decisions, so the same party seen by two clients shares one system debtor. - Invoice debtor (
InvoiceDebtor) - the debtor snapshot captured on a specific invoice (name and addresses as stated at issue time). It is tied to that invoice and does not change if the client debtor is later edited. - System debtor (internal) (
SystemDebtorInternal) - an internal grouping that links a debtor’s records by an internal identification number; mostly used by Quiddly’s own processing and not something integrations create.
See Manage Debtors for how debtors are created and updated.
Service accounts created by a client user are bound to that client; they cannot see another client’s debtors. System/Admin users can.