Project Management – Billing Plan vs Billings (Conceptual Overview)

Project Management – Billing Plan vs Billings (Conceptual Overview)

4 min. read
Last update: 16.06.2026

Purpose

This article explains the conceptual and operational relationship between the Project Billing Plan and Billings.

Although these features are closely related, they serve different purposes in the project-to-cash lifecycle:

• Billing Plan defines what should be billed and when (planning & control)
• Billings manages how billing is executed and processed (operational execution)

Understanding this separation is essential for proper financial governance, automation, and traceability.

High-Level Concept

In short:

💡 The Billing Plan (within Project) - plans Billing.
       Billings - execute Billing.

The Billing Lifecycle at a Glance

1. Billing conditions are defined centrally in the Control Center.
2. Billing events are planned in the Project Billing Plan.
3. Based on the configured Issue Notification Lead Time, the system generates a notification when a billing event is approaching.
4. If all required conditions are met, users can create a Billing Record.
5. Billing execution is managed in the Billings module.
6. Billing status feeds back into project financials and KPIs.

Billing Plan: Planning & Financial Control

What the Billing Plan Is

The Billing Plan belongs to a project and represents a financial schedule of future billing events.

It answers questions such as:

• When should this project be billed?
• For how much?
• Under which contractual conditions?

What the Billing Plan Contains

Each Billing Plan entry typically defines:

• Planned issue date
• Planned amount
• SOW percentage
• Holdback amount or percentage
• Billing description / document identifier

These records are not billing documents.

They are planned billing commitments used for forecasting and financial control.

Control Center: Billing Rules & Automation

Before billing execution can occur, billing rules are configured centrally.

Configured under:

💡 Operations Management → Billings → Configuration

These rules define:

• Which project statuses allow billing creation
• Which timesheet statuses allow billing creation
• Issue notification lead time
• Conditions required to create billing records
• Allowed billing status transitions

These rules ensure that billing remains:

• Consistent
• Auditable
• Aligned with operational and contractual constraints

Billing Notifications & Billing Record Creation

What Happens Before the Planned Issue Date

When the configured Issue Notification Lead Time is reached, the system evaluates the planned billing event and generates a notification.

The system verifies:

• Billing Plan validity
• Project status
• Timesheet status (if applicable)
• Control Center configuration rules

If all conditions are satisfied, users are allowed to create a Billing Record.

The Billing Record then becomes available in the Billings module for operational processing.

This approach ensures:

• Upcoming billings are visible in advance
• Billing creation follows defined governance rules
• Project and finance teams maintain full traceability between planning and execution

Billings: Execution & Financial Processing

What the Billings Module Is

The Billings feature inside the Operations module is the operational execution layer where billing documents are:

• Created
• Reviewed
• Approved
• Issued
• Cancelled or closed

This is where financial execution and control take place.

Typical Billing Status Flow

Billing documents typically progress through stages such as:

• Worksheet (Draft)
• Submitted
• Validated
• Issued
• Cancelled / Closed

The exact lifecycle depends on the system configuration.

Relationship Between Billing Plan and Billings

A single Billing Plan entry will typically result in one Billing Record.

However, execution status always resides in Billings, not in the project.

Financial Traceability

This separation ensures:

• Clear audit trails
• Accurate revenue recognition
• Controlled billing approval processes
• Consistent reporting

Project users:

Plan billing within the project.

Finance and operational users:

Execute / Validate billing in Billings.

Both views remain synchronised throughout the lifecycle.

Common Misconceptions

"If I create a Billing Plan, I already billed the customer."

❌ Incorrect — you only planned the billing.

"Billing records are automatically created on the planned date."

❌ Incorrect — the system generates notifications and allows billing creation only when the configured conditions are satisfied.

"Billing Plan and Billings are the same thing."

❌ Incorrect — they support different phases of the billing lifecycle.

Best Practices

• Define the Billing Plan early in the project lifecycle.
• Validate billing rules in the Control Center.
• Monitor upcoming billing notifications regularly.
• Use holdbacks to manage delivery risk.
• Create Billing Records only when all prerequisites have been fulfilled.
• Manage approvals and issuance exclusively in the Billings module.

Summary

• Billing Plan = financial planning and scheduling
• Billings = financial execution and control
• Control Center - rules govern billing behaviour
• Notifications - bridge planning and execution
• Billing Records can only be created when all required conditions are met

This design ensures scalability, compliance, governance, and financial accuracy.

Related Articles

Project Management – Projects (Overview)
Project Management – Billing Plan
Project Management – Commercials
Operations Management – Billings
Operations Management – Billing Configuration
Project Management – Track Project Progress & KPIs