Before exporting or handing over invoice data, confirm that the buyer identity, address, identifiers, contact details and references belong to the intended transaction. Compare the completed record with the customer’s current billing instructions and order evidence. A complete-looking buyer block can still identify the wrong entity or contain a reference that the recipient cannot match.
The buyer-information preparation guide covers collection and entry. This checklist is for the final review after those tasks. It helps distinguish facts already confirmed from requirements that still need clarification, supporting software or a separate delivery process.
Check the entity being billed
Read the buyer name in full and compare it with the agreement or confirmed customer instruction. Do not substitute a group brand, department label or project contact for the actual buyer without establishing that representation. Similar names and shared email domains do not prove that the entities are interchangeable.
Check any recent change against the authorised source and affected transaction. A new contact or office location does not automatically establish a new buyer. If the change affects an already issued document, follow the appropriate correction process rather than treating it as an ordinary draft edit.
For a fictional equipment sale, the person collecting the goods may work at a depot while the order names a separate operating company. The buyer check should connect the confirmed entity with the order and supply, not merely reproduce the delivery contact’s details.
Check address roles and components
Confirm that the buyer address is the appropriate billing information for this record. Keep delivery, service-site and processing-centre details distinct when they have different roles. A real address can still be inappropriate for the buyer field if it describes another part of the transaction.
Compare the entered address with its confirmed components, including building information, locality, postal information where applicable and country. Check that the address text does not retain an old country name while the separate selection shows a different one.
The current application does not verify postal existence or legal suitability of the address. Its multiline block also does not prove that an external standard’s separate address components have been mapped. Preserve the source components for supporting software when needed.
Check each identifier’s purpose
Label and confirm the buyer tax identifier, any registration identifier and electronic addressing information separately. Do not use one as a substitute for another merely because it fits a field. If a technical address needs scheme information, retain the complete instruction for the final process.
The current creator records a general tax ID and optional email but does not implement a full endpoint model or external registration checks. An accepted text value is not a verified identity. If a relevant external service was used, keep evidence of the exact question checked and result obtained.
A registration result also does not determine the correct tax treatment of the transaction. Confirm that decision separately through appropriate sources or advice, rather than inferring it solely from a buyer country or identifier.
Check references and their scope
Compare the general buyer reference with the order and routing instructions. Identify separately any purchase order, project, contract, department or line reference the recipient needs. Keep values and their purposes together, including meaningful characters that can affect matching.
If the final profile requires several typed references, do not report that one combined string satisfies them. The current model has one general reference field, not a complete procurement integration. A note can help a reader without establishing that the required structured elements exist.
For a fictional invoice covering two approved order lines, confirm both the document-level order and any line relationships required by the customer. The total can be correct even when the reference is attached to the wrong work or entity.
Check contacts, instructions and remaining tasks
Confirm the billing email’s role and whether it differs from the technical delivery destination. The creator does not verify mailbox ownership, connect to Peppol or submit invoices to government platforms. Downloading a local file leaves any actual transmission with the chosen external process.
The customer-instruction review workflow helps identify the applicable format, profile, version and submission route. Check that the instruction applies to this customer entity and transaction. Do not rely on an old example or another group company’s onboarding pack without confirmation.
Where the requirement exceeds the current creator, keep the gap visible in the hand-off. Printable output, application JSON and line-items CSV have specific limited purposes. None is a verified recognised-format export in this release.
Check the reviewed version before sharing
After loading or importing a draft, repeat the buyer review rather than assuming the stored values are current. Saving on the device is explicit, and earlier downloads do not change when the open form changes. Confirm the actual file selected for attachment or external processing.
Keep a concise record of what was confirmed, the relevant source and any unresolved action. A useful buyer checklist establishes that the preparation record is coherent for its intended use. It does not guarantee recipient acceptance or replace formal mapping, validation and delivery evidence where those stages are required.