You can prepare basic invoice information without an accounting package by keeping reliable source records, entering the confirmed details in a suitable creator and reviewing the result before sharing it. You still need a way to allocate invoice numbers, record what was issued and track later corrections. A browser editor can help with document preparation, but it does not replace those business records.
Start by checking the recipient’s required format. If the customer needs a specific structured standard, you will need software that actually produces and validates that output. EInvoiceCreator currently provides printable output, application JSON and line-items CSV; it does not generate recognised standards-based e-invoices. This limitation matters before you commit to a tool-based workflow.
Keep a small set of reliable records
Maintain a billing register appropriate to your business. For preparation, it should let you identify which invoice references have been allocated, which customer and supply each concerns, and where the reviewed document is stored. The current creator cannot check numbers against documents produced elsewhere or maintain an account-based issued-invoice history.
Keep agreed prices, order approvals and delivery or service evidence separately from the invoice draft. Those records answer whether you should bill an amount. The editor answers whether the amount entered can be calculated and displayed. Confusing these jobs can make an arithmetically correct invoice commercially incorrect.
The first-invoice workflow provides an order for gathering these records. If your only source is an email saying “please invoice us”, request the missing billing entity, item detail and references rather than treating the message as a complete instruction.
Prepare the data in a simple worksheet
Use labelled rows or boxes for seller, buyer, invoice number, dates, currency and payment details. Make a second table for the items supplied. Each item should identify its description, quantity, unit, agreed price and confirmed tax information. This organisation is useful even when you plan to enter every value manually.
Keep uncertainty visible. A cell marked “buyer reference to confirm” is better than copying a reference from another customer. Do not add a provisional tax rate to the final invoice merely to complete the worksheet. Resolve the treatment through the relevant advice or authority when the facts are unclear.
A worksheet is not automatically an import file. The current application does not accept arbitrary spreadsheets or CSV files as complete invoices. Its supported import uses the application’s editable JSON structure. Use the worksheet as a source for entry unless you have an external process that explicitly supports the destination’s data model.
Work through a basic service example
Imagine a fictional language tutor billing four agreed sessions at GBP 35 each. The starting net amount is GBP 140. The preparation record should also identify the customer, session description, relevant period and payment instructions. Any applicable tax treatment needs its own confirmed decision; the service label and currency do not determine it.
In the creator, choose GBP, enter the parties and reference, then add quantity 4, unit “session” and price 35.00. Read the preview to verify that it describes the actual agreement. If you accidentally leave the unit as “hour”, the total can remain GBP 140 while the meaning becomes wrong.
If the agreement includes an advance payment, do not simply reduce the price until the desired remaining balance appears. The product does not implement a complete prepayment structure. Retain the facts and use supporting software where the transaction requires fields outside the current model.
Save drafts deliberately
The creator processes the open document in the browser. Save on this device writes one draft in the current browser profile when requested; it does not automatically capture every subsequent edit. A downloaded editable JSON draft can preserve incomplete work for a later supported import, but its privacy and storage remain your responsibility.
If you work on a shared device, consider whether leaving customer and payment information in browser storage is appropriate. Deleting a saved draft removes that browser copy, not previously downloaded files. Keep draft filenames distinct from reviewed documents so another person does not send an incomplete version by mistake.
The information-organisation checklist can help keep the preparation sheet, evidence and working draft together without putting private customer information into filenames or public page URLs unnecessarily.
Review the document and the wider process
Run the field checks, then manually verify the business meaning of each entry. Confirm the buyer, price agreement, tax decision, currency and payment instructions. The current validation checks required values, valid dates and supported numeric ranges; it does not authenticate the parties or determine legal treatment.
Inspect the actual exported file, not only the on-screen preview. A printable invoice may suit a recipient asking for a readable document. Application JSON may suit your own revision process. Neither should be presented as a standard that the exporter has not implemented.
Move to a more capable system when your needs include recognised-format generation, automated ledger records, multiple saved invoices, credit notes, advanced tax scenarios or transmission integrations. Keeping the first workflow simple is reasonable, provided its boundaries are explicit and the independent records remain dependable.