Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 14 · Project Billing: Contracts, Invoice and Revenue Methods
What breaks
Lesson 151 of 198 · 2 min
"This cost will not bill." Check in this order. One. Is the project associated with a contract line? Two. Is the SPECIFIC TASK associated — or is it excluded? Three. Is the contract approved and active on the transaction date? Four. Is there a bill plan on that contract line? Five. Has a hard limit been reached? Six. Is the cost marked billable — or was it adjusted to non-billable? Then eight cases. One. "The invoice run produced nothing." Contract not approved, or no project association. Two. "Half the project is billing and half is not." Task-level association. Working exactly as designed, and usually correctly. Three. "Billing stopped mid-month." Hard limit reached. Working as configured — somebody needs to raise a change order, which is a commercial action rather than a support ticket. Four. "Revenue and invoice amounts do not match, and Finance is alarmed." THEY ARE NOT MEANT TO.…
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.
In this module: Module 14 · Project Billing: Contracts, Invoice and Revenue Methods
- 1The contract dependency
- 2Contracts, lines and projects
- 3Bill plans and revenue plansFree preview
- 4Invoice methods
- 5Revenue methods
- 6Creating a contract
- 7Associating projects and tasks
- 8Contract types and approval
- 9Proving the association works
- 10What breaks
- 11Lab: a master agreement, a fixed price, and one task that must not bill