Loading
Because the invoice is usually re-keyed. Somebody reads a project report, decides what is billable and types it in, and a dropped discount or a missed milestone surfaces when the customer queries it, or never.
An invoice in Books is assembled from lines that already exist — delivered work, approved expenses, contracted milestones — rather than typed from a delivery note. Every line keeps a link back to the thing it bills.
Lines pull from Loop for delivered work and from approved expense claims, priced at the catalogue rate in force on the quote date. Payment terms come from the contract rather than a system default.
A February milestone slips to March. The work is recorded delivered in March, so it bills in March at February's agreed rate, and the variance shows against the original schedule instead of quietly disappearing.
It will not issue an invoice on its own. The schedule drafts automatically; sending is a decision, on the rule that where a customer would find the error, somebody should see it first.
Flow holds the contract and the agreed rate, Loop the delivery record, Desk any out-of-contract support time. The posting reaches the general ledger and the aging report the moment the invoice is issued.
Not the sent document. You raise a credit note against it, which keeps the numbering and the audit trail intact — which is what an auditor expects to see.
Yes. Bill a percentage or a fixed amount, and the remainder stays on the schedule against the same milestone.
Yes, with the rate stamped at issue. The ledger keeps both the transaction and the base currency amount.
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.