Practical guide

Review a Freelancer Invoice Before It Leaves Your Computer

An invoice can have the right total and still be wrong.

The client’s legal name may be stale. A service description may be too vague. The date may belong to last month’s draft. A discount or caller-supplied tax input may have been applied to the wrong amount. Once the document leaves your computer, each mistake becomes a client conversation.

A local invoice review covers a smaller job: turn supplied billing facts into an inspectable draft, compare the calculations with the document, and decide whether a human should deliver it.

Keep the review separate from the invoice service

Invoice Ninja handles much more than document checking. Its current documentation covers invoice creation, client-facing PDFs, email delivery, invoice states, linked payments, reminders, recurring billing, reports, and a client portal.

Those functions belong to the wider business process. They should not be treated as proof that a local review sends an invoice or confirms payment.

For the immediate review, the input can stay narrow:

client identity and contact details;
invoice and due dates;
currency;
service descriptions, quantities, and unit rates;
supplied discounts or tax inputs;
notes and payment terms.

The stopping point is a reviewed document. Delivery comes later through a method you choose.

Recalculate from the source lines

Start with the line items, not the displayed total. Each quantity, rate, discount, and supplied tax input should contribute to a result you can reproduce from the source facts.

The reviewed local mechanism stores currency amounts in minor units during calculation. That avoids treating a formatted currency string as the source number. It can then preserve the same invoice in CSV and JSON representations for comparison.

The named fictional Invoice Ninja example demonstrated a draft state, an issued representation, a total in minor units, and CSV and JSON outputs. A separate reviewed invoice workflow also produced a human-readable HTML view.

These examples establish a bounded calculation and review chain. They do not reproduce Invoice Ninja’s hosted functions.

Read the document like your client will

Structured files make fields easy to compare. The rendered view exposes a different class of mistake.

Read the draft from top to bottom and ask:

Does the client identity match the engagement record?
Do the dates and payment terms say what you intend?
Can the client recognize every service line without private shorthand?
Can you reproduce the displayed total from the supplied values?
Are discounts and tax inputs clearly sourced rather than guessed?
Do the notes explain the work without introducing a new promise?

Write corrections as review notes before changing the invoice facts. This keeps the reason for an edit separate from the revised record.

Compare the views before choosing delivery

The reviewed invoice workflow produced repeatable CSV and JSON exports from unchanged invoice records. It also refused to silently replace an existing export. Formula-like spreadsheet content was made inert in CSV output.

Use those properties to compare three views:

the source facts show what you supplied;
the structured export shows what the process stored;
the human-readable document shows what a client would read.

All three should agree on identity, dates, line descriptions, adjustments, and total. If one differs, stop and correct the source before delivery.

Know what the review cannot decide

A local document review does not prove that an email arrived or that a client opened the invoice. A paid label does not establish that money moved. A tax field does not supply tax advice. A clean export does not place the transaction into your books.

Keep the wider service when you need payment collection, reminders, recurring billing, shared account access, accounting sync, reconciliation, or a client portal. Get qualified advice when legal wording, tax treatment, or jurisdiction-specific document rules affect the invoice.

The local approach fits when one freelancer owns the draft, the billing facts are already supplied, and the immediate decision is whether the document is internally consistent.

Takeaway

The replacement job is checking whether an unsent invoice agrees with its source facts. That boundary gives you a document, a calculation trail, and a clear stopping point without treating review as delivery or payment.

Review one unsent invoice

Copy one unsent invoice into a checklist with five groups: client identity, dates, line items, adjustments, and delivery instructions. Resolve every blank and mismatch before choosing how to send it.