Run sheet

1The desks

Only the financing desk needs an account. The two confirmation pages are reached by link, by people who will never sign up for anything.

2The run

Everything below happens on the financing desk except the two confirmations, which happen in somebody else's inbox.

1. 1
   Sign in/receivables/login?next=/receivables/desk

   Signs you in as the financier and opens the desk.
2. 2
   Record the deal/verify/desk

   First card. Client, debtor, invoice no, amount are required. Everything else is whatever the contract says. "+ Add a field" for anything we did not anticipate.
3. 3
   Attach the papers/verify/desk

   PDF or photo, 5 MB each, as many as needed. Fingerprinted the moment they land.
4. 4
   Ask the debtor to confirm/verify/desk

   Creates a single-use link and copies it. Send it to the debtor. Send a second one to a different person there if the amount warrants it.
5. 5
   Debtor answers/verify/authenticate

   No account. They read the papers, type their own reference from their records, tick four separate boxes, and confirm — or say it is not theirs.
6. 6
   Advance, and register the claim/verify/desk

   The headroom banner and the debtor confirmation are both on screen before the decision.
7. 7
   Ask the client to confirm receipt/verify/desk

   "Ask client" on the claim row. Until he answers, the claim reads "not confirmed".
8. 8
   Client confirms the money arrived/verify/countersign

   No account. This is what stops a lender registering an advance he never made.
9. 9
   A second lender checks the ID/verify/registry

   No account. Headroom is gone, so the check shows the receivable fully financed before a second advance. This is the demo moment.
10. 10
    Debtor pays; mark the claim settled/verify/desk

    Headroom returns. No old claim outlives the payment.

3Say these before he finds them

Naming the gaps first is what earned the co-design in the first place. Do it again.

Signing is the platform key, not each party.

A confirmation proves "someone holding this link asserted it", not "the debtor asserted it". Party-level keys are not built.

Any signed-in account can look up any receivable by ID.

The ID is unguessable and never enumerable, but there is no authorized-financier list.

An unconfirmed claim still consumes headroom.

So a lender could register an advance he never made and block others until someone notices. The desk now shows "not confirmed" — but the number does not move.

The duplicate check only sees records at Almstins, at the same amount.

It compares the same debtor with the debtor’s reference, or with the client and invoice number, at the same amount and currency, and warns while the invoice is entered and again before a claim. A different amount or currency, or a debtor named differently, does not match. A client named differently, or a different invoice number, matches only through the same debtor reference. Records kept outside Almstins are not compared. It warns; the lender decides.

The terms of the advance are not recorded.

The claim captures an amount, not the rate, fee, or what it costs the client.

The registry only sees claims registered in it.

A prior undisclosed assignment, or a floating charge over all receivables, is invisible.

4Questions for him

This is the payload. If the call runs short, cut the demo, not these.

Do you contact the debtor as a matter of course?

Or would some clients walk if you did? The whole product assumes you can ask the paying company to confirm. If half your book is confidential discounting, that assumption is wrong and we need to know today.

What is your standard of proof?

What evidence clears your bar to advance against this? Name the evidence you need, not the evidence we happen to produce.

Would you advance against this one?

At what amount, on what basis, and what specifically would stop you or reprice it?

Do you buy the invoice, or lend against it?

This settles our vocabulary, and it decides whether "repaid" is even the right event to record.

Should an unconfirmed advance expire?

Right now a registered claim consumes the headroom whether or not your client ever confirms the money arrived. That protects you the moment you advance, but it also means a lender could block an invoice with a claim he never funded. Should it lapse if nobody confirms, and in how long?

Then, as time allows:

Do you issue a written offer the client signs?

Or is the advance agreed in person and recorded after? This decides whether the desk needs an offer step, and where the interest and fees live. Right now the record holds an amount and nothing about what it costs your client.

Do you take a director’s guarantee?

If a guarantee is what makes deals fundable, it belongs in the core evidence set, not as a bolt-on.

Are your promissory notes witnessed as a matter of course?

If they already are, recording the witness is capturing a field you have, not a new feature.

Will debtors give you their own PO or contract number?

The desk now asks for it up front, and the duplicate check compares on it. It is the only identifier your client does not control, so it is the strongest match we have. Is it realistic to expect it on every deal?

How long must you keep the paperwork?

We delete the contract within a day of the last person answering, and keep only its fingerprint. If your obligations require you to hold it longer, say so — that is our design, not a law.

How do you protect against a prior undisclosed assignment today?

How do you handle an adverse or disputed claim today?

Does the National Collateral Registry already cover receivables per-invoice?

Searchable and timely enough to rely on when advancing? Are we a complement or filling a gap?

Would your firm register every claim if checking required it?

Contribute-to-search, the way credit bureaus solved coverage.

What should the barrier to entry be for a financier account?

5What to capture

Time per step, against how he does the same receivable today.

Calls, emails, a buyer confirmation letter. That comparison is the business case.

What a second financier can verify independently.

Without taking anyone's word for anything, including ours.

Where it misses his bar.

That list is the actual output of the session, and it sets the build order.