Accounts Payable

A payables system is the last stage of supply-chain management. It allows companies to pay suppliers for merchandise and services. There are several opportunities in Oracle Payables for automation, because the terms and conditions are known at the purchase order (PO) stage and, assuming that the goods are accepted, payment follows at a fixed time later.


Payables controls are equally applicable to paying employee expenses and paying vendors for expensed and capitalized items. It is no more than prudent management to pay invoices only when they are due and, invoice or not, to be sure that payment is not made before delivery unless it has been explicitly agreed.

Receiving goods and paying for them weeks later amounts to an interest- free loan from your supplier. Supermarkets are champions at using the good terms offered by suppliers. Supermarkets might be operating on wafer-thin margins, but they regularly sell their stock days—if not weeks—before they pay for it. They have a surplus working capital, which they invest for profit. Supermarkets are an extreme exponent of investing other people's money wisely; however, managing suppliers' payment terms is a business practice from which all commercial organizations can benefit.

The Payables cycle consists of the following four steps:
   1. Enter invoices. (This process may or may not include matching each invoice to a purchase order.)
   2. Approve invoices for payment.
   3. Select and pay approved invoices.
   4. Reconcile the payments with the bank statement (part of Oracle Cash Management).

Payables Workbenches
Payables includes two fully integrated workbenches, the Invoice Workbench and the Payment Manager. You can perform most of your transactions in Payables using the Invoice Workbench or the Payment Manager. You enter, adjust, and review invoices and invoice batches in the Invoice Workbench. You create, adjust, and review payments and payment batches in the Payments Manager.
You may be restricted in the windows, buttons, and actions you can access based on the Function Security implemented by your System Administrator.


Invoices

An invoice is an itemized list of goods shipped or services rendered, with an account of all costs. Oracle Payables lets you capture all the attributes of the real-life invoice documents you receive from your suppliers. When you enter an invoice in Payables, the invoice information is divided between the invoice header and the invoice lines.


Invoice Header
The invoice header defines the common information about the invoice: invoice number and date, supplier information, remittance information, and payment terms. Information specified at the invoice header level defaults down to the line level. You can override the header level information for individual lines, as required.

Invoice Lines
The invoice lines define the details of the goods and services as well as the tax, freight, and miscellaneous charges invoiced by the supplier. There can be multiple invoice lines for each invoice header. The Lines tab of the Invoice Workbench captures all of the details for the invoice line necessary for accounting, as well as for cross-product integration with other Oracle E-Business Suite applications, such as Assets, Grants Accounting, Inventory, Projects, Purchasing, Property Manager, and Receivables.

For each invoice, you can manually enter invoice lines, or you can automatically generate lines by matching the invoice to a purchase order shipment, pay item, or receipt

Invoice Types
1.1 Standard A regular supplier invoice. The invoice usually includes line item details, including a description and price.

1.2 PO Default An invoice for which you know the matching purchase order number. Payables fills out as much information from the purchase order as possible: supplier name, supplier number, supplier site, and the currency.

1.3 QuickMatch
An invoice you want to match automatically to a specified purchase order and all the shipment lines on the purchase order. Oracle Payables completes the match automatically for each shipment line, where the quantity ordered is greater than the quantity already billed against that shipment line.

1.4 Mixed
A standard or credit/debit memo invoice that you want to match to a purchase order, another invoice, or both. You can enter either a positive or negative amount for a Mixed invoice.

2. Credit Memo An invoice you receive from a supplier representing a credit for goods or services purchased.

3. Debit Memo An invoice that notifies a supplier of a credit you recorded for goods or services purchased.

4. Prepayment An invoice used to make advance payments for expenses to a supplier or employee. In this case, you might not have actually received the goods or services yet.

5. Expense Report An invoice you enter to record business-related expenses for employees. The employee is the supplier.

6. Witholding Tax

7. Interest Invoice
Note :  Once you have saved an invoice with the type of PO Default, Mixed, or QuickMatch invoice, Payables will change the invoice type to Standard. You cannot later search and find PO Default, Mixed, or QuickMatch invoices in the Invoice Workbench.


 

Invoice Workbench

You usually enter supplier invoices in either the Invoice Workbench or the Quick Invoices window.

Invoice Workbench
Used to enter any invoice directly into the Payables system. Use this instead of the Quick Invoices when entering complex
invoices or invoices that require online validation and defaulting. Also used when entering an invoice that needs immediate action, such as payment.

Functionality available only by invoice entry in the Invoice Workbench Use the Invoice Workbench to:
• Enter Prepayment type invoices Invoices
• Enter Debit Memo type invoices
• Match Credit Memos to invoices
• Calculate taxes on invoices

Online results seen only in the Invoice Workbench Although the following occurs during import, in the Invoice Workbench you can see online results of the following:
• Tax lines and distributions
• Allocation
• Automatic sequential voucher numbering

AP: Use Invoice Batch Controls
The above profile option needs to be set as
Yes to access the AP Batch window, else the syetem would throw the following error

 
Entering Invoice Batches in the Invoice Workbench
 
You can use invoices batches to:
  • Enter invoice defaults at the batch level that override system or supplier site defaults for all invoices in the batch.
  • Maximize accuracy by tracking variances between the control invoice count and total and the actual invoice count and total resulting from your invoice entry.
  • Easily locate a batch online and review the name of the person who created the batch and the date it was created.
Prerequisites
  1. Enable the AP: Use Invoice Batch Controls profile option. This profile option is setup to allow creation of invoice either in batch or in single mode. The profile option can be set up in user level and should be NO to create invoice without batch.

2. Group unentered invoices into batches.
3. Establish a systematic naming convention to help you locate batches. For example, you may want to include in your invoice batch name the date or the initials of the person who entered the batch.
Tip: If you file physical documents by invoice batch name, a systematic naming convention will facilitate retrieval.

To enter an invoice batch:
1. In the Invoice Batches window enter a unique value in the Invoice Batch Name field. This name will appear on your reports and will help you locate the batch online.
2. Enter the number of invoices in the batch in the Control Count field.
Enter the sum of invoice amounts in the batch in the Control Total field. Payables tracks variances between the Control Count and Total and the Actual Count and Total as you enter invoices.
Note: If there is a discrepancy between the invoice amount and batch amount, Payables warns you when you exit a batch but it does not prevent Invoice Validation and payment of the individual invoices within a batch. You can make a correction immediately, or you can adjust the invoice batch later.
3. Enter any Invoice Defaults you want for the invoices. Defaults include: Currency, Type, Document Category, Hold Name, Liability Account, Payment Terms, Pay Group, GL Date, and Hold Reason.
These values you enter for defaults override any system and supplier site defaults for the invoices. For example, if you want the purchase order to provide the default value for Payment Terms on the invoice, then leave the Payment Terms field here blank. When you enter individual invoices you can override any values that default from the batch.
4. Choose the Invoices button and enter the invoices.


Enter Invoices with Matched PO & Receipts

You can match Payables invoices to purchase orders to ensure that you pay only for the goods that you have ordered, or you can match to purchase order receipts to ensure that you pay only for goods that you have received. Purchase order matched invoices are invoices that you match to any of the following:

  • Purchase order shipments
  • Purchase order receipts
  • Purchase order receipt lines
  • Purchase order distributions
Matching Invoices to PO
Oracle Payables shares purchase order information from your purchasing system to enable online matching with invoices. Match your billed (invoices) items to the original purchase orders to ensure that you pay only for the goods or services you
ordered. If you are billed for an item over the amount and quantity tolerances you define in the Invoice Tolerance window, during approval, Oracle Payables applies a hold to the invoice, which prevents payment.

You can match a single invoice to multiple purchase order shipments, or you can match multiple invoices to a single purchase order shipment. Oracle Payables ensures that you match only to purchase orders for the supplier on the invoice and that the purchase order and invoice currencies match. 
When you enter an invoice and match it, Payables automatically creates distributions for you and checks that the match is within the tolerance you define.


After you save the match, Payables updates the quantity or amount billed for each matched shipment and its corresponding distribution(s) based on the amount you enter in the Quantity Invoiced field. Payables also updates the amount billed on the purchase order distribution(s).

Entering Basic Invoices in the Invoice Workbench

You can use the Invoice Workbench to enter basic invoices. A basic invoice is a trade invoice you receive from a supplier that will not be matched to a purchase order or receipt.

Prerequisite
Enter the supplier and at least one pay site in the Suppliers window Select Standard or Mixed for the invoice Type.
Note: Standard invoices must have positive lines and Mixed invoices can have positive or negative lines.

Header Information

1. Select Standard or Mixed for the invoice Type. Note: Standard invoices must have positive lines and Mixed invoices can have positive or negative lines.

2. Enter the supplier number, invoice date and invoice number.Accept defaults for the basic invoice header information such as the Trading Partner, Supplier Number, Supplier Site, Invoice Date, Invoice Number, Invoice Currency, and Invoice Amount.  Payables prints the address for the Supplier Site on the payment.

3. Review and update the Payment Terms, Payment Terms Date, Pay Group, Payment Method, as necessary.

4. Payables automatically schedules payment of the invoice using the following header fields: Invoice Amount, Terms, and Terms Date. Enter or review the defaults for these fields.
Line Information
1. To enter invoice lines, select the Lines tab. Enter an invoice line for each line that appears on a supplier's invoice.
Note: The Gross Total for the invoice lines must be the same as the Invoice Amount for the invoice header, or the invoice will not pass validation.

2. Enter the line Type. Possible types are: Item, Freight, Miscellaneous, or Tax. You can only enter tax lines if your tax setup permits.

3. Optionally, enter the Quantity Invoiced, UOM, and Unit Price of the item you are invoicing.

4. Enter the total Amount of the invoice line as shown on the supplier's invoice.

Distribution Information
The distributions you enter for an invoice allocate the total invoice amount to various expense or asset accounts. For example, you can distribute expenses from one office supply invoice to expense accounts for several departments. Payables uses distributions to create accounting entries for invoices.
Enter distribution information for the line. You can enter distributions in the following ways:
  • Automatically using a Distribution Set. Review the Distribution Set for the line. If the Distribution Set defaulted from the invoice header, you can change the distribution set as required.
  • Automatically by Matching to Purchase Order. If the invoice is matched to a purchase order, the distributions default into the invoice from the purchase order. Review the distributions by clicking Distributions.
  • Manually in the Distributions Window. To manually enter distributions for the line, click Distributions. You cannot enter distributions manually for the following types of invoice lines: purchase order/receipt matched lines, prepayment applications/unapplications, automatic withholding tax lines, or lines related to corrections.
  • Manually by allocating charges. If you are entering a Freight or Miscellaneous line, you can create distributions by allocation. Click Allocation

Payment Schedules
When you first save the invoice header, Payables automatically schedules payment for each invoice based on the Payment Terms and Terms Date you enter for the invoice. Then during Invoice Validation, the system recreates the scheduled payments and overwrites any manual adjustments if:
• The Recalculated Scheduled Payment Payables Option is enabled, or
• The Exclude Tax from Discount Calculation Payables option is enabled and you have made changes to the tax amount on the invoice.
Payables uses the Payment Terms definition to calculate the due date, discount date, and discount amount for each scheduled payment. For example, if an invoice has Payment Terms of Net 30, Payables calculates the due date as 30 days after the Terms Date. You can assign default Payment Terms to a supplier. If you enable the Recalculate Scheduled Payment Payables option, Payables will also recalculate your scheduled payments during Invoice Validation. This recalculation is based on your most favorable available payment terms and start dates.

Tax Lines
Enter tax lines for the invoice. You can enter tax lines:
  • Automatically :  Click Calculate Tax and E-Business Tax determines the applicable taxes based on the invoice header and line information and calculates the appropriate tax lines and distributions.
  • Manually : If your tax setup permits, you can enter tax lines.

Creating Distributions by Allocation

You can use the Charge Allocations window to automatically create freight or miscellaneous distributions.
The charge distributions you create are allocated Freight or Miscellaneous distributions. Allocation associates a charge with the cost of an item on a receipt. This allocation information is used to record the full cost of a receipt item if you use one of the Periodic Costing options available in Oracle Cost Management.


In the Charge Allocations window, you specify the following:
  • The charge amount and type (freight or miscellaneous)
  • The distributions to which the charge will be allocated
  • The charge amount associated with each distribution. You can either specify an exact amount to allocate to each distribution, or you can prorate the charge amount across all selected distributions.
For each selected distribution, Payables creates a charge distribution and records the allocation. The new distribution has the same GL account as the distribution to which you allocate it. After Payables creates the distribution you can update the account any time before the invoice is accounted.

For example, on a $110 invoice, you want to allocate $10 of a miscellaneous charge to two Item distributions. Enter the $110 invoice and enter two Item distributions, one for $75 and one for $25. Prorate the Miscellaneous charge of $10 to the two Item distributions. Payables creates two Miscellaneous distributions, one for $7.50 and one for $2.50. The Miscellaneous distributions have the same account as the Item distributions.

Allocation Concept

You can allocate charges other than the cost of goods to invoice distributions. Allocation records the amount of the tax, freight, or miscellaneous charge that is associated with an invoice distribution. If you allocate a freight or miscellaneous charge to a distribution that has been matched to a receipt, then the charge is included in the cost of the item on the receipt. This enables you to accurately record all costs associated with a receipt item.

You allocate the freight cost to the computer and printer, but not to the distribution for service. You can specify the freight amounts allocated to each invoice distribution, or you can have the system prorate the allocated amounts based on the Item distribution amounts.

The following table shows the charge distribution types that you can allocate, and to which distribution types you can allocate them. You cannot allocate Item, Prepayment, or Withholding Tax distributions to other distributions.

Automatic Allocation by Payables
Payables automatically records the charge allocation for freight or miscellaneous charge distributions when the charge distributions are created by any of the following methods:
  • You prorate freight or miscellaneous charges during a match of a material invoice to a purchase order or receipt.
  • You create Freight or Miscellaneous distributions by allocating to other distributions.
  • You match a credit memo or debit memo to an invoice for the full amount of the invoice.
Payables does not automatically record freight, or miscellaneous charge allocations when it creates distributions in any other way, including:
  • You match a credit memo or debit memo to an invoice for less than the full amount of the invoice.
During Invoice Validation, if the amount of a Freight, Miscellaneous, or Tax distribution is not fully allocated (either not allocated, or a corresponding distribution was reversed or deleted) and is not associated with a receipt, then Payables prorates the allocation to all eligible distributions on the invoice.

Payment Schedules

When you first save the invoice header, Payables automatically schedules payment for each invoice based on the Payment Terms and Terms Date you enter for the invoice. Then during Invoice Validation, the system recreates the scheduled payments and overwrites any manual adjustments if:

  1. The Recalculated Scheduled Payment Payables Option is enabled, or
  2. The Exclude Tax from Discount Calculation Payables option is enabled and you have made changes to the tax amount on the invoice.
  • Payables uses the Payment Terms definition to calculate the due date, discount date, and discount amount for each scheduled payment. For example, if an invoice has Payment Terms of Net 30, Payables calculates the due date as 30 days after the Terms Date.

  • You can assign default Payment Terms to a supplier.
  • If you enable the Recalculate Scheduled Payment Payables option, Payables will also recalculate your scheduled payments during Invoice Validation. This recalculation is based on your most favorable available payment terms and start dates.
  • If you enable the Exclude Tax from Discount Calculation Payables option and the invoice has changes to the tax amount after the invoice is initially saved, Invoice Validation will automatically recalculate the Discountable Amount and recreate the scheduled payments to reflect the new Discount Amount. You can query the invoice to view the new Discount Amount in the Scheduled Payments tab.
The invoice Terms Date defaults from the supplier site Terms Date Basis option you select:
  • System. System date on day of invoice entry.
  • Goods Received. The date you receive goods for invoices you match to purchase orders.
  • Invoice. Invoice date.
  • Invoice Received. Date you receive an invoice.
Use the Scheduled Payments tab to review or adjust dates and amounts of all payments, including discount schedules, for an invoice. You can also schedule partial payments and place all or part of the scheduled payment on hold.

Important: You can manually adjust scheduled payments or use the Split Schedule functionality to adjust scheduled payments. The Recalculate Scheduled Payment Payables functionality will not overwrite those changes. However, if the Exclude Tax from Discount Calculation Payables option is enabled and changes have been made to the tax amounts and if the invoice is not fully paid, then Invoice Validation will overwrite any manual scheduled payments changes.

Discounts
Payables uses payment terms you assign to an invoice to pay invoices at a discounted rate. You define discount payment terms in the Payment Terms window. You can define discount payment terms that have Payables vary the discount amount
depending on how old the invoice is. You also define the payment terms to pay the full invoice amount if you have missed the discount date. For example, you can define payment terms to take a 10 percent discount if the invoice is paid within 5 days of the Terms Date, or a 5 percent discount if the invoice is paid within 10 days. If the invoice is over 10 days old, Payables pays the full invoice amount on the due date you specify.

When you first save the header information for an invoice, Payables automatically creates a scheduled payment. If the invoice uses discount payment, the schedule payment includes a discount date and discount amount. If you enter an invoice that does not have discount terms, you can modify the scheduled payment to include a discount.
If you take a discount, Payables uses the Discount Distribution Method you specify in the Payables Options window to credit the appropriate accounts. The Exclude Tax From Discount Calculation option you specify in the Payables Options window controls whether Payables subtracts the tax amount from the invoice amount when it calculates the invoice amount applicable to discount. Note that if you apply a prepayment with a discount to an invoice due a discount, you may need to adjust the discountable amount by the prepayment application amount to ensure that the discount taken is not
overstated.

If the Exclude Tax From Discount Calculation option is enabled and changes have been made to the tax amounts and if the invoice is not fully paid, then the Invoice Validation recreates the scheduled payments based on the new discountable amount.

DISCOUNT RESTRICTIONS
BANK CHARGES: You cannot use the Discount feature if you enable the Use Bank Charges Payables option.

Invoice Matching : How and What

1. First you enter the invoice header details and selects the Match option as Purchase order/Recepit/Invoice.

 
 
2. Click on Match and Select Matching type(Item, Freight, Miscellaneous, Tax) and either the PO/Receipt information (You can query either with PO/Receipt information and it has not effect on with which you are matching the invoice i.e. even with Invoice Match Option as receipt you can use PO number in Find receipt for matching form. This form is used only for querying PO/Receipt to be matched with Invoice)
 
3. Select the PO/Receipt and match it with the invoice and that will automatically creates the distribution for the invoice.

3.1 You can match an invoice with a receipt if you have selected Recipt as the Invoice Match Option in PO shipmnet line else system 'll show the below error message
 
3.2 Select the correct PO/Receipt line for which invoice is being created and click on distribute if you want to match each distribution line or else click on match. System 'll automatically creates the invoice lines and distribution

4. Verify the invoice lines and distributions.
 
 
 
 
 

Prepayments

  • A supplier might send an invoice that references a prepayment. If a supplier reduces the invoice amount by the amount of the prepayment and associated tax, you can use the Prepayment on Invoice feature to enter the invoice.
  • You can enter two types of prepayments: Temporary and Permanent. Temporary prepayments can be applied to invoices or expense reports you receive. For example, you use a Temporary prepayment to pay a hotel a catering deposit. When the hotel's invoice arrives, apply the prepayment to the invoice to reduce the invoice amount you pay. Permanent prepayments cannot be applied to invoices. For example, you use a Permanent prepayment to pay a lease deposit for which you do not expect to be invoiced.
  • The default ‘Settlement Date’ is calculated based on Prepayment Settlement Days Payables option. You can update this value.
  • In the Invoice Workbench you can enter and apply prepayments. In the Quick Invoices window you cannot enter prepayments, but you can apply existing prepayments to invoices you enter.
Entering Prepayments
You enter a prepayment as you enter any other invoice. However, you additionally specify 1) the prepayment type, Temporary or Permanent, and 2) the settlement date, the date after which the prepayment can be applied to an invoice. You can apply a hold to a prepayment if you want to control payment of it. You can also enter an invoice amount that includes a prepayment.
 
  1. On a prepayment, you can enter any number of distributions, either manually, or automatically by purchase order matching, distribution sets, or allocating. You can also take discounts on prepayments.
  2. You can apply paid Temporary prepayments on and after the prepayment settlement date. You can apply only Item distributions from the prepayment. The prepayment remains available until you apply the full amount of the prepayment Item distributions to one or more invoices. You can review the Prepayment Status Report to check the status of all prepayments in Payables.
  3. When you enter a Standard invoice in the Invoice Workbench, or enter an expense report in the Expense Reports window, Payables notifies you if you have available prepayments for the same supplier.
  4. You apply prepayments to invoices and expense reports differently, depending on where you enter them: Invoice Workbench, Quick Invoices, Expense Reports window, or Oracle Internet Expenses
Applying and Releasing Holds on Prepayments
To prevent payment of a prepayment, you can apply one or more holds to the prepayment or you can hold the scheduled payment. Apply these holds as you would for any other invoice.
You release holds from a prepayment just as you would for any other invoice.

Paying Prepayments
Pay a prepayment just as you would any other invoice. However, you cannot partially pay a prepayment; you must fully pay it.
 
Accounting Entries
1. When prepayment invoice is created(PP1):          
Prepaid Expense A/c Dr.
                          Supplier Liability A/C Cr.
 
When you enter a prepayment, Payables provides a default repayment account for each Item distribution. During prepayment entry, you can override the accounts Payables provides.
Payables looks in the following order and uses the first valid prepayment account it finds: supplier site, supplier, Financials option.
However, if the prepayment is purchase order matched and if the Build Prepayment Accounts When Matching Payables option is enabled, then Payables builds each account for you and defaults the built account if it is a valid accounting combination.



