Software delivery and payment milestones
Connect deliverable acceptance to milestone payments and claims.
The scenario
ForSoftware service providers, clients and project managers
Track requirements, implementation and acceptance testing as separate milestones, recording claims and approvals for accepted deliverables.
What this makes visible
Trace which deliverables were accepted and which claims were issued or paid from each milestone.
Token and business-data roles
Represented by tokens
Distinguish contractual terms and issuance units with BondToken, and map payment/redemption to DebtManager. Reference deliverable files in business storage.
Managed in business systems
Project/milestone IDs, deliverable versions, reviewers, terms, invoices and payment records.
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 | Manage milestone terms and issuance units. |
| DebtManager | Track payment schedules, claims and redemption. |
| AgreementManager | Record bilateral offers and acceptance where appropriate. |
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
Agree on milestones
Define deliverables, acceptance criteria, deadlines and fees per milestone.
Accept a deliverable
Record the accepted version and reviewer, then identify the issuance target.
Allocate the claim
Issue rights under the agreed terms and link them to the invoice register.
Reconcile payment
Reconcile funding, claims and redemption, and list unresolved milestones.
Operating considerations
Change requests
Record agreed versions and approvals for additional work or changed acceptance criteria, alongside amounts.
Completion criteria
Display delivery, acceptance and payment as distinct states so operators can identify progress.
Implement this use case
These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.