Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Accelerator Authorizations................................................................................. 9
Accelerator program authorizations ......................................................................................... 9
Accelerator Program ................................................................................................................. 9
Special Authorizations ............................................................................................................... 9
Notes ......................................................................................................................................... 9
Any program where a transport is to be created ..................................................................... 9
Ability to create transports ....................................................................................................... 9
Only necessary if you want to create a transport request to save the entries of that screen. 9
Thread Testing Program ............................................................................................................ 9
SM37 Access .............................................................................................................................. 9
SM37 access is needed to view the background job status...................................................... 9
Maintenance Screen Authorization Groups............................................................................ 10
Steps to change the authorization on Vertex tables: ....................................................... 10
Vertex SIC - User Authorization............................................................................................... 11
Overview ........................................................................................................................... 11
Scope ................................................................................................................................. 11
SAP Configuration.............................................................................................................. 11
Configuring Vertex Tax Calculation in SAP for U.S. and Canada .........................16
SAP Configuration.................................................................................................................... 17
Tax Procedure for U.S.............................................................................................................. 19
Tax Procedure for CA............................................................................................................... 20
Specify Structure for Tax Jurisdiction Code ............................................................................ 22
Activate External Tax Calculation ............................................................................................ 22
Assign Tax Codes for Non-Taxable Transaction (OBCL) .......................................................... 23
Tax Codes Setup (FTXP) ........................................................................................................... 23
Terminology ......................................................................................................52
Glossary of Terms .................................................................................................................... 53
Preface
This preface contains information about Vertex services, Vertex® Indirect Tax O
Series®, and its documentation.
Vertex services
Vertex provides the following services:
D
For... Go to...
Document Description
Provides installation instructions for the Tax Accelerator for
Vertex® Indirect Tax Accelerator for
the Vertex® Indirect Tax O Series®.
SAP ERP Installation Guide
Intended audience: SAP technical team (Basis),
Details the process of using the O Series Tax Assist feature
Vertex® Indirect Tax Accelerator for to assign SAP Tax Codes to Value Added Tax (VAT)
SAP ERP Tax Code Mapping User's transactions.
Guide Intended audience: O Series functional team and SAP
functional team.
Provides an overview of the Tax Accelerator and describes
Vertex® Indirect Tax Accelerator for how the Tax Accelerator works with SAP and Vertex®
SAP ERP User's Guide Indirect Tax O Series®.
Intended audience: SAP functional team and/or end-users.
Provides an overview of changes and additions to the Tax
Vertex® Indirect Tax Accelerator for
Accelerator features and functions.
SAP ERP Release Notes
Intended audience: Everyone
Provides information on configuring SAP for Vertex. Covers
Vertex® Indirect Tax Accelerator for authorizations, VAT configuration and US configuration
SAP ERP Implementation Guide tasks.
Intended audience: SAP functional team
Used by Vertex Consulting or other Vertex implementation
Vertex® Indirect Tax Accelerator for
partners to activate the Accelerator.
SAP ERP Activation Guide
Intended audience: SAP technical team (Development)
Accelerator Authorizations
Certain features of the Accelerator require special permissions in order to be run
properly. This section covers any programs which require special authorizations
as well as authorizations needed for SIC and table authorizations.
In this chapter
Maintenance Screen Authorization Groups.................................. 10
Vertex SIC - User Authorization..................................................... 11
Scope
This section outlines the steps necessary to import the role and setup a profile
for that role. The scope of this document shall cover only the role import process
and profile creation. Creating the SIC user and assigning the role are not in the
scope of this document.
There are two Vertex defined user roles:
• Z_VTX_SIC_ROLE – A role with open RFC authorizations. This is the
recommended role because it does not limit the type of RFC the user may
use. This role is somewhat future-proof in the fact that it does not limit the
functions that can be utilized.
• Z_VTX_ACC_SEC_ROLE – A new role designed for Accelerator customers who
are very concerned about security. This role is very limited to just the
function groups used by the Accelerator. This does not account for any new
features that might be added in the future so this role may need to be
changed if any new function groups are added with Accelerator
enhancements.
SAP Configuration
1. Go to transaction PFCG.
5. If prompted with a SAP GUI Security windows that asks if you want to grant
access to the file, just click allow.
6. Click the green check mark.
7. This message will show up at the bottom of the screen when the role
uploads:
8. Create the profile for the role. In that same window click the Change icon.
12. Change the name of the default profile to say VTX_SIC and click the green
check mark.
https://assets.cdn.sap.com/sapcom/docs/2017/01/f07e198b-a17c-0010-82c7-
eda71af511fa.pdf.
The above document explains in detail the configuration steps to compute US and
Canadian Sales & Use Taxes using an external tax system. It covers Standard SAP
Sales & Use Tax Interface System to 3rd party tax packages.
In this chapter
SAP Configuration.......................................................................... 17
Tax Procedure for U.S.................................................................... 19
Tax Procedure for CA..................................................................... 20
Specify Structure for Tax Jurisdiction Code .................................. 22
Activate External Tax Calculation .................................................. 22
Assign Tax Codes for Non-Taxable Transaction (OBCL) ................ 23
Tax Codes Setup (FTXP) ................................................................. 23
CA Input Tax Code ................................................................... 24
CA Output Tax Code ................................................................ 25
Tax Code Properties ................................................................ 25
Default Tax Mapping for CA .................................................... 25
SAP Configuration
Note: Using this guide to implement SAP integration to Vertex O Series requires a good
understanding of SAP FI, SD and MM configuration including tax and pricing procedure setup.
Below is a list of typical SAP configurations required to setup SAP integration to external
system in general. This document provides information on some configuration steps that
requires specific setting for Vertex and may not contain detail on general SAP configuration
steps.
12 OBCL Allocate tax codes for IMG > Financial Accounting > Financial accounting global settings > Tax
non-taxable on sales/purchases > Posting > Allocate tax codes for non-taxable
transactions transactions
13 OVK4 Define tax relevancy IMG > Sales and Distribution > Basic functions > Taxes > Define tax
of master records > relevancy of master records > Control: Materials
Control: Materials
14 OVK3 Define tax relevancy IMG > Sales and Distribution > Basic functions > Taxes > Define tax
of master records > relevancy of master records > Control: Customers
Control: Customers
15 OVK1 Define tax IMG > Sales and Distribution > Basic functions > Taxes > Define tax
determination rules determination rules
16 SPRO Define tax Condition IMG > Sales and Distribution > Basic functions > Pricing > Pricing
Types Control > Define Condition Types
17 OX10 Plant > Define tax IMG > Materials Management > Purchasing > Environment Data >
jurisdiction Define tax jurisdiction > Details
18 M/06 MM > Conditions > IMG > Materials Management > Purchasing > Conditions > Define Price
Define condition Determination Process > Define condition types
Types
19 OMKK Set tax indicator for IMG > Materials Management > Purchasing > Taxes > Set tax indicator
material for material
20 OMKN Assign tax indicators IMG > Materials Management > Purchasing > Taxes > Assign tax
for plants indicators for plants
21 OMKM Set tax indicator for IMG > Materials Management > Purchasing > Taxes > Set tax indicator
plant for plant
22 OBCN Change settings for IMG > Financial Accounting > Financial accounting global settings > Tax
tax processing on sales/purchases > Basic Settings > Check and change settings for tax
processing
23 OMKO Assign tax indicators IMG > Materials Management > Purchasing > Taxes > Assign tax
for account indicators for account assignments
assignments
24 OMKL Set tax indicator for IMG > Materials Management > Purchasing > Taxes > Set tax indicator
account assignment for account assignment
Vertex recommends SAP standard tax procedure TAXUSX to handle US Sales and Use Tax
calculation/postings. If a modification is required due to specific tax requirements, it is best
practice to copy and modify the tax procedure to a new tax procedure and then modify it.
In Canada, four types of sales taxes are levied. These are as follows:
• Goods and Services Tax (GST), a value added tax on the supplies of goods or services
purchased in Canada and levied by the federal government (Revenue Canada).
• Provincial Sales Tax (PST) and Retail Sales Tax (RST) are sales taxes and are collected
and levied by the provinces.
• Harmonized Sales Tax (HST), a consumption tax in used in provinces where both the
federal goods and services tax (GST) and the provincial sales tax (PST) have been
combined into a single value added sales tax and levied by the federal government.
• Quebec Sales Tax (QST), not a true HST, represents federal goods and services tax
and the Quebec sales tax and is considered a value added tax and is levied by
Quebec Province.
Note: Set the RFC Destination according to your configuration. It does not have
to be “VERTEX”.
Update RFC Destination will follow RFC Destination if it is not filled in.
Please maintain Non-Taxable jurisdiction code in OBCL with 7700000000 for US and CA
company codes.
It is also possible to use Tax Relevancy setting in Tax Code Properties (FTXP) to default zero
tax.
Vertex recommends to use standard SAP tax codes for US Sales and Use Tax such as O1, I1,
and U1. Please refer SAP document R3 Tax Interface Configuration Guide for explanation of
setup of these tax codes.
Full Partial
Recoverability Recoverability
Cond. Account
Step Description GL Account
Type Key PST PST PST PST
Paid to Self- Paid to Self-
Vendor Assess Vendor Assess
100 BASB Base Amount
105 Calculated Call
200 Shared with G/L
210 XP1I A/P Sales Tax 1 Inv. NVV
N/A (Distributed
220 XP2I A/P Sales Tax 2 Inv. NVV 100 100 100 100 to Expense)
230 XP3I A/P Sales Tax 3 Inv. NVV
Input tax
240 XP4I A/P Sales Tax 4 Inv. VSF 100 100 GST/HST
250 XP5I A/P Sales Tax 5 Inv. VSC 100 100 Input tax QST
N/A (Distributed
260 XP6I A/P Sales Tax 6 Inv. NVV 100 100 to Expense)
300 Expensed
A/P Sales Tax 1
310 XP1E Exp. ZS1 100 100 100 100 Clearing GL Acct
A/P Sales Tax 2
320 XP2E Exp. VS2
A/P Sales Tax 3
330 XP3E Exp. ZS3 100 100 100 100 Clearing GL Acct
A/P Sales Tax 4
340 XP4E Exp. VS4
350 XP5E A/P Sales Tax 5 Exp VS4
360 XP6E A/P Sales Tax 6 Exp VS4
400 Self-assessment
410 XP1U A/P Sales Tax 1 Use MW1
420 XP2U A/P Sales Tax 2 Use MW2 -100 -100 Input tax PST
430 XP3U A/P Sales Tax 3 Use MW3
440 XP4U A/P Sales Tax 4 Use MW4 -100 -100 Clearing GL Acct
450 XP5U A/P Sales Tax 5 Use MW5 -100 -100 Clearing GL Acct
460 XP6U A/P Sales Tax 6 Use ZW6 -100 -100 Clearing GL Acct
However for Canada input taxes, changes need to be done to the tax-mappings.xml as
follows:
3 – Input QST
4 – Recoverable portion of GST (for partial recoverability requirement)
5 – Recoverable portion of QST (for partial recoverability requirement)
6 – Total non-recoverable (for partial recoverability requirement)
With Accelerator 3.0, it is possible to configure SIC tax mappings inside of SAP (using t-code
/VERTEX/TAXMAPPINGS), which already has the above mapping for CA. Please refer to
Accelerator 3.0 User Guide on how to enable SIC Tax Mapping Configuration in Accelerator.
In this chapter
Overview ....................................................................................... 27
Vertex Tax Procedure for VAT Countries ...................................... 27
Activating Vertex for VAT Countries ............................................. 29
Assign Tax Codes for Non-Taxable Transaction (OBCL) ................ 29
Tax Codes Setup (FTXP) ................................................................. 30
VAT Input Tax Code ............................................................... 30
VAT Output Tax Code ............................................................ 31
Tax Code Properties .............................................................. 31
Default Tax Mappings for VAT .............................................. 31
SD Access Sequence for VAT ......................................................... 31
SD Pricing Condition Types for VAT............................................... 32
SD tax determination rules for VAT .............................................. 36
Sales and Distribution condition records for VAT ......................... 36
Sales and Distribution Pricing Procedure for VAT ......................... 37
Overview
SAP standard integration with external tax system was built for tax calculation with
jurisdiction code (U.S. and Canada) only. However, the need of using external tax system for
other countries than U.S. and Canada is raising, especially for multinational companies.
Vertex addresses this requirement with Accelerator, which make it possible to use Vertex for
VAT calculation using SAP’s built-in external tax integration for U.S and Canada, but without
the need to use tax jurisdiction code.
Configuration steps required to enable Vertex for VAT in many ways is similar with U.S. and
Canada activation. This section provides information on settings that are specific for VAT
countries.
For Hybrid tax (mix of Value Added Tax and sales tax) please use the same tax procedure as
for Canada. Sample of country with hybrid tax is China.
It is recommended to copy the tax procedure for each countries in scope, although it is
possible to use one tax procedure for more than one country.
Note: Condition ZVT2 and ZSA2 are optional. These condition types are only required to
handle partial recoverability on AP invoices.
Copy condition XP4I to ZVT1, enter text (example: Vertex Input VAT) and save. This will be
used for Input VAT.
1. (Optional) Copy ZVT1 to ZVT2, enter text and save. This will be used for the non-
recoverable portion of input tax paid to vendor.
2. (Optional) Copy XP4U to ZSA2, enter text and save. This will be used for the non-
recoverable portion of input tax paid to vendor (to offset Input VAT GL Account).
3. Copy ZVT1 to ZRC1, enter text and save. This will be used for reverse charge (input
acquisition).
4. Copy ZSA2 to ZSA4, enter text and save. This will be used for reverse charge (output
acquisition).
5. Copy condition XR1 to ZAR1, enter text and save. This will be used for Output VAT.
Please make sure Non-Taxable jurisdiction code in OBCL is blank for VAT company codes.
Unlike tax code for US or CA (jurisdictional) that has Tax Relevancy setting in Tax Code
Properties (FTXP) to default zero tax (by setting it to ‘2’), SAP hides this field in tax code
properties for countries with non-jurisdictional setting.
In order to default zero tax for VAT tax code other maintaining the tax code in OBCL (OBCL
can only be setup with one tax code), it can be configured with Accelerator setting: Country
Tax Code Setting (/VERTEX/TCI). Please refer to Accelerator 3.0 User Guide for detail on this
setting.
For VAT countries Accelerator has Dynamic Tax Code functionality with following benefit:
1. Any sales or purchase process can be setup with one tax code: the calling tax code.
One calling tax code for sales/AR, and one calling tax code for purchase/AP.
2. Vertex O Series decides taxability and determine a new tax code (response tax code)
according to tax result, and send it back to SAP.
3. Accelerator changes/flips the calling tax code to the response tax code within the SAP
transaction/document.
Refer to the next page for the Vertex recommended VAT tax code setup:
However to handle partial recoverability, a new tax-mapping need to be added to the tax-
mappings.xml as follows:
2 – Non Recoverable VAT
Create the new SD access sequence for VAT, e.g. ZVTX, or copy existing access sequence
(such as MWST or UTX1) based on tax requirement. In most cases, condition table 2
(Domestic Taxes) is sufficient to default the calling tax code.
Similar to pricing condition RVAXUD, Vertex recommends to use formula 500/501 so Vertex
is called once for multiple items, although there is no max tax requirement for VAT.
1. Copy condition type UTXJ to ZTXJ, and assign the access sequence created in
previous step.
2. Copy condition UTXD to ZTXD, assign the same access sequence as for ZTXJ, and
enter ZTXJ as the reference condition type (RefConType).
Specify the tax category ZTXJ for tax determination rules for VAT on the Define Tax
Determination page as shown in the following example:
Maintain condition record to default the tax code to calling tax code.
For all tax relevant VAT pricing procedures, add following Vertex condition types and formula
below:
Condition
Value
Type
ZTXD 500
ZTXE 501
ZAR1 301
The following figure provides an example page with these values entered.
In this chapter
Freight Handling ............................................................................ 39
Freight on a Separate Line ........................................................ 39
Freight Included on the Line ..................................................... 39
Freight and the Document Currency Feature ........................... 40
Surcharge Handling ....................................................................... 41
Surcharges and the Document Currency Feature..................... 42
Freight Handling
SAP can apply tax on freight charges in two ways, each with advantages and disadvantages.
Using separate freight line items offers the advantage of calculating freight taxability on the
basis of a taxability driver (product class) in O Series. You may prefer to do this when the
freight taxability scenarios are particularly complex.
In the example below freight condition type is copied into subtotal 4 in the pricing procedure
and map it using the Accelerator Data Mapping tool into the FREIGHT_AM field.
If freight is included on the line item as freight condition type, a child line item for freight will
be generated by SIC.
SIC takes the tax base amount & freight amount and calculates a Sales or Use tax for each by:
• Forming a child line for each line item in the call to SIC when creating the O Series
XML request.
• Using the same parameters for the child line as the parameters that were entered in
the parent line, with the following exceptions:
o ExtendedPrice - Uses the SAP FREIGHT_AM parameter instead of AMOUNT.
o lineItemNumber - Uses the SAP POS_NO parameter plus the FreightOffset
value in the SIC configuration file (10000000 is the default value).
o productClass - Uses the FreightCode value in the SIC configuration file.
(SAPFREIGHT is the default value)
o productCode - Uses the parent line’s productClass.
o Quantity - Defaults to 1.
• If the FreightIncluded parameter in the SIC configuration file is set to true, SIC
subtracts the freight amount from the amount in the parent line item.
• When the calculation is done, tax amounts for the freight component are added to
the corresponding tax amounts for the parent line item. This is done because SAP
cannot accept the freight child line item separately.
Surcharge Handling
Surcharges work in a similar fashion to freight with a few minor differences:
• Surcharges only work for sales transactions.
• /VERTEX/SUR_CODE(1-5) - Pass the product class for the surcharge to this field in the
Data mapping tool.
• /VERTEX/SUR_AMT(1-5) - Pass the surcharge amount to this field in the Data
mapping tool.
In the below example we mapped a hard coded value of HANDLING to /VERTEX/SUR_CODE1.
We then mapped the KOMP-KZWI1 amount to /VERTEX/SUR_AMT1 for the child line’s
ExtendedPrice. Make sure to check the Numeric checkbox as the /VERTEX/SUR_AMT1 is a
string field data type. We used a condition which checks if handling fee is greater than zero.
In this chapter
Vertex Configuration Settings ....................................................... 44
SIC Tax Mapping Configuration ................................................. 44
Accelerator Parameters GUI ..................................................... 45
TXJCD Lookup and Address Cleansing .................................. 45
Data Mapping Configuration ................................................ 46
Location Fields – Sales / AR................................................... 46
Location Fields – Purchasing / AP ......................................... 47
Customer & Vendor Registrations - Customer ..................... 47
Customer & Vendor Registrations - Vendor ......................... 47
Tax Jurisdiction Code Conversion Setup (ADRC)................... 48
Logging .................................................................................. 49
VAT Specific Requirements ................................................... 49
Company with VAT and US/CA Registrations ....................... 50
Vertex Data Mapping .................................................................... 50
Vertex Queue Monitor .................................................................. 51
Logging
Intercompany Billing
Terminology
This chapter lists all of the abbreviations and SAP/Accelerator/O Series terminology and a
description for each.
In this chapter
Glossary of Terms .......................................................................... 53
Glossary of Terms
Term Description
This refers to the Vertex developed SAP Integration Component. It is the
connector that takes SAP RFC and translates it to XML and vice-versa. It allows
SIC SAP to send tax calculations and jurisdiction lookups to O Series and get the
responses back in SAP. This is mandatory if you want to use Vertex as an
external tax system.
SAP Transaction Code for the main SAP configuration settings. This is where
SPRO most SAP configuration is done when setting up an external tax system to
communicate with SAP.
Another name for the Accelerator reports. This name was developed by LCR-
SPOT
Dixon who created and maintains the Accelerator reports.
The O Series Tax Journal. This is where all posting transactions are stored until a
Journal
Tax Journal Export is run to move them to the O Series reporting database.
Abbreviation for web services. O Series uses web services to do many of the
functions for Accelerator. Some examples are: CalculateTaxDoc – where the
WS calculations go, LookupTaxAreasDoc – where jurisdiction lookups go and
VertexVersion70 – where the O Series version information is pulled from the
Accelerator version list program.
Abbreviation for Value Added Tax. A type of consumption tax that is collected
VAT incrementally, based on the surplus value, added to the price on the work at
each stage of production. This tax type is used outside of the United States.
Vertex Tax Area ID. A unique identifier for a tax jurisdiction. This is what
TAID
populates the SAP Tax Jurisdiction Code field.