Referral Revenue Ledger
A referral revenue ledger is the record that exists when work leaves a business rather than entering it. Where an enquiry is passed to another provider — because of capacity, jurisdiction, scope or conflict — the outbound relationship produces expected income but opens no delivery record, so the primary system of record never learns about it. A referral revenue ledger gives that relationship an object: counterparty, expected fee, agreement reference, status and last-contact date. Without one, the revenue line can only be reconstructed from memory and correspondence.
Definition
Businesses that decline work still route it somewhere. In a system landscape built around a delivery record — a matter, a job, a policy, a chart — declining work means no delivery record is created, so the outbound relationship has no home. A referral revenue ledger is a deliberately separate object type capturing what the delivery system cannot: who the work went to, what was agreed, what income is expected, what state the relationship is in, and how long it has been in that state. It is not an invoice and not a pipeline stage; it is an aging register for revenue that will arrive from outside.
Why it matters
Where outbound referral is handled conversationally, the only trace is an email thread and a calendar entry. Neither can be aged, assigned or reconciled against an incoming payment. When the counterparty resolves the work, nothing in the referring business surfaces the event, so collection depends on someone remembering. Giving the relationship a record turns a memory-based revenue line into a reconcilable one, and it produces the list needed to compare expected income against payments actually received.