Project Billing
Project Billing holds a named billing rule with a rule type and its own priced lines: project, category, quantity, price and discount.
What it is for
The screen stores the rule and works out its line amounts. Nothing else reads it: the Project Contract picks its billing rule type from a fixed list and keeps its own billing lines.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Project Billing | The code | Required, and must not already exist |
| Name | What the rule is | Free text |
| Billing Rule | The kind of billing | Unit of Delivery, Milestone or Progress |
| Project Contract | A contract the rule is for | Pick a Project Contract. A reference only |
Lines
| Column | What it means |
|---|---|
| Project | The project |
| Catogery | A category of the project or estimation |
| Quantity, Unit | How much |
| Sequence | The order |
| Price | The price per unit |
| Gross Amount | Quantity x Price, worked out |
| Discount %, Discount Amount | Type either; the other follows |
| Net Amount | Gross Amount - Discount Amount, worked out |
All amounts are rounded to two places.
How to configure it
Nothing to configure. Set the billing on the contract itself.
Scenarios
- A standard milestone plan is reused on many jobs. Keep it here for reference, and type its lines on each contract.
What it is connected to
- Project Contract - where billing is really agreed.
If something looks wrong
- The save is refused on the code. The code is missing or already used.