2. 
    When you receive the real invoice and enter with a charge account :
                                                                    Invoice Charge (/AP Accrual) A/C Dr.
                                                                                                          Supplier Liability A/C Cr.             
When Prepayment is applied to an invoice(INV1) :  Supplier Liability A/C Dr.
                                                                                                                      Prepayment A/C Cr.

So the final account entries are Charge A/C Dr
                                                                                 Supplier Liability Cr
  
    
                                                            
 

Applying Prepayments to Invoices and Expense Reports

You can apply the available amount of Item type distributions from a Temporary type prepayment to one or more invoices to offset the amount you pay on the invoice(s). If you entered the prepayment as a Permanent type and want to apply it, you can query the prepayment in the Invoices window and change the Prepayment Type to Temporary.


You can apply a prepayment in the following ways:
  • Applying Prepayments in the Invoice Workbench
  • Applying Prepayments in the Quick Invoices Window
  • Applying Prepayments to Invoice Records in the Payable Open Interface
  • Applying Prepayments to Expense Reports
Applying Prepayments in the Invoice Workbench
When you apply a prepayment to an invoice, you can see all available prepayment Item distributions for the same supplier in the Apply/Unapply Prepayments window. You can partially apply a Prepayment distribution by applying only a portion of its available amount.

To apply a prepayment, you can either create or query the prepayment and then select the invoice to which the prepayment will be applied, or you can create or query the invoice and then select the Prepayment distributions you want to apply. If you want to apply specific Prepayment Item distributions to the invoice, then you must query the invoice and apply the prepayment to the invoice. Otherwise, Payables will apply the amount of the application across the available Prepayment Item distributions, starting with the first Prepayment Item distribution, up to the application amount.

When you apply a prepayment, you can print a Prepayment Remittance Notice, which you can send to the supplier. This notice states that a prepayment has been applied to an invoice and this may result in a decreased payment or nonpayment of the invoice.

Applying Prepayments to Expense Reports
In the Expense Reports window, you apply prepayments, also known as advances, to expense reports during expense report entry. You can specify whether you want Payables to apply to an expense report all outstanding and available advances, one specific advance, one specific advance Item distribution, or a certain maximum amount of advances. Unless you specify a specific advance to apply, Payables applies all outstanding, available advances, starting with the oldest, up to the amount of the expense report. If you do not specify an advance Item distribution to apply, then Payables applies available advance Item distributions, starting with the one with the lowest distribution number.

For expense reports entered in Internet expenses, advances are applied during Expense Report Export if the Apply Advances Payables option is enabled. Payables applies all outstanding, available advances, starting with the oldest, up to the amount of the expense report.

Credit and Debit Memos

Enter a credit or debit memo to record a credit for goods or services purchased.
Credit/debit memos are netted with basic invoices at payment time.

  • Credit Memo: Negative amount invoice created by a supplier and sent to you to notify you of a credit.
  • Debit Memo: Negative amount invoice created by you and sent to a supplier to notify the supplier of a credit you are recording. Usually sent with a note explaining the debit memo.
Entering Credit/Debit Memos
To enter a credit/debit memo:
1. In the Invoice Workbench enter either the Credit Memo or Debit Memo Invoice Type. Enter a negative invoice amount and all basic invoice information. Enter Immediate Payment Terms, if appropriate.
2. Enter distributions. You can enter them manually or enter them automatically in one of the following ways:
  • Enter a skeleton Distribution Set.
  • Match to the original invoice you entered.
  • Match to a purchase order or receipt.
Matching Credit/Debit Memos to Purchase Orders and Invoices
When you enter a credit/debit memo, you can match it to existing invoice(s), purchase orders, or receipts to have Payables automatically copy the accounting information and create invoice distributions for the credit/debit memo.
For example, if you receive a credit for items you returned to a supplier, you can enter a credit memo and match it to the original invoice you entered to ensure that the credit memo distributes the credit to the same accounts originally charged. If you match a credit memo to an invoice for the full amount of the invoice, then the allocations on the invoice are copied to the credit memo. If you match a credit memo to only a portion of the invoice, then no allocations are copied to the credit memo. You can manually allocate credit memo distributions, or you can allow Payables to allocate during Invoice Validation of the credit memo.

Payables calculates discounts on credit and debit memos if the following conditions are met:
  • You match them to invoices you paid using a discount.
  • You use the same payment terms that were used on the original invoice
  • The credit memo must be paid within the terms of the discount.
You can match to an invoice even if it is paid and posted. You can match the credit memo to multiple invoices, and at different levels of detail. Your available choices depend on whether the originating invoice was purchase order matched or not.

Clearing a Credit
You can clear a credit or debit memo you have entered and have been unable to include in a payment. For example, a supplier sends you cash in lieu of a credit invoice, and you have already entered a debit memo. You can pay the debit memo with a refund. 
Alternatively, you can perform the following task to enter a positive amount invoice to balance out the impact of the credit/debit memo. To clear a credit that will not be used:
1. Enter a Standard type invoice for the positive amount of the credit/debit memo. For example, if you entered a credit for -$10, enter a new invoice for $10. Other than the invoice amount and invoice number, enter all of the same basic invoice information you entered on the credit/debit memo.
You may want to enter a write off account on the distribution if you do not want the accounts on the credit or debit memo to bear the impact of the unrecovered credit.
2. If you matched the credit/debit memo to a purchase order, match the new invoice to the purchase order to correct the purchase order information.
3. Create a zero amount payment at payment time to net the new invoice with the credit/debit and clear both from your Invoice Aging.

Mixed Invoices

Mixed Invoices are invoices or credit/debit memos for which you can perform both positive and negative matching to purchase orders and to other invoices.
For example, you can enter an invoice for -$100 with Invoice Type Mixed. You can match to an invoice for $-200, and match to a purchase order for $100.

To enter a Mixed invoice:

1. In the Invoice Workbench, enter a Mixed invoice Type. Enter all basic invoice information.
You can enter either a positive or negative invoice amount.


2. Match to purchase orders, and/or invoices.

Recurring Invoices

You can enter invoices for periodic expenses for which you may not receive invoices, such as rent. To enter recurring invoices, define a recurring invoice template, then create invoices based on that template.
Recurring Invoices can also be used to create debit memos.

Prerequisites
Recurring invoices are affected by the following prerequisites.
1. Supplier Information : Supplier for which invoice 'll be created.

2. Special Calendars and Term Date Basis: Determine the frequency of your recurring invoices. For example, once a week or monthly. In addition, consider how the due date will be determined when you define your special calendar. When
Payables creates recurring invoices, the invoice date is the first date of the period in which the recurring invoice is created. The Terms Date depends on the Terms Date Basis setting at the supplier site. If the Terms Date Basis is System Date, then the Terms Date is the same date that the recurring invoice was created. If the Terms Date Basis is set to anything else, then the Terms Date is the invoice date, the first day of the period in which the recurring invoice is created.


3.1 Invoice Number: 
The invoice number.

3.2.
Withholding Tax: If applicable, the withholding tax group defined on the template will be used as a basis for withholding from invoices created from a template. If the Payables System Option Setting for Apply Withholding Tax has been defined with either At Invoice Validation or Payment, the value will default from the supplier site or can be entered directly in the template.

3.3. Document Sequencing: If the Document Sequencing profile option is defined as Always Used or Partially Used, you must define a sequence as Automatic. The  sequence should be assigned to the Recurring Standard Invoices category for invoices and Debit Memo Invoices for debit memos.

4.1 Purchase Orders:
You can use Purchasing Orders to plan for recurring invoices.
Match option: Recurring invoice processing requires that the purchase order schedules or pay items be defined with a Match Option of Purchase Order to prevent invoice creation conflicts if the receipt or work confirmation has not occurred by the time of invoicing. The Match Approval Level can be 2-way, 3-way, or 4-way.

Attributes Inherited from the Purchase Order: While the Recurring Invoices Template may have several tax fields, the Purchase Order attributes will take precedence over the template. The invoices will inherit the accounting distributions from the purchase order shipment or pay item with the line amount being prorated if there is more than one distribution. The invoice may also inherit the purchase order shipment or pay item descriptive flexfields if the Payables System Option setting for Transfer PO Descriptive Flexfield Information is set to yes.

Quantity:
If the purchase order shipment or pay item is quantity based, Payables calculates the quantity by subtracting the calculated tax from the amount then dividing it by the unit price. This is important to evaluate when defining your template amounts to avoid matching holds on the resulting invoices.
 
Blanket Purchase Orders: If you are using a blanket purchase order, to avoid errors, enter the revision number and verify it each time you create invoices from the template.

4.2 Distribution Sets:  If not using a purchase order, define a Distribution Set for default accounts, distributions, and line descriptions. For example, define a Distribution Set to split a monthly recurring rent amount to different departments that share the rented space. The line amount to be distributed will be the invoice amount minus calculated tax. The invoices' line description will be inherited from the Distribution Set if one is defined. If the Distribution Set does not have a description, the invoice will inherit the value for Line Description from the Recurring Invoices template. The invoice will also inherit the Descriptive Flexfields from the Distribution Set.

5. Payment Attributes: By anticipating the attributes needed for payment and fiscal reporting of the recurring invoices, you can either define these on the Supplier Site for defaulting to the Recurring Invoice template or enter them directly on the template. Payment attributes consist of pay group, payment priority, payment method, remit to bank account, delivery channel, bank charge bearer, payment reason, and payment reason comments. Note that the Payment Method may also
default based on a company policy.
 

Invoice Approval Workflow: If you want your recurring invoices to go through an approval process, enable the Use Approval Workflow Payables Option and configure approver rules in Approvals Management. If your approver requirements include the requester, enter the requester , enter the requester on the recurring invoice template. If you do not want your recurring invoices to require approval event though you have enabled the Payables Option, you may uncheck the Approval Workflow Required check box on the Recurring Invoices template.

Payment Requests

Payables provides the ability to disburse funds to a party (a payee) who is not defined as a trading partner in your supplier master. E-Business Suite products, such as Oracle Receivables and Oracle Loans, can submit disbursement requests to Payables, where you can disburse the funds and manage the payment process using the payment management features that are available in Payables. When a disbursement request is submitted to Payables, it is recorded as a payment request.

You can submit a payment request from another application, for example, from Receivables to pay a customer for an On Account Credit Memo, or from Loans to disburse funds for a loan, and Payables will verify, account, tax, and approve the
payment request. You can track the progress of the payment request in the originating application. Once the payment request is approved, you can report and audit the payment request in Payables.

You can only submit a payment request from other applications; you cannot enter a payment request for a payee directly in Payables.

The payment request process is as follows:

1. Submit a request to disburse funds from another application, such as Receivables or Loans. Note that you cannot submit a payment request in Payables.
2. Payables automatically creates a payment request, in real-time.
3. Once the payment request is created, you can search for it just as you would search for an invoice. Enter Payment Request in the Type field and enter the payee name in the Trading Partner field. Note that because the payee is not a supplier, do not enter a Supplier Number.
4. If the payment request requires approval, use the Invoice Approval Workflow to approve payment requests.
5. Payables applies holds to the payment request if there are any exceptions.
6. Once the holds are released and the payment request is approved, it can be paid as a single payment or as part of a payment batch.
Once the payment request is paid, your auditors can view the request to disburse funds in the originating application and the payment request in Payables.
Once you enter a payment request, you cannot delete payment request or update payment request fields. If necessary, you can cancel the payment request or void the payment, just as you would for an invoice. Payables notifies the originating application to respond to these actions.

Setting Up Payment Requests:
There are no specific setup steps required to use payment requests; however, the setup steps listed below do affect the payment request process. Review these steps if you plan to use payment requests.

Oracle Applications
Document Sequencing – Payment Request Document Category If the Sequential Numbering profile is set to Partially Used or Always Used, ensure that you have assigned a sequence to the Payment Request document category.

Oracle Payments

  • You can use the following Oracle Payments setups to define custom payment methods for payment requests, define defaulting rules, and specify whether you want to manage payment requests separately from other payments.
  • Payment Method Controls
  • Payment Method Defaulting Rules
  • Payment Instruction and Report Formats
  • Payment Attribute Validations
  • Payment Process Profiles
  • Disbursement Option

Oracle Payables
Payables Options - Use Invoice Approval Workflow Enable the Use the Invoice Approval Workflow Payables Approval Option to approve payment requests using the workflow.

Financial Options
Depending on how much information is provided in the originating application, Payables may default attributes from the Financial Options window, including Liability GL Account, Payment Terms, Pay Group, and Terms Date Basis. See:

Oracle Approvals Management
Approval Rules
If you are using the Invoice Approval Workflow for payment requests, define the approval rules.

Validation

Before you can pay or create accounting entries for any invoice, the Invoice Validation process must validate the invoice.

Invoice Validation checks the 

  1. period status
  2. tax
  3. exchange rate
  4. distribution information
  5. matching(IMO, invoice matching option)
  6. tollerence
Invoice validation does the following job
1. It creates/modifies the payment schdule on the basis of payment term and term date basis.
2. Invoice validation is a accounting event. so after the completion of it we can create accounting.
It checks the supplier site to determine which invoice tolerance template to use. If no invoice tolerance template is specified, tolerance checking is not performed. If an invoice tolerance template is specified, Invoice Validation will check against the specific invoice tolerances template stored in the Invoice Tolerances window to determine if the invoice falls within the defined tolerances and automatically applies holds to exception invoices.
If an invoice has a hold, you can release the hold by correcting the exception that caused Invoice Validation to apply the hold by updating the invoice or the purchase order, or changing the invoice tolerances. Then resubmit Invoice Validation to release the hold. In the Invoice Holds tab, you can manually release certain invoice holds, even if you have not resolved the matching error condition.

Note: When the invoice is in a Validated state, the Liability Account field cannot be updated.

1. Authorized users can always correct an invoice, even if you have validated, approved, paid, or created accounting entries for the invoice.

2. You can identify all invoices that Payables has not yet reviewed with Invoice Validation by submitting the Invoice Register and selecting the Unvalidated Invoices Only parameter. You can review the validation status of an invoice online in the Invoice Overview window or the Invoices window.

3. Payables and Oracle Alert integrate to alert the appropriate accounts payable or purchasing staff when you or Payables place an invoice on hold. Oracle Alert also provides an integrated system of alerts, messages, and message distribution to focus attention on time-sensitive or critical information and streamline the validation process.

Exception reporting in Oracle Alert is accomplished using either electronic mail or paper reports.

4. You can submit an invoice for validation in one of the following ways:
  • Online by using either the Validate or the Validate Related Invoices check box in the Invoice Actions window.
  • Online by using the Validate button in the Invoice Batches window.
  • Batch by submitting the Payables Invoice Validation program from the Submit Request window.
5. The order of the Invoice Validation process and Invoice Approval Workflow Program is based on the Approval Processing Sequence Payables option. For example, you might want to validate before you approve if you enter invoices that require the Invoice Validation process to create tax distributions for you. If your approvers need to review tax details before they approve an invoice, then we recommend that you select an option that validates before approving. For more information on submitting invoices for approval.

Validation Example
Invoice Validation places three invoices on matching hold. The first invoice is on matching hold because the quantity billed exceeds the quantity received. The second invoice is on matching hold because the invoice price exceeds the purchase order shipment price. The third invoice is on matching hold because the quantity billed exceeds the quantity ordered.

Invoice 1. Your receiving department receives the goods and records the receipt information. Your invoice now matches the receipt and Payables releases the hold when you submit Invoice Validation.

Invoice 2. A supplier sends a credit to correct the amount due on a previous invoice.
You match the credit to the purchase order as a price correction and associate it with the invoice during the match. The weighted average price of the invoice and credit memo now matches the purchase order shipment price. Payables releases the hold when you resubmit Invoice Validation. Use the Validate Related Invoices option in the Invoice Actions window to submit Invoice Validation for both the credit and the original invoice.

Invoice 3. You increase your tolerance levels using the Invoice Tolerances window.
Your invoice now matches your receipt and purchase order within your newly-defined tolerance levels and Payables releases the hold when you resubmit Invoice Validation

Suppliers

Set up suppliers in the Suppliers window to record information about individuals and companies from whom you purchase goods and services. You can also enter employees whom you reimburse for expense reports.

When you enter a supplier that does business from multiple locations, you store supplier information only once, and enter supplier sites for each location. You can designate supplier sites as pay sites, purchasing sites, RFQ only sites, or procurement card sites. For example, for a single supplier, you can buy from several different sites and send payments to several different sites. Most supplier information automatically defaults to all supplier sites to facilitate supplier site entry. However, you can override these defaults and have unique information for each site.

The system uses information you enter for suppliers and supplier sites to enter default values when you later enter transactions for a supplier site. Most information you enter in the Suppliers window is used only to enter defaults in the Supplier Sites window. When the system enters that information in a later transaction, it only uses supplier site information as a default, even if the supplier site value is null and the supplier has a value. If you update information at the supplier level,
existing supplier sites are not updated.

When you enter a supplier, you can also record information for your own reference, such as names of contacts or the customer number your supplier has assigned to you.

 
 
Oracle Payables contains a hierarchy of options and defaults to expedite and control data entry. Options and defaults set at one level automatically cascade down to all lower levels in the hierarchy. Although you need to define these options and defaults only once, you can update them at any time to change controls and defaults for future transactions. You can override options and defaults at lower levels in the hierarchy.

Expense Reports and Credit Cards

Use the Expense Reports window in Payables to enter Payables expense reports for your employees. You can also use this window to review and modify any of the following expense reports:
  • Expense reports entered in the Payables Expense Reports window.
  • Expense reports submitted by your enterprise’s employees using Oracle Internet Expenses.
  • Expense reports entered in Oracle Projects and then transferred from Projects to Payables.
If you have paid advances to an employee you can use this window to apply advances to expense reports to reduce the amount you pay. You can also apply a hold to an expense report to prevent payment. You can apply advances and holds to expense reports that are from any source.

Before you can pay expense reports you must submit the Expense Report Export program which automatically creates invoices from the expense reports. You can then use Payables to validate, pay, and account for the invoices. You cannot view expense reports in this window if they have been purged. If you do not purge expense reports, you can still view successfully imported expense reports in this window, but you cannot modify them.

To manage expense reports:

1. Enter employees and their locations, expense addresses, Supervisors, and default expense accounts.

2. Define the employee as a supplier using either of the following methods:
  • Enable the Create Employee As Supplier Payables option to automatically create suppliers from employees when you submit Expense Report Export.
  • Enter the employee as a supplier in the Suppliers window before submitting Expense Report Export for expense reports.
3. For expense reports entered in Payables and Oracle Internet Expenses, define expense report templates that model the different expense report formats your employees use and the rate and policy schedules that your enterprise uses.

4. Enter expense reports in any of the following products:
  • Payables.
  • Oracle Internet Expenses.
  • Oracle Projects.
5. In the Payables Expense Reports window optionally apply holds and/or apply advances to the expense reports. Optionally modify or review Payables or Projects expense reports.

6. Submit Expense Report Export to create invoices and invoice distributions for the expense reports. Review the Expense Report Export. If there are exceptions, correct any expense reports that caused exceptions and resubmit Expense Report Export.

7. Submit the Employee Update Program to update employee-type supplier records with up-to-date name and address information from the employee record.

8. Pay the invoices as you would any other invoices.

Entering a basic expense report

1. In the Expense Reports window, either enter the employee name in the Employee field, or enter the employee number in the Number field.

2. Optionally change the GL Account, which defaults from the employee record.

3. In the Send to field, optionally change the location to which you want to send payment for the expense report. You control the default expense address in the Financials Options window.

4. In the Date field, enter the period ending date for the expense report. Payables uses this date as the GL Date for invoice distributions created from the expense report. When you submit Expense Report Export you have the option to override this date.

5. Either enter an Invoice Number, or Payables will enter the invoice date or the expense report date as the Invoice Number. Enter a Description of the expense report. This will become the invoice description, and it will appear on reports.

6. Enter the total Amount of the expense report. Payables will confirm that the sum of the item amounts matches this amount.

7. If you enable the Reviewed By Payables check box, this indicates that receipts are not required for this expense report. Consequently, the Receipt Verified check box in the Expense Audit tabbed region becomes nonupdatable.

8. Enter the expense report Template you want to use. If a default template is defined in the Payables Options window and the template is active, then Payables displays that default value. The template determines which items you can select. The template also might provide default values for Type, Includes Tax, Tax Code, and GL Account. During Expense Report Export, Payables creates invoice distributions from the item lines.

For each Item line on the expense report, select the item and enter the item amount. Optionally change the tax value in the Tax Code field associated with the item. The value for the Includes Tax check box defaults from the Expense Report Template for that item. If you use inclusive automatic tax calculation at the Line or Tax Code level and if the Allow Override (Distribution Amount Includes Tax) Payables option is enabled and if the item amount includes tax, then you can adjust the Includes Tax check box.

Optionally update the GL Account. The default GL Account for each item line is the GL Account for the employee overlaid with any segments defined on the template for the expense item.

9. Save your work.

Expense Report Restrictions
UNIQUE INVOICE NUMBER. The same invoice number cannot be used twice for the same employee.
DATE. If the period ending Date is in a Never Opened accounting period, then Payables does not import the expense report, and Payables lists the expense report in the Exceptions section of the Expense Report Import Report. If the period ending Date is in a Closed period, Expense Report Import uses the first day of the next Open or Future accounting period as the GL date. If no open or future period is available then import will reject the expense report.

