Prepare a buyer address by confirming the customer’s billing entity and the address that belongs with that entity for the transaction. Use current authorised billing instructions and reconcile them with the purchase order. Do not assume that a delivery label, project contact’s office or old customer template supplies the right buyer address.
The buyer-information workflow puts this confirmation before the final document. The current creator records multiline address text and a separate country selection; it does not verify addresses or establish which customer location fulfils a particular legal or recipient-profile requirement.
Request a usable billing address
Ask the customer’s billing or procurement team for the complete address and the entity it identifies. If a purchase order names one entity while an email supplies another address, ask how the two relate. An address without a clear entity can be real yet inappropriate for the intended buyer record.
Keep the response associated with the transaction or customer onboarding instruction. A general public website may list several offices without explaining which handles this purchase. Do not choose the headquarters address simply because it is the most visible search result.
For a fictional equipment customer, the order may name “Fieldstone Services Ltd” while goods go to a depot operated for several companies. The depot address should not automatically replace the buyer’s billing address. Record each location’s confirmed role before deciding what belongs in the form.
Reconcile differences instead of guessing
Compare the supplied billing address with the order and relevant customer records. Identify whether a difference concerns a spelling correction, an office move, a processing centre or a different business entity. These are not interchangeable explanations, so “use the new address” may need more context.
If the instruction affects an already issued invoice, establish the appropriate correction process. The current creator does not maintain issuance status or determine whether a change can be treated as a draft edit. Keep the source of the correction and the affected document identifiable.
The billing and delivery address guide explains the role distinction when both addresses appear. Resolving that distinction is more reliable than placing all addresses in one multiline block and expecting a reader or receiving system to infer which is which.
Preserve complete components
Keep building or unit information, street details, locality, postal code where applicable, region where relevant and country in the preparation records. International addresses do not all follow the same pattern, so do not manufacture a postal code or remove an unfamiliar locality to match the sample’s layout.
When copying from a PDF or email, check line-wrap artefacts and missing characters. A line break can be a visual convenience rather than part of the street name. A delivery instruction such as “use side entrance” may describe physical access rather than a billing address component.
For structured preparation, OpenPeppol’s published buyer postal-address group illustrates how a profile can represent address components separately. That is different from a single readable application block. Preserve the components so an appropriate external mapper can place them according to the actual target specification.
Enter the address and country consistently
Use the multiline address field to make the confirmed buyer address readable. Check the separate buyer-country selection against the address text. If an older draft contains a country name inside the text, replacing only the selector can leave a contradiction in the visible record.
The overall country context is separate from the buyer-country selection. It does not apply the buyer’s national invoice rules or determine the tax treatment. Likewise, invoice currency does not identify the buyer location, and a common currency does not prove that the parties share a country.
If the named country list does not represent the address fully, retain the exact confirmed information in your preparation records and assess whether the available output suits the task. A final structured profile may need a formal country code, which the current context selection does not guarantee.
Check the preview without changing meaning
Read the buyer block beside the seller block so the two addresses are not accidentally swapped. Verify complete locality and unit information, and check how long lines wrap. Do not replace a meaningful part of an address with an abbreviation merely to keep the block visually short.
Inspect the actual print output if that is the intended file. A live preview can wrap differently from the browser’s printed document. Application JSON stores the application’s address text, while line-items CSV does not contain the full buyer address record.
The field checker requires a buyer address value but does not verify postal existence, entity association or compliance with an external profile. A complete-looking block therefore needs the source confirmation established at the start of the process.
Preserve the confirmation for the next stage
Once the address is confirmed, you can enter the buyer details in the invoice creator and review them with the invoice references and line items. Keep any additional delivery address, routing instruction or separate typed component available for supporting software.
A useful hand-off identifies the buyer entity, the billing address source and any unresolved mapping requirement. It does not claim recognised-format validation or recipient acceptance. The preparation is reliable when the selected address has the right role and the full confirmed information survives entry and export.