MSAMM
Back to course

Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 14 · Project Billing: Contracts, Invoice and Revenue Methods

The contract dependency

Lesson 142 of 198 · 2 min

Quick check first. This module needs Enterprise Contracts. If your environment does not have it, you can follow along and you cannot build — and it is better to know that in the first thirty seconds than in lesson six. PROJECT BILLING RUNS THROUGH ENTERPRISE CONTRACTS. NO CONTRACT, NO INVOICE, NO REVENUE. That is the fact clients do not know, and it arrives late on more projects than anything else in this course. Why the design is that way, because it is worth defending rather than just stating. The commercial agreement determines what can be billed, at what price, up to what limit, and how revenue is recognized. Putting those rules on the contract rather than the project is correct — one contract can fund several projects, and one project can be funded by several contracts. Rules on the project could not express either. IF THE CLIENT HAS NOT LICENSED…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 14 · Project Billing: Contracts, Invoice and Revenue Methods

  1. 1The contract dependency
  2. 2Contracts, lines and projects
  3. 3Bill plans and revenue plansFree preview
  4. 4Invoice methods
  5. 5Revenue methods
  6. 6Creating a contract
  7. 7Associating projects and tasks
  8. 8Contract types and approval
  9. 9Proving the association works
  10. 10What breaks
  11. 11Lab: a master agreement, a fixed price, and one task that must not bill