There are two common ways to account for parcel spend, and they differ mainly in when the money moves and where the matching work lands. With carrier invoicing you ship first, receive a bill later, and reconcile that bill against what you expected to pay. With a prepaid ledger you fund a balance first, each label debits it at purchase, and month-end is a matter of tying deposits to debits. Neither is better in general: the invoice model is the right one for shippers on their own carrier contracts, and the prepaid model suits teams that buy labels through a platform account.

What is carrier invoice reconciliation?

Carrier invoice reconciliation is the process of matching each line on a carrier bill to a shipment you actually sent and a price you agreed to pay. The carrier bills your account after the parcels move, and the invoice is the first document that states the final charge for each one.

The work has three parts. First, confirm that every tracking number on the invoice belongs to you and appears once. Second, compare the billed amount to the amount your shipping system quoted or your contract implies. Third, code each charge to the right customer, department, or order so it lands in the correct general ledger account.

The second part is where the time goes. A billed amount can differ from the quote because the carrier measured a different weight or size, because a charge was added after pickup, or because a contract term was applied differently than you expected. Each difference is either accepted, disputed with the carrier, or passed on to a customer, and someone has to decide which.

What is a prepaid ledger?

A prepaid ledger is a running record of a balance you fund in advance and spend one label at a time. You add money to a wallet, every label purchase debits the quoted amount on the date it was bought, and any later adjustment posts as its own entry.

The accounting document is the ledger rather than an invoice. Each entry has a date, an amount, and whatever reference you attached to the shipment, such as a purchase order or sales order number. If you set that reference deliberately, the ledger export already carries the coding that an invoice process has to add afterward. Our post on allocating parcel costs by customer covers how to structure it.

Reconciliation still exists in this model. It is simply a different exercise: deposits in your bank records should equal the top-ups in the ledger, and top-ups minus debits should equal the closing balance.

How do the two models compare?

They compare on timing, document, and effort, and the table below lays out the practical differences.

Question	Carrier invoice model	Prepaid ledger model
When does cash leave?	After shipping, on the invoice due date	Before shipping, when the balance is funded
What is the source document?	The carrier invoice	The ledger export plus funding receipts
When is the final cost known?	When the invoice arrives	At purchase, apart from later adjustments
Where do adjustments appear?	As lines or revisions on a later invoice	As separate dated ledger entries
Who holds the carrier relationship?	You do, under your own contract	The platform does
What needs approval?	Each invoice, through accounts payable	Each top-up, or a standing funding rule
Main month-end task	Accrue unbilled shipments, match billed ones	Tie deposits and debits to the balance
Main risk	Paying for errors nobody caught	Cash sitting idle in a balance

Two rows deserve a closer look. Under invoicing, shipments sent in the last days of a period are usually not billed yet, so finance has to accrue an estimate and true it up later. Under prepayment, the unspent balance is not an expense at all until labels are bought. One possible approach is to record it as a prepaid asset and expense each debit as it happens, but confirm with your accountant how to treat it in your books.

When is the invoice model the right choice?

The invoice model is the right choice whenever you ship on your own carrier contract, because the invoice is the only place your negotiated terms are actually applied and can be checked.

If your company has negotiated rates, the discount structure lives in an agreement between you and the carrier. Checking that the agreement is honored means reading the bill. A prepaid platform account does not replace that, since it uses the platform's rates and not yours.

Invoicing also fits well when:

You need payment terms. Paying in arrears keeps cash in the business longer, and for large parcel budgets that matters to treasury.
Your accounts payable process is built around three-way matching and approval workflows, and auditors expect to see a vendor invoice for each expense.
You have enough volume to justify dedicated audit effort or software, so the matching work is worth the effort. Our guide to parcel spend management describes what that program looks like.
You ship freight as well as parcels and want one payables process for both.

The cost of the model is labor and delay. Someone has to do the matching, and the true cost of a shipment is not known until days or weeks after it leaves.

When does a prepaid ledger fit better?

A prepaid ledger fits better when you do not hold carrier contracts and want the cost of each shipment recorded at the moment it is created.

Typical cases are a distributor or manufacturer whose parcel volume is real but below the level where a negotiated contract makes sense, a business unit or branch that ships outside the corporate contract, or a team that needs several carriers without opening and managing an account with each. In these situations there is no negotiated rate to audit, so the invoice matching step has little to verify.

The tradeoffs are worth stating plainly. You pay before you ship, so the balance is working capital you have committed. You depend on the platform's rates. And you need a funding routine, either a person who tops up on a schedule or a rule that someone has approved, so that a low balance never stops the shipping dock.

What does month-end look like in each model?

Month-end under invoicing is an accrual and matching exercise, while under prepayment it is a three-number tie-out. The figures below are a hypothetical example, invented for illustration only.

Suppose a wholesaler ships 1,000 parcels in a month and its shipping system quoted $12,400 in total.

Invoice model. The carrier invoices for that month arrive over the following weeks and total $12,910. The $510 difference has to be explained line by line:

38 parcels billed at a higher weight or size than quoted: $304.
12 parcels with a charge added after pickup: $156.
2 tracking numbers billed twice: $50.

Finance accepts the first two groups after spot checks, disputes the $50 in duplicates, and recodes the $460 of accepted adjustments to the orders that caused them. At month-end close, before all invoices had arrived, the team had accrued an estimate and now trues it up.

Prepaid model. The same wholesaler funds a wallet with three top-ups of $4,500, or $13,500 in total. The ledger shows $12,400 in label debits and $460 in adjustment entries, each dated and carrying the order reference. The closing balance is $640. The tie-out is: $13,500 funded, minus $12,860 debited, equals $640 remaining. The three top-ups match three bank transactions. Duplicate billing does not arise in this example because a debit exists only when a label is bought.

The adjustments did not disappear in the second version. They are simply visible as individual entries as they post, instead of surfacing on a later bill.

Where GoatLabels fits

GoatLabels uses the prepaid ledger model only. You fund a wallet by card, Apple Pay, Google Pay, ACH, or crypto, and every label debits the quoted amount to a dated ledger entry that carries your reference. Re-weigh adjustments post to the same ledger. A multi-carton order produces several labels, each its own ledger line with the same reference, which is what makes shipping cost allocation by order or customer workable from an export.

The limits matter for this decision. GoatLabels does not support bring-your-own carrier accounts or negotiated rates, so if you ship on your own contracts, keep the invoice model for that volume and audit those bills as you do today. There is no LTL or freight, there are no sub-accounts or per-client balances, and nothing writes back into an ERP automatically. Getting ledger data into your accounting system is a CSV export or an API job that your team builds, as described on the ERP shipping integration page.

Where it does fit is the parcel volume that sits outside a carrier contract. USPS, UPS, FedEx, and DHL are rate-shopped from one account, the Free plan covers 50 shipments a month, and Pro is a flat $40 a month with no contract. Details are on the pricing page.