The job of this console
Attach a plan, keep it aligned with the contract, and let invoices flow — do not type the same amount twice.
Finance · Billing
Billing Plans
How a contract will be billed over time — plans on PurchaseOrder / project, not the invoice register itself.
Scroll to Flowcharts. Scenario: Attach a billing plan to a contract.
Bill schedule
When the contract turns into invoices
Billing plans schedule invoices against a PO or project. The invoice list remains the bill register.
Finance → Billing plans
Route
/finance/billing-plans
Org flag billingPlansEnabled
Finance Manager · Admin
Seat at the table
Finance managers and admins. Delivery PMs see project financials, not always this editor.
The working rhythm
Open plan, attach PO/project, set dates, confirm invoice drafts.
Moments that bring you here
Milestone billing. Monthly retainers. A contract change. Before first invoice.
ⓘ
Schedule, not the bill
Invoice is the document. Credit notes adjust bills. Recognition is a sibling.
Flowcharts
1 — Plan then invoice
Set the schedule, let invoices be created from it.
flowchart TD
A[Open Billing plans] --> B[Select PO / project]
B --> C[Set schedule]
C --> D[Invoices generate / match]
D --> E[Do not double-key]
- 1OpenFinance → Billing plans.
- 2AttachPO or project.
- 3ScheduleMilestones or cycle.
- 4BillsInvoice register.
Overview
Billing plans describe when to bill. Invoices are the documents. Recognition may follow a related policy.
How to use
1. One plan per contract intent
Do not fork silently.
2. Invoices win as bills
Plan is the schedule.
3. Change control
Altering a live plan mid-invoice needs care.