Skip to Main Content
Return to Navigation

Understanding VAT

This section discusses:

VAT Functionality

VAT is used in many countries around the world. VAT is a governmental sales tax, a straight percentage that is added to the cost of goods or services. VAT can be inclusive, in which case VAT is included in the price of goods or services, or exclusive, in which case VAT must be added to the price of goods or services.

The core concept of VAT is simple: at each step in the supply chain, VAT is calculated by multiplying the cost of the goods or services by the tax rate and then charged by the seller to the buyer; normally, at each step in the supply chain except the last, the buyer can recover the VAT incurred. VAT charged by the seller and remitted to the government is referred to as output VAT , while VAT incurred by the purchaser and potentially recoverable from the government is referred to as input VAT. The application of the tax can be complex because each country has specific requirements. PeopleSoft global VAT functionality fully supports these country-specific requirements.

To implement VAT effectively in Oracle's PeopleSoft Financials and Supply Chain applications, you must fully understand the legislation governing VAT in the applicable countries before implementing the applications.

To use VAT in PeopleSoft applications, you must first set up the VAT environment. You can then create various VAT documents, such as sales orders, customer invoices, purchase orders, and vouchers. You can also record VAT for employee expense reports, asset retirements (in case of sale), bank fees incurred, and general ledger journal entries.

The VAT on these documents and transactions is calculated based upon the information that you enter. For example, the VAT codes that you enter determine the VAT rates that the system uses to calculate the VAT amount. In PeopleSoft Purchasing, Payables, Treasury, Expenses, and General Ledger, the VAT use type that you enter partly determines the amount of VAT that is recoverable.

The VAT information on all transactions and documents is loaded into the VAT transaction table by a background process and by a second process into the VAT reporting tables, from which you can create VAT returns and other VAT reports.

PeopleSoft applications enable an organization to effectively administer VAT by:

  • Charging VAT on invoices to customers, recording VAT collected from customers, and paying and recording VAT charged by suppliers.

  • Determining what percentage of VAT paid on purchases is recoverable to offset the amount of output VAT that must be sent to VAT authorities.

  • Accounting for and reporting both the VAT paid on purchases and the VAT collected on sales.

To implement this functionality, you must be able to enter transactions into the system, correctly calculating and recording the VAT. You must also be able to report VAT correctly on the VAT return as well as account for it correctly.

Taxable Status and VAT Rates

In PeopleSoft applications, you identify the taxable status for a given transaction by specifying the VAT applicability for a transaction line. This table lists the system-defined values that are provided:

VAT Applicability

Description

Taxable

VAT is chargeable either at a zero or nonzero rate.

Exempt

Item is nontaxable or exempt from VAT, and no VAT is charged.

Exonerated

Used when the purchasing organization has been exonerated from paying VAT. This value is the same as taxable at a zero rate.

Outside Scope of VAT

Item is outside the scope of VAT, and no VAT is charged.

Suspended

Used when the purchasing organization has been granted suspension from paying VAT. This value is the same as taxable at a zero rate.

VAT-Only

This value is applicable only within PeopleSoft Payables when you enter a third-party voucher and within PeopleSoft General Ledger when you enter a journal line against a VAT account.

Not Applicable

This value is valid only for transactions that are completely non-VAT applicable.

For taxable lines, VAT must be calculated at the rate applicable to the goods or services being sold or purchased, as defined by the tax authorities in each country.

Within the PeopleSoft VAT environment, you define VAT rates at the VAT authority. One or more VAT authorities may be combined under one VAT code. The total of the VAT rates specified on all the associated authorities is the VAT rate applicable to that VAT code. A VAT code is applied to a transaction line, which enables VAT for that line to be calculated at the rate specified for that VAT code.

VAT Reporting and Accounting

Three key VAT setup elements facilitate VAT accounting and reporting: VAT codes, VAT accounting entry types, and VAT transaction types. These setup elements are used in combination by the PeopleSoft VAT report definitions to determine the information to be included on each line of the VAT return. To facilitate reconciliation between the general ledger and the VAT return, these elements are also used in combination to determine the ChartFields to which VAT amounts are posted.

