As previously discussed with Gianna, location ID is steering the address shown on the invoice header. In the paper world, the address is needed as the paper invoice will be sent to the address and person shown. However, within SIS and the e-Invoicing environment this is different.
First of all, we differentiate between billing entity and billed entity – both have:
- a MAIN location
- a UATP location
- some additional locations
Normally the main location should be used, unless another address is needed for the billing and/or billed entity because of legal and tax reasons. This means, that a billed carrier would need a specific address (in the e-Invoicing environment) in case of VAT reclaim, for example.
The IS-IDEC/IS-XML files will include all invoices to a billed entity, regardless of the location ID used. This also applies to IS-WEB.
When processing the IS-IDEC / IS-XML a billed carrier would never use the “location ID” for:
For posting the Charge Category, Charge Code – and as appropriate Charge Code Type, Product ID, Location (= Station where service was provided) etc. – would be used. Please note “Location” is a different field than “Location ID”.
- Routing to the correct station/person/team for checking
The billed carrier would also use Charge Category, Charge Code – and as appropriate Charge Code Type, Product ID, Location (= Station where service was provided). Additionally, only the invoices which cannot be reconciled automatically would be routed to a team/person for manual check.
Hence, when discussing Location ID during the requirements phase, the SIS Miscellaneous WG agreed that even large carriers might not need more than around 15 location IDs.
Hope this clarifies.
Posted: Friday, June 10, 2011 10:24 AM
Subject: Automated initial Location-Id-generation
Dear all, due to a huge number of location-id's we have to define for locations worldwide: it would be very helpful if we could submit the "raw data" in a predefined form (csv) to SIS and the respective location-ids are returned. Manual capture of each and every location is very time-consuming and error-prone. Please think this over - it would be a great help for us. Thank you!