Expense Report Import
To create invoice from the expense report run the below program
  • Expense Report Import (in 11i) and
  • Expense Report Export (in R12).
Select the source Payables Expense Reports or internet expense as applicable.
Once the program completes, verify the invoice (invoice number is same as exponse report number) in invoice work bench.

Setting Up Suppliers and Supplier Sites

For every supplier, you can create an unlimited number of sites with different addresses and contacts. For example, for a single supplier, you can buy from several different sites and send the payments to only one site.

  • You can designate supplier sites as one of the following types:
- Pay Site: You can only enter an invoice for a supplier site that is designated as Pay Site.
- Purchasing Site: You can only create purchase orders in a Purchasing Site.
- RFQ Only Site: In Oracle Purchasing you can only create request for quotations from a Request For Quotations (RFQ) Only Site. You cannot create purchase orders in an RFQ Only Site.
  • For every supplier site, you can enter contact information (name, address, and telephone number) specific to that site. Contact information is for your reference only and is not used by the system.
Avoiding Duplicate Suppliers
Before setting up a new supplier, verify that the supplier does not already exist in the system. The verification eliminates the possibility of having duplicate suppliers and invoices in the system and improves the system performance.
  • Perform a Find or Query on the supplier name.
  • Submit a Suppliers Report.
  • Submit a Supplier Audit Report to obtain a listing of suppliers whose names are the same up to a specific number of characters.
  • Compare the supplier name with the names on these reports to ensure that the supplier does not already exist in the system.

Entering Basic Supplier Information

1. After verifying that a supplier does not already exist, set up a new supplier with a unique name in the Suppliers Summary or the Suppliers window. Use a naming convention to prevent future duplications (for example, Oracle Corporation, not Oracle Corp.)
2 If you do not enable the Automatic Supplier Numbering option in the Financials Options window, enter a unique supplier number.
3 Optionally, enter the Taxpayer ID, usually the tax identification number (TIN) for a company or the social security number for an individual.
4 If you are entering a value-added tax (VAT) supplier, optionally enter the VAT registration number in the Tax Registration Num field.
5 To prevent invoice or purchase order entry for this supplier after a certain date, enter the inactive date in the Inactive After field.

Enter Supplier Information in the General Region
Define parent/subsidiary relationships in the General region.
1 In the Parent Supplier Name field, enter the name of the supplier’s parent company if the supplier is a franchise or subsidiary. The parent company must be defined as a supplier in the system first.
In the Number field, the system displays the parent supplier number.
2 In the Customer Number field, enter the number that your supplier uses to identify your company or organization. This number appears on the Oracle Purchasing standard purchase orders.

Supplier Information in the Classification Region
Except for Type and Employee name, classification information is not used by the system and is for your reference only.
1. Select a supplier type from the Supplier Type list of values to group the supplier for reporting purposes. If you are entering an employee as a supplier, you must select Employee in this field.
2. Enter the employee name if applicable. You define employees as supplier to enter expense report (from which you create invoice and pays to employees for expenses occurred due to official reasons)
3. If you do not expect to do repeat business with a supplier, select the One Time check box.

In the United States, customers often use this region to classify their suppliers for government reporting purposes. For example, some customers receive certain government contracts only if a percentage of their suppliers are classified in certain categories.
1. In the SIC field, enter the standard industry code (SIC) for your supplier.
2. In the Minority Owned field, select the type of minority-owned business from the list of values.
3. If you want to track business with small companies, select the Small Business check box.
4. If you want to track business with companies owned by women, select the Woman Owned check box.

Suppliers: Electronic Data Interchange
(N) Suppliers—>Entry (B) Open
This region is accessible only when you select Electronic as the payment method in the Payment Region of this window.
1. In the Payment Method field, indicate how the electronic payment is to be made.
2. In the Payment Format field, indicate the type of information that is transmitted with the funds if the Payment Method is ACH.
3. In the Remittance Method field, indicate which party is responsible for sending the remittance advice to the payee.
4. In the Remittance Instruction field, you can enter the specific wire or other electronic payment instructions for an intermediary or recipient financial institution.
5. In the Transaction Handling field, select one of standard EDI transaction codes.

Bank Accounts/Accouting/Payment Region

How to Enter Supplier Information in the Bank Accounts Region
Use the Bank Accounts region to record the supplier bank accounts information that you use for making electronic payment transactions.
Prerequisite: In the Bank Accounts window, define the bank accounts for which your supplier is the account holder.
1. In the Name field, select the name of the bank account.
In the Number field, Oracle Payables displays the bank account number.
In the Cur field, Oracle Payables displays the currency for the bank account.
2. Select the Primary check box if you want to use this bank account as a default when you pay this supplier electronically.
3. In the Effective Dates From and To fields, enter dates to limit the time during which a supplier site uses this bank account as the primary bank account for receiving electronic payments.
Oracle Payables displays the supplier’s bank and branch information in the Bank and Branch fields.


Accounting information
Accounting information is entered only at the supplier site level.

Suppliers: Payment Region
(N) Suppliers—>Entry (B) Open
The defaults in the Payment region come from the defaults that you enter in the Financials Options window, except for the default for Pay Group, which comes from the Payables Options window.
1.  In the Terms field, select a payment term for the supplier. Oracle Payables uses payment terms to calculate due dates, discount dates, and discount amounts for each invoice.
2. In the Pay Group field, assign a Pay Group to the supplier. When you create a payment batch, you can choose a Pay Group to pay a category of suppliers or invoices at the same time.
3. In the Payment Priority field, enter a number, between 1 (high) and 99 (low), that represents the priority of payment.
4. In the Invoice Currency field, select the invoice currency for the supplier. The invoice currency is used as a default for the Purchasing documents and Oracle Payables transactions that you enter for a supplier.

5.  In the Terms Date Basis field, select the date from which Oracle Payables calculates a scheduled payment for a supplier.
- If you select Current, when you enter invoices, Oracle Payables defaults the current date as the terms date.
- If you select Goods Received, when you enter invoices, Oracle Payables prompts you to enter the date on which you received the goods for an invoice as the terms date.
- If you select Invoice, when you enter invoices, Oracle Payables defaults the invoice date as the terms date.
- If you select Invoice Received, when you enter invoices, Oracle Payables prompts you to enter the date on which you received an invoice as the terms date.
6. In the Pay Date Basis field, select Due or Discount as the pay date basis for the supplier. The pay date basis determines the pay date for the supplier’s invoices.
7 In the Payment Method field, select the method you use most frequently to pay the supplier’s invoices:
- If you select Check, you can pay with a manual payment, a Quick payment, or in a payment batch.
- If you select Electronic, you pay electronic payments either through the EDI Gateway or by delivering a payment batch file to your bank.
- If you select Wire, you can manually record an external wire transfer of funds between your bank and your supplier’s bank.
- If you select Clearing, you can record invoice payments to internal suppliers.
- If you select Future Dated, you can create payments with a future date that instructs your bank when to disburse funds to your supplier’s bank (for example, a bill of exchange).
- If you select Manual Future Dated, you can disburse funds to a supplier who sends an invoice with a payment notice attached. You approve the supplier’s payment notice, which includes a future payment date, and send it to your bank.

8. In the Invoice Currency field, select the default currency for all supplier invoices.
9. In the Payment Currency field, select the default currency for payments to the supplier.
10. Always Take Discount: Select this option to have Oracle Payables always take the available discount for a supplier, regardless of when you pay the invoice.
11. Exclude Freight From Discount: If this option is selected, Oracle Payables automatically subtracts the freight amount from the invoice amount when calculating the invoice amount subject to discount.
12. Allow Interest Invoices: If you select this option, Oracle Payables calculates interest for the supplier’s overdue invoices and creates corresponding interest invoices when you pay the overdue invoices. You can select this option, if you have already selected the Allow Interest Invoices check box in the Payables Options window.
13. Pay Alone: If you select this option, Oracle Payables creates a separate payment for each invoice. If the Pay Alone option is not selected, all invoices for the same supplier site are paid on a single payment.

Control/ Purchasing and Receiving option

Suppliers: Control Region
(N) Suppliers—>Entry (B) Open


You can prevent payment of multiple supplier invoices by applying a hold to the supplier rather than on each individual invoice. There are several types of supplier related holds that you can select for a supplier.
1 Invoice Amount Limit: If you enter an invoice that exceeds the invoice amount limit specified in this field, Oracle Payables applies an Amount hold to the invoice during approval.
2 By selecting the Hold All Payments check box, you prevent the supplier from being selected for payment during a payment batch or for a Quick payment.
3 By selecting the Hold Unmatched Invoices check box, you do not match an invoice to a purchase order (and instead enter distributions manually or with a distribution set), Oracle Payables places a Matching Required hold on the invoice during approval.
4 By selecting the Hold Future Invoices check box, Oracle Payables automatically applies a Supplier hold to all new invoices entered for the supplier. However, you can pay invoices that were entered before selecting this option.
5 In the Hold Reason field, specify the reason that you are applying an invoice hold to invoices
6. Select the Invoice Match Option
IMO(Invoice Match Option) determines for which transaction(a PO/receipt) you are making an invoice. When you create an invoice and validates it the system ‘ll check the invoice details with the PO/Receipt details as mentioned in the IMO.
The details verified are supplier information, qty, price etc.

MAL(Match Approval Level) is used in receiving option. The available options are
2-way matching
This verifies that Purchase order and invoice information match within your tolerances as follows and check following:
Invoice price <= Purchase order price
Quantity billed <= Quantity Ordered
3-way matching
This verifies that the receipt and invoice information match with the quantity tolerances defined and check following:
Invoice price <= Purchase order price
Quantity billed <= Quantity Ordered
Quantity billed <= Quantity received
4-way matching
This verifies that acceptance documents and invoice information match within the quantity tolerances defined and check following:
Invoice price <= Purchase order price
Quantity billed <= Quantity Ordered
Quantity billed <= Quantity received
Quantity billed <= Quantity accepted

The Invoice Match Option and the Match Approval Level are independent options. You can perform whichever Invoice Match Option you want regardless of the Match Approval Level.
For example, you can set a PO to any one of the following examples:
#1 - PO#5049 - 2-way/Purchase Order
#2 - PO#5050 - 2-way/Receipt
#3 - PO#5051 - 3 way/Purchase Order
#4 - PO#5052 - 3 way/Receipt

The Invoice Match Option determines what document you can match the invoice two. In #2 & #4 If I do not create a Receipt for these POs and try to match to the PO number, the system will not allow me to. It will give me a

APP-SQLAP-10655: You cannot match to this document

You can match only to the document (purchase order or receipt) specified by the Invoice Match option on the purchase order shipment. Either match to the specified document, or update the Invoice Match option for the shipment and then complete this match.
The Match Approval Level determines what if any type of hold will be placed based on the Invoice Tolerance setup.

So let's say we create a PO like #3 PO#5051 - 3 way/Purchase Order, however, we do not receive the PO. In this case we will receive a qty hold because we have the PO set to 3 way matching.  Purchase order, receipt, and invoice quantities must match within tolerance before the corresponding invoice can be paid.

Invoice Tax/Withholding Tax/Tax Reporting Region


Suppliers: Invoice Tax Region
(N) Suppliers—>Entry (B) Open
1.  In the Invoice Tax Name field, select the tax name that represents the tax charges you generally receive on invoices from the supplier.
2. In the Offset Tax Name field, select a tax name that is used in conjunction with a value added taxes (VAT) invoice tax name for reporting intra-EU VAT charges. on invoices.
Note: If you use the Multiple Organization feature, you can enter values in the Invoice Tax Name and Offset Tax Name fields only at the supplier site level.
3. Select the appropriate Calculation Level at which you want Oracle Payables to automatically calculate taxes.
- Header: Automatically create tax distributions based on the invoice amount and tax name.
- Line: Automatically create tax distributions based on the distribution amount, tax name.
4. Select the Allow Calculation Level Override check box if you want to allow updates of the default value of the Calculation Level option for the supplier sites
5. In the Rounding Rule field, select the method that you want the system to use to round the tax amount. You can select Up to round up, or round Down to round down, or round Nearest to round to the nearest.
6. Select the Distribution Amounts Include Tax check box, if you have selected Line as your Calculation Level, and if you want Oracle Payables to make an inclusive tax calculation where the calculated tax amount is subtracted from the item distribution lines.

Suppliers: Withholding Tax Region
(N) Suppliers—>Entry (B) Open
Use this region to enter withholding tax information for a supplier and supplier site.
You have access to this region only if you selected the Use Withholding Tax check box in the Payables Option window. The options that you select for a supplier default to the new supplier sites that you enter and then default to invoices that you enter for the site.
1. Select the Allow Withholding Tax check box to allow withholding taxes for the supplier and supplier site. If you do not allow withholding tax for a supplier, you cannot allow withholding tax for any of the supplier’s sites. As a result, you cannot withhold taxes for any invoices entered for this supplier site.
2. In the Withholding Tax Group field, select a default withholding tax group to assign to all invoices for the supplier site.

Suppliers: Tax Reporting Region
(N) Suppliers—>Entry (B) Open
1. Identify a supplier as Federal and State reportable by selecting the appropriate check box.
2. In the Income Tax Type field, select the appropriate tax type for the supplier.
In the Reporting Site field, Oracle Payables displays the supplier site that you chose as the income tax reporting site. For income tax reporting purposes, Oracle Payables requires a tax reporting site for each 1099 supplier. You can only choose one supplier site as the income tax reporting site for a supplier.
3. Reporting Name: This field is required only if the tax reporting name for the supplier differs from the supplier name. Oracle Payables prints this name, instead of the supplier name, on all 1099 reports for the supplier.
4. Name Control: Enter the first four characters of the last name of the 1099 supplier in this field. Oracle Payables displays the Name Control you enter here when you create the 1099 Tape for federally reportable suppliers.
5. In the Verification Date field, enter the date on which you received tax verification from the supplier. In Oracle Payables you can submit Tax Information Verification Letters for your suppliers. Oracle Payables prevents the generation of any further letters to a supplier after the verification date.
6. In the Organization Type field, select the type of organization for this supplier. The United States Internal Revenue Service (IRS) requires this information if you use magnetic media to file your 1099 tax information.

Entering Employees as Suppliers

Suppliers: Classification Region
(N) Suppliers—>Entry (B) Open

You must enter an employee as a supplier before you can pay the employee’s expense reports. You can enable the Automatic Create Employee as Supplier Payables option to automatically enter an employee as a supplier during Invoice Import, or you can enter the employee manually as a supplier in the Suppliers window.
To enter an employee as a supplier manually:
1 In the Classification region of the Suppliers window, select Employee as the supplier type.
2 Enter the employee name and employee number in the appropriate fields.

Merging Suppliers

Although the system prevents you from entering duplicate supplier names, you may inadvertently define the same supplier by using two different names. For example, you might enter ABC Corporation and ABC Corp, or you might enter a contractor under his name and his company name. You might also create duplicate suppliers if you import suppliers from another accounts payable system.

  • Use Supplier Merge to combine two or more suppliers that you identify as duplicates. You can update purchase orders and invoices for the old supplier to refer to the new supplier. The Supplier Merge window also enables you to merge supplier sites so that any sites assigned to an old supplier can be reassigned to the new supplier.
  • When you merge suppliers, you transfer invoices, purchase orders, or both from one supplier and site to another supplier and site. You can transfer to a new supplier and site unpaid invoices only or all invoices (including paid and partially paid invoices). Oracle Payables will not merge invoices if the merge would create a duplicate invoice for a supplier.
  • For best auditing results, transfer both paid and unpaid invoices to a new supplier and site so you can identify duplicate payments easily. Also, transfer both purchase orders and invoices to a new supplier and site so all invoice and purchase order information refers to the same supplier.
  • After you have merged suppliers, Oracle Payables automatically prints the Purchase Order Header Updates Report and the Supplier Merge Report as an audit trail of your supplier merge activity. The Supplier Merge Report also lists any duplicate invoices that it did not merge. Research the duplicated invoice. You can then update the invoice number if the invoice has not been paid or posted.
Merging Suppliers
(N) Suppliers—>Supplier Merge
1. Select which invoices to transfer from the Old Supplier to the New Supplier: All, Unpaid, or None. Also make sure the New Supplier site is a Pay Site, because you can only enter an invoice for a supplier that is defined as Pay site.
2. Select the PO check box if you want to transfer purchase orders. The New Supplier Site must be a Purchasing Site, because you can only enter purchase orders for a Purchasing Site.
3. Enter the Old Supplier Name and Site and the New Supplier Name in the appropriate fields.
- To copy the Old Supplier Site to the new Supplier, select Copy Site; do not enter a New Supplier Site. During the merge, Oracle Payables enters the merge date as the inactive date for the Old Supplier Site and creates a new site for the New Supplier with the information you selected to transfer.
- To merge the Old Supplier Site information with the New Supplier Site information, do not select Copy Site; enter one of the New Supplier’s existing sites in the Site field. During the merge, Oracle Payables enters the merge date as the inactive date for the Old Supplier site and combines all of the information you selected with the New Supplier Site.
4. Check Merge to transfer the information from the Old Supplier to the New Supplier.

Invoices: Integration with Oracle Projects


Importing Expenses from Oracle Projects and Creating Invoices Oracle Payables integrates with Oracle Projects so that you can create Payables invoices based on expense reports entered in Oracle Projects. Submit a streamlined process from the Submit Processes window in Oracle Projects to combine the following processes in one step:
1 Transfer expense reports to Oracle Payables.
2 Submit Invoice Import.
3 Verify invoices from Oracle Payables.
When you enter expense reports in Oracle Projects, you enter the same types of information thatyou enter for Payables expense reports (such as employee name, week ending date, project, task expenditure type, and amounts). Oracle Projects generates the general ledger account for each expense report expense item by using the AutoAccounting rules you have defined. After you transfer the expense report to the Payables Invoice Import Interface Tables, you can submit Invoice Import to create an invoice from the expense report.
If you enable the Automatically Create Employee As Supplier Payables option, Oracle Payables automatically creates suppliers and supplier sites for employees who are not already suppliers

Payments

Oracle Payables provides a variety of features for fast, controlled payment processing.
With Oracle Payables you can do the following:
  • Distribute funds by using multiple payment methods
  • Ensure that duplicate invoice payments never occur
  • Pay only invoices that are due, and automatically take the maximum discount available
  • Select invoices for payment, using a wide variety of criteria, and create payments automatically
  • Print checks online
  • Choose from different payment method options including checks, EDI, electronic funds transfer (EFT), and wire
  • Record stop payments
  • Void payments
  • Review information online on the result and status of every payment

Manual Payment

A manual payment is a payment that you create outside of Oracle Payables. The following are two examples of manual payments:

  • Handwritten checks
  • Wire
After making the payment through handwritten check/wire, you can record the payment within Oracle Payables and update the invoices that you paid. With a manual payment, you can override some payment controls of Oracle Payables. You can record a single payment for multiple pay alone invoices. You can record payment for invoices that are associated with any payment method type except EFT.
Prerequisites for processing manual payments in Oracle Payables are:
  • Create the payment outside of Payables.
  • The invoice you paid must be approved, uncancelled, without holds, and must have the same currency as the payment.
  • The bank account must have at least one payment document that uses the recorded or combined disbursement type.
Recording a Manual Payment
How to Initiate a Manual Payment
1. In the Type field, select Manual.
2. Select the bank account you use for the payment.
3. Select a payment document name.
4. Enter the payment document number.
5. Enter the payment date.
6. Enter the payment amount.
7. If you are using a multiple currency bank account with a multiple currency payment document, optionally, change the payment currency.
8. Enter either the supplier name or number.
9. Enter the supplier site.
10. If necessary, enter or adjust other information.
How to Select Invoices to Pay
1. From the Payments window, click Enter/Adjust Invoices to select approved invoices that are not on hold.
2. Select as many approved invoices as will fit on a single check stub.
3. To record a manual payment, save your work at this point and you are done.
4. To create a computer-generated payment, from the Payment window, click Actions to navigate to the Payment Actions window; format and print the check. Optionally, create a check, save it, and print it later.

Paying Invoices from the Invoice Workbench
(N) Invoices—>Entry—>Invoices (B) Actions
You can initiate payment of one or more invoices by selecting the invoices in the Invoices window and using the Pay in Full option in the Invoice Actions window. When you pay using this method, you can generate a manual payment or a Quick payment. Oracle Payables automatically enters most of the payment information for you, and you omit the invoice selection step you would perform if you were to create the payment in the Payment Workbench.
To pay an invoice or scheduled payment from the Invoice Workbench:
1. Make certain the invoices that you want to pay are fully approved.
2a. To pay one or more invoices in full, select the relevant invoices from the Invoices window; clickActions to navigate to the Actions window, and select the Pay in Full check box to open the Payments—Pay in Full window.
2b. To pay a portion of an invoice, select the invoice from the Invoices window; click Scheduled Payments, and select one or more scheduled payments. Click Pay to pay the selected payments.
3. In the Payments window, choose Quick or Manual for the payment type. Enter the bank account from which you want to make the payment, and enter the payment document you want to use. Oracle Payables automatically enters the remaining fields for you.
4. If necessary, enter or adjust other information in the Payments window.
5. If you are creating a manual payment, save your work to complete the payment.
Oracle Payables records the payment and updates the invoices as paid. If you are creating a quick payment, continue with Step 6.
6. Click Actions to navigate to the Payment Actions window. Format and, optionally, print the check.
7. Save your work.
Oracle Payables records the payment and updates the invoices as paid.