VAT Codes

You use VAT codes to specify the rate at which VAT is calculated.

The VAT rate is frequently the key to reporting VAT because VAT amounts must often be reported separately by VAT rate on a VAT return. Therefore, the VAT code is part of the reporting definition.

To facilitate reconciliation between the general ledger and the VAT return, VAT amounts are usually recorded separately by VAT rate in the general ledger. For this reason, you define VAT accounting information (also referred to as the VAT accounting template) by VAT code.

VAT Accounting Entry Types

In addition to requiring that VAT amounts be reported separately by VAT rate, your VAT return may require that VAT amounts for certain types of transactions be reported separately. For example, you may need to report adjustments made to VAT or VAT recorded on advance payments separately.

Again, to facilitate reconciliation between the general ledger and the VAT return, VAT amounts are usually recorded separately in the general ledger for each of the different types of transactions.

VAT accounting entry types are one of the mechanisms used to enable the correct reporting and accounting of these transactions. These are system-defined values that identify the different types of VAT accounting entries that may be required (for example, input-recoverable, input discount adjustments, output, output on credit memos, or output for purchases).

When you define VAT reports, VAT accounting entry types are used to identify the general types of transactions that should be included on any given line on the VAT return. For example, you might specify that input-recoverable VAT amounts be included on one line of the return while output VAT amounts be included on another line.

For accounting purposes, you define VAT accounting information for each of the VAT accounting entry types defined in the VAT accounting template. The accounting entry types available in this template are determined by the PeopleSoft applications you have installed. Not all of the VAT accounting entry types apply to your organization, so you can define dummy VAT accounts for those that do not apply.

Note: This chapter includes a table that lists the delivered VAT accounting entry types.

See VAT Environment Setup.

VAT Transaction Types

You use VAT transaction types to classify and categorize transactions at a more detailed level for both VAT reporting and accounting. These are specified for each transaction line when you enter a transaction.

You define the VAT transaction types that you need for your VAT setup. PeopleSoft software also provides a set of VAT transaction types as sample data.

In your VAT reporting definition, you use VAT transaction types to fine-tune the information that you want to include on a given line on the VAT return. You can do this by specifically including, or effectively excluding, certain types of transactions. For example, if you are located within the European Union (EU), you may need to report self-assessed output VAT for intra-EU acquisitions on one line in the return, while reporting self-assessed output VAT for services provided by foreign suppliers on another line. For both lines on the report, you indicate that you want to include transaction lines with a VAT accounting entry type indicating VAT Output on Purchase. For the first line, you also indicate that you want to include only those transactions that are flagged with a VAT transaction type indicating an intra-EU acquisition. For the second line, you indicate that you want to include only lines flagged with a VAT transaction type indicating a service provided by a foreign supplier.

For accounting purposes, VAT accounting information defined for each given VAT accounting entry type is applicable for all VAT transaction types unless it is overridden at the more detailed VAT transaction type level. In the cases in which you need to record VAT amounts in the general ledger at the more detailed level, you can indicate that VAT amounts for a given VAT accounting entry type be posted to different sets of ChartFields defined for each specific VAT transaction type.

VAT Recoverability

Another key component that you must put in place are the rules that determine whether input or purchase VAT can be recovered, and if so, how much.

Whether the VAT paid on any given purchase is recoverable depends on two factors: the nature of the purchased goods or services and how the purchased goods or services are to be used. In some countries, you cannot fully recover the VAT paid for specific items, regardless of how they are used. For example, in the United Kingdom (UK), you are unable to recover input VAT incurred on business entertainment expenses, regardless of the taxable status of your business activities. You can achieve this functionality within PeopleSoft VAT defaults setup by defining inventory items and expense types that are not 100 percent recoverable.

If goods or services are used in a taxable activity (for example, an activity that ultimately results in the production of a taxable product), then VAT paid on the purchase of those goods or services is recoverable. But if the goods or services are used in a nontaxable or exempt activity (for example, an activity that ultimately results in the production of a nontaxable product), then the VAT paid on the purchase of those goods or services is not recoverable. Sometimes, purchased goods or services are used in a mixture of taxable and exempt activity. In this case, the VAT paid on the purchase of those goods or services would be partially recoverable.

