Before exporting invoice data, check that the seller name, address, country, identifiers and contact details describe the same confirmed supplier. Compare the completed record with its source evidence rather than judging only whether the preview looks professional. Non-empty fields can still belong to the wrong business or to different versions of the supplier record.
Use this checklist after preparation and entry. The seller-information guide explains the broader workflow; this page provides a final review sequence so that inconsistencies are caught before a file is shared or handed to a standard-specific mapper.
Check the supplier identity
Confirm the supplier against the agreement and authorised business records. Distinguish any trading label from the formal identity needed for the transaction. If the name was shortened to fit a layout, establish whether that representation is appropriate rather than assuming a familiar abbreviation is sufficient.
Check related entities carefully. A shared brand, office or owner does not establish that a tax identifier belongs with the selected seller name. Where the contract and business records disagree, resolve the difference through an appropriate authorised source before presenting the record as final.
For a fictional design group, a customer’s order may name the operating company while the draft still carries another group company’s details from a previous invoice. The names can both look credible. The check must identify which entity supplied this transaction, not simply whether the name is spelled correctly.
Check the address and its role
Confirm why the chosen address belongs in the seller record. Distinguish registered, trading, branch and correspondence roles where relevant. Keep a service or delivery location separate unless the requirements call for it to be represented in the seller address.
Compare the entered block with its confirmed components. Ensure that building or unit information, locality and postal information have not been lost during copying. Check that the address text and separate country selection do not contradict one another.
Do not impose another country’s postal pattern or invent a missing component to make the address look complete. The application does not verify postal existence or determine whether an address fulfils the applicable legal disclosure requirement. Those facts need suitable source confirmation.
Check identifiers by purpose
Read each identifier’s label and confirm that the value belongs to the intended supplier. A tax ID, company registration number, electronic address and customer-assigned supplier reference serve different roles. Do not treat one as an acceptable substitute for another because it fits a general text box.
Where the target profile needs an identifier scheme, retain both the value and scheme with their source. The current creator has a general seller tax-ID field rather than a complete standard-specific identifier structure. Any additional mapping requirement must remain explicit for supporting software.
Entering an identifier does not verify registration. If an external check was performed, record the service, relevant result and scope separately. A field-check pass should not be used as evidence that the identifier was authenticated or that the transaction’s tax treatment was determined.
Check contact and payment relationships
Confirm that the contact email is appropriate for invoice questions and belongs to the seller’s intended communication role. A well-formed address can still be out of date or copied from another business. Do not interpret it as a network endpoint unless the relevant specification and confirmed instructions establish that use.
Review payment information through trusted records. The supplier name and payee may require separate explanation under the actual arrangement, and a changed seller block does not authenticate changed account instructions. The product neither verifies bank-account ownership nor processes a payment.
Remove unnecessary personal information from notes while retaining information required for the transaction and recipient workflow. Privacy decisions should not lead to fictional substitute identities or addresses. Seek appropriate advice where necessary disclosure is unclear.
Check loaded drafts and recent changes
Review the seller record after loading a saved draft or importing an editable file. The data can be structurally acceptable while containing an old address, contact or sample identifier. The current application does not maintain a supplier master-data history or automatically reconcile imported details with newer records.
Use the revision-consistency checks if any seller fact changed after the draft was first reviewed. Confirm which version was updated and whether a downloaded output still contains the earlier details. Browser files do not update themselves when the form changes.
For an issued invoice needing correction, use the applicable process and supporting software. Do not present an edited draft as an unchanged original or claim an accounting audit trail the current product does not maintain.
Check the final representation and hand-off
Once the facts are confirmed, you can review the supplier details in the invoice creator. Read the seller block in the preview, then inspect the actual output chosen for the next task. Check complete names and address wrapping rather than shortening business identity merely to reduce lines.
The printable invoice and application JSON help with preparation. The CSV contains line items rather than a full seller record. None is a verified recognised-format export in this release, and a readable seller block does not prove that external identifier or address fields have been mapped correctly.
Keep the source confirmation and any unresolved external requirements with the reviewed data. A completed seller checklist establishes a coherent preparation record. Formal format validation, registry verification and recipient acceptance remain distinct tasks that need their own evidence.