Scheduling Payments from the Invoice Workbench
1. Make certain the invoices that you want to pay are fully approved.
2. To pay a portion of an invoice, select the invoice from the Invoices window.
3. Click Scheduled Payments.
4. Make any updates to unpaid scheduled payments, and create any new scheduled payments.
5. To split a scheduled payment, update the amount, and then click Split Schedule.
Oracle Payables creates an additional scheduled payment with the net amount due.
6. Adjust the dates as appropriate and, optionally, apply a hold to the scheduled payment.
7. Save your work.

Future Dated Payments - Manual payment


 
1. Make certain the invoice that you want to pay is fully approved.
2. In the Payments window, record the invoice payment as a manual payment.
- If you use the payment document your supplier sent you and do not create a payment document, enter Manual Future Dated in the Payment Method field.
- If you manually created a future dated payment that you want to record, enter Future Dated in the Payment Method field.
3. Enter a maturity date.
4. Return the payment notice to the supplier.
5. The supplier submits the payment request to the bank.
6. The bank disburses funds on the maturity date the supplier specified on the payment notice.
7. Your bank sends you payment reconciliation information.
 

Computer-Generated Payments

You can create and print a computer-generated payment to pay a supplier for one or more invoices.
Examples of computer-generated payments are:

  • Check run
  • Electronic funds transfer (EFT)
Creating and Maintaining Computer-Generated Payments
(N) Payments—>Entry—>Payments
To create a computer-generated check, you must enable the Allow Online Print Payables option; the invoices must be approved, uncanceled, and without holds; the invoices must have check as their payment method and have the same currency as the payment; and the bank account must have at least one payment document that uses computer-generated or combined disbursement type.
In the Payments window:
  • You can, optionally, change the payment document number, which defaults to the next available number.
  • You can, optionally, change the payment currency if you are using a multicurrency bank account with a multicurrency payment document.
  • The payment date must be in an open or future period.
  • Unless you enable the Allow Pre-Date Payables option, you cannot predate a computer-generated payment.
  •  
How to Select Invoices to Pay
(N) Payments—>Entry—>Payments (B) Enter/Adjust Invoices
1. From the Payments window, click Enter/Adjust Invoices to select approved invoices that are not on hold.
2. Select the invoices that you want to pay. The invoices must have Check as their payment method and must have the same currency as the payment.
3. To create a computer-generated payment, click Actions to navigate to the Payment Actions window; format and print the check. Optionally, create a check, save it, and print it later. The bank account must have at least one payment document that uses computer-generated or combined disbursement type.

Recording Stop and Void Payments

 
 
Recording Stop Payments

(N) Payments—>Entry—>Payments (B) Actions
1. Find the payment online. In the Payments window, select the payment, and click Actions.
2. In the Payment Actions window, select Initiate Stop.
3. Click OK to have Oracle Payables update the payment status to Stop Initiated.
4. Save your work.
5. Use the Stop Payments Report to review all current stop payments. Oracle Payables does not list any stop payments that were initiated but then released or voided at a later time. Oracle Payables sorts the report by bank, bank account, payment document, and document number.

Releasing Stop Payments
(N) Payments—>Entry—>Payments (B) Actions
How to Release Stop Payments
1 Find the payment online. In the Payments window, select the payment and click Actions.
2 In the Payment Actions window, select Release Stop.
3 Click OK to have Oracle Payables release the stop on the payment and reset the status to Negotiable.
4 Save your work.

Voiding Payments
(N) Payments—>Entry—>Payments (B) Actions

When you void a payment, Oracle Payables automatically reverses the following:
  •  The accounting and payment records. Your general ledger will then have the correct information, and the status of the paid invoices is then reset to Unpaid.
  •  Any realized gains or losses on foreign currency invoices recorded as paid by the payment
  •  All related interest invoices when you void a past-due payment for the supplier site (if you enable the Allow Interest Invoices option for a supplier site)
  • If you withhold taxes at payment time and you void a payment that paid an invoice with an associated withholding tax invoice, then Payables automatically creates a negative (reversing) invoice for the tax authority supplier to offset the amount of the tax withholding invoice. You determine when you withhold taxes by the Apply Withholding Tax
    option you select in the Payables Options window.
Because you cannot reverse a void payment, before recording it have the uncashed payment document you want to void in your possession, or have proof that the payment did not clear the bank and that the bank was able to stop payment Review the invoices paid by that payment before you void it to make sure that you are voiding the correct payment. You can review these invoices in the Invoice Workbench.

How to Void Payments 
1. Find the payment online; and from the Payments window, select the payment, and click Actions.

2. In the Payment Actions window, select Void. Review and, optionally, change the void date and the GL date you want Oracle Payables to use for the accounting distributions.
- To change to Unpaid the status of the related invoices, select None for the invoice action. The invoices will be available for payment on a new payment document. Click OK to have Oracle Payables void the payment document.
- To apply a hold to the related invoices, select Hold for the invoice action, and select a Hold Name in the Hold window. Click Hold, then click OK to have Oracle Payables void the payment document, reset the status of the related invoices to Unpaid, and apply the hold you selected to the related invoices.
- To cancel all related invoices and reset their amounts to zero, select Cancel for the invoice action. Click OK to have Oracle Payables void the payment document and cancel the related invoices.

3. Save your work.

Voiding Unused Payment Documents
Payment Documents: Additional Information Region
(N) Setup—>Payment—>Banks (B) Bank Accounts (B) Payables Documents
You can do a mass void of unused check stock in the Document Information region of the Payment Documents window.
Oracle Payables prevents you from voiding negotiable payments using this window.
1. To query the bank, choose Bank Accounts, and query the bank account in the Bank Accounts window.
2. Click Payment Documents to navigate to the Payment Documents window.
3. In the Additional Information region, choose Void Unused Documents.
4. Enter the range of documents you want to void, and enter a void date. These documents will no longer be available for use.
5. Save your work.

Void Payment Restrictions:
INVOICES PAID BY ANOTHER PAYMENT: When you void a payment, you cannot cancel a related invoice if it was partially paid by a second payment. Instead, when you choose Cancel Invoice, the system applies an ”Invoice Cancel” hold to the invoice for your reference. You can release the hold manually in the Invoice Holds window.

CANCELLING ASSOCIATED INVOICES: If you attempt to cancel an invoice that has been partially paid by another payment by using the Cancel Invoice Action, instead of cancelling the invoice, Payables
applies an Invoice Cancel hold to the invoice. This hold is manually releasable.

CLEARED PAYMENTS: You cannot void a payment that the bank has already cleared.

PREPAYMENTS: You cannot void payment on a payment document that pays a prepayment that you have applied to an invoice. You must first unapply any prepayments, and then you can void the payment.
 

Refunds

When a supplier or employee sends you a refund for an invoice payment you have made, you can record the refund in Payables. A refund closes out an outstanding credit balance, so you are actually making a negative payment for a credit balance. The credit balance can consist of the outstanding balance of any combination of the following documents, as long as the sum is negative and equals the refund amount: 

  • Invoices
  • Debit memos
  • Credit memos
  • Expense report
Paying these documents with a refund records each document as paid, and gives you a complete supplier transaction history.
For example, suppose you want to stop doing business with a supplier. You have an overall $100 credit balance with the supplier. The supplier sends you a $100 refund for the credit balance, which consists of a credit memo of $250 and an unpaid invoice of $150. You enter a $100 refund (a $100 negative payment), and apply it to the invoice and credit memo. After you apply the refund, the invoice and credit memo are recorded as paid, and you have no outstanding documents for the supplier.

When you record a refund, Payables debits either your cash or cash clearing account and credits either your expense or liability account, depending on whether you use cash or accrual accounting. You can take discounts on payables documents you pay with a refund.
Note: If you withhold taxes at payment time, Oracle Payables does not automatically withhold taxes if you pay with a refund. 

Refunds for Prepayments
You may receive refunds from suppliers for prepayments you have made to them, for example, a refund for a deposit or repayment of a travel advance.
If you receive a refund for a prepayment, enter an invoice and apply the prepayment to it. Enter a debit memo for the invoice. You can then pay the debit memo with the refund.

Entering Refunds
Use the Payments window to record a refund payment for one or more outstanding Payables documents. This enables you to close an open credit balance and maintain a full transaction history for the supplier. The Payables documents you select must be in the same currency as the refund currency, and the sum of the documents you select must equal the amount of the refund.
You can identify negative supplier balances by submitting the Accounts Payable Trial Balance Report with the parameter Negative Balances Only set to Yes.

Recording Refunds for Invoices When a Credit Balance Exists
You pay debit balance with refunds in the Payments window. If you know the credit or debit memo you want to pay, you can query it in the Invoices window, choose the Scheduled Payments tab, and then choose the Pay button.

Prerequisite
Set up the bank account in which you will deposit the refund. This can be the same bank account you use to make payments. Set up the appropriate cash account and, if applicable, set up a cash clearing account.

Recording a refund when a credit balance exists:

1. In the Payments window, enter a negative value in the Payment Amount field. Trading Partner, Bank Account, Payment Date, Payment Method, and Document Number are required fields.
Enter any other relevant information.
2. Click Enter/Adjust Invoices. The Select Invoices window opens.
3. Query the supplier's unpaid or partially paid invoices that are in the same payment currency as the refund currency. Select any combination of positive and negative amount invoices. For each invoice, enter the amount that you want to pay with the refund.
To see additional information about any invoice, choose the Invoice Overview button.
4. Save your work. Payables records the refund and updates the status of each selected invoice to Paid.

Recording Refunds When No Credit Balance Exists
Your supplier may send you a refund when no credit balance exists, for example, for an applied prepayment. You can record it by entering a debit memo and paying it with a refund.

Prerequisite
Set up the bank account in which you will deposit the refund. This can be the same bank account you use to make payments. Set up the appropriate cash account and, if applicable, set up a cash clearing account.

To record a refund when a credit balance does not exist:
1. Enter and validate a debit memo for the refund amount. Select the debit memo in the Invoices window.
Click Actions. Select the Pay in Full option. The Payments window opens.
2. Enter a Bank Account, Payment Date, and Document Number. Enter any other relevant information.
3. Save your work. Payables records the refund and updates the debit memo status to Paid.

Accounting in Payables


Now in release 11i, Oracle Payables creates and stores accounting entries in the subledger. You can create accounting entries for invoice and payment transactions in Payables. Each transaction that has accounting impact is called an accounting event.
You can create accounting entries by submitting a batch program(Payables Accounting Process). Or you can create accounting entries from the transaction window for a specific invoice, invoice batch, payment, or payment batch. After Payables creates accounting entries, you can view the accounting entries in the following windows in Payables:

  • View Accounting Lines, which also appears with the following names, depending on where you are in the application when you navigate to the window.
– View Invoice Accounting
– View Payment Accounting
  • Update Accounting Entries. In this window you can update accounts on any accounting entries that were created with invalid accounts. After you create accounting entries, you can submit the Payables Transfer to General Ledger Program to transfer them to an interface.
From the interface, you can create journal entries and transfer them to your general ledger for posting. If you post entries in Oracle General Ledger, you can drill down from a journal entry line to the accounting entry or transaction in Payables. If you use budgetary control, then when you account for an invoice, Payables also creates any necessary encumbrances or encumbrance adjustments for the invoice. You can view encumbrances in the View Encumbrances window

Accounting Events

An accounting event is a Payables transaction that has accounting impact. After an accounting event completes, you can create accounting entries for it by creating accounting entries for the category or document class that includes the event. The two document classes in Payables are invoices and payments. The following is the complete list of the accounting events in Payables, listed by document class.
Invoices
– invoice
– invoice adjustment
– invoice cancellation
– prepayment application
– prepayment unapplication

Payments
– payment
– payment adjustment
– payment cancellation
– (future dated) payment maturity
– payment clearing
– payment unclearing
The following descriptions give an overview of the event and the accounting that Payables does for each event. These descriptions assume that you use accrual basis accounting, unless there is a specific reference to cash basis accounting.

Invoice Event
The invoice event occurs when the Invoice Validation process successfully validates a new invoice. Accounting entries for this event are created for the accounts on each invoice distribution, and the liability account of the invoice.

  • If you do not use Automatic Offsets, the system creates a single liability entry for the invoice liability account.
  • If you use Automatic Offsets, then Payables creates liability entries to offset each distribution on the invoice. It builds the liability account based on your automatic offset method, either balancing segment or account.
In addition, during accounting for the invoice event, Payables creates or adjusts encumbrances, if necessary. If the invoice is purchase order matched, then Payables also records encumbrances for any invoice price variance or exchange rate variance.
If you use cash basis accounting, when you submit the accounting process for an invoice event, Payables will update the status to accounted, but Payables will create no accounting entries.

For the invoice event, the accounting date is the GL Date on the invoice distribution. Note that if an invoice has distributions with different GL Dates, the earliest GL Date will be used when accounting for the invoice event, and Payables will record the distributions with the later GL Date as an invoice adjustment event.

Invoice Adjustment Event
The following are examples of transactions that are invoice adjustment events:
  • Reversal of an existing distribution for an accounted invoice
  • Adding a new distribution to an accounted invoice
  • Accounting for the invoice event for this invoice includes only the distributions with the earliest GL date. Payables groups the other distributions by GL Date and accounting for these groups of distributions are recorded for separate accounting events.
Note that if the invoice is paid and the payment has already been accounted, if you adjust the invoice, the system will not  automatically adjust the payment accounting entries. The accounting date for this event is the GL Date on the invoice distribution.

Invoice Cancellation Event
This event occurs when you cancel an accounted invoice. This event accounts for the new, negative amount distributions (reversals) that are created when you cancel an invoice. This event reverses all existing accounting entries for the invoice.
The accounting date for this event is the GL Date on the invoice distribution.

Prepayment Application Event

This event accounts for the application of a prepayment to an invoice. Since this is an invoice event, cash basis accounting will not account for it until you pay the invoice.
This event credits the prepaid account for the amount of the application, and debits the liability account because the prepayment was a payment on the invoice. The accounting date for this event is the GL Date on the Prepayment type invoice distribution.

Prepayment Unapplication Event
This event accounts for the unapplication of a prepayment. It reverses any accounting entries that were recorded for the prepayment  application. The accounting date for this event is the GL Date on the Prepayment type invoice distribution.

Payment Event
Accounting entries for this event record payment of an accounted invoice.
Payables will not account for a payment until the paid invoices are accounted.
  •  If you use accrual basis accounting, Payables creates entries to relieve the liability of the invoice accounting entries. Payables will also record any gains and losses if you account for gains and losses at payment issue.
  •  For cash basis accounting, accounting for the payment event creates entries for the accounts on the paid invoice distributions. Payables creates accounting entries for this event only if the Account for Payment When Payment is Issued option is enabled in the Payables Options window.
When the payment accounting options in the Payables Options window are set to account for payments when they are issued:
• If you account for payments at payment issue only, then accounting entries for this event credit the cash account.
• If you account for payments at both issue and clearing, accounting entries for this event credit the cash clearing account.
For future dated payments, accounting entries for this event credit the Future Dated Payment Account from either the payment document or the supplier site, depending on your Payables option.

Based on your system setup and the transaction details, this event might also create discount or rounding entries. For payments, including future dated payments, the accounting date for this event is the payment date. If the payment date is in a closed period, then the GL Date is the first day of the next open period.
If you account for payments only when they clear, then Payables does not record any entries for the payment event, but instead records the payment during the payment clearing event.

Payment Maturity Event
This event creates accounting entries for future dated payments when their status is updated from Issued to Negotiable. After a future dated payment matures, you can update its status in two ways:
• Submit the Update Matured Future Payment Status program
• Manually update the status in the Status field of the Payments window.

Accounting entries for this event debit the future dated payment account.
• If you account for payments only at payment issue, then accounting entries for this event credit the cash account.
• If you also account for payments at payment clearing, then accounting entries for this event credit the cash clearing account.
Payables creates accounting entries for this event only if the Account for Payment When Payment is Issued option is enabled in the Payables  Options window.
The accounting date for this event is the maturity date on the future dated payment.

Payment Adjustment Event
A payment adjustment event occurs when you change the invoices recorded on a Manual payment.
For the newly selected invoices, the accounting entries for this event relieve the liability accounts in the amount of the payment. For the originally paid invoices, the entries reverse the invoice liability that the payment had relieved.
Payables also reverses any gains or losses for the originally paid invoices, and records any gains or losses for the newly selected invoices.

Payables creates accounting entries for this event only if the Account for Payment When Payment is Issued option is enabled in the Payables Options window. For payments the accounting date for this event is the payment date. If the payment date is in a closed period, then the GL Date is the first day of the next open period.

Payment Cancellation Event
This event occurs when you cancel (void) a payment. This event reverses accounting entries for the payment.
The accounting date for this event is the void GL Date on the payment. If the void GL date and the payment date are different, then when you account for the payment, you will get both a payment event and a payment cancellation event.
Payables creates accounting entries for this event only if the Account for Payment When Payment is Issued option is enabled in the Payables Options window.

Payment Clearing Event
This event occurs when you either clear or reconcile a payment in Oracle Cash Management. Payables creates accounting entries for this event only if the Account for Payment When Payment Clears option is enabled in the Payables Options window.
Accounting entries for this event credit the cash account.
• If you account for payments both at issue and clearing, then accounting entries for this event debit the cash clearing account.
• If you account for payments only at clearing,
– and you use accrual basis accounting, then accounting entries for this event debit the liability account.
– and you use cash basis accounting, then accounting entries for this event debit the expense account.

Also, you may have accounting entries for gains, losses, bank charges, and negative amount bank errors.
Note that positive amount bank errors are recorded through Oracle Receivables.

The accounting date for this event is the Clear Date you enter in Oracle Cash Management.

Payment Unclearing Event
This event occurs when you either unclear or unreconcile a payment in Oracle Cash Management.
Accounting entries for this event reverse the accounting entries that were recorded during the payment clearing event.
Payables creates accounting entries for this event only if the Account for Payment When Payment Clears option is enabled in the Payables Options window and after the corresponding clearing event is accounted.
The accounting date for this event is the GL Date on the uncleared payment.

Distribution Sets

You can use a Distribution Set to automatically enter distributions for an invoice when you are not matching it to a purchase order. For example, you can create for an advertising supplier a Distribution Set that allocates advertising expense on an invoice to four advertising departments.


  • Assign a default distribution set to a supplier site so that Oracle Payables will use it for every invoice you enter for that supplier site, or assign a distribution set to an invoice when you enter it.
  • Enter a name that describes the use of the Distribution Set, and identify the distribution set as either full (with all percent amounts totaling 100%) or skeleton (with all percent amounts equaling 0%).
If you create a skeleton distribution set, include skeleton in the name to remind you during invoice entry to enter the amounts on the invoice distributions.
  • Define an unlimited number of distribution lines for a distribution set.
  • Optionally, assign an iIncome tax type or an invoice tax name to distribution sets.
To create a Skeleton Distribution Set:
1. In the Distribution Sets window enter the Name and Description of the Distribution Set you are creating.
Suggestion: If you create a skeleton Distribution Set, include skeleton in the name to remind you to enter the line amounts.

2. Enter the Account and Description for each distribution and leave the Percentage at zero. Create as many distributions as you need. If you are creating a Distribution Set for a federally reportable supplier, optionally enter an Income Tax Type.

3. Save your work. Payables automatically assigns type Skeleton to your Distribution Set.

 



Voucher Numbers and Document Sequences

You can assign a unique voucher number to each invoice and payment document in your Payables system so you have a unique identifier for each document. For example, you may get two invoices with identical invoice numbers from two different suppliers. If you assign a voucher number to each, you can locate each invoice based on its unique voucher number.


Assigning unique voucher numbers to documents is called document sequencing. You can set up document sequencing for all of the documents you use in all of your Oracle Applications. Voucher numbers provide proof of completeness. If you use sequential voucher numbers, you can confirm that no document has been lost. Even if invoices or payments are deleted, each voucher number retains audit records. You can also maintain an audit trail because you can trace a journal entry back to the original document in Payables.

When setting up document sequencing, you select a set of numbers, called a sequence, that you will assign to a type of document. The type of document is called a document category. For example, you may decide to assign the sequence of numbers to a document category of Credit Memo Invoices. Then, each Credit Memo you create will have a unique voucher number. Specifying the sequence that will be assigned to a category is called assignment. When you create and save a sequence, you cannot change it. When you save it, a concurrent process starts that automatically generates the sequence. Wait until this process completes successfully before continuing with assigning the sequences to a category.
Attention: Do not use voucher numbers that exceed nine digits. If your a voucher number exceeds nine digits in Payables, then Payables cannot process the document.

Sequential Numbering Profile Option
The Sequential Numbering profile option controls whether you can assign voucher numbers to documents, and whether you are required to assign voucher numbers to documents. This option can be enabled at the Responsibility, Application, Site, or User level. You can choose one of the following options:
  • Not used :The system does not enforce sequential numbering. It does ensure that any numbers entered are unique but it does not require the next available number. You cannot enable the Allow Document Override Payables Option. You cannot enter a document category or sequence name.
  • Partially Used : The system enforces sequential numbering for all of the sequences that are assigned to a document category. If you create a document and no active sequence has been assigned to its document category, then Payables displays a warning message that a sequence does not exist. You can proceed without a sequence, or you can define and assign the sequence before you proceed.
  • Always Used :The system enforces sequential numbering for all document categories. If you attempt to create a document and no active sequence has been assigned to its document category, then you cannot proceed until you define and assign a sequence.