In Canada, certain public service organizations, categorized as public service body types, are eligible to reclaim an additional portion of their input VAT that would normally be nonrecoverable. This eligibility is called a rebate. Each Canadian VAT authority has established its own set of rebate percentages by public service body type to be used in the calculation of VAT rebates.

Two ways that you define the usage portion of recoverability are the VAT use type and VAT apportionment.

VAT Use Type

The VAT use type identifies the end use of a given purchase by defining how much of a given activity or use is taxable, and how much of that activity is exempt, based on the tax status of the goods or services ultimately produced from those procured. In general, you specify the use type for each transaction line, thereby indicating how the purchased good or service on that line is used.

You can specify the ratio of taxable activity to nontaxable activity directly on the use type, or you can specify that mixed apportionment be used to define the ratio of taxable to nontaxable activity at the ChartField level, if you are required to calculate recoverability at a detailed level.

The VAT use type must also be linked to a public service body type for public service type organizations in Canada to retrieve the appropriate rebate percentage for transactions with exempt activity.

VAT Apportionment

VAT apportionment is based on the idea that the usage of a given good or service can be determined based on the business unit or the ChartFields to which the purchase or expense is charged. In other words, usage can be determined based on which business unit, department, or project might be using the purchased item.

You do not need to set up VAT apportionment information unless you are required to calculate your recoverable VAT at a very detailed level. If you elect to use VAT apportionment to calculate recoverability, you first determine a priority 1 ChartField and a priority 2 ChartField to be used in determining recoverability (for example, department or project). You can choose to define the ratio of taxable to nontaxable activity only at the business unit level. VAT apportionment information defined at the business unit level can be overridden by information defined at the more detailed ChartField level. When defining VAT information for either the priority 1 or priority 2 ChartField, you specify the ratio of taxable activity to nontaxable activity for any given ChartField value (or portion of a ChartField value—for example, all department IDs that begin with 10).

When a VAT use type that indicates VAT apportionment is specified for a line, the system looks for a match in the VAT apportionment data for the value specified first in the priority 1 ChartField and, if not found, then second in the priority 2 ChartField. If a match is still not found, the system looks for a match in the business unit. If a match is found, the system uses the ratio of taxable to exempt activity defined for that ChartField or business unit value to calculate the recovery and rebate. However, if no match is found, the system treats the line as 100 percent nonrecoverable. For this reason, it is imperative that you specify enough VAT apportionment data so that a match is always found.

The system uses either the transaction business unit, the transaction's general ledger business unit, or the distribution line general ledger business unit to access VAT apportionment information, based on the type of business unit that you define as the VAT apportionment control for the PeopleSoft Payables, Purchasing, General Ledger, Expenses, and Treasury business unit VAT drivers in the common VAT defaults table.

Calculating Recovery and Rebate

In addition to the rebate rates defined for public service bodies (PSB) and any recovery rate that may have been defined for the individual item or expense, the system uses the percentages defined for taxable and exempt activity to calculate the recovery and rebate percentages that are then used to calculate the recoverable and rebate VAT in the following way:

  • VAT recovery percent is calculated as [(item recovery percent/100) × (taxable activity/100)] × 100

  • VAT recovery amount is then calculated as gross VAT amount × (VAT recovery percent ÷ 100)

  • VAT rebate percent is calculated as [(item recovery percent/100) × (exempt activity percent/100)] × PSB type rebate rate

  • VAT rebate amount is then calculated as gross VAT amount × (VAT rebate percent ÷ 100)

For example, for a school in Ontario, Canada, the rebate rate is 68 percent. If the school incurred input VAT in the amount of 250.00 CAD for an item defined as recoverable at 50 percent and it was associated with a VAT use type with a taxable activity percent of 75 percent, then the result would be:

VAT recovery percent = 
((50/100) x (75/100)) x 100 = (.5 x .75) x100 = 37.5 = 37.5%
VAT recovery amount = 250.00 x (37.5/100) = 250.00 x .375 = 93.75
VAT rebate percent = ((50/100) x (25/100)) x 68 = (.5 x .25) x 68 = 8.5 = 8.5%
VAT rebate amount = 250.00 x (8.5/100) = 250.00 x .085 = 21.25

