When a business has a registered address and a different trading address, confirm which address is appropriate for the invoice and the recipient’s required representation. Do not assume that the address where work happens is always the address that should identify the seller. Equally, do not assume that every address difference means a different supplier entity.
The answer depends on the business arrangement and applicable requirements. The seller-information workflow begins with the supplier identity, which must remain clear whichever address role is relevant. This article concerns choosing and documenting that role; postal line formatting is a separate task.
Identify what each address describes
A registered address can relate to an entity’s formal registration. A trading address can identify where the business operates. A correspondence address can describe where communications should be sent. Those descriptions are not interchangeable, and a particular business may have more than one location in each category.
Write the role beside each address in the preparation sheet. Avoid an unlabelled pair of address blocks that leaves the person entering the invoice to choose whichever looks complete. Record the source establishing the role, such as an authorised business instruction or relevant registration record.
For a fictional workshop, the production site might be where goods are made while a separate address appears in the business’s registration records. A customer may also have an older correspondence address on file. Each fact can be real without every address being suitable for the same invoice field.
Check requirements before selecting a block
Consult the invoicing requirements applicable to the transaction and the recipient’s current instructions. If they refer to a specific supplier address role, establish how that role relates to the business’s records. Do not treat a customer’s informal preference as permission to misstate the seller’s identity.
The current creator cannot make this legal or contractual decision. It offers one seller-address block, not an address-role engine. If both addresses or additional structured fields are needed, retain the information and use software that can represent the final requirements.
When uncertain, ask a focused question of an appropriate adviser or authorised business contact. Include the two addresses, their sources and the intended invoice transaction. “Which address looks more professional?” does not address the underlying role or required disclosure.
Keep the name and identifiers consistent
Before using an address, check that it belongs to the seller represented by the name and identifiers. A group company’s registered office should not be combined with another entity’s tax identifier merely because both share the same brand. Resolve the entity relationship separately from the postal-address question.
A move or change of office can also affect the source records. Identify which address applied to the relevant transaction and whether a current correction is required. Do not retroactively rewrite a historic issued invoice simply because a newer business address now exists.
The seller-details consistency checks help manage these relationships through revisions. A value that is current for one purpose may not automatically replace every historical or role-specific address in the preparation records.
Avoid using notes as a universal solution
A readable note can explain a correspondence address or service location where appropriate. It does not automatically satisfy a structured field required by a recipient profile. A receiving system may need to distinguish seller identity from delivery or contact information without interpreting a paragraph.
If the final mapping requires separate address components, preserve them before entering a multiline block. EInvoiceCreator’s application JSON carries the application’s address text, not a verified mapping of every address role into an external standard. Adding two labelled blocks to one text field can preserve readability while still leaving a structured requirement unresolved.
For a fictional seller with a registered office and workshop, the preparer should know which address the chosen field represents and which information remains for a downstream system. That is more reliable than concatenating both addresses and reporting that all requirements have been fulfilled.
Handle personal-address concerns deliberately
For some small businesses, an available address may also be a home address. Consider privacy and necessary invoice information together. Do not invent a commercial location, remove required information without advice or substitute the customer’s address to avoid the issue.
Seek an appropriate business-address arrangement or clarification where needed. The application cannot determine which arrangements are permissible for a particular business. Optional notes should not become a place for unrelated personal details simply because the address question prompted a broader disclosure.
Review the selected representation
After confirming the role, enter the address and country accurately. Inspect the preview and the intended output for legibility, complete components and consistency with the seller name. Check that an old trading location or copied correspondence line has not remained inside the address block.
Retain the explanation of why that address was selected. If the customer questions it, you should be able to identify its role and source rather than saying it was the first address a form accepted. Passing an application field check only establishes that a value was provided in an accepted shape.
A good preparation outcome keeps identity, address role and postal components distinguishable. That makes the readable document clearer and gives any later standard-specific mapping enough context to represent the supplier without guessing.