Document Categories
A document category is a set of documents (invoices or payments) that share similar characteristics. You can assign a single document sequence to one or more document categories. For example, you could assign one sequence to all invoice categories. Payables predefines the following categories for Payables documents:
Predefined invoice categories: Standard Invoices, Credit Memo Invoices, Debit Memo Invoices, Expense Report, Interest Invoices,Mixed Invoices, Prepayment Invoices, Recurring Standard Invoices
Predefined payment categories: Check Payments, Clearing Payments, Electronic Payments, Supplier Refund Payments, Wire Payments.
  • When a document is created, Payables automatically assigns the default document category to the document.
Invoices: Payables assigns a default invoice document category in the Document Category Name field in the Invoices window based on the value you select in the Invoice Type field in the Invoices window
Payments: In the Payment Documents window, Payables defaults the payment document category based on the payment
method you assign to the payment document. When you create a payment, the document category defaults from the payment document.
  • You can use the document categories that Payables provides and you can define additional categories. If you enable Document Category Override in the Invoices and Payments regions of the Payables Options window, you can override the default document category that Payables automatically assigns to invoices or payments. If you enable this Payables option for payments you can also override the document category in the Payment Documents window.

Choosing a Set of Books


Your set of books defines the account structure, accounting calendar, and functional currency your organization uses to record transactions in Payables. If you are not using the Multiple Organization support feature, you can choose one primary set of books for each installation of Payables. You can choose one primary set of books for each installation of Payables. You can choose a secondary set of books in the Accounting Methods region of the Payables Options window if you are keeping both an accrual and cash set of books.

Your system administrator associates sets of books with one or more responsibilities. Your responsibility determines with which set of books you are working. You have the option of setting up multiple organizations within one installation of Payables. Your system
administrator associates a responsibility with a particular organization and set of books. The name of your set of books appears on all reports you generate in Payables.

If you use the Multiple Reporting Currencies feature, read the Multiple Reporting Currencies in Oracle Applications manual for information on your sets of books.

Payables Options

Use this window to set control options and defaults used throughout Payables. You can set defaults in this window that will simplify supplier entry, invoice entry, and automatic payment processing. Although you need to define these options and defaults only once, you can update most of them at any time to change controls and defaults for future transactions.

 
When you set up Payables you choose a primary accounting method. In the Payables Options window you can also choose a secondary accounting method. The accounting method determines the types of accounting entries Payables creates. For each accounting method, cash or accrual, you choose a set of books in which you will account for transactions.

Set up Payables to create accounting entries in compliance with one of the following accounting methods:
  • Cash Basis Accounting You account only for cash transations. You account only for payments, and do not record liability information for invoices. The payment accounting entries typically debit your expense or asset account and credit your cash or cash clearing account. When you create accounting entries, Payables might also create entries for discount taken and foreign currency exchange gain or loss.
    Payables uses the payment date as the accounting date for your expense and cash journal entries.
  • Accrual Basis Accounting You create accounting entries for invoices and payments. The invoice accounting entries generally debit your expense or asset account and credit your liability account. For prepayments, Payables creates accounting entries that debit your prepayment account and credit your liability account. For prepayment applications, Payables creates accounting entries that debit your liability account and credit your prepayment account.
Payment accounting entries typically debit the liability account and credit the cash or cash clearing account. Payables might also create accounting entries for discount taken and foreign currency exchange gain or loss. When you reconcile payments using Oracle Cash Management, Payables might also create accounting entries for cash clearing, bank charges, bank errors, and foreign currency exchange gain or loss between payment and reconciliation time.
  • Combined Basis Accounting You maintain one set of books for cash accounting and one set of books for accrual accounting.
    You choose which will be your primary and your secondary set of books. Invoice accounting entries are recorded for your
    accrual set of books, and payment accounting entries are recorded in both your cash set of books and accrual set of books.
    Combined basis accounting allows you to produce financial reports for either your cash or accrual set of books. For example, you may want to manage your company on an accrual basis, but require cash basis accounting information for certain regulatory reporting on a periodic basis.
  • 1. Primary Accounting Method Accounting method you use for your primary set of books. Although Primary Accounting Method is not a required field, you cannot create accounting entries until you have entered a primary accounting method. Payables creates accounting entries according to the accounting method you choose.
– Accrual
– Cash
  • 2. Secondary Accounting Method If you want to use combined basis accounting, choose Accrual or Cash for the accounting method you use for your secondary set of books. If you do not want to use combined basis accounting, choose None.
– Accrual
– Cash
– None
  • 3. Set of Books (Primary/Secondary) Payables displays the primary set of books you selected in the Choose Set of Bookswindow. If you use a secondary set of books, select its namefrom the list of values. Your secondary set of books must have the same currency, chart of accounts, and calendar as your primary set of books.
  • 4. Automatic Offset Method Enable Automatic Offsets by selecting Balancing or Account as your Offset Method if you want Payables to automatically create balancing accounting entries for your invoice and payment transactions.
Attention: Carefully consider this option before setting it.  Changing your automatic offset setting after creating accounting entries can result in slower Payables Accounting Process performance. Also, under certain circumstances, changing this setting can result in accounting irregularities.
None : Do not use Automatic Offsets. For your invoice transactions, Payables creates one liability accounting entry, and for your payment transactions, Payables creates one cash type accounting entry.
Balancing :  Payables uses the supplier site’s default liability account and overwrites the balancing segment (usually the company code) with the balancing segment from the expense distribution GL Account.
Account :  When creating the offsetting liability account, Payables uses the expense GL Account from the invoice distribution and overwrites the account segment with the default liability account from the supplier site.
  • 5. Prevent Prepayment Application Across Balancing Segments. If you use Automatic Offsets, you can enable this option to prevent the application of a prepayment amount to an invoice or expense report amount that is charged to a different balancing segment.

Transfer to GL/Mathcing/Currency

Transfer to GL Payables Options
Use this region to set defaults for submission of the Payables Transfer to General Ledger Process. If you use Oracle General Ledger you can also set defaults for submitting Expense Report Import, which transfers accounting lines to Oracle General Ledger.

Transfer to GL Interface
Select the level at which you want to summarize accounting entries when you submit the Payables Transfer to General Ledger program. If Payables creates summarized journal entries, Payables combines all the invoice or payment transactions for a particular account or date into a single journal entry line. If you do not create summarized journal entries, then Payables creates a journal entry line for each accounting entry. The original accounting entries remain in Payables until you purge them.

  •  In Detail. Do not summarize the entries.
  •  Summarize by Accounting Date. Summarize the accounting lines by account and date.
  •  Summarize by Accounting Period. Summarize the accounting lines by account and accounting period.
Submit Journal Import
Enable this option if you want to submit journal import when you submit Payables Transfer to General Ledger. Journal Import imports accounting entries from the GL Interface into Oracle General Ledger.

Allow Override At Program Submission
If this option is enabled, then when users submit the Payables Transfer to General Ledger Process, they can change the defaults that you set in this region. Choose this option if you want users to change the Transfer to GL Interface parameter when submitting the report for individual journal  categories.

Matching Payables Options
Allow Final Matching Enable this option to allow final matching of purchase order matched invoices. You can indicate a final match when you match an invoice to a purchase order during invoice entry or when you adjust a matched invoice distribution. You cannot final match when you match invoices to receipts.
Attention: If you final match to a purchase order, any subsequent invoices matched to the purchase order will be placed on hold, and you cannot manually release the hold.

Allow Distribution Level Matching Enable this option if you want to allow matching to purchase order distributions. If you enable this
option, you can match an invoice to one or more purchase order distributions. If you do not enable this option, Payables only allows
you to match an invoice to a purchase order shipment.

Allow Matching Account Override Enable this option if you want to allow override of the account for an invoice distribution created from matching to a purchase order. You can override the account for a matched invoice distribution in the Distributions window of the
Invoice Workbench, or on any imported invoices. You cannot override the account for a matched invoice distribution if you use encumbrance accounting, or perpetual receipt accrual. In addition, you cannot override the account if the purchase order is projects related and the item destination for the purchase order distribution is Inventory.

Transfer PO Descriptive Flexfield Information Enable this option if you want Payables to automatically transfer the descriptive flexfield information from the purchase order distribution to the invoice distribution when you match an invoice to a purchase order. If you enable this option, make sure that the flexfield structure is the same for purchase order distributions and invoice distributions.

Currency Payables Options
Use Multiple Currencies Enable this option if you want to enter and pay invoices in a currency different from your functional currency. Payables also allows you to define a multiple currency payment format and bank account if you enable this option.

If you update this Payables option from enabled to disabled, Payables checks and warns you if you have any multiple currency bank accounts that are using multiple currency payment formats. You must inactivate the payment documents that use multiple currency payment formats and change the Multiple Currency field value on multiple currency bank accounts to disabled before you can change this Payables option from enabled to disabled.

Require Exchange Rate Entry Enable this option to require entry of an exchange rate whenever you enter an invoice or a payment in a currency other than your functional currency or an associated fixed rate currency. If you maintain daily rates in the Daily Rates window, Payables defaults the rate automatically, based on the date and the Rate type you enter. If the exchange rate type is User, then Payables always requires an exchange rate, either entered by the user or calculated by the system.

You cannot create accounting entries for or pay foreign currency invoices without exchange rates. After you have entered invoices or
created payments, you can enter exchange rates, either manually, or by using the AutoRate program. When you create future dated payments, you are required to enter the Maturity Rate, Maturity Rate Type, and Maturity Rate Date.

Calculate User Exchange Rate If you already know the functional currency amounts of any foreign currency invoices you are entering, then you can enable this option so Payables can calculate and enter effective invoice exchange rates for those invoices.
This functionality applies to invoices you enter in the Invoices window and invoices you import from the Payables Open Interface. If this option is enabled, then when you enter a foreign currency invoice, if you select the exchange rate type of User and you provide the functional currency amount, then Payables calculates and enters the exchange rate.
Payables allows you to enter a value for functional currency amount in the Invoices window only if this option is enabled. If this option is enabled then when you enter a foreign currency invoice, you still have the option of entering a foreign currency invoice amount and exchange rate so Payables will calculate and enter the functional currency amount.

Exchange Rate Type Payables uses this as the default exchange rate type when you enter invoices or create payments.

Realized Gain/Loss Payables uses these accounts as the default realized gain and loss accounts for payments from each of your bank accounts. If the exchange rate changes between invoice entry and payment, Payables automatically calculates the realized gain or loss and records it in this account. Payables records gains and losses only if you use accrual basis accounting. The Account for Gain/Loss Payables option controls when Payables accounts for gains and losses.

Rounding Payables uses this account for currency rounding at the following times:
  • You use multiple currencies and the payment currency does not round within the payment currency precision. For example, if a payment rounds to 100.001 GBP, the payment will be for 100.00 GBP, and the rounding error of .001 will be recorded in this account.
  • The functional currency amounts of payments do not equal the amount recorded as the liability. The system charges the remaining amount to the rounding account to fully relieve liability. This happens when you make the final payment of an invoice that is already partially paid.
  • You have enabled automatic offsets and the cash account is pooled, and you have rounding errors. The system charges the remaining amount to the rounding account to fully relieve the cash clearing account. This happens when you make the final payment of an invoice that is already partially paid.

Invoice/Expense Report/Interest/Withholding Tax

Invoice Payables Options

1.1 Use Invoice Approval Workflow :  Enable this option if you want to use the Invoice Approval Workflow feature to automate your invoice approval process. The workflow determines if an invoice needs any individuals to approve payment of the invoice, and if so, automatically routes the invoice to designated approvers who then approve or reject the invoice. When you enable this option, almost all invoices must be processed by the Invoice Approval Workflow.

You cannot submit the Invoice Approval Workflow Program unless you enable this option.

1.2 Allow Force Approval: Enable this option if you use the Invoice Approval Workflow Program and want to allow accounts payable processors to override the workflow and manually approve invoices by using the Force Approval option in the Invoice Actions window. You might want to force approve an invoice if the Invoice Approval Workflow does not complete for an invoice, or if you have authority to pay an invoice without using the workflow process.

1.3 Require Validation Before Approval : If you enable this option, then Invoice Approval Workflow does not select any invoice for processing unless the invoice status is Validated. You might want to enable this option if you need the Invoice Validation process to create tax distributions for an invoice before approvers review it.
You cannot enable this option unless you first enable the Use Invoice Approval Workflow Payables option.

2.1 Allow Adjustments to Paid Invoices: Enable this option if you want to allow users to update the distributions of a paid invoice. If you enable this option you can also reverse a match to a purchase order document and then match to another purchase order document that is not final matched. This means you could create a distribution variance on a paid invoice if you do not ensure the distributions total equals the invoice amount when you do your invoice adjustments. You would discover this possible error when you submit Invoice Validation because Invoice Validation would place a Distribution Variance hold on the invoice and prevent you from creating accounting entries for the invoice.

2.2 Recalculate Scheduled Payment: Payables calculates scheduled payments using a start date and payment terms. For example, if the start date is 01–JAN–2002 and the payment terms are Net 30, the invoice will be payable in full on 30–JAN–2002. During invoice entry, Payables automatically calculates scheduled payments for invoices using the invoice payment terms, and the invoice terms date as the start date.

If you enable the Recalculate Scheduled Payment Payables option, Payables automatically recalculates scheduled payments of invoices during Invoice Validation, unless you have manually updated any of the scheduled payments or used the Split Schedule functionality. During recalculation, Payables uses the most recent of the available start date options and the most favorable of the available payment terms options so you can optimize your cash flow. Payables determines which payment terms are more favorable by comparing the rank you assigned to the terms in the Payment Terms window. The following table shows which options Payables uses during the recalculation. The available options are different depending on whether the invoice is purchase order matched.

3.Automatically Create Freight Distribution: If you enable this option, Payables checks the Create Freight Distribution check box in the Invoices window and automatically creates a single freight distribution using the Freight Amount and Freight Account you enter for an invoice. If you usually allocate freight to invoice distributions, or enter freight distributions manually, then do not enable this option.
Freight Account. If you enable the Automatically Create Freight Distribution Payables option, you must enter a freight account.

Payables uses this account as the default freight account for an invoice. You can override this account during invoice entry.
The system uses the value you enter here for all freight charges your suppliers enter online in Oracle iSupplier Portal. If you do not enter a value here then the system prorates freight charges across Item lines on iSupplier Portal invoices. The system uses the value you enter here for all freight charges your suppliers send in XML invoices. If you do not enter a value here then the import prorates freight charges across Item lines on XML invoices.

4.1 Confirm Date as Invoice Number: If you enable this option, then during invoice entry when you accept the invoice date as the default for invoice number, Payables displays a pop–up window that reads, ”Use the Invoice Date as the Invoice Number?”.

4.2 Allow Online Validation: Enable this option if you want to allow users to select Invoice Validation from the Invoice Actions window or choose the Validate button in the Invoice Batches window.

4.3 Allow Document Category Override: Enable this option if you want to allow users to override the default Document Category assigned to an invoice by Payables. Payables automatically assigns a document category to an invoice if your Sequential Numbering profile option is Partially Used or Always Used. Payables predefines a document category for each invoice type. Your system administrator can define additional document categories for an invoice type.

If your Sequential Numbering profile option is Not Used, Payables does not assign a document category to an invoice and you cannot enable this option, or enter a document category for an invoice.

5. GL Date Basis: The date you want Payables to use as the default accounting date for invoices during invoice entry.
  •  Invoice Date. Invoice date you enter during invoice entry.
  •  System Date. Current date for your Payables system. The date you enter the invoice.
  •  Goods Received/Invoice Date. Date that you enter in the Date Goods Received field. If no value is entered, then the invoice date is used.
  •  Goods Received/System Date. Date that you enter in the Date Goods Received field. If no value is entered, then the system date is used.
  •  
6.1 Prepayment Payment Terms: Payment terms that you want to use for all prepayments. For example, you may want to have immediate payment terms for all prepayment type invoices. Note that this value does not exist at the supplier or supplier site level; the value you enter here defaults to all prepayment invoices.

6.2 Prepayment Settlement Days: Number of days you want Payables to add to the system date to calculate a default settlement date for a prepayment. Payables prevents you from applying the prepayment to an invoice until on or after the settlement date. If you do not enter a value here, then Payables will default the supplier site value for invoice payment terms to prepayments you enter.

6.3 Build Prepayment Accounts When Matching: If you enable this option, then when you match a prepayment to a purchase order or receipt, Payables builds the account on each prepayment Item distribution using:
  •  the natural (charge) account segment from the supplier site’s prepayment account, and
  •  all other account segments from the corresponding purchase order or receipt distribution. Payables validates the built account, and if the resulting GL account is not valid and active, then Payables instead defaults the supplier site’s prepayment account. Therefore, if you use this option, you might have some Item distributions that use a built account and some that use the supplier site’s prepayment account, even on the same invoice.
  • If you do not enable this option then Payables always defaults the supplier site’s prepayment account to prepayment Item distributions.
Expense Report Payables Options
Default Template The default expense report template that you want to use in the Payables Expense Reports window. You can override this value in the Expense Reports window. A default expense report template appears in the Expense Reports window only if the expense report template is active.

Payment Terms
Payment terms you want to assign to any suppliers that you create from employees during Expense Report Import.
Suggestion: Define and assign immediate payment terms for your employee suppliers.

Pay Group Pay Group you want to assign to any suppliers that you create from employees during Expense Report Import. You can define additional values for Pay Group in the Purchasing Lookups window.

Payment Priority Payment priority you want to assign to any suppliers that you create from employees during Expense Report
Import. A number, between 1 (high) and 99 (low), which represents the priority of payment for a supplier.

Apply Advances Default value for the Apply Advances option in the Expense Reports window in Payables. If you enable this option,
Payables applies advances to employee expense reports if the employee has any outstanding, available advances. You can override this default during expense report entry.
If you use Internet Expenses and you enable this option, then Expense Report Import applies all outstanding, available advances, starting with the oldest, up to the amount of the Internet expense report.

Automatically Create Employee as Supplier If you enable this option, when you import Payables expense reports, Payables automatically creates a supplier for any expense report where an employee does not already exist as a supplier. If the supplier site you are paying (HOME or OFFICE) does not yet exist, Payables adds the supplier site to an existing supplier. Payables creates a HOME or OFFICE supplier site with the appropriate address, depending on where you are paying the expense report. The Home address is from the PER_ADDRESSES table, and the Office address is from the HR_LOCATIONS table.

Payables creates suppliers based on the defaults you select in this region and employee information from the Enter Person window. You can review suppliers and adjust any defaults in the Suppliers window.

If you do not enable this option, enter an employee as a supplier in the Suppliers window and link the Employee Name/Number to the
supplier before you use Expense Report Import. Payables cannot import expense reports without corresponding suppliers, and lists
them on the Exceptions section of the Expense Report Import Report.

Hold Unmatched Expense Reports This option defaults to the Hold Unmatched Invoices option for the supplier and supplier site for any suppliers Payables creates during Expense Report Import.
When Hold Unmatched Invoices for a supplier site is enabled, Payables requires that you match each invoice for the supplier site to
either a purchase order or receipt. If you enable this option for a site, then Payables applies a Matching Required hold to an invoice if it has Item type distributions that are not matched to a purchase order or receipt. Payables applies the hold to the invoice during Invoice Validation. You cannot pay the invoice until you release the hold. You can release this hold by matching the invoice to a purchase order or receipt and resubmitting Invoice Validation, or you can manually release the hold in the Holds window of the Invoice Workbench.

Payables will not apply a hold if the sum of the invoice distributions by accounting code combination is zero.

Interest Payables Options
Use this region to enable Automatic Interest Calculation and then enter defaults, such as expense and liability accounts, for the interest invoices Payables creates automatically when you pay overdue invoices.

Allow Interest Invoices: Enable this option if you want to allow Payables to calculate interest for overdue invoices and create interest invoices for selected suppliers. Payables automatically creates interest invoices when you pay overdue invoices in a payment batch or with a Quick payment. If you pay an overdue invoice using a manual payment, Payables warns you that interest is due on the invoice and you should pay the invoice in a payment batch or with a Quick payment.

If you enable this option, the setting of the Prorate Across Overdue Invoice option below indicates how you want Payables to account for interest invoices.
When you enable the Allow Interest Invoices Payables option, Payables enables the Allow Interest Invoices option in the Payment Region of the Suppliers window for all new suppliers you enter. You can override this default value at any time. If you do not enable the Allow Interest Invoices Payables option, you cannot enable the Allow Interest Invoices option in the Suppliers window.

Prorate Across Overdue Invoice: If you enable this option, Payables prorates the interest amount across the item distributions on the overdue invoice. It then builds the account for each interest invoice distribution by using
  • the natural (charge) account segment from the interest invoice expense account that you enter below, and
  • all other account segments from the corresponding item distribution of the overdue invoice.
  •  
If Dynamic Insertion is disabled and the GL accounts that Payables builds are not valid and active, then Payables will instead use the
expense interest account for each distribution.

If your enterprise is a United States agency that uses USSGL transaction codes, then Payables also copies the USSGL transaction
codes from the item distributions on the overdue invoice to the item distributions on the interest invoice.
If you do not enable this option then Payables creates interest invoices with one distribution and the expense interest invoice account.

Expense Interest Invoice Account: If the Prorate Across Overdue Invoice option is disabled then when Payables creates an interest invoice it creates a single distribution with this account. If the Prorate Across Overdue Invoice option is enabled then Payables uses the natural (charge) account from the account you enter here when it builds expense accounts for an interest invoice.