(When you calculate the VAT rebate amount, the rebate percentage is applied against the gross VAT amount, rather than the nonrecoverable VAT amount, because the exempt activity percentage was taken into account when you originally calculated the rebate percentage.)

This example involves calculating the PSB type rebate rate with a VAT code that is made up of multiple VAT authorities, each with its own individual rebate rate. In this example, the rebate rate is calculated as the sum of (VAT authority rebate rate × VAT authority tax rate) for each VAT authority within the VAT Code divided by the sum of (VAT authority tax rate) for each VAT authority within the VAT Code. (VAT authority rebate rate × VAT authority tax rate) for each VAT authority within the VAT Code) ÷ (sum (VAT authority tax rate) for each VAT authority within the VAT Code).

For a school in New Brunswick, Canada, the PSB rebate rate would be calculated as:

 ((68 x 7) + (0 x 8)) / (7 + 8) = 476 / 15 = 31.73 

VAT Defaults

Based on the VAT rules that apply in different business scenarios, the system is designed to automatically provide as much VAT information as possible about a transaction. For the system to determine which scenario and VAT rules are applicable to a given transaction, you must set up various VAT defaults and other VAT-related pieces of information.

This PeopleSoft application delivers a VAT structure for defaults that:

  1. Defines most of the setup structure as predefined system data, including the fields relevant to VAT; the VAT drivers, such as items, products, customers, suppliers, and business units for which certain VAT defaults can be specified; and the transaction-specific hierarchies for defaults.

  2. Stores as user data the individual factors that make up much of the VAT rules, for example, how VAT must be calculated, when VAT must be declared, how VAT must be recorded, and whether purchase VAT can be recovered. Data considered to be an attribute of VAT drivers, for example, customer VAT registration information, is stored in the application VAT table of defaults, while all VAT data is stored in a common VAT table of defaults.

  3. Contains the logic dictated by the various VAT authorities to determine the VAT information that is conditionally based on a combination of factors. For example, once all the country, VAT registration, and VAT exception data is retrieved, the system can determine the VAT treatment. The system automatically supplies as much VAT information about a transaction as possible, either retrieved from the stored defaults or derived from the logic, based on the VAT values already associated with the transaction.

Note: This chapter contains a table listing the VAT drivers for which you can define defaults and the associated VAT controls and defaults.

VAT Defaults and the Organizational Structure

VAT drivers and the organizational structure affect VAT transactions.

VAT Reporting and Registration Countries

Before the system can determine the VAT treatment, it must first determine the VAT reporting country and, if applicable, the VAT registration country for the trading partner.

For sales and procurement transactions for which the physical nature is goods, this determination is made based on whether each trading partner is registered in the ship to country, the ship from country, or both, taking into account the rules that apply both within and outside of the EU.

For sales and procurement transactions for which the physical nature is services, the process is more complex. For freight transport services within the EU, the system determines whether each trading partner is registered in the ship to country, the ship from country, or both. For other types of services, the system looks at where each trading partner's business is established, where the service is physically performed, and where the VAT is most often liable for the type of service being provided.

If the system is unable to determine the VAT reporting country based on the applicable rules, it uses the VAT registration country designated as the home country for the VAT entity. If no country is defined as the home country, the system displays an error message. A valid VAT reporting country must be specified for processing to continue.

The VAT reporting country is also important because it is the main driver for retrieval of VAT defaults from the VAT defaults table.

Services Place of Supply Country

The place of the supply country is another factor in determining the VAT treatment for sales and procurement transactions with a physical nature of services. This is the country in which the VAT is liable for the service. The system determines the place of supply country by looking at the countries in which both trading partners are registered for VAT, the countries in which both trading partners have established their businesses, the type of service being provided (freight transport or other), and where the VAT is most often liable for the type of service being provided.

VAT Exceptions

