Registration Numbers in XML Input
Determination handles registration numbers in XML input data according to the company role.
If your company has established a registration number for an authority configured in Determination, and you pass in a registration number for the same role on a transaction or establish the registration number on the transaction using a TransEditor, the registration number passed in or created by a TransEditor overrides the registration number you configured in Determination.
For example, if a company has registrations set for France, Germany, and Spain in the database, it only takes one registration in the XML input data to ignore all of the database registrations. If the company creates a Seller invoice and passes in a Seller Registration for Belgium, the company will not be considered registered in France, Germany, or Spain - only in Belgium. If instead of a Seller Registration of Belgium, the input XML included a Buyer Registration for Belgium, all of the database registrations would be used for the Seller and the XMLregistration would be used for the buyer.
These descriptions explain the behavior:
Company Role |
Treatment of Registration Numbers |
---|---|
Seller |
Seller Role registration number The seller registration number in the XML input data overrides a configured seller registration number when:
Buyer Role registration number The configured registration number is used for the seller and joined with the registration number for the buyer to apply both to the transaction when:
|
Buyer |
Buyer Role registration number The buyer registration number in the XML indata overrides a configured buyer registration number when:
Seller Role registration number The configured registration number is used for the buyer and joined with the registration for the seller to apply both to the transaction when:
|
For more information about using registration numbers in XML input, see Invoice Level Input XML Elements and Line Level Input XML Elements.