Liability Interest Invoice Account: If you enable the Allow Interest Invoices option, you must enter a liability account. Payables uses this account as the liability account when it creates accounting entries for interest invoices. This liability account is always used when interest invoices are automatically created during the payment process. Payables does not overwrite the liability account if you use Automatic Offsets.
Minimum Interest Amount: If you enable the Allow Interest Invoices option, you must enter a value in this field that represents the minimum interest amount Payables will pay. If the calculated interest amount is less than this amount, Payables does not create an interest invoice.

Withholding Tax Payables Options
Use Withholding Tax. Select this option to enable Automatic Withholding Tax. If you enable this option, you have the option to allow your suppliers and supplier sites to be subject to withholding tax.

Allow Manual Withholding. Enable this option to allow manual creation and adjustments of Withholding Tax type distributions for your invoices.

Tax Group. The name of the withholding tax group that you would like to use as the default withholding tax group for the new suppliers you enter.

Apply Withholding Tax. Select the time at which you would like Payables to apply withholding taxes to your supplier's invoices:
  • Never.
  • At Invoice Validation Time. Note: If Payables withholds tax at Invoice Validation, it calculates withholding only once. If you adjust an invoice after you submit Invoice Validation, then you need to manually adjust the withholding tax.
  • At Payment Time. When you create payments in a payment batch or with a Quick payment.
Withholding Amount Basis.
  • Include Discount Amount. Payables includes the invoice discount amount when it calculates withholding tax amounts for the invoice.
  • Include Tax Amount. Payables includes the invoice tax amount when it calculates withholding tax amounts for the invoice.
Create Withholding Invoice. Select the time at which you would like Payables to automatically create withholding tax invoices to remit withheld taxes to tax authorities:
  • Never. You can create a withholding type tax code without entering a tax authority. However, if you change to an option other than Never, you will need to manually ensure that each withholding type tax code has an associated tax authority.
  • At Invoice Validation Time.
  • At Payment Time.
Include Income Tax Type on Withholding Distributions. If you enable this option then you can report on federal income tax withheld (MISC4) for 1099 suppliers.
When this option is enabled, then when Payables automatically creates distributions of type Withholding Tax for 1099 reportable suppliers, Payables automatically provides the following values:
Income Tax Type value of MISC4.
Income Tax Region value, if the Combined Filing Payables option is enabled.
Note: Payables provides these values only for distributions it creates automatically. If you create a Withholding Tax distribution manually, then you need to enter these values manually.

When you enable this option, Payables initiates the Update 1099 Withholding Tax Distributions program, which updates these values on existing Withholding Tax distributions. The program selects distributions to update as follows:

If the current date is before March 1 of the current calendar year then the program updates distributions with a payment date of January 1 of the previous calendar year or later.
If the current date is March 1 of the current calendar year or later, then the program updates distributions that have a payment date of January 1 of the current year or later.
 

Payment accounting/Payment


Bank Account:  The internal bank account you use to disburse funds. Payables uses this value as a default in the Payment Batches window, and the Payments window.

Payment Batch Limit: The default maximum outlay amount Payables will pay for each payment batch. If a payment batch exceeds the maximum outlay, Payables displays a warning message that you are exceeding your maximum outlay, but allows you to proceed with the payment batch.

EFT User Number The number which identifies you as a user of electronic funds transfer services to your bank or clearing organization. Payables includes this information in some EFT payment formats.

Additional Pay Through Days Number of days between your regular payment batches. Payables uses the additional pay through days to determine the default Pay Through Date when you initiate a payment batch. For example, if you define 5 as the value in this field, Payables adds 5 days to the system date to calculate the default Pay through Date when you initiate a payment batch.

Allow Document Category Override Enable this option if you want to allow users to override the default document category assigned to a payment document by Payables. If your Sequential Numbering profile option is Partially Used or Always Used, Payables automatically assigns a document category to a payment document when you define a payment format for the payment document. Payables predefines a document category for each payment method. Your system
administrator can define additional document categories for a payment method. You can then use these additional document categories to override the default document category for a payment document, only if you enable this Payables option.

If your Sequential Numbering profile option is set to Not Used, Payables does not assign a document category to a payment document and you cannot enter a value in this field. Payables also does not allow you to enter a document category for a payment.

Exclude Tax From Discount Calculation If you enable this option, when you enter an invoice, and if you use Header level tax calculation, Payables subtracts the tax amount from the invoice amount when it enters the invoice amount applicable to discount in the Invoices window. If you enable this option, you cannot select Prorate Tax for your Discount Distribution Method Payables option. Note that even if you enable this option, taxes with corresponding offset taxes, such as VAT taxes, will not be excluded from discount calculation.

If you do not enable this option, Payables uses the gross amount (including the tax amount) of an invoice as the invoice amount applicable to discount. When you enter an invoice you can always override the default invoice amount applicable to discount.

Discount Method The method you want Payables to use for distributing the discounts you take when making payments.
If you leave this field blank, Payables uses the System Account method for distributing your discounts.

Prorate Expense: Payables automatically prorates any discounts across all the invoice distributions. Payables assigns the
discount to the charge account unless the invoice is matched to a purchase order with Accrue on Receipt enabled, in which case it is assigned to the price variance account.
If your Exclude Tax From Discount Payables option is enabled in this window and you enable this option, then the discount is prorated only to the expense lines and not the tax lines. 

Prorate Tax: Payables automatically prorates a percentage of the discount amount across the tax distributions. Payables only prorates the percentage of discount amount equal to the percentage of your tax distributions. Payables credits the
remaining discount amount to the Discount Taken account you enter in the Financials Options window.
For example, if your tax distributions are 10 percent of the total invoice amount, Payables prorates 10 percent of the discount amount across the tax distributions. Payables credits the remaining 90 percent of the discount amount to the Discount Taken account.
You cannot select Prorate Tax if your Exclude Tax From Discount Payables option is enabled in this window.

System Account: Payables credits all discounts to the system Discount Taken account you define in the Financials Options
window. If you enable Automatic Offsets, and you want to have Payables distribute Discount Taken amounts across balancing segments, choose this method.
If you enable the Use Bank Charges option in the payment region, the Discount Distribution Method defaults to System
Account and you cannot update it.

Allow Print:
If you enable this option, then you can print Quick payments. You print a Quick payment by selecting the Print Now option in the Payment Actions window.
Suggestion: If you are going to print Quick payments, you may want to have a fast, dedicated concurrent manager queue
and a dedicated printer with checks ready to print.

Allow Pre–Date: If you enable this option, Payables allows you to create payments with a payment date before the system date for any payment except a manual payment.

Allow Void and Reissue: If you enable this option, you can reissue a Quick payment. You may need to reissue a check for a Quick payment if it is spoiled during printing. When you reissue a check, Payables voids the old check and creates a replacement check. The checks are identical except that the new check has a new check number, payment date, and payment exchange rate if you are using multiple currencies.
You cannot select the Void and Reissue option for future dated payments.

Allow Address Change Enable this option if you want to allow users to address a payment to an address other than the invoice’s supplier site’s address.

XML Payments Automatic Confirmation Enable this option if you use the XML Payments feature and want the system to automatically confirm payment batches that generate Process Payment Request XML messages. If you enable this option, then when your system receives a Confirm Business Object Document XML message from your bank that indicates that the XML payment transmission was successful, the system automatically confirms the payment batch that generated the
payment XML message. When the system automatically confirms a payment batch, the user who formatted the payment batch receives a workflow notification that the payment batch was confirmed.

Allow Remit–to Account Override: Check this check box if you want to allow users to change the default primary supplier site bank account during Quick payment and payment batch creation. If you enable this option, you can override the Payables default of the Remit–to field of the Payments window and the Modify Payment Batch window. You can then select an alternate Remit–to account from a list of the supplier site’s active bank accounts that use the same payment currency. If you do not enable this option, you can override the Remit–to Bank Account only in the Scheduled Payments window.

Use Bank Charges: If you want to use the Bank charge feature, enable this option.
If you enable this option, you must enter a value for the Bank Charge bearer field in the Supplier region of the Payables Options window. Also, if you enable this feature, Payables will enter System Account as the value for the discount distribution method field in the Payment region of the Payables Options window, and you cannot override this value.

If you enable this option, you cannot take discounts on invoices.

Account For Payment
Choose when you want to create payment accounting entries. You can select one or both options.
Payables creates the following accounting entries, depending on how the Account for Payment option is set. This accounting assumes you use accrual basis accounting. You specify the GL accounts when you define the payment document. Any accounting entries for gain and loss are controlled by the Account for Gain/Loss Payables option, so they are not included here.


 

I. Both (When Payment is Issued, and When Payment Clears):
Payables accounts for each payment you issue twice—once as an unreconciled payment and once again as a cleared payment. If you select both options you have the same functionality as the Allow Reconciliation Accounting option provided in previous releases.
Payables creates the following accounting entries after payment issue:
1. unreconciled payment: debit the AP Liability account and credit the Cash Clearing account
For future dated payments, debit the AP Liability account and credit the Future Dated Payment Account. Then, at payment maturity, debit the Future Dated payment Account and credit the Cash Clearing account.

2. Payables then creates the following accounting entries after payment reconciliation or clearing in Cash Management:
2.1 reconciled payment: debit the Cash Clearing account and credit the Cash account
2.2 bank charges: debit the Bank Charges account and credit the Cash account
2.3 bank errors: account in Cash account and Bank Errors account. Debits and credits depend whether the bank error was a positive or negative amount

II. When Payment is Issued: Payables accounts for each payment once, after payment issue. After you issue the payment, Payables creates the following accounting entries.
- unreconciled payment: debit the AP Liability account and credit the Cash account.
For future dated payments, debit the AP Liability account and credit the Future Dated Payment Account. Then, at payment maturity, debit the Future Dated payment Account and credit the Cash account.

Although you can reconcile the payment in Cash Management, Payables does not create accounting entries for payment reconciliation, bank charges, or bank errors, or gain and loss at reconciliation.

III. When Payment Clears If you select only this option, Payables accounts for each payment once, after clearing. After you clear the payment in Oracle Cash Management, Payables creates the following accounting entries.
– reconciled payment: debit the AP Liability account and credit the Cash (asset) account.
– bank charges: debit the Bank Charges account and credit the Cash account.
– bank errors: account in Cash account and Bank Errors account. Debits and credits depend whether the bank error was a positive or negative amount.

Supplier Payables Options


Use this region to enter defaults for the Suppliers window. These values then default to the Supplier Site, and then to the invoice. You can override these defaults at any time.

Pay Group: The Pay Group you want to assign to any new suppliers you enter. You can choose any Pay Group you have defined in the Oracle Purchasing Lookups window.

Invoice Currency: The currency that you use as a default for each new supplier you enter.

Terms Date Basis: The date that Payables uses as the payment terms start date when Payables calculates the due and discount date for invoice scheduled payments.
  1.  System. Current date of your Payables system.
  2.  Goods Received. The date you receive goods for invoices you match to purchase orders.
  3.  Invoice. Invoice date.
  4.  Invoice Received. Date you receive an invoice.
Pay Date Basis: The Pay Date Basis default for each new supplier you enter. The Pay Date Basis for a supplier defaults to the new supplier sites you enter for the supplier. You can override the default for each supplier and supplier site.
  •  Discount. Payables selects invoices for payment based on the scheduled payment discount date.
  •  Due. Payables selects invoices for payment based on the scheduled payment due date, regardless of any available discounts.
Bank Charge Bearer:  If you use the Bank Charges feature, indicate whether you or your supplier will pay for any bank charges associated with payments to your suppliers. If your suppliers pay, indicate whether your suppliers use the standard or negotiated rate. This value will default to all new suppliers you enter. You can override this value at the supplier and supplier site. 
  1.   Internal. You will pay bank charges.
  2.  Supplier/Negotiated. Your supplier will bear any bank charges at a negotiated rate.
  3.  Supplier/Standard. Your supplier will bear any bank charges at a standard rate.
Combined Filing Program: Enable this option if you are using 1099 Combined Filing Program reporting. When you submit the 1099 Electronic Media report, Payables will produce K–records for all tax regions participating in the Combined Filing Program that have qualifying payments.
Attention: If you use electronic filing or magnetic media to file your tax information with the Internal Revenue Service and
you are not participating in the Combined Filing Program, do not enable this option. The Internal Revenue Service may
return your 1099 magnetic tape if the tape contains K records.

Use Pay Site Tax Region: You can enable this option only if you enable the Combined Filing Program Payables option.
Enable this option if you want to use a 1099 supplier’s tax region as the default tax region. If you enable this option, Payables uses the 1099 supplier site’s region as the default tax region for the invoice  distributions. You can override this default region for each invoice distribution in Distributions window.

Do not enable this option if you do not want to use a supplier site’s tax region as the default tax region. You must then enter the default tax region you want to use for all invoices in the next field, the Income Tax Region Name field.
The default you choose here determines how many K records Payables will produce on your 1099 Electronic Media. Payables produces one K record for each tax region. If you are participating in the Combined Filing Program, Payables forwards your 1099 qualifying payment information to all the tax regions that participate in the Combined Filing Program. If you enable this option, you may have as many K records as you have different supplier tax regions.

If you choose a default Income Tax region in the next field, you may have only one K record. This would be a K record for that one default tax region. Of course, you can always override the default tax region for each invoice distribution. In this case, Payables will then produce additional K records on your 1099 Electronic Media, one K record for each tax region. Payables only produces K records for tax regions that participate in the Combined Filing Program and that you have entered
(either as a default or manually) on a paid distribution for a 1099 supplier. You can also choose to have your 1099 payment information forwarded to only one tax region regardless of which region your 1099 suppliers do business from. You do this by entering a value in the following Income Tax Region name field. Income Tax Region. You can enter this field only if you enable the Combined Filing Program Payables option and did not enable the Use Pay Site Tax Region option. Enter the tax region you wish to use as the default for the invoice distributions of your 1099 suppliers. You can override this default region for each invoice distribution.

Invoice Tax/Witholding Tax/Tax Defaults and Rules

Tax Defaults and Rules Payables Options

Use this region to set a hierarchy for Payables to use when it provides default values for Tax Code fields. Payables searches the sources you enable, in the order you designate until it finds a valid active Tax Code value (tax code or tax group). When it finds a tax value, it stops searching and defaults the tax value to the document you are creating.

Enable each source you want to use by checking its check box. For each source, enter a rank (1 is searched first), and give each source a unique, consecutive number starting with 1.
Note: Two Payables options supersede the hierarchy you define. If you enable the Enforce Tax from Purchase Order option, Payables always searches first at the Purchase Order Level for purchase order matched documents. If you enable the Enforce Tax From Account option, Payables always searches next at the Natural Account. If the invoice is not purchase order matched or if you have not enabled the Enforce Tax from Purchase Order option, Payables checks the Natural Account first.

Enforce Tax From Account : Enable this option if you want to enforce the relationship between the tax code and the expense or asset account for distributions. If the following conditions are true then Invoice Validation checks that for every account to which you have assigned a tax code, that the tax code matches:

  •  You have enabled the Enforce Tax From Account option.
  •  You have assigned tax codes to accounts in the Tax Options window in General Ledger.
  •  You have disabled the Allow Tax Code Override option in the Tax Options window in General Ledger.

If the tax code does not match the account then Invoice Validation will place the invoice on Natural Account Tax hold.
If you enable the Enforce Tax From Account option, then during Expense Report Import and Payables Open Interface Import the system checks the tax codes of all accounts that have tax codes assigned to them. If the tax code is incorrect, Payables will not import the invoice or expense report and will list it as an exception.

If you enable this option we recommend that you rank Account at or near the top of your source hierarchy to minimize holds.

Enforce Tax From Purchase Order :Enable this option if you want Payables to honor the Taxable flag on the purchase order shipment, and if you want Invoice Validation to verify that the invoice Tax Code value matches the Tax Code value on the purchase order document that the invoice is matched to. If this option is enabled, the system looks at the Taxable flag on the purchase order shipment during matching. If the shipment is nontaxable, then the system does not use your Tax Code Defaults hierarchy, and enters no Tax Code value on the invoice distribution. If the purchase order shipment is taxable, then the system defaults the Tax Code value from the shipment, regardless of the rank you assign to the PO for Matched Invoices source in your Tax Code Defaults hierarchy.

If this option is not enabled, then even though the purchase order shipment is nontaxable, the system continues searching in your Tax Code Defaults hierarchy if it finds no Tax Code value on the purchase order shipment.
If the purchase order shipment to which you matched is defined in Purchasing as taxable, and the Tax Code values on the invoice and the purchase order are not the same, then Invoice Validation automatically applies a Tax Difference hold to the invoice. Invoice Validation also applies a Tax Difference hold to an invoice if the invoice and purchase order Tax Code values are the same and the purchase order shipment to which you matched is non–taxable. Payables releases the hold when
you submit Invoice Validation after correcting the Tax Code on the invoice or on the purchase order you matched to. You can also manually release a Tax Difference hold in the Holds window and the Invoice Actions window.
Note: If you enable this option we recommend that you do not also enable the Enforce Tax From Account Payables option in the Tax Defaults and Rules tabbed region.


Invoice Tax Payables Options

 

Require Tax Entry at Header. If you enable this option, Payables requires you to enter a Tax Code and Tax Amount in the Invoices window when you enter an invoice. This option does not apply to any imported invoices or to credit and debit memos that are entered in the Invoice Workbench. If you use Automatic Tax Calculation at the Header level, Payables automatically calculates a Tax Amount. You are required to enter a value for a Tax Code field only if one has not defaulted from a source designated in your tax hierarchy.

If you have enabled this option and the invoice has no tax, in the Invoices window you enter a tax code with a zero-percent tax rate assigned to it. If you enter a Tax Code and Tax Amount for an invoice, or if your system is set up with a Tax Code default and an automatically calculated Tax Amount, then Payables creates a tax distribution. You can adjust the tax distribution in the Distributions window.

You cannot enable this option if you select Line or Tax Code as your Calculation Level Payables option. If you allow override of the tax calculation level and you enter an invoice using Line or Tax Code level calculation, Payables will not require you to enter a Tax Code or Tax Amount in the Invoices window even if you have enabled the Require Tax Entry at Header option.

Do not enable this option if you want to enter Use type tax codes on invoices. If you enable this option, Payables prevents you from entering Use tax codes on invoices. In addition, when you enable this option and enter a Use type tax code as the default tax code for a supplier site, Payables does not assign the default to the invoices you enter for the supplier site.

You may not want to enable this option if you want to allocate tax across selected invoice distributions.

If the Require Tax Entry at Header Payables option is disabled when you enter an invoice, then the Tax Code and Tax Amount fields are optional.

Note that if you enable this option and if you process expense reports in Payables, then the Expense Report Import program rejects any expense reports that do not have at least one tax line. If an expense report has no tax, you can enter a zero amount line with a zero rate tax.

Use Automatic Tax Calculation. Select this option if you want to enable Payables to automatically calculate and enter tax on invoices. If this option is not enabled, Payables will disable Automatic Tax Calculation options throughout the system. If you disable this option after you have enabled it, Payables will not automatically calculate sales tax for any invoice entered after you disable the option.

If you want to use Automatic Tax Calculation for some invoices, and you also want to create tax distributions for other invoices by manually entering tax distributions, by allocating tax across selected invoice distributions, or by matching to purchase orders, then enable this option. You can selectively disable Automatic Tax Calculation for a particular supplier, supplier site, or invoice. See: Disabling Automatic Tax Calculation.

If you do not enable this option, Payables does no tax calculation but will automatically create a tax distribution if you enter values for Tax Code and Tax Amount in the Invoices window. Payables copies the invoice tax code and tax amount values to the new tax distribution but does no tax calculation.

Calculation Level. If you enable the Use Automatic Tax Calculation option, select the level at which you want Payables to automatically calculate sales tax. This value defaults to new suppliers you enter.
Automatically create tax distributions based on the Invoice Amount and Tax Code in the Invoices window:
  • Header. Automatically create tax distributions based on the Invoice Amount and Tax Code in the Invoices window:
  • Tax Code. Automatically create tax distributions based on the distribution Amount, Tax Code, and Includes Tax check box in the Distributions window. When calculating tax amounts, group lines with the same tax code and Includes Tax check box setting together, calculate tax, and then round the tax amount.
  • Line. Automatically create tax distributions based on the distribution Amount, Tax Code, and Includes Tax check box in the Distributions window. When calculating tax amounts, calculate tax for each distribution, round the tax amount, then add the tax amounts. Allow Calculation Level Override. Enable this option if you want to allow users to adjust the default value of the Calculation Level option for new and existing suppliers.
The Calculation Level defaults in the following order: Payables Options -> Suppliers -> Supplier Site -> Invoices. You can adjust the default calculation level in the Supplier, Supplier Sites, and Invoices windows only if the Allow Override option is currently enabled in the previous window. You can enable the Allow Calculation Level override check box in the Suppliers window for new and existing suppliers only if the Allow Calculation Level Override check box in the Payables Options window is currently enabled.

Distribution Amounts Include Tax. Enable this option if you use Automatic Tax Calculation at the Line level or Tax Code level, and you want the Distribution Amounts Includes Tax check box to be enabled by default for all new suppliers you enter.

When the Distribution Amount Includes Tax check box is enabled at the supplier site, Payables subtracts the calculated tax from non-Tax (Item, Misc, Freight, Prepayment type) distributions when Payables automatically creates tax distributions. When you select this option at the supplier site, Payables always checks the Includes Tax check box for invoice distributions and recurring invoice templates.