You also need to consider whether the purchasing organization has been granted some type of exemption from paying VAT. These exemptions, referred to within PeopleSoft applications as VAT exceptions, take the form of either an exoneration or suspension from paying VAT. An organization may be exonerated from paying VAT because of the nature of its business. For example, a government agency may be granted exoneration from paying VAT. In certain countries, such as France, an organization may be granted a temporary suspension from paying VAT because it regularly has a much higher level of recoverable input VAT (as opposed to output VAT) and would always receive a large VAT refund. By granting suspension from paying the input VAT, the refund is either reduced or eliminated.

You can specify whether a VAT exception is applicable to a customer or VAT entity, as the purchasing organization, and, if so, if that exception is an exoneration or suspension from paying VAT. If a valid exception is applicable to a transaction, the transaction uses this information to apply the appropriate default zero-rate VAT code and VAT transaction type.

VAT Treatment

Once the VAT reporting country is known, the main driver for processing VAT on sales and procurement transactions is the VAT treatment. This determines which default values to apply and also controls, to some extent, the availability of some VAT-related fields.

In addition, many countries are required to report the sale and purchase of goods separately from services. To support this requirement, PeopleSoft enables you to distinguish between transactions involving goods and transactions involving services.

For a sale of goods, for example, when the system determines the VAT treatment, it looks first at the combination of the ship-from and ship-to countries. The system then looks at the countries in which the buyer and seller are registered for VAT. If the ship-from and ship-to countries are the same and, in procurement, if the supplier is registered for VAT in that country, then the transaction is treated as domestic. If the supplier is not registered for VAT, the transaction is treated as outside the scope of VAT. If the ship-from and ship-to countries are different, the system determines whether both countries are located within the EU. If they are, the system looks at the VAT registration for each trading partner to determine whether the transaction should be treated as an intra-EU sale or purchase, distance sale, domestic, or outside the scope of VAT. If either or both of the countries are located outside of the EU and, in procurement, if the supplier is not registered in the ship-to country, then the transaction is treated as an export or import. If the supplier is registered in the ship-to country, the transaction is treated as domestic.

