How to handle vendor payment based on task completion in Aurora?
Aurora provides flexibility so the client can determine the best way to support vendor payment based on task completion. There are many options: • Build the same way one did previously to implementing critical chain. For example, if a client had a billing method based on the completion of tasks in Primavera, one could use this same task-completion methodology and report the project to Aurora, Aurora would interface back to Primavera with information on what has been completed, and billing would continue as normal. • The ability to utilize the completion of major or all Critical Chain tasks. E.g. if the vendor is billing based on Critical Chain, then the Critical Chain can be used on task-completions to bill all the feeder tasks intermittently between the last billing. • The last option is to be able to bill all tasks. This may be a propos when there are long feeder chains that occur before the first critical chain task even occurs, so there may be extensive delays to payment if one use
Related Questions
- Is the $25,000 threshold for reporting detailed information about vendor payments based on a single payment or based on the cumulative payments to a vender during a reporting period?
- If the critical chain changes during execution, how does Aurora handle buffers, CC completion and task prioritization?
- Can I receive payment into different vendor accounts based on geography?