You cannot enable this option unless you enable Automatic Tax Calculation and you select Line or Tax Code as your Calculation Level.
This value defaults to the Distribution Amounts Include Tax option in the Suppliers window, and you can change it in the Suppliers window if you enable the following option, Allow Override.

Allow Override. If you enable the Allow Override option, you can override the Distribution Amounts Include Tax check box default value for all suppliers.
If you enable this option you can also adjust the Includes Tax check boxes in the Expense Report Templates window.
Note that if you enable Header as the Calculation Level Payables option, then you cannot enable this option. Therefore you can never enable the Includes Tax check box in any of the following windows: Distributions, Invoice Gateway, Expense Report Templates.


Payment Terms

In the Payment Terms window, you define payment terms that you can assign to an invoice to automatically create scheduled payments and to calcualte discount. when you submit Payables Invoice Validation for the invoice. You can define payment terms to create multiple scheduled payment lines and multiple levels of discounts.
 
You can create an unlimited number of payment terms. Payment terms have one or more payment terms lines, each of which creates one scheduled payment. Each payment terms line and each corresponding scheduled payment has a due date or a discount date based on one of the following:
  1.  a specific day of a month, such as the 15th of the month
  2.  a specific date, for example, March 15, 2002.
  3.  a number of days added to your terms date, such as 14 days after the terms date
  4.  a special calendar that specifies a due date for the period that includes the invoice terms date. Only due dates can be based on a special calendar. Discount dates cannot be based on a special calendar.
Each payment terms line also defines the due or discount amount on a scheduled payment. When you define payment terms you specify payment amounts either by percentages or by fixed amounts. After you define your payment terms, in the Payables Options window you can select default payment terms that Payables automatically assigns to the suppliers and supplier sites you enter.

The payment terms for a supplier site default to the invoices you enter for the site except in the following circumstances:
  • You enter a PO Default or QuickMatch invoice in the Invoice Workbench, in which case the terms default from the purchase order.
  • You import an invoice record that has payment terms specified on the record, or the import process can derive terms from purchase order matching.
You can override the default payment terms on any invoice.

Attention: If you update the payment terms on an invoice, Payables immediately recalculates the scheduled payment for
the invoice. Thus, you must re–enter any manual adjustments you made to the previous scheduled payment. For example, if you update the payment priority on a particular scheduled payment and then change the payment terms, Payables will
immediately recalculate the scheduled payment using the same payment priority defaults as before and you will need to update the payment priority again.

1.1 Cutoff Day  For Day of Month type terms only, the day of month after which the due and discount dates of the scheduled payment will be in a future month. The exact month depends on the value you enter for Months Ahead. Payables compares the invoice terms date to the Cutoff Day. If you leave this field blank, Payables always uses the current accounting month to determine the due and discount dates. For example, your Cutoff Day is 11, your Months ahead is zero, and your Day Of Month due date is 15. If you enter an invoice with a terms date of January 12, Payables will set the due date for February 15. If you use Due Days or Fixed Date type terms, do not enter a cutoff day.

1.2 Rank If you enable Recalculate Scheduled Payment, enter a unique value to rank your invoice terms. 1 is the highest rank. Payables uses ranks to choose the most favorable payment terms from the invoice and purchase order. During Payables Invoice Validation, Payables recalculates the scheduled payment using the most favorable terms only if the Recalculate Scheduled Payment Payables option is enabled.

2.1 % Due The portion of an invoice due. The total of your scheduled payment lines must equal 100%. You cannot combine percentages due and amounts due for one set of payment terms.

2.2 Amount For amount due terms only, enter the amount due. Typically amount due terms have more than one payment terms line since you must specify zero as the amount on your last payment terms line.
Payables uses the zero amount payment line to determine the remaining amount due on the last scheduled payment.

3.1 Calendar If you enter a value in the Calendar field, Payables determines due dates for scheduled payments by using a special calendar. A special calendar is divided into periods, and each period has a due date assigned to it. When you assign due dates to the periods of a payment terms calendar, you can avoid weekends, holidays, and so on. You can define special calendars for payment terms in the Special Calendar window.
Note: If you use calendar–based terms, be sure to use calendars with periods defined for any invoice terms date that you will use. You cannot assign calendar–based terms in the Invoices window if there is not a period defined for the terms date. If you do so in the Invoice Gateway, then the system will use the terms date as the due date. If you do so for an expense report, you cannot import it.

3.2 Fixed Date Specific month, day, and year on which payment terms are due.

3.3 Days Payables adds this number of days to the invoice terms date to determine the due or discount date on your scheduled payment line. You cannot enter values in the Day of Month and Months Ahead fields for a payment terms line if you enter a value in this field.

3.4 Day of Month/Months Ahead
Day of Month. Payables uses the value you enter here to calculate a due or discount date for a scheduled payment. For example, enter 15 to have Payables schedule payment for the 15th day of the month. Enter 31 if you want to have Payables schedule payment for the final day of the month, including months with less than 31 days.

Months Ahead. For Day of Month type terms only. Payables uses the value you enter here in conjunction with the Cutoff Day you enter to calculate the due or discount date of a scheduled payment line. If you enter zero in this field and the terms date of an invoice is the same as or later than the Cutoff Day, then Payables uses the day in the Day of Month field for the next month as the due date of an invoice payment line. If you enter 1 in this field, Payables uses one month beyond the next month as the due date.

You cannot enter a value in this field if you enter a value in the Due Days field.

4.1 % Discount Payables uses the percentage you enter here to calculate the discount amount available for a scheduled payment. Payables multiplies this percentage with the amount due on the scheduled payment line to determine the discount amount available on the scheduled payment line. In the Second and Third Discount regions, you can enter second and third discount percentages for discounts available if you miss the first discount date. Do not enter a value in this field if there is no discount available.

Invoice Tolerances

Use the Invoice Tolerances window to define the matching and tax tolerances you want to allow for variances between invoice, purchase order, receipt, and tax information. You can define both percentage–based and amount–based tolerances.

Tolerances determine whether Payables places matching or tax holds on an invoice. When you submit Payables Invoice Validation for an invoice that you have matched to a purchase order or receipt, Payables checks that the invoice matches the purchase order or receipt within the purchase order matching tolerances you define. When you submit Payables Invoice Validation for an invoice with a tax amount, Payables checks that the actual invoice tax amount equals the calculated tax amount within the tolerances you define.

If you use a percentage based tolerance, Payables calculates the tolerance based on the invoice amount, including tax. For example, you have a $100 item on an invoice and the tax rate is 8%. You have a 10% tax tolerance. You can enter a tax distribution amount between $7.20 to $8.80 without getting a Tax Variance hold on the invoice. If you enter a zero for a percentage tolerance and enable the check box for that tolerance, Payables will not allow any variance at all. If you want a low tolerance, you can enter a very small percentage. If you enter no value, then Payables will allow infinite variance.
Payables displays next to the tolerance field the name of the hold that Payables Invoice Validation applies to your invoice if the variance exceeds the tolerance you define.

PO Matching Purchase order matching tolerances apply to any purchase order matched invoice, including invoices matched to receipts.

• Maximum/Quantity Ordered. Enter either the percent or quantity difference above purchase order shipment line quantity ordered that you allow suppliers to invoice. Payables Invoice Validation checks the quantity billed against the quantity ordered without taking price into consideration. Enter a Maximum Quantity Ordered tolerance only if most of your purchase orders are for the same relative value.

• Maximum/Quantity Received. Enter either the percent or quantity difference above purchase order shipment line quantity received that you allow suppliers to invoice. Payables Invoice Validation checks the quantity billed against the quantity received without taking price into consideration. Enter a Maximum Quantity Received quantity tolerance only if most of your purchase orders are for the same relative value.

• Price. The percentage difference above purchase order shipment line unit price that you allow suppliers to invoice.

• Exchange Rate Amount. The amount of variance you allow between an invoice amount and the amount of the purchase order shipment to which it is matched. Payables compares the functional currency of each, based on the invoice and purchase order exchange rates, respectively. Enter a value in this field only if you enter foreign currency invoices in Payables.

• Shipment Amount. The amount of variance you allow between all invoice amounts (in transaction currency) matched to a shipment and the amount of the purchase order shipment. Payables Invoice Validation applies the Maximum Shipment Amount hold if the match exceeds the tolerance.

• Total Amount. The total amount of variance you allow for both the Exchange Rate Amount variance and the Shipment Amount combined. If you do not use foreign currency, do not enter a value in this field.

Invoice Hold and Release Names


Use the Invoice Hold and Release Names window to define the names that you use to manually hold or release invoices. You can define hold names that you assign to an invoice during entry to place the invoice on hold. For example, ”Needs CFO Approval”. You can also define release names that you use in the Invoice Holds window or Invoice Actions window to remove the holds you apply to invoices. For example, ”CFO Approved”. You cannot pay an invoice that has a hold applied to it.
  • You can define as many invoice hold and release names as you need.
  • You can also determine whether to allow accounting entry creation for the hold names you define. If you assign to an invoice a hold name that does not allow accounting, then you cannot create accounting entries for the invoice until you remove the hold.
Payables predefined invoice hold names
Payables predefines hold names and release holds that it uses to apply and release invoice holds during Invoice Validation.
In the Invoice Hold and Release Names window, you can query the predefined hold and release names that Payables provides, but you cannot modify them.
 
Release Types
Release type names are used by Invoice Validation when it releases holds. You can manually release holds using names with release types Invoice Release Reason, Matching Release Reason, Variance Release Reason, Hold Quick Release Reason, and Invoice Quick Release Reason. Release hold names appear on a list of values for the Release field of the Invoice Actions and Invoice Holds windows of the Invoices form. You can define release names for the following release types:

Invoice Release Reason You can use names with this release type to release one manually releasable hold for one invoice in the Invoice Holds window.
  • Invoice Quick Release Reason. You can use names with this release type to release all manually releasable holds for one invoice in the Invoice Holds window.
  • Hold Quick Release Reason. In the Invoice Actions window, you can use the release name with this release type to release all holds from invoices that you query in the Invoice Workbench. In the Invoice Actions window, you can use only release names with this release type. Payables releases only the type of hold you entered as part of your search criteria.
  • Matching Release Reason. You can use release names with this release type to release a Matching hold that Payables automatically applies to an invoice during Invoice Validation.
  • Variance Release Reason. You can use this type of release name to release Variance Holds that Invoice Validation automatically applies to invoices that have a tax variance.
The following release types are predefined by Payables:
  1. Acct Release Reason. For an invoice, Payables releases an account hold when you correct the invalid account and submit Invoice Validation.
  2. Amount Lowered Reason. When you submit Invoice Validation, Payables releases a Prepaid Amount hold after you have unapplied a prepayment that, after tax calculation, exceeded the amount of the invoice to which is was applied
  3. Funds Release Reason. Payables uses these releases for funds checking if you use budgetary control. Payables releases a Funds hold on an invoice during Invoice Validation if sufficient funds exist for an invoice or if Payables can perform funds checking.
  4. Sufficient Information. Payables predefines one release name with the Sufficient Information type. Payables places a Sufficient Information release name on an invoice after you enter an exchange rate for a foreign currency invoice.
  5. Variance Release Reason. Payables predefines two release names with the Variance Release Reason type.
Payables places the Variance Corrected release name on an invoice if you correct an invoice variance. Payables places this
release name when you submit Invoice Validation for an invoice with a distribution or tax variance hold for which you have
corrected the variance.

You cannot enter a variance release reason for an invoice with a Distribution Variance hold. You must adjust the invoice so that the total of the invoice distributions equals the invoice amount. You can enter Variance Override for an invoice if you want to release an invoice from a tax variance hold using the Holds window. You can also define other Variance Release Reasons to use for releasing invoices from tax variance hold.

Interest Rates


In the Payment Interest Rates window, you define interest rates Payables uses to calculate and pay interest on overdue invoices. Payables calculates interest on overdue invoices only if you enable both the Allow Interest Invoices Payables option, and the Allow Interest Invoices option for the supplier site of an invoice.

Payables calculates interest based on the rate you enter in this window in accordance with the United States Prompt Payment Act. The formula used compounds monthly, up to a maximum of 356 days interest.

For each rate you define, specify during which dates the rate is effective. Effective dates of rates cannot overlap. For example, the current interest rate is 7% for all unpaid balances. The interest rate on overdue invoices will rise to 7.5% on December 1, 2002. This new rate will be valid for four months. You enter two date ranges and interest rates, the first from today’s date to November 30, 2002 (interest rate 7%) and the next from December 1, 2002 to March 31, 2003 (interest rate 7.5%).

You can add or change a rate at any time. Payables uses the interest rate that is valid on your payment date to calculate and pay interest on overdue invoices.

If the system cannot find a rate then it uses zero as the rate.

Tax Recovery Rules


If you record partially recoverable and nonrecoverable taxes in Payables or Purchasing, the system calculates the recovery rate for tax codes (including tax codes in tax groups) you use for invoices and purchases order distributions. In the Tax Codes window you specify the recovery rate by entering either a fixed percentage rate or a tax recovery rule. Use a tax recovery rule if the recovery rate varies, depending on the following distribution attributes:
  • Distribution account
  • Invoice date
  • Condition (for example, supplier type)
In the Tax Recovery Rules window you can define tax recovery rules. Each tax recovery rule can have multiple rates. Each active rate must have a unique combination of account range, effective dates, and condition. For example, you set up a recovery rule with different recovery rates for January and February. When the system calculates the recovery rate for a January invoice distribution, it uses the January rate and for a February distribution it uses the February rate.
The degree of tax recovery can be influenced by factors such as:
  1. the nature of the business or the organization
  2. the nature of the goods or services purchased
  3. the intended usage for the items purchased
The account for a purchased item provides information about its recovery rate. For example, the account records information that might influence the recovery rate such as the division or cost center purchasing the item, and the natural account of the item. You can set up recovery rules to assign recovery rates based on the rate you assign to an account range.

When you define a recovery rule, you can specify the recovery rate with either a percentage rate or a PL*SQL function name. Specify a PL*SQL function name when you need to use a complex tax rule.

Tax Codes


In the Tax Codes window, you define the tax names, or tax codes, you use on invoices to record invoice taxes you pay to suppliers and tax authorities. Each tax code has a tax type, a tax rate, and an account to which you charge tax amounts.

You can define tax codes that have different tax rates during an effective date range you specify. For example, you can define a tax code that has a 10% rate one year, and a 10.5% rate the next year. Payables automatically uses the correct rate depending on the invoice date.

You define the Tax Code Defaults hierarchy in the Payables Options window to determine the order in which Payables searches for a tax value (tax code or tax group) when a Payables document requires a default tax value. You can assign tax codes to expense or asset accounts so that Payables will automatically enter the appropriate tax code when you enter an
account. If you use automatic tax calculation, Payables calculates the invoice sales tax and automatically creates tax distributions. You do not need to define special tax codes for distributions that include tax. Simply select the Includes Tax check box when you enter the distribution, and Payables adjusts the calculation.

During the Payables Invoice Validation process, Payables uses the tax code to validate that you have entered tax distributions correctly. After you define tax codes, you can group them into tax groups in the Tax Groups window. You can then enter a tax group in the Tax Code field for Payables and Purchasing transactions to calculate multiple taxes on a single taxable item.

Offset Tax Codes
Offset taxes are negative–rate taxes. In the Tax Codes window you can associate Offset taxes with Sales or User–defined taxes. When you use the Sales or User–defined tax on an invoice, you record the tax, but the associated Offset tax reduces or eliminates your tax liability.

To associate an Offset tax with a Sales or User–defined tax, first define the Offset tax. Then when you define the Sales or User–defined tax, enter the Offset tax code in the Offset Tax field.

Withholding Tax Codes
Withholding Tax type tax codes can have multiple rates, effective date ranges, tax amount limits, and taxable amount limits. You can also link a tax authority supplier to a Withholding Tax type tax code so you can create invoices to pay taxes you withheld from your suppliers.

Tax Groups


Use Tax Groups to combine your tax codes into tax groups to calculate multiple taxes on single taxable items in your Payables and Purchasing transactions. You can also use this feature to manage multiple tax recovery requirements. If you only use single tax codes with a single recovery rate, you do not need to set up tax groups.

You can use your tax groups with any transactions that you enter along your procure–to–pay chain. When you use a tax group, the system calculates the tax amounts for each tax code in that tax group. You can assign any Sales or user–defined tax code to a tax group. These tax codes can have associated offset taxes, and recovery rules or recovery rates.
Attention: The tax rates and accounting entries used throughout this manual are provided for illustration purposes only.

Please contact a tax professional for specific implementation requirements. You can assign individual tax codes to tax groups in the Tax Groups window. After you define your tax groups, you can either enter a tax group or an individual tax code in fields that require a tax code. For example, you can enter a tax group name in the Tax Code field in the Invoices window. The system will then calculate multiple taxes for the invoice. You can assign the same tax group to multiple taxable items on an invoice. However, you can use only one tax group within a single invoice.

The Tax Defaulting Hierarchy can also use tax group values to provide default tax values to transactions you enter.

Bank Charges


Use the Bank Charges window to specify charges associated with transferring money between banks. If you use Payables you specify charges between your remittance banks and your suppliers’ banks. If you use Receivables you specify charges between your customers’ banks and your banks. You can define charges:
  • from a single bank to a single bank
  • from a single bank to all banks (i.e., to all banks including the transferring bank)
  • from a single bank to all other banks (i.e., to all banks except the transferring bank)
  • from all banks to a single bank
  • from all banks to all banks 
Any time you specify a single bank, you have the choice of selecting a particular branch of that bank or all branches.
Both Payables and Receivables users use this window. Bank charges information, however, is not shared between the products.

Payment Formats


Use the Payment Formats window to define the payment formats you need to define payment documents in the Banks window. You define payment formats for the four payment methods that Payables uses. You can define as many payment formats as you require for each payment method; however, each payment format must be unique for that payment method.
1.1.  Payment Method.
  • Check Payment in a payment batch, Quick payment, or manual payment.
  • Electronic You pay electronic payments either through the e–Commerce Gateway, or by delivering a payment batch file to your bank. For both methods, Payables creates a file during payment batch creation. For e–Commerce Gateway payments, the file is processed through the e–Commerce Gateway and delivered to your bank to create payments. For electronic funds transfers, the file is formatted and delivered to your ap.out directory for you to deliver to your bank.
  • Wire A payment method where you pay invoices outside of Payables by notifying your bank that you want to debit your account and credit your supplier’s account with appropriate funds. You provide your bank with your supplier’s bank information, and your bank sends you confirmation of your transaction. Your supplier’s bank sends your supplier confirmation of the payment. Typically, you then record the transaction with a manual payment. However, you can also use a payment batch or Quick payment.
  • Clearing Payment method you use to account for intercompany expenses when you do not actually disburse funds through banks. Generally, you do not generate a payment document with the Clearing payment method. When you enter the invoice, you enter Clearing for the payment method. You can record a clearing payment using a Manual type payment only.
1.2. Transmittable Enable this check box if you use the Automatic Bank Transmission feature and want to use this payment format to automatically transmit payment files to your bank. You can choose this option only if you have selected the Electronic payment method and an electronically transmittable payment program, such as NACHA. Even if you enable the Transmittable check box, you can also use this payment format for payments that do not use the Automatic Bank Transmission feature.

1.3 Zero Amount Payments Only Enable this option if you want this payment format to be used only to create zero amount payments. Disable this option if you want this payment format to be used to create nonzero amount payments. You cannot update this value for a payment format used in a payment batch in progress.

1.4 Group by Due Date Enable this option if you want this format to group payments by due date. If you enable this option, Payables groups payments for invoices with the same due date on the same payment document. Invoices with different due dates are paid using a separate payment document for each due date.

If you enable this options for future dated payments, the format groups all payments by maturity date. If you disable this option, Payables groups payments on payment documents according to the order in which the invoices were selected
when you initiate a payment batch.

Bank File Character Set: If you do not use Payables in Japan, then leave this option blank. The setting of this field is used only by the Zengin payment format. If you use Payables in Japan and want to use the Zengin Format Payment Program, contact your local Oracle representative for more information on this option.
2. Currency
If you enable the Use Multiple Currencies Payables option, you can change this option from Single to Multiple at any time; however, you can change the currency from Multiple to Single only if you have not already assigned the payment format to a payment document.
  1. Multiple. Select Multiple if you want to use a payment format to pay invoices of different currencies. You can select Multiple only if you enable the Use Multiple Currencies Payables option. You can only use a multiple currency format with a bank account whose bank account currency is the same as your functional currency.
  2. Single. Select Single if you want to use a payment format to pay invoices of only one currency. You must select the currency you want to pay with this format in the next field. You can then use this format for either a multiple currency bank account or a bank account that uses the currency you define for this payment format.
Currency. Enter a currency code for a Single currency payment format. If you do not enable the Use Multiple Currencies Payables option, Payables enters your functional currency in this field and you cannot change it.

3. Remittance
Choose where you want to print remittance advice for the payments you create using this payment format.
Before Document Payables prints a remittance advice on the payment document stub, before it prints the payment.
After Document Payables prints a remittance advice on the payment document stub, after it prints the payment.
None Payables prints a separate remittance advice, based on the remittance advice program you select for the payment format.
Number of Invoices The number of invoices you want to appear on your remittance advice for this payment format. This value applies only to a remittance advice included in your Format Payments programs (not a Separate Remittance Advice program). Do not change this value for the payment formats that Payables predefines.

Note that for any of the External type payment formats, the maximum value that defaults in this field is 37, and if you enter a value greater than 37 your payment format will not work.

