Software delivery and payment milestones
https://docs.hazbase.com/en/use-cases/it-development-token/deep-dive/

USE CASES
 ← All use cases Software delivery and payment milestones
 Connect deliverable acceptance to milestone payments and claims.
 Receivables & participation Example architecture 
 The scenario
 For Software 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
 1 Agree on milestones
 Define deliverables, acceptance criteria, deadlines and fees per milestone.

 2 Accept a deliverable
 Record the accepted version and reviewer, then identify the issuance target.

 3 Allocate the claim
 Issue rights under the agreed terms and link them to the invoice register.

 4 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.

 Review approvals, reconciliation and recovery 
 Implement this use case
 These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.
 Debt & asset finance
 Model distinct rights and connect repayment, distributions and records.
 Explore the implementation Evidence & disclosure
 Combine metadata, credentials and zero-knowledge proofs.
 Explore the implementation 
 Start with a sample Discuss an integration 

 Related use cases
 Construction milestones and receivables Participation in urban infrastructure projects 
 ← Back to all use cases