When seller details conflict across records, identify which facts disagree, establish what each source describes and obtain an authorised clarification before changing the invoice. Do not choose the newest-looking document automatically or combine the most complete-looking values from several sources. That can create a seller identity that no source actually confirms.
Use the seller-information workflow to review the identity as a coherent record. The task here is resolving conflicting evidence, rather than formatting a name or address after it has already been confirmed. Keep the draft visibly unresolved while a material identity question remains open.
List the conflicting facts
Write down the exact difference: a formal name versus a trading label, two addresses with different roles, an old registration value, a changed contact or an identifier belonging to a related company. Avoid a vague note saying “supplier details inconsistent” without showing which fields are affected.
Record the source and date for each value. A contract, customer supplier record, email signature and official registration record can serve different purposes. Their disagreement may reflect an outdated record, but it can also reflect different entities or address roles that should not be collapsed into one.
For a fictional example, a contract might name “Brook Engineering Ltd”, an email signature use “Brook Works”, and a customer’s system retain a previous office address. Those records need interpretation. They do not justify inventing a combined name and assuming that either tax number found in the folder will fit.
Identify the transaction and period
Establish which supply and invoice the clarification affects. A current business change does not automatically rewrite the identity relevant to an earlier contract or issued document. Ask whether the issue concerns a draft for a new transaction or a correction to an existing invoice.
If the entity itself changed, involve the authorised business owner or adviser rather than treating the change as a typographical update. The current creator cannot determine contractual succession, legal status or which supplier is entitled to bill. It records the information that has been confirmed.
If the difference is a spelling error or display label, still record the correction source. Small changes can affect a recipient’s supplier matching, and a later operator should not have to infer whether a shortened label was deliberate or accidental.
Ask the right person a focused question
Send the relevant conflicting values and explain the transaction. Ask which seller identity, address and identifiers should be used, what source confirms them and whether any customer-record update is needed. Include only the information necessary for the question through an appropriate channel.
An accountant may clarify some tax and accounting matters, while an authorised company contact, registration authority or legal adviser may be needed for other identity issues. Do not assume one general approval resolves every question. If the answer establishes the name but not the tax identifier, keep the latter unresolved.
The questions to ask when seller details are unclear can help prepare that request. A focused inquiry is more likely to produce an entry-ready answer than asking someone to approve a screenshot without seeing the underlying conflict.
Keep roles separate while resolving the conflict
A trading name, legal identity, address, bank payee and network endpoint can all differ for legitimate reasons under a particular arrangement. The preparation record should explain the confirmed relationships rather than treating every difference as an error to erase.
Do not change seller information to match an incorrect customer supplier record simply because doing so might prevent an automated rejection. Use the customer’s established correction process and obtain the relevant confirmation. Successful matching is not a sound outcome if the underlying supplier identity is misstated.
Bank-detail changes need their own trusted verification. A message that explains a name discrepancy does not automatically authenticate a different payment account. Keep identity resolution and payment-security checks distinct.
Update one controlled working version
After clarification, identify the draft to update and change the affected fields deliberately. Review dependencies such as country, tax ID and contact information. A name replacement may leave an old address or sample email behind, and a basic field checker may accept all of those non-empty values.
The current creator stores one explicitly saved browser draft and can import its own editable JSON. It does not automatically update earlier downloads or maintain a historical entity database. Review a loaded draft before reusing it, because it can restore the very values you just corrected in another working copy.
If a reviewed export has changed, identify the appropriate new version and inspect the actual file. Do not assume the attachment selected in another application reflects the open browser tab. For an already issued document, follow the applicable correction process using suitable supporting software.
Preserve the decision and remaining work
Retain a concise record of the confirmed value, source, affected transaction and any qualification. If a downstream mapper needs separate formal and trading names or typed identifiers, pass those distinctions with the data. Do not flatten the explanation into a single ambiguous name field.
The resolution is complete when the seller record and its evidence agree for the intended use. It is not a certification of the application, a determination of every tax consequence or proof of recipient acceptance. Keeping that scope precise makes the corrected information more dependable for everyone who uses the invoice next.