Loading
Because delivery and billing are separate systems. Somebody reads a project report, decides what is billable, and types it into the accounting system — dropping a line or a rate on the way.
Project invoicing turns delivered work into billable lines: milestones reached, approved billable hours, and expenses coded to the project.
Lines assemble from what the project records as delivered and approved. Rates come from the contract in Flow, not from today's price list, and the draft goes to Books for issue.
A phase completes and forty billable hours sit against it. One invoice carries the milestone at its contracted value and the hours at their rate, each line traceable to the work behind it.
Loop does not issue invoices. It assembles what is billable and hands it over; raising and sending are decisions that belong in Books with the people accountable for them.
Flow holds the contract and its rates, timesheets supply the billable hours, and Books issues the invoice and owns the ledger posting.
Yes, on one invoice, with the fixed element against the milestone.
Drawn down by logged hours, with the balance visible to both sides.
Yes, where you expose it in the portal, before the invoice is issued.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.