Setting Up Tax Interface Control
Use Tax Interface Control (29.12.24) to define settings and implementation options for managing the relationship between the QAD ERP application and SUTI.
Important: You must set up GTM before setting up this control program.
Control Settings with Multiple Domains
In QAD ERP versions that support multiple domains, most control settings are specific to individual domains. However, settings in Tax Interface Control affect the entire database. When you enable the API, it is enabled database-wide. However, SUTI is only invoked in those domains where the proper GTM setup has been done. So, for example, SUTI would not affect the tax calculations in a European domain.
Tax elements may be common across diverse geographical regions; therefore, in QAD EE basic tax setup data is defined at database level. This avoids having to repeat similar setup in a multiple-domain environment. See Implementing Vertex with QAD EE
for more information.
Tax Interface Control (29.12.24)
Enter Yes to enable users with access to Quantum to run SUTI.
When this field is Yes, for each user who logs into the QAD ERP application, the system checks the User ID/Group field, also in Tax Interface Control, to determine whether they have access to SUTI. If so, it starts the API. Otherwise, the API does not start.
If you set this field to No, SUTI cannot be started for any user.
Note: Setting this field to No does not close any existing open Quantum sessions.
This field establishes the country code that defaults to tax zone records generated by the Tax Zone Update Utility (29.12.13) for US addresses. Define this value in Country Code Data Maintenance (2.14.1). This field cannot be blank.
This field establishes the country code that defaults to tax zone records generated by the Tax Zone Update Utility (29.12.13) for Canadian addresses. Define this value in Country Code Data Maintenance. This field cannot be blank.
Specify the currency code for US dollars, as defined in Currency Create (26.1.1).
Vertex’s Quantum for Sales and Use Tax system requires transactions to be in US dollars for its calculations. SUTI uses the currency code specified here and its corresponding exchange rates to convert non-US dollar transaction amounts into US dollars for processing by Quantum, and then to convert the resulting tax amounts back into the original transaction currency. This field cannot be blank.
Sums-Into Tax Zone
Specify a sums-into tax zone to default to all tax zone records generated by the Tax Zone Update Utility.
Enter Yes to enable Quantum to identify compressed city names.
Example: When this field is Yes and the city in a QAD ERP address record is Riv Cty, the system identifies it as River City.
For more information about this feature, consult the Quantum user documentation.
Use Primary/Invoice Tax Entity
Indicate which entity code (Primary or Invoice) the QAD ERP application should send to the Sales and Use Tax Interface for sales tax records maintained in the Quantum database.
Primary (the default): Invoice Post sends the value of the primary entity defined in Domain/Account Control.
Invoice: Invoice Post sends the value of the entity associated with the site specified on the invoice header. With this setting, more than one entity can be recorded in the Quantum database.
If your QAD ERP database includes more than one entity and you report taxes by entity, you should set this field to Invoice. In this case, the sales tax reports generated from Quantum by company can be reconciled against QAD ERP general ledger reports by entity.
Use Primary/PO Header Tax Entity
Indicate which entity code (Primary or PO Header) the QAD ERP application should send to the Sales and Use Tax Interface for tax records for the current working domain maintained in the Quantum database.
Primary (the default): Purchase order functions send the value of the primary entity defined in Domain Create.
PO Header: These functions send the value of the entity associated with the site specified on the PO header. With this setting, more than one entity can be recorded in the Quantum database.
If the current working domain in the QAD ERP application includes more than one entity and you report taxes by entity, you should set this field to PO Header. This allows for better control and wider functionality of the Quantum Vertex TDM (Tax Decision Maker) database and associated tax override rates and exemptions.
Use Ship-To for Customer Exceptions
Indicate which customer code (ship-to or sold-to) the QAD ERP application should send to the Sales and Use Tax Interface for finding tax exceptions in the Quantum database.
No (the default): The customer sold-to address is used.
Yes: The customer ship-to address is used.
For sales orders and invoices, the QAD ERP application passes a customer code to the Sales and Use Tax Interface, which is used to locate any customer tax exceptions or customer exemption certificates. Tax exemptions can be set up in Quantum for sold-to customers so that the exemption applies regardless of where goods are shipped. Some users prefer to set up exemptions by ship-to address, since regional jurisdiction may affect exemptions. This setting lets you determine which address code to use.
Use Sold-To for Tax Usage Exceptions
Indicate which customer code (ship-to or sold-to) the QAD ERP application should use to determine the default tax usage code during order processing.
No (the default): The tax usage code associated with the customer ship-to address is used and is passed to Vertex as the customer class exception code.
Yes: The tax usage code associated with customer sold-to address is used and is passed to Vertex as the customer class exception code.
During processing of sales orders, invoices, calls, and return material authorizations (RMAs), a pop-up displays for entry of data used by Global Tax Management to calculate appropriate taxes. Most tax-related values default from the ship-to address, including taxable, tax included, and tax class. The tax environment is based on the tax zones associated with the ship-from site and ship-to address and the tax class associated with the ship-to address.
By default, tax usage also defaults from the ship-to customer. However, in some business environments, the tax usage associated with the ship-to address is not appropriate.
The tax usage code can indicate a tax exemption status for a non-profit or government organization. Some companies normally deliver goods as drop shipment; they essentially ship to their customer's customer. When the sold-to customer is a non-exempt business but the drop shipment is made to an exempt organization, full tax must still be calculated. In this case, the tax usage should be determined by the sold-to customer, not the ship-to customer.
A similar situation occurs when the sold-to is a tax exempt organization such as a government agency but items are shipped to non-exempt subcontractors. In this case, the tax exemption of the sold-to customer should apply.
In these situations, you can set Use Sold-To for Tax Usage Exceptions to Yes so that the default tax usage code is based on the customer sold-to address. If necessary, the default can be modified during order entry.
The setting of this field affects the following programs:
• Sales Quote Maintenance (7.12.1)
• Sales Order Maintenance (7.1.1)
• Pending Invoice Maintenance (7.13.1)
• Call Quote Maintenance (188.8.131.52)
• Call Activity Recording (184.108.40.206)
• Call Invoice Recording (220.127.116.11)
• RMA Maintenance (18.104.22.168)
Zero Tax/Exemptions as Non-Taxable
Specify how taxes set up for individual jurisdictions are handled in the QAD ERP application based on TDM information when tax exemptions or zero tax rates are involved.
Yes: When taxes are set up in Quantum based on VQ-10, VQ-20, VQ‑30, and VQ-40 tax types, both taxable lines with exceptions or exemptions and those with zero tax rate are recorded as non-taxable in the QAD ERP application. See Tax Types
No: This is the default value. Under the same circumstances, the non-taxable information from the TDM is recorded as taxable in the QAD ERP application.
Use Extended Zip Codes
Select this field to enable the use of extended, nine-character zip codes.
Clear this field if you want the system to only recognize standard, five-character zip codes. In this case, if you create an address that has a nine-character zip code, the last four characters are not processed by the system.
Use the second frame of Tax Interface Control to set up security for SUTI functions.
Tax Interface Control (29.12.24)
Use this field to set up security for SUTI functions by password, user, or user group.
Specify individual user IDs or user groups to identify users who can access SUTI functions. Define user IDs and user groups in User Maintenance (36.3.1). The SUTI API is started for each user in this list when they log in to the QAD ERP application.
See User Guide: QAD Security and Controls for more information.
A valid user ID and password are always required.
The asterisk (*) and exclamation point (!) are special characters when used in this field:
• Use the asterisk to give access to all users and groups. A blank operates the same way as an asterisk, allowing access to all users.
• The exclamation point restricts specific users by user ID, not by group. For example: !user1,* means all users except user1 have access to the interface.
• When using the exclamation point, you must enter exclusions first: *,!user1 gives access to all users including user1. To exclude multiple users, enter:
Session ID Examples
shows some examples. Session IDs are not case-sensitive.
Session ID Examples
All users have access.
No users have access.
All users whose session ID begins with payroll have access.
Only users using the session IDs mary and manager have access.
Everyone but the person whose session ID is jcd has access.
Using SUTI with QAD Desktop
If you are planning to use SUTI from the QAD Desktop interface, you must specify an asterisk (*) for the User ID/Group field so that any user can start the interface. This is because the telnet sessions used by the Desktop are potentially shared by many users, so the particular log-in identity is not known soon enough to start the interface when it is needed.