Customer Invoicing Process Template
Every drafted invoice checked against its own contract or PO before the run ships, and every deduction logged whether or not it got a credit memo.
Free download · No account needed
Billing Calendar
[Company] — invoice line checked against its own contract before the run ships
The rate card is a fallback, not a default. Every drafted line is checked against the contract or PO first, and the two only need to differ once for the run to go out wrong.
| Customer | Contract or PO | Item | Rate used to bill | Contract rate | Variance | Status |
|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — |
| — | — | — | — | — | — | — |
| — | — | — | — | — | — | — |
| Lines checked | — | — | — | — | — | — |
Two ways a line goes wrong, and both look correct from inside the invoice
| Overbilled | The rate card was used where the contract carries a lower negotiated rate |
| Underbilled | An escalator or volume tier took effect and the invoice still used the prior rate |
Only the contract or PO knows which rate is actually current. A rate-card check can never catch either error, because the rate card is the thing that is wrong.
Most invoicing templates generate the bill from a price list or last month's file, then wait for the customer to flag anything wrong. Stonefield Industrial Supply checked 58 drafted invoices against the purchase orders and contracts behind them first. Eleven did not match. Seven were priced at the rate card instead of the negotiated rate, overbilling seven customers by 17,452.50 combined. Four were still billed at last year's rate after a volume escalator took effect, underbilling by 1,648.00. Sent as drafted, the run misstates 19,100.50 across those eleven lines.
A credit memo is something the seller decides to issue, so it carries an approval chain, a reason code and a total that shows up in a report. A deduction the customer just takes is not. Uniform Commercial Code section 2-717 lets a buyer who has notified the seller deduct damages straight from the price still owed, with no credit memo required. Stonefield's customers used that right 17 times over six months, for 32,360.00 against 14 formal memos worth only 21,380.00. Informal deductions ran 1.51 times the formal total.
One customer, Foundry Row Logistics, holds 76.1 percent of every informal dollar. Two of its nine deductions arrived more than 60 days after delivery, despite each carrying a stated reason. Section 2-607(3)(a) bars a remedy the buyer never raised within a reasonable time of discovering it, a defense that only exists once someone has dated the discovery. The Billing Calendar ties every invoice to the contracts scored in the revenue recognition policy pack. The Dispute Log feeds that population to the ASC 606 contract memo whenever one agreement needs its own conclusion.
What's in the pack
Billing Calendar sheet
Every contracted line checked against the PO or contract rate before the run ships, not after a customer disputes the total.
Dispute Log sheet
Every deduction logged the day it surfaces, formal credit memo or a bare short-pay, with the delivery date recorded next to it.
Credit Issued Trend sheet
Formal memos and informal deductions charted side by side each month, so a customer quietly taking the same amount every quarter stands out.
Billing Procedure doc
The order of truth for a rate: the signed contract or PO first, the rate card only for a sale that has neither.
Revenue Leakage Note doc
Why an informal deduction earns its own line instead of hiding inside accounts receivable, with the UCC provision that makes it a buyer's real right.
Dispute Resolution Process doc
How a claim gets investigated and closed, credit memo, rebill, or write-off, and the clock that UCC notice timing starts running on.
Credit Memo Policy doc
Approval thresholds, required fields and the reason codes a memo needs before it can reduce what a customer still owes.
Space rule
Every invoice ties to its contract line. Where none exists, the row says so instead of defaulting to the rate card unnoticed.
How to use it
- 1
Open in River, or download it
Open the pack in River and let the agent build it from your own contracts and invoice history, or download the blank Word and CSV files instantly with no account.
- 2
Send the contracts and invoices
Signed contracts, purchase orders, the invoices already drafted for this run, and however disputes get raised today: email, a customer portal, or a note on a remittance.
- 3
Validate before the run ships
Every drafted invoice checked against its own contract line first, so a rate-card mismatch gets fixed before it reaches the customer, not after.
- 4
Log, trend, and act
Every deduction lands on the Dispute Log the day it surfaces. The Credit Issued Trend shows whose informal share is climbing, the question the ARR bridge asks when a committed dollar never lands.
Frequently asked questions
Is this template free?
Yes, all of it. Word documents and CSV sheets, no signup, no card. Edit with AI is a separate optional route for anyone who would rather hand over a folder of contracts and past invoices than retype one. Everything else River publishes sits in the template library.
Why validate against the contract instead of the rate card?
Because the rate card is what a system remembers, and a system only updates when someone tells it to. An escalator or a committed-volume tier lives in the signed paper first, the same paper a revenue timing review would have priced before signature. Checking the invoice against it catches the gap before the customer does.
What counts as an informal deduction?
Any amount a customer keeps without a credit memo: a short-pay against an invoice, a deduction taken on a remittance, a chargeback with no paperwork behind it. UCC section 2-717 gives a notifying buyer the right to do this, so the deduction is legitimate. What is missing is a seller who logged it the same day.
Does logging a deduction mean the seller has accepted it?
No. Logging only starts the clock and creates the record. The Dispute Resolution Process routes every entry to a credit memo, a rebill, or a write-off, and a claim that never resolves still has to move through the bad debt and write-off pack rather than sit open.
What if a customer has no signed contract at all?
Then the rate card is the correct source, and the Billing Calendar says so instead of leaving the column blank. The gap only matters once a PO or an order form exists, because that is the document the monthly close will expect the invoice to match.
What format are the downloaded files?
Four .docx documents covering the procedure, the dispute process, the credit memo policy and the leakage note, plus three .csv sheets, zipped into one file. They open natively in Word, Pages, Google Docs, Excel, Numbers and Sheets.
Bill against the contract, not the rate card
Download the blank pack as Word and CSV files, or open this exact pack in River and let the agent check your own invoices against your own contracts.
Edit with AI