Skip to main content

Oracle R12 E-Business Tax (EBTax): Considering an Upgrade or New Implementation?

Oracle R12 E-Business Tax (EBTax): Considering an Upgrade or New Implementation?



New features
Several new features are available through E-BusinesTax that improvfunctionality including tax repository guided configuration, tax rules, and fiscal classification.

Considering an Upgrade or New Implementation?


There are two optionfor taconfiguration when upgrading froOracle 11i to Oracle R12:
1. Use upgraded E-BusinesTax
2. Configure new implementation of E-BusinesTax


Option 1: Upgraded E-Business Tax


Choosing to use the OraclE-BusinesTax upgrade configuration offers Oracle customers the ability to continue to use the current business tacalculation design and configuration methodology posupgrade. The concept of using tax codes assigned tcustomerssuppliers, oinventory items will remain the same post upgrade.

Previously, taconfigurations were housed in the Oracle Receivables or OraclPayables modules. After upgrading to R12, all taconfigurations are migrated to Oracle E-BusinesTax in a central location.

From an implementatioperspective, this option involves thfollowing:
 Assess impact to existing customizations and reporting
    Review master data anOracle E-Business Tax configuratiopost upgrade
    Identify modifications or new setups in additioto the upgrade configuration

Example of the Oracle E-BusinesTax setup that results as a part of the R12 upgrade from 11i:



Option 2: New Implementation of E-Business Ta

Configuring Oracle R12 E-BusinesTax as a fresh installation offers the ability to utilize new functionality introduced as a part of R12. Where the automation of tacalculation was limited in prior Oraclversions, R12 offers the ability tocreate multiple tax rules and reduces the amount of ongoing setups required to calculate taxes.

From an implementatioperspective, this option involves the following:

    Gap analysis of E-Business Tax functionality to current anfuture business requirements

 Solution design anE-Business Tax module configuration

 Assess impact to existing customizations and reporting


Considerations foEach Approach

The decision to upgrade should be based upon the followinkey factors:

 Project implementation timeline

 Business and system needs to scale with tax law changes oexpansions into new regions coverebdifferent tax laws

 Need for automatic tax calculation




Option 1: Upgrade E-
Business Tax
Configuration
Option 2: Reconfigure E-
Business Tax
Pros
 Faster implementationtime
 Minimal work tomaintaicurrent taxcalculation requirements
 Fewer changes to enduser and low impact fortraining
 Automation of tax decisionsthrougcreation of tax rules
 Flexibility to createconditional tax rules basedupon party product, processoplace
Cons
 Restrictions on creatingnew tax rules and modifyingexisting tax rules
 Restrictions fotaxpartner integrations suchas Vertex or
Taxware
 Full implementation ofOracle TCA geography hierarchy and E-BusinesTax
 Longeimplementation timeframe
 Required data clean up onmastedata




New Features and Benefits of E-Business Tax


E-BusinesTax is a single-point solution for managing your transaction-based tax requirements. It delivers tacontent to alEBS Businesflow through one application interface. It reduces the tax configuration time and resolves complex tosimple adjustments needed from changes in local jurisdiction, legislation, ratesand exceptions for products and customers. This ensures a uniform tasetup across applications, with a centrally managed system of automated tax services andcontrol over manuaintervention and update. New features of E-BusinesTax include:

Tax Repository


    Is part of the single source of transactional tax information (i.e. Tax lines) for all calculated E-Business Tax

 Allows for calculated taxes, parties involved to be stored in location

 Allows for tax reporting, tax accounting, antax reconciliation

 Is the underlying infrastructure for users to see and/or modif(override) tax lines

 Guided Configuration


    Provides Home Page to guide the user through a stebstep process of configuration

    Home Page allows access to other models to gain pre anpost requisites configuration required for tax configurations

Self Assessment/Reverse Charge


 Allows for transactions to capture Use Tax in the US or ReversCharges in Europe

    Adds tax line that will not be part of the Payable transaction total, buwill be booked in if Use tax or Reverse Charge should be assessed on invoice   that originally did not have taxes from supplier

 Tax rules


 Allow for complex tax legislations to be met

 Can be derivebdate effectiveness

 Can produce guideor expert configuration flows

    Include several type of rules such as Place of Supply, Tax Calculation, and Tax applicability

 Fiscal Classification

Consists of Party, Product, Process, oPlace (the 4 Ps)

    Party  E-Business Tax allows for link in Fiscal classificatiotypes for existinparties categories in TCA

 Product  Allows for classificatioof existing inventory categories onon-inventory item classification codes

 In addition, defining specific intended usage

    Transaction (Process)  Allows certain Transaction Business Categories to hold generic classification where tax cabe very specific in its requirements

    Place  This parameter is used in identifyinthe above focus othshipper, receiver, from the order to cash/procure to pay process


Tax Simulator

E-BusinesTax provides a way to test new rules out without impacting your production instance (Live Instance).

Tax Jurisdiction

This allowfor the defining of specific geographies for tax and taxing authorities.

Content and Services Subscriptions

This permits third-party software and services to connect with EBusiness Tax.

Events and Configuration Owner Options

E-BusinesTax helps control tax configure informationsuch arounding and units.

Multiple Tax Registrations

This allowseveral parties to have several tax registrations.


Comments
You do not have permission to add comments.

Comments

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...