Siebel Order Management Guide > Integrating Order Management with Third-Party Taxation Applications > Taxware Integration with Siebel eSales >
Taxware Adapter Business Service
The Taxware Adapter Service business service:
- Receives input from the Tax Calculator business service in XML format.
- Passes the following information to Taxware:
- Static information from the Tax - Configuration (Taxware) integration object
- Dynamic information from the Tax Integration (Taxware Input) integration object
- Receives information back from Taxware.
- Passes XML data back to the Tax Calculator business service.
The Taxware Adapter Service consists of the following methods:
- CalculateTax. This is the main method for calculating the tax. It converts the input XML string to a property set and calls the Taxware software to get the tax information as a property set. It then converts the tax information to an XML string as an output.
- Initialize. This method uses the input property set to initialize the variables for the business service.
- OpenClose. This method opens and closes files used by Taxware to calculate taxes.
Taxware uses an Audit File to store transactional information for tax reporting purposes. The Audit File for Sales/Use is a text file that you can edit. There is a special editor for the WORLDTAX Audit File that marks transactions that have been altered.
When calculating taxes in Siebel eSales, set the audit file indicator (AUDFILEIND) to 2 (No Record) because the customer has not yet confirmed the order.
To write to the audit file, a separate call to Taxware must be made from the order. This setup requires creating Order integration objects and mappings to the Taxware integration objects.
You can set the value for AUDFILEIND by changing the value in the Tax - Configuration (Taxware) integration object user properties. For orders, you can set a separate default value in the data mapping.
Address Verification for Taxware
Completion codes are returned that indicate the status of the process running UTL if one of the following occurs:
- The customer enters an improper city/state/zip combination.
In most cases the completion code appears, indicating that a jurisdiction error occurred, which means something was wrong with the zip/state combination.
- The customer enters a city/state/zip combination that maps to more than one jurisdiction.
Taxware defaults to the most likely match and applies that rate for the transaction. The application generally uses the jurisdiction with the highest population, as rates for heavily populated areas are usually higher than those for areas with less population. However, the default rate used is not always the highest rate out of the possible matches.