Bulk Maintenance Billing Proposal
One run bills maintenance for every unit of a property that is on a sales agreement. Save makes one Maintenance Billing Proposal per agreement, and each of those posts its own customer invoice.
What it is for
The run looks at every unit of the property that has a sales agreement and every maintenance line that applies to it on the Billing Proposal Date (matching category, type, sub type, Unit No and Phase where the line sets them), and bills each period not yet billed. Each agreement gets its own Maintenance Billing Proposal, dated the run's date, with every line ticked, and each posts a customer invoice.
The one rule people get wrong: the run screen itself has no lines to check. Everything it makes is on the maintenance billing proposals it creates; review them there.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Transaction | The run's number | Required |
| Billing Proposal Date | Bill up to this date | Required |
| Project | The project | Required |
| Property | The property | Required |
How to configure it
As for Maintenance Billing Proposal.
Scenarios
- First of the month: bill every owner of the tower. One run for the property, dated the end of the period.
What it is connected to
- Maintenance Pricing Agreement gives the rates.
- Maintenance Billing Proposal receives one proposal per agreement.
If something looks wrong
- "No Billing Found". Nothing is due for any unit of the property on that date.
- A message from Maintenance Billing Proposal (journal, customer payment method or term). One proposal could not be saved, and the whole run stops. Fix the cause and run again.