Before you start
- Use a Lender identity authorized for the assignment operations. The service derives the tenant from that validated identity; you do not supply a tenant in a request.
- Register the receiving fund before creating a set. The registration holds its administrator details, cession rate, eligibility limits, document mode, and the layout used for its offer file.
- Treat each external fact as evidence. Sending a file, receiving a remessa, signing a term, paying, transferring, and accepting are separate facts with separate controls.
The assignment flow
1
Register the fund
Create or update the assignment-fund registration. Its configuration supplies the cession rate and the concentration and repeated-cut rules used when Lender evaluates a pool. The receiving fund’s document and registry settings also determine the later document and acceptance paths.
2
Review eligible receivables
Read the fund-scoped candidate pool. Lender evaluates each candidate against the fund configuration and the assignment context, returning an eligibility verdict rather than silently dropping ineligible receivables. When it cannot read a required source, it reports that condition instead of treating the constraint as satisfied.
3
Assemble and score a draft set
Create a draft from the receivables you selected. Lender freezes the set’s composition and the fund settings it needs for that journey. Score the draft against the fund rule before approval; an unapproved set can be re-scored.
4
Approve the set
Approval re-reads the relevant receivable state before it records the decision. A receivable that changed since assembly can leave the set or be repriced, so review the approval result rather than assuming the draft survives unchanged.
5
Exchange the fund files
Download the offer file only after approval, then record that it was sent. Ingest the fund administrator’s remessa against that same set; Lender reconciles the file with the offered composition and records the outcome.
6
Record the completion facts
Record the endorsement term and the externally observed payment, transfer, and acceptance facts as they occur. Lender enforces the lifecycle transition for each fact. An accepted receivable is removed from the active holding path only when the required acceptance processing succeeds.
Documents and exceptions
Lender can produce a receivable dossier from the facts it holds. The first materialization freezes the evidence snapshot used for that dossier, so a later retrieval represents the same recorded evidence. The journey can also surface exception cases, such as a repeated cut, a remessa conflict or divergence, a receivable that cannot be valued, or a derecognition that cannot be posted. Resolve those cases through the assignment exception flow; do not substitute a lifecycle fact for the missing resolution.
Operational guardrails
- A set is not a completed cession. Draft, eligibility, approval, offer delivery, remessa, term, payment, transfer, and acceptance are distinct lifecycle steps.
- Fund changes do not rewrite a set already in progress. Lender freezes the relevant fund configuration at set assembly.
- Approval is intentionally defensive. It validates the current receivable state before a fund receives an offer.
- Acceptance is money-path sensitive. If Lender cannot complete its required processing, it refuses the acceptance instead of marking the receivable as sold.
Next steps
Lender REST API
Start from the service API and the generated operation reference.
Accounting and accrual runs
See how Lender keeps durable accounting work separate from inline requests.