Before exporting a first invoice, compare the completed draft with your source records, run the application’s field checks and confirm that the chosen output suits the next task. Inspect the exported file itself before sharing it. A preview that looks complete and a successful download do not establish that the recipient has received or accepted the document.
Use this checklist after data entry, not as a substitute for gathering the information initially. The first-invoice workflow provides that wider sequence. Here the purpose is to catch inconsistencies and wrong-version mistakes at the point where a draft is about to become a file someone else may rely on.
Check the document identity
Confirm the invoice number against the reference allocated in your records. Check the issue date and due date individually rather than assuming the initial values were appropriate. Review any purchase order or buyer reference against the customer’s current instructions, including spelling, punctuation and leading zeros where meaningful.
Look for sample values and stale references. Replacing the main invoice number does not necessarily replace a copied payment reference or a number included in notes. A search for distinctive example names or old references can help, but still read the document because a wrong value may look entirely ordinary.
The current creator does not check number uniqueness across your records. Its due-date rule rejects a date preceding the issue date, but passing that rule does not confirm that the payment term matches your agreement. These remain factual checks for the business.
Confirm both parties
Read the seller and buyer names, addresses, countries, identifiers and contact details. Compare the buyer with the legal billing entity, not only the person who approved the work. Review any changed customer details using the trusted source that confirmed the change.
Make sure no fictional example email or identifier remains after a company name has been replaced. A non-empty field can pass an application check while referring to the wrong entity. A country selection also does not establish a national invoice profile or the correct tax treatment.
If a recipient needs identifiers or references that the current model cannot represent, identify that gap before choosing final output. Do not disguise a missing typed field by putting unrelated values into one text box and reporting that the specification is satisfied.
Reconcile lines and amounts
Compare every description, quantity, unit and unit price with the approved billing records. Check the charging basis, particularly where packs, individual items, hours or sessions could be confused. Read discounts separately from prices so that the invoice reflects the actual agreement.
For a fictional first invoice, two agreed sessions at EUR 90 produce EUR 180 before any adjustment or tax. If a third session is a draft entry that was not approved, remove or resolve it before export. A correct multiplication of all three sessions would not resolve the billing question.
Review subtotal, discount, tax breakdown and total independently. EInvoiceCreator calculates its supported line-level amounts with fixed-point arithmetic and its own rounding policy. It cannot represent every standard’s adjustment structure, prepayment arrangement or credit-note scenario. Do not force unsupported transactions into the ordinary positive-invoice model to obtain a desired total.
Confirm tax and payment decisions
Enter only tax information you have confirmed for the actual transaction. Read any exemption or outside-scope reason for accuracy and relevance. The field checker can require a reason and a zero numeric rate for certain categories; it cannot determine whether the treatment legally applies.
Check payment instructions against trusted records. Confirm that the payment reference matches the intended reconciliation process and that a new bank instruction has been verified through an appropriate channel. The product does not validate account ownership or process the payment.
Read notes last. Remove demonstration text or outdated customer messages, while retaining genuinely useful information. A note should not be used to claim unsupported validation, delivery or tax-authority acceptance.
Run the checks and inspect the output choice
Run application field validation and follow error links to the affected inputs. Fix errors from the source information, then check again. Do not invent placeholder information merely to obtain a passed result. If a required fact remains unknown, keep a draft and resolve the question first.
The preview review guide explains which visible details can be checked on screen. Review the actual print preview as well if using printable output. Paper size, page breaks and scaling can differ from the live workspace, especially for long descriptions or multiple pages.
Choose among the outputs the product actually implements. Printing and browser Save as PDF create readable documents. Application JSON contains the application’s own data and calculated totals. CSV contains line items rather than a complete seller-and-buyer invoice record. None is a verified standards-based e-invoice export in this release.
Preserve the reviewed version
If you want to revisit incomplete work, download an editable JSON draft or explicitly save on the device. Saving is not autosave, and a local draft is not a cross-device invoice history. Keep private business data in an appropriate location and distinguish draft files from reviewed exports.
You can prepare and review the invoice before choosing an export when the current workflow suits your task. After downloading, open the actual file and confirm that it contains the approved version, correct data and intended output type.
Only then hand it to the appropriate recipient or external processing step. If recognised-format mapping, formal validation or a network submission is still required, record that remaining task explicitly. The completed checklist establishes a reviewed preparation stage, not proof that every downstream requirement has been fulfilled.