Choose the seller country that belongs with the confirmed seller address, and treat the separate country context as descriptive information about the invoice preparation. Neither selection establishes the correct tax treatment or proves that the output meets a national invoicing profile. A country name in a form is not evidence that the application has implemented that country’s rules.
Start by confirming the seller identity and the role of the address you are entering. The seller-details workflow explains how these facts fit together. If a business has several locations, the preparation question is which confirmed location belongs in this record, not which selection produces a familiar-looking invoice.
Understand the two country selections
EInvoiceCreator has an overall country context and separate country selections for seller and buyer details. The context records the selected background for preparation. The party selections record countries alongside the party information. They are not a hidden standards adapter and do not add missing mandatory identifiers or select a tax rate.
A transaction can involve a seller and buyer in different countries, so the three selections need not always be identical. Conversely, seeing different values should prompt a factual check rather than an automatic attempt to make everything match. Confirm what each selected value represents in the actual transaction.
The current country list includes named choices and an “Other” option. That is an application selection list, not a complete formal country-code mapping. If the final recipient needs a specific code in a structured field, supporting software must represent it according to the relevant specification.
Use the address as evidence, not as a tax decision
Check the seller address against the reliable record that established it. If the source says the supplier is based at a confirmed address in one country, do not choose another country because the customer prefers its local currency or because the invoice is written in another language.
Address country, invoice currency and interface language answer different questions. A fictional business can agree a price in a currency different from its address country’s common currency. Selecting that currency does not relocate the supplier, and selecting the supplier country does not convert monetary amounts.
For address entry itself, the seller-address preparation guide explains how to preserve components and avoid imposing another country’s postal pattern. Keep the country consistent with the address text, especially when the source contains a country name that was copied from an older document.
Keep tax facts separate
The correct treatment of a supply can depend on more than a postal country. Parties, registration status, the nature of the supply and other facts can matter under applicable rules. The creator does not establish those facts or offer a country-based tax determination service.
Enter a rate and category only after confirming the relevant treatment through appropriate records or advice. Do not select a country and infer that the sample rate has become correct. Sample amounts and percentages demonstrate the product, not the tax rules for a business that happens to choose the same country.
If a particular national process requires additional seller identifiers, references or document types, preserve those requirements separately. The current editor cannot satisfy them merely because it recognises the country label. Mark the missing representation for the external generator rather than placing invented data in unrelated fields.
Review a cross-border preparation example
Suppose a fictional supplier’s confirmed address is in Germany and its customer’s billing address is in Belgium. The agreement is in EUR, and the customer asks for a particular structured output. These facts need to be recorded separately: seller country, buyer country, currency and required format.
They do not provide enough information for this application to decide the tax treatment or deliver an invoice through a network. A preparer should obtain the relevant tax decision and the recipient’s technical instructions. Changing the overall context to Belgium would not implement the customer’s requested document or route.
Likewise, a seller with a correspondence office in another country needs to identify which address belongs in the seller record. The form cannot infer establishment or registration relationships from a mailing location. Resolve that identity question before using the selection as a final value.
Recognise a country profile by implemented behaviour
A real country-specific profile would need defined field requirements, mappings and applicable validation, with a clearly identified scope and version. A selector that stores a label is a much narrower feature. Ask what the application actually does after the selection rather than assuming the interface terminology proves national support.
EInvoiceCreator does not currently generate or formally validate country-standard documents. Its printable output, application JSON and line-items CSV remain those same output types regardless of the selected country. It also does not submit through government systems or transmit through Peppol.
Check before export and hand-off
Review seller country, buyer country, context and currency as distinct entries. Compare the address text with the country values. Check any inconsistency against the source instead of normalising it solely for visual appearance.
If the next stage needs formal country codes, additional identifiers or a national profile, include those requirements with the preparation data. The country selection is useful when it preserves a confirmed fact. It becomes misleading when it is reported as proof that tax rules or recipient-specific obligations have been fulfilled.