PRACTICAL INVOICE GUIDES

Invoice tracker spreadsheet: a CSV preparation checklist

By Evrani · Published 26 October 2026

An invoice tracker spreadsheet works best when each row describes one invoice consistently. Before importing a CSV into another tool, check the structure and the meaning of each column. A tidy preview is useful only if the amounts, payment totals and dates behind it are also correct.

Start with one invoice per row

Keep invoice-level records separate from individual payment transactions. If an invoice has three payments, repeating its full amount on three rows can make a tracker appear to hold three invoices. A payment ledger can keep those transactions, while the invoice tracker holds their cumulative paid total.

Use a stable invoice reference and client name. If your business reuses invoice references across clients, preserve the client distinction as well. Do not change references simply to make a duplicate warning disappear; first decide whether the row is a real additional invoice or another copy of an existing one.

Invoice reference: the identifier from the invoice already issued.
Client name and verified billing email: the intended recipient.
Currency: an explicit code such as GBP, USD or EUR.
Invoice amount and total paid so far: separate numeric columns.
Due date: the agreed payment date, not the date of the import.

Keep currency separate from amounts

A number such as 250 is not enough to identify a currency. Use a dedicated currency column and keep invoice amount and total paid in that same currency. Do not add a dollar invoice to a pound invoice and describe the result as a pound balance unless you have a separate, documented conversion process.

For a straightforward import, use decimal amounts such as 250.00 without currency symbols or thousands separators. Check whether the destination expects major units, such as pounds, or minor units, such as pence. In Evrani's CSV importer, 250.00 represents £250.00 when the mapped currency is GBP; it is not a request to enter 25000.

Remove date ambiguity before exporting

Dates such as 04/05/2026 can be interpreted differently across locales. A consistent year-month-day value, such as 2026-05-04, removes that ambiguity. Check the exported CSV itself: a spreadsheet may display one format while saving a different underlying value.

Avoid formulas whose results change unexpectedly when the file is opened elsewhere. Export the values you actually intend to import and retain a copy of the original spreadsheet. Review empty dates and impossible calendar dates before trying to fix them inside the destination tool.

Check cumulative payments and duplicate rows

Total paid so far should describe the amount recorded against that invoice, not only the latest transfer. For a £250 invoice with £100 recorded as paid, the row should show 250.00 as the invoice amount and 100.00 as total paid. Its remaining balance is £150.

Look for copied rows, repeated exports and invoices already present in the destination workspace. A preview that skips duplicates is protecting the existing record. It should not be assumed to update that record with a newer payment amount. Use the existing invoice's edit flow when you need to change its saved details.

Use a small sample and read the preview

Test a few sample rows before a larger import. Include an unpaid invoice, a partially paid invoice and a fully paid invoice so you can check all three balances. Keep unrelated confidential information out of the sample.

Map columns deliberately, then inspect the preview summary: how many rows are ready, how many have errors and how many are duplicates? Check at least one amount, due date, currency and client on the preview against your source. Saving the right number of rows is not enough if the column mapping was wrong.

Fix invalid rows instead of treating a partial import as complete.
Check quoted text, commas in client names and notes on multiple lines.
Confirm the saved records remain after refreshing the page.
Compare the imported balances with the source before enabling follow-ups.

Keep importing separate from permission to send

Adding an email address to a tracker is not the same as deciding to send a reminder now. Review payment status and the recipient before enabling any automatic follow-up. Paid, disputed or paused invoices should not enter a routine unpaid-invoice sequence.

Evrani lets you import invoice details, match columns and review rows before saving. Imported invoices start with automatic reminders off; workspace delivery and each invoice require their own opt-in. Evrani uses invoices you have already issued and does not create tax invoices or reconcile your bank account. Its current development pilot is for test data only while setup is completed.