|
| 1 | +# How to submit Milestone Evidence and Withdraw Milestones |
| 2 | + |
| 3 | +At this point your vendor smart contract should already be deployed and active.  |
| 4 | + |
| 5 | +Your vendor smart contract commits your project and delivery schedule; milestone name, deliverable, payment date and amount, immutably to the Cardano blockchain. This metadata and any subsequent agreed changes will be publicly available.  |
| 6 | + |
| 7 | +The following instructions will step you through how to submit evidence and withdraw a milestone payment.  |
| 8 | + |
| 9 | +These instructions can only be completed by the credential associated with your vendor smart contract.  |
| 10 | + |
| 11 | +## Step 1: |
| 12 | + |
| 13 | +In your pre-agreed communication channel with the Intersect Delivery Assurance team, vendors should provide a completed Milestone Acceptance Form (MAF) for each individual milestone on or before the **Milestone Completion Date** as set out in your legal contract.  |
| 14 | + |
| 15 | +_**Best practice tip:**_ It is advised to template these MAFs out for each milestone in advance, share them and work on them in transparency with the delivery assurance team. Intersect may be able to provide feedback throughout the process, not just at the end, this is likely to speed up the review and acceptance process.  |
| 16 | + |
| 17 | +The delivery assurance team will review and provide acceptance that the attestation provided in the MAF meets the deliverables and acceptance criteria from your legal contract. |
| 18 | + |
| 19 | +If accepted:  |
| 20 | + |
| 21 | +* The delivery assurance team will host your MAF and provide a link to your completed MAF. This link will be used later when submitting evidence on-chain. Continue to step 2. |
| 22 | + |
| 23 | +(Optionally, if agreed with the delivery assurance team, the vendor may host and provide a link to the completed MAF themselves) |
| 24 | + |
| 25 | +If **not** accepted or a MAF has not been provided by the Milestone Completion date: |
| 26 | + |
| 27 | +* The delivery assurance team will provide feedback as to why the MAF is not acceptable and provide remediation steps for the vendor to compete |
| 28 | +* If a MAF is not provided at all the delivery assurance team will recommend that the current and all future milestones be paused |
| 29 | + |
| 30 | +## Step 2: |
| 31 | + |
| 32 | +Navigate to the Smart Contract Administration Dashboard, URL: [https://treasury.sundae.fi/instances](https://treasury.sundae.fi/instances) and Log In using the wallet/credential that you provided within your legal contract.  |
| 33 | + |
| 34 | +<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcg7hXSC20_Jbfyv2N0dtcJSaogQviglC6OjnAsriAh1UjjIme3LNBQ5Iknpgp3mLUswZhjsguZqvB1XLe5LP082Dyq1_rJxd92t7MAAkRz1q1laS4iHYBJBR_MNn4XWRKMfn9i?key=aqi7BCFOfE-J3aVJptAoVQ" alt=""><figcaption></figcaption></figure> |
| 35 | + |
| 36 | +## Step 3: |
| 37 | + |
| 38 | +Navigate to your vendor smart contract. The ‘Contract Name’ will be similar or an abbreviated version of your legal contract name.  |
| 39 | + |
| 40 | +In some cases where a vendor has multiple successful projects the name may be a combination of all successful project names. Also longer projects may be broken down into smaller smart contracts (the vendor will have one legal contract and multiple smart contracts), in these instances the project names should be agreed in advance. |
| 41 | + |
| 42 | +Smart contracts where your credential has available actions will be highlighted: |
| 43 | + |
| 44 | +* Example of a claimable milestone. ‘Instances’ > ‘Intersect Treasury Reserve Contracts 1’, highlighted below in green |
| 45 | +* Open your vendor smart contract, continue to step 4 |
| 46 | + |
| 47 | +<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdSjbVIGGbsVCrFdvwfB0IsNMgrnLB8RfVJTyISLNnf4Lj3Evu4CfGHU5tW2JqjDleB0tNGGHs8jaCzJaMckWftQb3nwkQZLdbZ5rtGxbk2LEhpkEVITgr29DXM9EU-4F4E2yySBw?key=aqi7BCFOfE-J3aVJptAoVQ" alt=""><figcaption></figcaption></figure> |
| 48 | + |
| 49 | +## Step 4: |
| 50 | + |
| 51 | +Click on the button to ‘Submit Evidence’, highlighted green below. |
| 52 | + |
| 53 | +<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeXZXK7nS0qjYBy26-SZukR_FXW9u5y9eus7GmSTOMAdOjbh72IjXnmE5XTsm64Qc1v_9sdKv8daVvTz2ZLL5Sqdh1OwEnESXyc5SxBh13cngVM-PiCr5SYbGGo1uB0YjjJCA83Ag?key=aqi7BCFOfE-J3aVJptAoVQ" alt=""><figcaption></figcaption></figure> |
| 54 | + |
| 55 | +Completed the pop-up form. |
| 56 | + |
| 57 | +* Milestone: Select the milestone the evidence is supportive of, as in some instances you have multiple milestones which require evidence being submitted |
| 58 | +* Title: Enter an appropriate title for the evidence, you should include the Milestone Number and Name as per your legal contract |
| 59 | +* Evidence URL: Enter the link pre-agreed with the Delivery Assurance team from step 1. This URL will point to your completed Milestone Acceptance Form (MAF) |
| 60 | + |
| 61 | +<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe1E9JvRqi4NknFGF51xmr_5LQtY7N-mPo6HKjIJK4Q2bMZFh2iJucD4dDpCX5szCIBPP_e_lwDyxlcHVhPdpsHHcdRVcEMfsZN2HmFVRREuUyufmsW9i2TwCIg8BqboX-g9JgjIg?key=aqi7BCFOfE-J3aVJptAoVQ" alt=""><figcaption></figcaption></figure> |
| 62 | + |
| 63 | +Once completed click the ‘Submit Evidence’ button. You may be asked to sign a transaction submitting the evidence to on-chain.  |
| 64 | + |
| 65 | +Failure to submit a MAF on or before the Milestone Completion Date to the delivery assurance team, or failure to submit a form at all, may result in the vendor smart contract Payment Date being paused.  |
| 66 | + |
| 67 | +Many organisations are still required to submit and process invoices. Please submit invoices within 5 working days of your Milestone Completion Date as per your legal contract, following the instructions within your contract.  |
| 68 | + |
| 69 | +In certain circumstances failure to submit invoices may also result in your smart contract payment date milestones being paused and ultimately funds may be delayed.  |
| 70 | + |
| 71 | +## Step 5: |
| 72 | + |
| 73 | +Once evidence has been submitted you may select the option to ‘Withdraw All Available Payments’ |
| 74 | + |
| 75 | +<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXesPmDMClzPV-6d67u8tpMCYTnepggzE-knhCnKkUA7WNKoLXS1yZ8Z1cQvnG9b8R-3OXafonORMuFuVKbryeASfqGggnOfaStrWVPH48E5NO6r6TXM4eZDZulA1Y3LfUXy2oSsfQ?key=aqi7BCFOfE-J3aVJptAoVQ" alt=""><figcaption></figcaption></figure> |
| 76 | + |
| 77 | +Follow the actions as prompted to withdraw any milestone payment dates which have matured.  |
| 78 | + |
| 79 | +Note, withdrawing milestones without providing evidence may result in all subsequent milestones being paused.  |
| 80 | + |
| 81 | +**End of Instructions.**  |
| 82 | + |
| 83 | + |
| 84 | + |
| 85 | +Additional Information: |
| 86 | + |
| 87 | +Where practical and possible on-chain smart contracts will be used to manage your proposals treasury funds. The following information will help you understand how smart contracts are used as part of Intersects Administration. |
| 88 | + |
| 89 | +* Smart Contract Dashboard -[ https://treasury.sundae.fi/](https://treasury.sundae.fi/) |
| 90 | +* [Smart Contracts and Cardano budgets blog](https://www.intersectmbo.org/news/%EF%B8%8F-smart-contracts-and-cardano-budgets) |
| 91 | +* [Smart Contracts as part of Intersects Administration Knowledge Base](https://docs.intersectmbo.org/cardano-facilitation-services/cardano-budget/intersect-administration-services/smart-contracts-as-part-of-our-administration) |
| 92 | +* [Treasury Oversight Management Video by SundaeLabs](https://www.youtube.com/watch?v=S6RFKzmAebo) |
0 commit comments