Construction milestones and receivables
Connect milestone acceptance, claim terms, holdings and repayment states.
The scenario
ForContractors, project owners, receivables teams and finance operators
Divide a project into foundation, construction and handover milestones, tracking claims for accepted work by issuance unit. Store photos and acceptance documents in business systems and trace the evidence behind issuance.
What this makes visible
See milestone approval, issued rights, holders, funding and redemption states within the same project.
Token and business-data roles
Represented by tokens
Use BondToken classes for terms and nonces for issuance units. Add DebtManager for coupons, principal and claims.
Managed in business systems
Project/milestone IDs, agreements, acceptance documents, invoices, due dates and bank receipts.
Map project, asset or order IDs to chainId, contract address and tokenId where applicable. Link the operation ID to the confirmed transaction so the application can trace the result.
Contract composition
| Contract | Role in this use case |
|---|---|
| BondToken | Track holdings by terms and issuance unit. |
| DebtManager | Manage payment schedules, funding, claims and redemption. |
| Whitelist | Maintain approved participant records. |
Follow each contract for its key operations, SDK and source. Select the components your workflow needs and connect them to business approvals and records.
User and processing flow
Define milestones and terms
Map contractual payment terms for each milestone to classId and nonceId.
Record acceptance
The reviewer checks evidence and records approval. Acceptance decisions remain in the business workflow.
Issue and allocate rights
Issue the approved milestone’s unit and retain holder and operation records.
Reconcile funding and redemption
Track actual receipts separately from token claims/redemption, then reconcile them in the project register.
Operating considerations
Milestone changes
Retain versioned terms and approvals for additional work, rejected acceptance or changed due dates.
Movement of funds
Bank-transfer verification and on-chain funding are separate operations. Define the payment evidence appropriate to the workflow.
Implement this use case
These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.