ESA invoice tracking template: follow each invoice through to the deposit

Download a blank register or a worked example

Download the free Excel invoice tracker with formulas. It includes a blank invoice register, separate payment allocations and a fictional worked example. Expected net, received and remaining amounts calculate from your entries. Review flags identify duplicate invoice numbers, unmatched allocations and negative balances. No signup is required.

The workbook has 200 prepared rows per table. Blue cells are inputs and green cells contain formulas. Split combined deposits across the matching invoices; enter each later partial payment on a new allocation row. Resolve flagged entries and reconcile allocations to actual deposits before relying on totals. It is a standalone worksheet, not the payment-import format for GetESAPaid.

Download the blank ESA invoice tracking CSV or the fictional completed register. Open either file in Excel or import it into Google Sheets. No signup is required.

The file is a manual working register, not an automated accounting workbook. It contains no formulas and does not connect to a bank, submit invoices or validate expense eligibility. Its job is to make an open item understandable: what was billed, what is expected, what has arrived and who needs to act next.

If you need to create the invoice itself, start with the ESA invoice template. For the documents behind the register, use the provider record-keeping guide.

Keep review status and payment status separate

A single “paid/unpaid” column cannot explain every open invoice. An invoice can be drafted but never submitted, awaiting information, approved but not settled, or partly matched to a deposit. Use the exact portal wording in the review-status field and your own clearly defined bank-matching status alongside it.

Field	What belongs there	What does not belong there
Invoice number	The unique identifier on the saved invoice	A new number invented for every follow-up message
Program and route	The actual program and direct-pay, reimbursement or marketplace route	A guess based only on a payment-platform logo
Submitted date	Date the document entered the approved channel	Date you started writing the draft
Portal status	Exact wording plus the date checked	“Paid” inferred from an approval email
Expected net	Amount expected after a documented adjustment	A universal assumed platform fee
Received to date	Amount allocated from identifiable payments	The whole combined deposit repeated on every invoice
Remaining	Expected net minus received to date	A balance silently forced to zero
Next action	A specific question, owner and follow-up date	A vague note saying “chase”

Use student references in the working sheet and restrict access to the matching identity records. The required student information still belongs on the official invoice when the program asks for it.

Worked register: three invoices, one unresolved balance

The fictional example uses three invoices totaling $470. The second has a documented $5 adjustment under an invented agreement. That produces expected net receipts of $465. Receipts allocated so far total $405, leaving $60 outstanding.

Invoice	Billed	Documented adjustment	Expected net	Received	Remaining
DEMO-SEP-001	$150	$0	$150	$150	$0
DEMO-SEP-002	$200	$5	$195	$195	$0
DEMO-SEP-003	$120	$0	$120	$60	$60

The $5 is not a statement about ClassWallet, Odyssey, Step Up or any state program's fees. Record an adjustment only when you have the applicable agreement or supporting explanation.

The first two invoices share a deposit reference totaling $345. Allocate $150 to one invoice and $195 to the other. If you enter $345 as received on both rows, you overstate receipts by $345. Keep a separate payment-allocation record when one invoice has several payments or one deposit covers several invoices.

Set up your first billing period

1. Make a private copy of the blank register. Keep a separate untouched copy of the template.
2. Enter the invoices you actually saved. Copy their exact invoice numbers, issue dates and billed amounts.
3. Link the submitted document and service or fulfillment evidence. Use file references accessible only to authorized people.
4. Check the relevant portal and enter the current status with a checked date. If you have not checked, leave it unknown rather than inferring approval.
5. Match payment evidence to bank receipts and allocate the amounts to invoice rows. Preserve the original export.
6. Calculate remaining balances. Investigate negative balances as possible overpayments, incorrect adjustments or duplicate allocations.
7. Give each unresolved row one next action and a follow-up date. Review those rows at the next billing run.

Keep refunds and reversals as explicit linked records. A deleted receipt destroys the explanation for a changed balance. If the amount billed itself was wrong, preserve the invoice correction trail rather than disguising the difference as a payment fee.

Following up without creating a duplicate claim

Before contacting support, collect the program, transaction or order reference, submission date, exact current status and the one thing you need clarified. Use the official account or support channel. A family may be the correct person to approve a step in one route and the wrong recipient for transaction documents in another.

For an approved-but-unmatched item, ask whether payment has been initiated and which reference identifies it. For a missing-information item, respond to the actual request rather than sending a new invoice with the same expense. Read the rejection and follow-up guide for sample wording.

Moving from the register to software

GetESAPaid can save invoice records and import payment reconciliation CSVs with column mapping. The blank tracking register on this page is not the payment-import format: it combines workflow notes with cumulative receipt totals. Use the reconciliation sample CSV to inspect a payment-import example and inspect your file before choosing Validate and import. That action applies valid matches; it is not a separate preview-and-confirm screen.

A spreadsheet may be sufficient when a small number of invoices are easy to reconcile. Consider testing software when you repeatedly reconstruct supporting documents, reuse old service dates or cannot tell which sessions have already been billed. The software evaluation guide includes a practical comparison exercise without assuming that every provider should replace their current tools.

Can this tell me how long payment will take?

No. The register records the dates and evidence you observe. It does not create an official payment deadline or turn approval into settlement. Consult your state payment guide and the current account-specific instructions, then measure your own elapsed times consistently.