4. Programs
Build Payments The Build Payments program this payment format uses during payment building to group the selected invoices for each payment, to order the payments using the order option you specify, to create any necessary overflow payments, and to determine the total number and amount of payments for a payment batch.
Attention: For this field, select the Standard Build Payments program that Payables provides. You do not need to define any
additional Build Payment programs.

Format Payments The Format Payments program that this payment format uses. You must select None for the Remittance option to select the BACS or the U.S. Treasury Format Payments program because these formats do not have remittance stubs. During payment formatting, Payables uses your payment format to create the layout of your checks or electronic funds transfer file. If you plan on using a laser printer to print checks, select the External Laser Format Payments Program.

Separate Remittance. The Remittance Advice program this payment format uses to create a separate remittance advice for each payment.
Choose the Tax Authority Remittance Advice if you use automatic withholding tax and are creating a payment format you will use when paying a tax authority.

Aging Periods

Use the Aging Periods window to define time periods for the Invoice Aging Report. The Invoice Aging Report provides information about invoice payments due during four periods you specify. Payables displays the invoice information in four columns. Each column corresponds to one period.

When you submit the Invoice Aging Report, you select the type of aging periods to use for the report.
For example, you define one type of aging period called Weeks Past Due, and define the following periods for Weeks Past Due: 1 Week, 2 Weeks, 3 Weeks, and Over 3 Weeks. You also define a type of aging period called Current, and define the following periods for Current: Due in More than 3 Weeks, Due in 3 Weeks, Due in 2 Weeks, and Due in 1 Week. When you submit the report, if you select Weeks Past Due for the Type parameter, Payables reports on the four periods with that type. You can use the Aging Periods window to modify or reorder the periods within an aging period type at any time.

Signing Limits

Managers can approve an expense report only if the total amount of the expense report does not exceed their signing limit. The Manager (Spending) Approval Process in the Expense Reporting workflow uses the signing limits you define to determine which manager has authority to approve expense reports. You assign signing limits in your primary functional currency.

When you assign signing limits to a manager, you also specify a cost center to which this signing limit applies. You can give managers signing limits for multiple cost centers.


To assign signing limits

1. Navigate to the Employee Signing Limits window.
2. Select AP Expense Report as the document type.
3. Enter the name of the manager to whom you want to assign a signing limit.
4. Enter the cost center for which you want this manager to approve expense reports.
5. Enter a signing limit for this manager.
6. Save your work.

Note Payables Invoice Approval is determined based on rules setup in AME. You can create whatever rules you need to meet your business conditions but these are all handled in AME (Approvals Management).

For instance, a simple scenario would be where you setup a rule where if supplier invoice amount is less than say 1000 USD, then approval is required from group X or if supplier invoice amount is between 1001 and 2000 USD, then approval is required from group Y.
Please review the Oracle Approvals Management Implementation Guide in note 227391.1 for full details on how to setup rules in AME.

For Release 11 and Release 11i where the Find Approver Method is used, signing  Limits are standard functionality in Internet Expenses.  It is not possible to  approve an expense report without signing limits unless there is customization.

For Release 11i on Mini-pack E (11i.OIE.E) or higher, Oracle Approvals Management enables you to build routing rules for expense report approvals. When enabled, the expense report workflow process uses the Oracle Approvals  management definition in place of the Find Approver method in the Internet Expenses application.  In addition, the signing limits of the Verify Authority  function are ignored.   For more informaiton on enabling OAM within Internet  Expenses and the Verify Authority API, reference the Oracle Internet Expenses  Implementation and Administration Guide Release 11i, Second Generation, Mini- pack E or higher.

Expense Report Template

Expense template is a mandatory field in expense report form. we create exepnse items in expense template by combining seeded expense categories with item type(item, frieght, tax and misc.)

Use the Expense Report Template window to define templates based on the expense report forms you regularly use in your enterprise. You can define default values for expense items, and you can then choose those items from a list of values when you enter expense reports.

During Expense Report Import, Payables uses the expense item information to create invoice distributions.
You define expense report templates for types of expense reports you use in your enterprise. For example, a company might define a Salesperson template that salespeople use to enter expense reports. That template would include expense items that are reimbursable, such as meals, airfare, and hotel. However, it would not include a mileage expense item because salespeople have car allowances.
In the Payables Options window, you can select an expense report template that will be the default template in the Expense Reports window.

Expense Report Templates for Oracle Internet Expenses
If Oracle Internet Expenses is installed, employees can enter expense reports using a standard Web browser. Only templates that have the Enable for Internet Expenses option enabled are available for use with Internet Expenses.

The Internet Expenses attributes in the Expense Report Templates window control some of the functionality of Internet Expenses. For example, you can use an Internet Expenses attribute to require employees to provide justifications for certain expense types. You also use the Expense Report Templates window to manage the assignment of rate and policy schedules to expense types.

Project–Related Expense Report Templates
Employees can enter project–related expense reports using Internet Expenses. To create a project–related expense report in Internet Expenses, an employee must choose project–related expense items from the list of values. To create project–related expense items, you associate expense items with Oracle Projects expenditure types. Employees can then associate a project number and a task number with the project–related expense items when they enter expense reports in Internet Expenses.

Each Oracle Projects expenditure type is assigned a unit of measure, such as currency, hours, miles. When defining a template, you can select expenditure types in the Projects Expenditure Type field only if they have currency as a unit of measure. You cannot select Expenditure types with cost rates.

Only the names defined in the Expense Item fields or the Prompt field of an Internet Expenses enabled template appear on the list of values in Internet Expenses. To have the Oracle Projects expenditure types appear in this list of values, establish a separate template where the expense item names are identical to the expenditure type names. Instruct Internet Expenses users who enter project–related expense reports to use this template.

Creating Accounting Entries in Payables

You can create accounting entries for Payables accounting events in two ways:

  • Submit the Payables Accounting Process.
  • Create accounting entries for a single transaction or batch.
After the process completes, Payables produces the Accounting Entries Audit Report and Accounting Entries Exception Report. The exception report lists any transactions that accounted with errors. In the Update Accounting Entries window, you can update any accounting entries that were created with invalid accounts.

Payables Accounting Process
Submit this batch process to create accounting entries in Payables.
After the process is complete, you can view the new accounting entries in the View Accounting Lines window.

Payables Accounting Process Report

Use this report to review accounting entries created by the Payables Accounting Process. The report has two sections:
  • Accounting Entries Audit Report. The audit report provides, in detail or summary, a listing of accounting entries created by the accounting process.
  • Accounting Entries Exceptions Report. The exception report lists in detail all accounting entries that were created with an error status and a description of that error. The Accounting Entries Exception Report is generated only when the accounting process encounters entries that fail validation.
Attention: If you see an entry that has a fatal error, please contact Oracle Support for technical assistance. If this
condition is encountered, then the transaction remains unaccounted.

Note that while the Payables Accounting Process is submitted for a document class, the report is organized by journal category. Oracle General Ledger associates each of your accounting entries with a journal entry category. This category is used to indicate the purpose or nature of the transaction. There are three journal entry categories for Oracle Payables transactions.
  1. Purchase Invoices. Assigned to journal entries originating from invoice accounting events. Invoice Accounting Events belong to the Invoice Document Class.
  2. Payments. Assigned to journal entries originating from payment accounting events, excluding payment reconciliation events.Payment Accounting Events belong to the Payments Document Class.
  3. Reconciled Payments. Assigned to journal entries originating from payment reconciliation events. Payment ReconciliationEvents belong to the Payments Document Class.

Automatic offset method

If you enter invoices for expenses or asset purchases for more than one balancing segment, you might want to use Automatic Offsets to keep your Payables transaction accounting entries balanced.

If you do not use Automatic Offsets, Payables creates a single liability accounting entry for invoice transactions (if you use accrual basis accounting) and a single cash type accounting entry for payment transactions.

When you use Automatic Offsets, Payables automatically creates balancing accounting entries for your transactions. The GL account that each of the offsetting accounting entry is charged to depends on which method you use, Balancing or Account:

  1. Balancing. Payables builds the offsetting GL account by taking the balancing segment (usually the cost center code) from the invoice distribution and overlaying it onto the appropriate default GL account, for example the Liability account from the supplier site.
  2. Account. The Account method takes the opposite approach with one segment (the designated account segment) being retained from the default GL account and all other segments being retained from the invoice distribution.
Although Payables builds the GL account to which amounts are charged differently depending on the method you use, in either case Payables automatically allocates the amount across the following accounting entries for an invoice:
  • Liability
  • Withholding Tax (if you apply the withheld amount at Invoice Validation time)
Payables also allocates the following entries for a payment:
  • Cash (if you use a pooled bank account)
  • Cash Clearing (if you use a pooled bank account, and if you account for payments at clearing time)
  • Discount
  • Exchange Gain/Loss
  • Future Dated Payment
  • Rounding
  • Withholding Tax (if you apply the withheld amount at Payment time)
  • Bank Charges
  • Bank Errors
Automatic Offsets affects only accounts listed above. For accounts other than these, for example, Interest Liability, you must make manual journal entries in your general ledger to keep the entries balanced at the balancing segment level.

Example
The following diagram illustrates how Payables builds a GL account on a liability distribution using the two different methods:


Automatic offset method : None

nvoice is cretaed with two distribution line with differnt balancing segments
Charge A/c with BS1: 01-000-1160-0000-000
Charge A/c with BS2: 02-430-5800-0000-000
 
Liability A/c in supplier sie: 01-000-2210-0000-000
When Accouting is done the system 'll Debit the charge A/Cs in two different balancing segments and it would  credit the liability given in supplier site.

Automatic offset method : Balancing

Invoice is cretaed with two distribution line with differnt balancing segments
Charge A/c with BS1: 01-000-1110-1100-210
Charge A/c with BS2: 03-120-7210-1100-130
 
Liability A/c in supplier sie: 01-000-2210-0000-000
When Accouting is done the system 'll create the Liability A/C for BS2 by repalcing the balancing segment of of the Liability A/c in BS1(i.e. 01-000-2210-0000-000) and the A/C would 03-000-2210-0000-000. The complete A/C 'll be

Automatic offset method : Accounting
Invoice is cretaed with two distribution line with differnt balancing segments
Charge A/c with BS1: 01-000-1110-1100-210
Charge A/c with BS2: 03-000-1813-0000-000

Liability A/c in supplier sie: 01-000-2210-0000-000
When Accouting is done the system 'll create the Liability A/C for BS2 by repalcing the natural a/c segment of of the charge A/c in BS2(i.e. 03-000-1813-0000-000) and the A/C would 03-000-2210-0000-000. The complete A/C 'll be

Viewing Accounting Entries

You can view accounting entries in the view accounting entries windows. Depending on how you open the window, the window title and the data that you see in the windows vary. Payables includes the following windows that you use to view accounting entries:
  • View Accounting Lines. You can navigate to this window from the Navigator.
  • View Invoice Accounting. You open this window from one of the following places: Invoices window, Update Accounting Entries window, or drilling down from Oracle General Ledger. This window limits you to viewing invoice accounting entries.
  • View Payment Accounting. You open this window from one of the following places: Payments window, Update Accounting Entries window, or drilling down from Oracle General Ledger. This window limits you to viewing payment accounting entries.
You can view the detail accounting lines for the queried transaction in the form of a balanced accounting entry (i.e., debits equal credits). You can also view the detail accounting as t–accounts in the T Accounts window, or view summarized accounting for each account in the Activity Summary window. Use these features to see how a transaction affects the account balances in your general ledger.

Transferring Accounting Entries to Your General Ledger


After you create accounting entries in Payables, submit the Payables Transfer to General Ledger program to send invoice and payment accounting entries to the general ledger interface.

If you use Oracle General Ledger, then you can submit Journal Import, which uses the data in the GL interface to create unposted journal entry batches, headers, and lines. You can then post these journal entry batches, headers, and lines within General Ledger to update your General Ledger account balances. You can submit Journal Import either when you submit the transfer program, or separately, after the transfer process completes.

If you do not use General Ledger, you can use the data in the GL interface to create and post journal entries in your general ledger. Payables retains the accounting entries, so you can continue to review them in Payables. Also, after you post journal entries in Oracle General Ledger, you can drill down to the related accounting entries or transactions in Payables.

If you use the Multiple Reporting Currencies feature, read the Multiple Reporting Currencies in Oracle Applications manual for information on transferring accounting entries when you use the Multiple Reporting Currency feature.

Adjusting Purchase Order Matched Invoices

  • If you accidentally matched to the wrong purchase order shipments or distributions, you can reverse matched distributions and create new distributions by matching to new purchase order shipments or distributions of the same purchase order or of another purchase order. If you add or reverse invoice distributions you must also change the scheduled payment amounts to match the new invoice total, or Oracle Payables will place holds on the invoice during approval.
  • You can adjust the GL Date, Income Tax Type, and Account fields of a purchase order matched invoice distribution. You can change the Account only if you have not yet posted the invoice and if you have selected the Allow Matching Account Override Payables option.
  • If a supplier submits a supplementary invoice for a change in unit price for an invoice you have matched to a purchase order, use a price correction to adjust the invoiced unit price of previously matched purchase order shipments or distributions without adjusting the quantity billed.
Price Corrections
• Use a price correction to record and update the invoiced unit price of previously matched purchase order shipments or distributions without adjusting the quantity billed in order to track price variances. Record a price decrease by entering a credit or debit memo invoice and then selecting the Price Correction check box when you perform matching.
• Record a price increase by entering a Standard or PO Default invoice type and then selecting the Price Correction check box when you perform matching.
• To record a price change for a purchase order shipment, select Price Correction, enter the unit price for the incremental amount of the price correction, and enter information into either Quantity Invoiced or the Match Amount field for each shipment you want to match

Recurring Invoices in 11i

Creating Recurring Invoices

Navigation : Invoices—>Entry—>Recurring Invoices (B) Create Invoices

  1. Determine how many invoices to create.
  2. Enter the number of invoices, and click Create Invoices. A period must be an open or future period for Oracle Payables to create an invoice.
  3. Optionally, create recurring invoices into an existing batch of similar invoices; for example, group all recurring rent invoices into one batch, and then add to the batch on a quarterly basis.
  4. Use the Create Invoices window to view summary information about the invoices created. Oracle Payables appends the payment number with the period name in which an invoice is created to create invoice numbers for recurring payments.
  5. Use the Invoices Summary

Voiding and Reissuing Quick Payments


The Void and Reissue feature provides an easy method for correcting any printing problems that you encounter when creating a check as a Quick payment. If a check you generate is spoiled, you can void the original payment and automatically reissue payment of the same invoices.

Note: You cannot use this option for future dated payments.

Prerequisites
  • Enable the Allow Void and Reissue Payables option.
  • The payment is a Quick payment.
  • The payment method of the invoices paid is Check.
  • The payment is not a future dated payment.
To void and reissue a Quick payment:
1. Load and properly align your payment document in the printer.

2. Find the Quick payment online, and from the Payments window select the payment and choose Actions.

3. In the Payment Actions window select Reissue. Enter the Payment Date, confirm the New Check Number and optionally record a Voucher Number. Payables automatically selects Void for you. Review and optionally update the void dates.

4. Choose OK to have Payables void the selected Quick payment and create a new Quick payment document to pay the invoices.

After Reissue
After reissue the stauts of the payment document changes to void and a new payment document with a different number is created. If required we can again create a reissue against the newly generated payment document.

Payment Documents

Use the Payment Documents window to define payment documents for an internal bank account
. Examples of payment documents are checks or electronic payments. You must create at least one payment document before you can use a bank account to create invoice payments. You can create an unlimited number of payment documents for an internal bank account.

When you define payment documents, you can only select payment formats that use the same currency as the bank account currency. If the bank account is a multiple currency bank account, you can choose foreign currency payment formats or multiple currency payment formats.

To define a payment document:


1. In the Bank Accounts window, query a disbursement bank account. Choose the Payables Documents button to navigate to the Payment Documents window.

2. Enter a name for the payment document that is unique for the bank account. Select a Disbursement Type and Payment Format. Enter in the Last Document Number field the last payment document number you used on a payment document. In the Last Available Document Number field, enter the last payment document number available for a payment document.

2.2 In the Additional Information region, enter the number of Setup  Checks you want Payables to print at the beginning of each automatic payment batch.
If you are using the sequential numbering feature, optionally assign a Document Category.

If you are using the Automatic Bank Transmission feature to automatically transmit this payment document, then in the
Additional Information tabbed region, select a transmission code.

2.3 If you have enabled Oracle Cash Management integration for reconciliation, optionally override the GL Accounts in the GL Accounts region.

2.4 If you want to use the payment document for future dated payments, then in the Future Dated payments tabbed region, set the Future Date Use option to either Allowed or Mandatory. If you use the future dated payment account from the payment document rather than the supplier site, then enter the account.

Payment Document Restrictions:
DOCUMENT NUMBERS: You cannot define a document number more than once for the same bank account. For example, if a payment document uses document numbers 0 – 1000, then other payment document numbers you define for the same bank account cannot use any numbers in that range

Other Topics

This topic describes the following specialized features in Payables:

  1. Period Close
  2. AuditTrail
  3. Positive Pay Integration
  4. Interest Invoices
  5. Automatic Withholding Tax
  6. Automatic Offsets
  7. Automatic Tax Calculation
  8. Budgetary Control and Encumbrance
  9. Intercompany Accounting
  10. Petty Cash Funds

Month End Close and Reconciliation

1. Run the program ‘Expense Report Import’ program.

2. Run the ‘Invoice Validation’ program for all parameters - This will validate all the invoices entered in the Operating Unit.

3. Run the ‘Invoice On Hold Report’ for the period to verify if any invoice is put on hold.
Submit the program with default parameters.
If there is any invoice on hold, resolve the issue and remove the hold.

4. Run 'Payable Accounting Process'.

5. Run ‘Unaccounted Transactions Report’ program to find out any unaccounted transaction for the period. Enter Period Name and submit the report.

6. For the previous month, run:
a) Account Payable Trial Balance Report

For the month just closed, run:
a) Posted Payment Register
b) Posted Invoice Register
c) Account Payable Trial Balance Report


Reconcile using:
Previous month Account Payable Trial Balance
+  Current Month Posted Invoice Register 
-  Current Month Posted Payment Register
= Current Month Account Payable Trial Balance

7. Transfer accounting transactions to GL by running 'Payables Transfer to General Ledger' program.

8.  Run ‘Account Analysis Report with Sub Ledger Detail’ for your AP Liability Account in GL.
The grand totals should match with AP Trial Balance Report.

9. To Close period in AP and open the next period:
Navigate to Accounting > Control Payables Periods
Close the current period and then open the next period

Setting Up Oracle Payables to Enter Expense Report


1.  Enter employees, their locations, and their expense addresses in the People window. If Oracle Human Resources is installed, all employees must be entered in the People window of Oracle Human Resources.

2. Define the employee as a supplier by using either of the following methods:
- Enable the Create Employee as Supplier Payables option to automatically create suppliers from employees when you submit Invoice Import.
- Enter the employee as a supplier in the Suppliers window before submitting Invoice Import for expense reports.

3. Define expense report templates that model the different expense report formats you receive.

Query the bank account of a Supplier Site

SELECT BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM
FROM IBY_EXT_BANK_ACCOUNTS
WHERE EXT_BANK_ACCOUNT_ID IN
(SELECT EXT_BANK_ACCOUNT_ID
FROM IBY_ACCOUNT_OWNERS
WHERE ACCOUNT_OWNER_PARTY_ID IN
(SELECT party_id
FROM hz_party_sites
WHERE party_site_name = '<site name>'))
;

Reason for invoices rejected by Payables Open Interface Import

Below simple code can be used to check reason for invoices rejected by  Payables Open Interface Import.

Select aii.Invoice_num , air.PARENT_TABLE, air.REJECT_LOOKUP_CODE, air.parent_id
From apps. AP_INTERFACE_REJECTIONS air,
apps. AP_INVOICE_LINES_INTERFACE aili,
apps. AP_INVOICES_INTERFACE aii
WHere aii.invoice_id=aili.invoice_id
AND  aili.invoice_id=air.parent_id
AND aii.Invoice_num = 'Invoice Number'

Supplier , Supplier Bank and Supplier bank branch - Oracle Apps 11i

Select a.bank_account_name, a.bank_account_num, a.iban_number, a.bank_account_type,
a.currency_code, a.bank_account_name_alt, a.org_id, a.creation_date,
b.bank_name, b.bank_branch_name, b.bank_num , b.eft_swift_code,
b.address_line1, b.address_line2, b.city, b.county, b.state, b.zip,
b.country, c.vendor_id,d.vendor_name,d.segment1 AS SUPPLIER_NUM

from apps.ap_bank_accounts_all a,
apps.ap_bank_branches b,
apps.ap_bank_account_uses_all c,
apps. PO_VENDORS d

where a.org_id=xxxx
AND a.bank_branch_id = b.bank_branch_id
AND a.bank_account_id = c.external_bank_account_id
AND c.vendor_id=d.vendor_id
 AND c.end_date IS NULL
 

Simple supplier & supplier site

Select pvs.creation_date, pv.segment1 as "Supplier num", pv.Vendor_name, pv.vendor_id, pv.vendor_type_lookup_code, pvs.vendor_site_id, pvs.vendor_site_code, pvs.vendor_site_code_alt, pvs.address_line1, pvs.city, pvs.country, pvs.attribute1, pvs.vat_registration_num from apps. PO_VENDOR_SITES_ALL pvs, apps. PO_VENDORS pv where pv.vendor_id=pvs.vendor_id and pvs.org_id=xxx Order by pvs.creation_date DESC