The determination of the treatment of services for the purposes of VAT varies a great deal more than for the treatment for goods. For services, when both the supplier and the customer are located in the same country and the services are physically performed in that country, the treatment is the same as the domestic VAT treatment for goods. However, the VAT treatment for services differs from the VAT treatment for goods when the services are performed by a foreign supplier (a supplier not registered in the customer's country).

In the case of services that are performed by a foreign supplier, no tangible goods can be stopped at the border. To deal with this, the requirement in many countries is for the customer to self-assess the VAT due on the supply of services. While this procedure is similar to that for intra-EU acquisition, differences exist. Intra-EU acquisition applies only when goods are moving between countries within the EU and when both trading partners are registered for VAT in the EU. The requirement to self-assess VAT on services performed by foreign suppliers exists for both EU and non-EU countries. Additionally, for customers in EU countries, VAT may be self-assessed on services performed by any supplier that is not located and not registered in the customer's country—regardless of whether that supplier is located in the EU.

Part of the process of determining whether the customer must self-assess the VAT is determining the place of supply of the service, as described previously. For service purchases, if the VAT reporting country is the same as the place of supply country, the purchasing organization records VAT on the purchase transaction. Whether this is self-assessed or not depends on whether the supplier is also registered in the place of supply country. If the place of supply country is different from the VAT reporting country, the transaction is recorded as outside of scope. For the sales of services, if the VAT reporting country is the same as the place of supply country, VAT is charged to the customer, as applicable. However, if the place of supply country is different from the VAT reporting country, the sale transaction is treated as either outside of scope or zero-rated, based on how the VAT reporting country is defined in the VAT country table.

Within PeopleSoft software, detail VAT treatment values on the transaction lines are used for applying the precise defaults applicable to the transaction lines. Each of these detail VAT treatment values is associated with a VAT treatment group. The system tracks the VAT treatment group on the header for PeopleSoft Billing, Receivables, and Payables transactions. The VAT treatment group allows individual transaction lines to be grouped together into invoices during batch processes and validates the detail line VAT treatment values on the transaction lines.

Domestic Reverse Charge

Some countries, such as the United Kingdom, require that a reverse charge be applied to domestic transactions between VAT registered traders involving the sale of certain goods such as mobile phones or computer chips. In these cases, if the goods that are specified on a given transaction line are subject to this reverse charge, the VAT treatment for the line will reflect domestic reverse charge. You can specify by country whether reverse VAT charges apply and whether specific VAT drivers (such as, products, inventory items, suppliers, and customers) are subject to the reverse charges.

PeopleSoft provides a VAT report, Reverse Charge Sales List, that shows the domestic business sales that are subject to reverse charges and the VAT that is due from the purchasers on these sales.

See Understanding VAT Reports.

How VAT Defaults Work

Once the VAT reporting country, VAT exception type, and VAT treatment for a transaction are known, the system can retrieve the defaults from the defaults table based on the VAT drivers on the transaction. In general, most of the fields contained within the VAT Controls group boxes on the transaction entry VAT pages are populated based on values retrieved for the VAT reporting country from the defaults table.

To supply the values within the VAT Details group box on the transaction line entry VAT pages, the system retrieves the VAT-applicable value from the defaults table and uses this along with VAT exception type and VAT treatment to determine the VAT applicability for the transaction line.

Once the VAT applicability for a line is derived, that value, along with the VAT treatment, is used in combination with the transaction-specific default hierarchy to retrieve the default VAT code and VAT transaction type values respectively from the common VAT defaults table.

PeopleSoft software VAT default structure is specifically designed to hold the most frequently used value on the driver at the top of the hierarchy and exceptions to this on drivers at lower levels. Default processing on transactions looks through the hierarchy starting at the bottom and stops once a value is found.

The system also makes some initial, basic assumptions about VAT suspension and VAT recoverability that would be applicable to each line:

  • Within procurement, before usage is taken into account, all items are assumed to be 100 percent recoverable.

  • When recording foreign VAT in expenses, all expense types are assumed to be 100 percent reclaimable.

  • For transactions for which the purchasing organization has been granted suspension from paying VAT, all lines are assumed to be subject to VAT suspension.

However, you can define exceptions to these assumptions:

  • You can define any item or expense type that, due to the nature of the item or expense, is not 100 percent recoverable.

  • You can define any expense type that, due to the nature of the expense when recording foreign VAT, is not 100 percent reclaimable.

  • You can define any sales line identifiers (products, charge codes, discounts, surcharges, inventory item, labor type, or generic identifiers), sales line identifier groups (VAT product groups, charge code VAT groups, CRM service type or inventory item group), asset classes, Treasury accounting templates, items or item categories that are not subject to VAT suspension.

    In other words, you can define certain VAT driver values that may still be taxable, regardless of whether the buyer has been granted suspension.

Note: Run the VAT 3000 report after setting up defaults to validate VAT default setup data and to expose any inconsistencies and missing default values.

Overriding VAT Defaults and Settings

In rare and specific cases, the system might not be able to provide all default VAT values as desired. Therefore, to enable the correct recording of a transaction, you can always override any default value on the transaction entry VAT pages. This topic is discussed in greater detail later in this chapter and in the application-specific documentations.

See Applicable Transaction Entry VAT Page.

VAT Report Production

Once you enter transactions into the system, you must be able to report those transactions on a VAT return. PeopleSoft software provides processes and report definitions to enable you to do this.

VAT Environment Setup

For the system to track and process VAT, you must first set up some basic information: VAT transaction types, VAT authorities, VAT codes and their associated VAT accounting templates, VAT countries, VAT entities, VAT use types, and VAT defaults. Each piece builds upon the next so, for the basic setup, you should implement each piece in the following order:

  1. VAT transaction types.

  2. VAT rates, VAT codes, and VAT accounting information.

  3. VAT countries.

  4. VAT entities.

  5. VAT use types.

  6. VAT apportionment if you have complex requirements for recovering input VAT.

  7. VAT defaults.

In addition to the information you must set up, PeopleSoft software delivers multiple accounting entry types for VAT accounting and reporting with every application. You cannot add your own.

Note: You should use only one setID for all your VAT setup. If VAT codes and transaction types are set up under multiple setIDs, an invalid VAT code or transaction type could supply by default onto a transaction entered for a business unit that is using a different setID for VAT.

This table lists the VAT accounting entry types:

Accounting Entry Type

Description

PeopleSoft Applications

VAT Reporting

Accounting

VI

VAT Input

Identifies input VAT transaction lines in the VAT transaction table. These lines are flagged as either VIR on the source transactions in PeopleSoft Payables and PeopleSoft Expenses, but may be flagged as VIR, VIN, or VIB on the original source transactions in PeopleSoft General Ledger. These items are flagged as VI on the original source transactions within PeopleSoft Treasury.

PeopleSoft Payables, Expenses, Treasury Management, General Ledger

Yes

No

VIB

VAT Input Rebate

Identifies accounting entries for input VAT rebate amounts.

PeopleSoft Payables, Expenses, Treasury Management, General Ledger

No

Yes

VIC

VAT Input Credit

Identifies input VAT credit transaction lines in the VAT transaction table. These lines are flagged as VICR on the source transactions in PeopleSoft Payables.

PeopleSoft Payables

Yes

No

VICB

VAT Input Rebate Credit

Identifies accounting entries for input VAT rebate credit amounts.

PeopleSoft Payables

No

Yes

VICN

VAT Input Non-Recoverable Credit

Identifies the accounting entry for nonrecoverable input VAT credit.

PeopleSoft Payables

No

Yes

VICR

VAT Input Recoverable Credit

Identifies the accounting entry for recoverable input VAT credit. When a VAT transaction is loaded to the transaction table, it is stored with the VAT distribution account type of VIC.

PeopleSoft Payables

No

Yes

VID

VAT Input Discount

Identifies adjustments to input VAT in the VAT transaction table due to taking a cash discount when VAT is recalculated at time of payment. These lines are flagged as VIDR on the original source transactions.

PeopleSoft Payables

Yes

No

VIDA

VAT Discount Taken on Purchases

Identifies the accounting entry that backs out the portion of the discount attributable to input VAT from the discount earned account when you recalculate VAT at the time of payment and a cash discount is taken.

Peoplesoft Payables

No

Yes

VIDN

VAT Input Discount Non-Recoverable

Identifies the accounting entry for the nonrecoverable portion of the input VAT discount adjustment.

PeopleSoft Payables

No

Yes

VIDR

VAT Input Discount Recoverable

Identifies the accounting entry for the recoverable portion of the input VAT discount adjustment. These entries are stored in the VAT transaction table as VID.

PeopleSoft Payables

No

Yes

VIIN

VAT Input Intermediate Non-Recoverable

Identifies the intermediate accounting entry created at invoice time for nonrecoverable input VAT when VAT is declared at time of payment.

PeopleSoft Payables, General Ledger

Used for Italian VAT register only.

Yes

VIIR

VAT Input Intermediate Recoverable

Identifies the intermediate accounting entry created at invoice time for recoverable input VAT when VAT is declared at time of payment.

PeopleSoft Payables, General Ledger

Used for Italian VAT register only.

Yes

VIN

VAT Input Non-Recoverable

Identifies the accounting entry for nonrecoverable input VAT.

PeopleSoft Payables, Expenses, Treasury Management, General Ledger

No

Yes

VINT

VAT Input Non-Taxable

Identifies nontaxable transaction lines in the VAT transaction table that are generated when the VAT applicability is exempt or outside the scope of VAT.

PeopleSoft Payables, Expenses, Treasury Management, General Ledger

Yes

No

VIR

VAT Input Recoverable

Identifies the accounting entry for recoverable input VAT. For PeopleSoft Payables, Expenses, and General Ledger, when a VAT transaction is loaded to the transaction table, it is stored with the VAT distribution account type of VI.

PeopleSoft Payables, Expenses, Treasury Management, General Ledger

No

Yes

VIW

VAT Input Write-Off

Identifies the VAT transaction entries in the VAT transaction table for the write-off of input VAT. These lines are flagged as VIWR on the original source transactions.

PeopleSoft Payables

Yes

No

VIWB

VAT Input Rebate Write-Off

Identifies the accounting entry for the write-off of rebate input VAT.

PeopleSoft Payables

No

Yes

VIWN

VAT Input Write-Off Non-Recoverable

Identifies the accounting entry for the write-off of nonrecoverable input VAT.

PeopleSoft Payables

No

Yes

VIWR

VAT Input Write-Off Recoverable

Identifies the accounting entry for the write-off of recoverable input VAT.

PeopleSoft Payables

No

Yes

VO

VAT Output

Identifies the accounting entry for output VAT and to identify the output VAT transaction lines in the VAT transaction table.

PeopleSoft Billing, Receivables, General Ledger, Asset Management

Yes

Yes

VOAA

VAT Output Advance with Adjustment

Identifies the adjustment accounting entry for output VAT on advance payments for France. In France, the AR Prepaid account should be credited with the advance payment amount INCLUDING VAT amount. To keep the transaction balanced, a VAT to Adjust accounting entry will be required. This advance payment is applied to an invoice. The VAT to Adjust accounting entry will be reverted. Whenever an advance payment is entered with VAT, there will be 2 VAT accounting entries for France, a credit to VAT Final, and a debit to VAT to Adjust.

PeopleSoft Receivables

Yes

Yes

VOCP

VAT Output for Purchases Credit

Identifies the accounting entry created for a credit against output VAT when you record both input and output VAT for a purchase. Also identifies those transaction lines in the VAT transaction table.

PeopleSoft Payables

Yes

Yes

VIRC

VAT Input Reclaimable

Identifies the accounting entry for reclaimable foreign VAT recorded on employee expense sheets.

PeopleSoft Expenses

No

Yes

VOD

VAT Output Discount

Identifies the accounting entry for adjustments to output VAT due to taking a cash discount when VAT is recalculated at time of payment. Also identifies those transaction lines in the VAT transaction table.

PeopleSoft Receivables

Yes

Yes

VOI

VAT Output Intermediate

Identifies the intermediate accounting entry created at invoice time for output VAT when VAT is declared at time of payment.

PeopleSoft Billing, Receivables, General Ledger

Used for Italian VAT register only.

Yes

VONT

VAT Output Non-Taxable

Identifies nontaxable transaction entries in the VAT transaction table that are generated when the VAT applicability is exempt or outside the scope of VAT.

PeopleSoft Receivables, Billing, General Ledger, Asset Management

Yes

No

VOP

VAT Output for Purchases

Identifies the accounting entry created for output VAT when you record both input and output VAT for a purchase. Also identifies those transaction lines in the VAT transaction table.

PeopleSoft Payables, Treasury Management, General Ledger

Yes

Yes

VOW

VAT Output Write-Off

Identifies the accounting entry for the write-off of output VAT. Also identifies those transaction lines in the VAT transaction table.

PeopleSoft Receivables

Yes

Yes

VOWP

VAT Output for Purchases Write-Off

Identifies the accounting entry created for write-off of output VAT when you record both input and output VAT for a purchase. Also identifies those transaction lines in the VAT transaction table.

PeopleSoft Payables

Yes

Yes

VODP

VAT Output Purchase Adjustment

Identifies the accounting entry for the adjustment to output VAT when you record both input and output VAT for a purchase, and for recalculating VAT at the time of payment when a cash discount is taken.

PeopleSoft Payables

Yes

Yes

VOIP

VAT Output Intermediate for Purchase

Identifies the intermediate accounting entry created at invoice time for output VAT when you record both input and output VAT on a purchase and when VAT is declared at time of payment.

PeopleSoft Payables

Used for Italian VAT register only.

Yes

VOAP

VAT Output Advance Payments

Identifies the accounting entry for output VAT on an advance payment.

PeopleSoft Receivables

Yes

Yes

VOC

VAT Output for Credits

Identifies the accounting for output VAT when a credit note is generated from PeopleSoft Billing.

PeopleSoft Billing, Receivables

Yes

Yes

VORE

VAT Output Asset Reinstatement

Identifies the accounting entry for output VAT for asset reinstatement.

PeopleSoft Asset Management

Yes

Yes