IceBossPro Blog — Ice Delivery Invoicing

Per-Delivery Billing in Ice Invoicing Software

Per-delivery billing is the workhorse model for most ice routes: you charge for exactly what was dropped at each stop, on each visit. It sounds simple, but doing it by hand is where operations bleed money — a bag delivered but not billed, a wholesale tier applied wrong, a ticket lost between the truck and the office. This post digs into how per-delivery billing actually works inside ice delivery invoicing software and why getting it automated pays for the whole platform on its own.

The delivered quantity is the invoice

In per-delivery billing, the number that matters is how much left the truck at that stop. Invoicing software captures that quantity at the point of delivery, in the driver's app, at the moment the ice is unloaded. That single entry does two jobs: it logs the drop as proof of delivery, and it generates the invoice line. There is no paper ticket to transcribe and nothing to reconcile back at the office. When the driver taps that a convenience store took thirty bags of ten-pound ice, an itemized invoice for thirty bags exists before the truck pulls away.

Per-bag pricing and wholesale tiers

Ice is priced by the unit, and the unit price is rarely flat. A small bar pays one rate for a ten-pound bag; a distributor buying pallets pays a lower wholesale rate; block ice and dry ice carry their own prices entirely. Invoicing software lets you set per-product pricing and assign wholesale tiers to accounts, so the correct rate is applied automatically based on who the stop is for and what they took. The driver never has to know the price. They record the quantity and the product; the platform does the math, applies the customer's tier, adds any sales tax, and produces a correct total every time.

Getting paid at or near the door

Per-delivery accounts are the ones where fast payment matters most, because the balance resets every visit. Invoicing software gives you several ways to close the loop immediately. A cash-and-carry stop can be paid at the door and marked collected in the app. An account with a card on file gets charged automatically the moment the delivery is invoiced. A larger buyer can be set to ACH so the charge clears their bank without card fees. Instead of mailing an invoice and waiting, the per-delivery charge is often settled the same day it is delivered.

Proof that ends disputes

Per-delivery billing invites more disputes than recurring billing, because there is a fresh charge on every visit and a customer can always claim they got less than you billed. This is exactly where the software earns its keep. Every per-delivery invoice is tied to a delivery record with a timestamp, the driver who made the drop, the location, and often a signature or photo. When a store owner questions a charge, you open the record and show the proof. The number is not your word against theirs; it is a logged, time-stamped event attached to the invoice itself.

Net terms and account statements for the big buyers

Not every per-delivery account pays at the door. A distributor or a chain buying pallets usually runs on net terms, taking delivery all month and settling on a statement. Per-delivery billing handles this without changing how the driver works: each drop still generates its own itemized invoice at the delivered quantity and wholesale tier, but instead of charging immediately the invoices accrue against the account. At the close of the period the software rolls every drop into one account statement — each delivery, each rate, sales tax, and a running balance — and emails it with a pay link to the customer portal. If the balance goes past its terms, automatic reminders and a late fee keep it moving. So the same per-delivery engine serves both the cash-and-carry bar that pays on the spot and the wholesale account that settles net-30, without you running two different systems.

AR reporting and clean books

Because every per-delivery invoice is tied to a specific stop, driver, product, and rate, the reporting underneath is precise. An accounts-receivable aging report shows exactly which drops are unpaid and how old they are, bucketed by current, thirty, sixty, and ninety days, so nothing quietly slips. You can slice revenue by product to see how ten-pound bags compare to block or dry ice, or by wholesale tier to check that your volume accounts are actually pulling their weight. A QuickBooks sync pushes the invoices and collected payments into your books automatically, and the Stripe payouts reconcile against the invoices they cleared. The per-delivery model generates a lot of small invoices; letting the software file, total, and report on all of them is what keeps that volume from burying your office.

Batch, review, and send

Even with same-day charging, you often want to review a day's worth of per-delivery invoices before they go out or get charged. Invoicing software lets you see every stop's invoice from the route in one batch, spot an obvious error, adjust a quantity if a driver mis-tapped, and then send or charge the whole run at once. It is the control of reviewing before you bill, without the labor of building each invoice from scratch. For how this compares to a manual grid, see our earlier post, Ice Delivery Invoicing Software vs Spreadsheets.