Organise invoice information into a small preparation pack containing recipient instructions, confirmed seller and buyer details, the billing agreement, item evidence and payment instructions. Keep unresolved questions in a separate list. This makes data entry a controlled transfer of known values rather than a search through scattered messages while the form is open.
The pack can be a worksheet, a labelled folder or another record appropriate to your business. It does not need an elaborate system, but it must make the source of important values clear. The first-invoice workflow shows when to gather information, while this article explains how to arrange it so another person can review the same facts.
Separate instructions from transaction evidence
Recipient instructions describe how the customer wants the invoice prepared and delivered. They may specify a buyer reference, billing entity, structured format or submission route. Keep the current instructions identifiable so that a previous customer’s requirements do not become the default for every new invoice.
Transaction evidence describes what you supplied and what was agreed. It might include an accepted quotation, order, approved hours or delivery confirmation. A recipient’s formatting guide does not establish that a particular quantity is billable. Conversely, an approved time record does not identify which structured invoice profile the customer accepts.
When a document contains both kinds of information, record which parts you are relying on. For example, an order may supply the agreed line prices and an order reference, while a separate onboarding document supplies the billing address. You should be able to trace each final value without rereading an entire email history.
Build a field-oriented preparation sheet
Arrange party identities, invoice identifiers and dates, currency, line items, tax information and payment details in separate groups. Use labels matching their meaning rather than their position on a previous invoice. Avoid a general “numbers” box containing the tax identifier, invoice number and order reference together.
Give each key value a status such as confirmed, to confirm or not applicable. Do not turn a blank into “not applicable” merely because you do not know the answer. A missing required buyer reference needs a question to the customer; a genuinely unnecessary internal project code may not belong on the invoice at all.
For example, a fictional consultant’s preparation sheet could show an approved eight hours, rate GBP 75, order reference PO-316 and a confirmed buyer entity. If the payment due date is unresolved, retain that question explicitly. Completing the other fields does not make the missing term less important.
Keep one authoritative value for each fact
A repeated value can drift when it appears in several notes. If the buyer changes its billing address, update the preparation sheet from the confirmed instruction and identify which supporting record is current. Do not choose whichever address appears most often in your folder.
Use clear version names for working material. Distinguish a quotation from an accepted quotation and a draft invoice from a reviewed export. A file labelled “latest” becomes ambiguous as soon as a second person downloads a copy and edits it elsewhere. A date and meaningful revision label can help, provided it does not expose unnecessary personal information.
Store payment instructions with particular care. A new bank detail in an email should be verified through an established contact route before it replaces your trusted record. The creator cannot decide which of two conflicting instructions is genuine.
Arrange items for efficient entry
Prepare one record per meaningful invoice line. Put quantity, unit and agreed unit price next to one another so their relationship is visible. Record discounts and confirmed tax treatment separately. This reduces the risk of copying a line total into a unit-price field or entering a pack quantity with an individual-item rate.
If the source is a spreadsheet, treat it as preparation data unless an actual supported import is available. EInvoiceCreator currently imports its own editable JSON drafts, not arbitrary worksheets. You can still use a spreadsheet to review the source values before entering them manually.
Mark transaction structures outside the application’s scope. Credit notes, negative prices, prepayment reconciliation and document-level adjustments need supporting software with appropriate fields. Do not distort the preparation sheet to make an unsupported scenario resemble a simple positive invoice.
Prepare a review hand-off
A useful hand-off tells the reviewer what was billed, where the facts came from, what remains unresolved and which output the recipient requires. It should not require access to every private conversation or unrelated customer file. Share only the evidence needed for that review through an appropriate channel.
For decisions the software cannot make, the manual invoice-review checklist identifies responsibilities that remain with the business. Decide who confirms prices, tax treatment, identities and payment instructions before asking that person to sign off the draft. An undifferentiated “please check” request can leave each reviewer assuming that someone else checked the sensitive values.
Bring the pack into the browser workflow
Enter the confirmed details, compare the preview with the sheet and run the field checks. The current creator works locally in the open browser tab, with explicit draft saving rather than autosave. Save or download the working draft deliberately if you need to preserve it while waiting for a missing answer.
The prepared pack remains useful after export. It explains why a value was entered and which version was reviewed. If the next step needs recognised-format mapping or formal validation, hand over the recipient specification and unresolved field requirements with the data. Organisation is successful when the next person can continue the process without guessing, not simply when every file sits in a tidy folder.