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. Show
Invoice Types
Invoice StructureInvoice HeaderThe 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 LinesThe 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. See: . Each invoice line can have multiple distributions tied to each line. Each distribution serves as the source for an accounting entry generated from the invoice. See: . If you need to enter a price or quantity correction, you can do so for the specific line. See: . You can set up line-level approvals using the Invoice Lines Approval workflow. Requesters must approve all lines before they can approve the invoice header. See: . The following different types of invoice lines are supported: Item LinesItem lines capture the details of the goods and services billed on your invoice. Freight and Miscellaneous LinesFreight lines capture the details of your freight charges. Freight charges can be allocated to Item lines as required. Miscellaneous lines capture the details of other charges on your invoices such as installation or service. Like Freight lines, Miscellaneous lines can be allocated to Item lines. Tax linesPayables integrates with Oracle E-Business Tax to automatically determine and calculate the applicable tax lines for your invoices. E-Business Tax uses your tax setup, plus fields on the invoice header and lines, known as tax drivers, to determine which taxes should be applied to the invoice, to calculate the tax using the appropriate tax rates, and to determine whether or not the tax is recoverable or non-recoverable. E-Business tax creates the necessary tax lines and distributions for the invoice and allocates tax. If your tax setup permits, you can update the tax lines or manually enter tax lines. See: Invoice TypesPayables provides the following invoice types:
You can use these invoice types to enter any type of invoice document you receive from a supplier. For example, you can enter basic invoices that are not matched to purchase orders or more complex invoices that matched to purchase orders at the header, lines, shipping or receipt levels. You can enter invoices in foreign currency or enter invoices for suppliers who are subject to income tax reporting requirements (1099). The characteristics of each invoice type are described below. Standard InvoicesStandard Invoice are invoices from a supplier representing an amount due for goods or services purchased. Standard invoices can be either matched to a purchase order or not matched. Standard invoices must be positive amounts. Mixed InvoicesMixed Invoices can be matched to both purchase orders and invoices. Mixed invoices can have either positive or negative amounts. PO Price Adjustment InvoicesPO Price Adjustment Invoices are for recording the difference in price between the original invoice and the new purchase order price. PO price adjustment invoices can be matched to both purchase orders and invoices. Credit MemoCredit Memos are memos from a supplier representing a credit amount toward goods or services. Credit memos are always negative amounts. Debit MemoDebit Memos are invoices you enter to record a credit for a supplier who does not send you a credit memo. PrepaymentPrepayments are invoices you enter to record an advance payment for expenses to a supplier or employee. Expense ReportsExpense Reports are invoices representing an amount due to an employee for business-related expenses. Scheduled PaymentsScheduled payments are created based on payment terms when the invoice header is saved. An invoice header can have one or more scheduled payments. DistributionsDistribution details include invoice accounting details, the GL date, charge accounts, and project information. An invoice line can have one or more invoice distributions. Entering Invoices OverviewYou can enter and import invoices into Payables in many ways: Manual Invoice EntryYou usually enter supplier invoices in either the Invoice Workbench or the Quick Invoices window. You can match to purchase orders when entering these invoices. For information on the differences between these windows, see the following section, .
The following features highlight the differences between the Invoice Workbench and Quick 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:
Tasks performed during invoice entry only in the Invoice Workbench Although you can perform the following tasks in the Invoice Workbench after you have imported Quick Invoices, use the Invoice Workbench if you want to perform any of these tasks during invoice entry:
Automatic Invoice CreationYou can set up your system to automatically create periodic invoices, for example, rent invoices:
Invoices ImportYou can import invoices or invoice information to create invoices in Payables. See: and .
Supporting Third Party PaymentFinancial settlement is one of the key components of a business process. It is the final step in completing the business transaction. In the Procure to Pay cycle, suppliers send invoices to customers after delivering goods or rendering services. Once the invoices are received, the accounts payables department of the customer validates the invoices and approves them for payments. The payments made to the suppliers during the settlement process are generally dependent on the agreement entered into between the customers and suppliers for carrying on the business transactions. Payments are generally made to the original supplier providing the goods or services, however there can be specific arrangements made wherein the suppliers can specify a different party to be paid on their behalf. The payments made to other parties on behalf of the suppliers are termed as Third Party payments. Third Party payments help parties involved in business to set off their liabilities without directly paying them. This reduces the direct funds movements and transactions are settled easily. When customers make payments from their Payables system, there might be instructions from the supplier to make the payment to a different party, that is the Third Party. In that case, the remittance of the payment goes to the Third Party. For all legal purpose including 1099, it is treated as a payment to the original supplier. The Payables department maintains the Supplier information. Establishing Third Party Payment relationship is part of the supplier maintenance activity. The Payables clerk may also have information of the Third Party at the time of entering the invoices. The Payables clerk can have the right to override the Third Party defaulted at the time of invoice entry. The Payments clerk processes the payment for the invoices that are due for payment. Generally the payments clerk is aware of the Third Party suppliers to whom the payments can be released on behalf of the supplier. The Payment's department have the right to override the actual party to whom the payment can be made at the time of making payments. This functionality lets you do the following:
Related Topics Differences Between Entering Invoices in the Quick Invoices Window and the Invoice WorkbenchYou can enter invoices in either the Quick Invoices window or the Invoice Workbench. The following discussion outlines the differences between entry in the two windows to help you decide when to use a particular window for invoice entry. When You Should Use Quick Invoices For Invoice EntryUse the Quick Invoices window for your everyday entry of invoice records. Use this window for rapid, high-volume entry of Standard and Credit Memo invoices that are not complex and do not require extensive online validation or defaulting of values during entry. You can use this window for purchase order matching and for applying prepayments to the invoice you are entering. See below for a list of invoice entry tasks that cannot be performed in the Quick Invoices window, and that you should perform in the Invoice Workbench instead. Use the Quick Invoices window if you want to use the Open Interface Workflow. You can customize the Open Interface Workflow to process your invoice records before you import them. For example, you can perform custom validation of cost center information before you submit import. When You Should Use the Invoice Workbench For Invoice EntryUse the Invoice Workbench for entering and maintaining more complex invoices for which you require extensive online validation and online defaulting. You may also want to use the Invoice Workbench if you need to perform an action on the invoice immediately after entering it. For example, if you need to enter an invoice and create a payment for it, then enter the invoice in the Invoice Workbench so the record is immediately accessible for validation and payment. Functionality available only by invoice entry in the Invoice WorkbenchUse the Invoice Workbench to:
Online results seen only in the Invoice WorkbenchAlthough the following occurs during import, in the Invoice Workbench you can see online results of the following:
Tasks performed during invoice entry only in the Invoice WorkbenchAlthough you can perform the following tasks in the Invoice Workbench after you have imported Quick Invoices invoices, use the Invoice Workbench if you want to perform any of these tasks during invoice entry:
Entering Invoice Batches in the Invoice WorkbenchYou can use invoices batches to:
Prerequisites
To enter an invoice batch:
Related Topics Entering Invoices in the Invoice WorkbenchUse the Invoice Workbench to enter and maintain complex invoices for which you require extensive online validation and online defaulting. Also, use the Invoice Workbench if you need to perform an action on the invoice immediately after entering it. For example, if you need to enter an invoice and create a payment for it, then enter the invoice in the Invoice Workbench so the record is immediately accessible for validation and payment. Related Topics Entering Basic Invoices in the Invoice WorkbenchYou 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
To enter an unmatched (basic) invoice:
Related Topics Attachments in Payables, Oracle Payables Implementation Guide Entering Supplier Information, Oracle iSupplier Portal Implementation Guide Financials Options, Oracle Payables Implementation Guide Payables Options, Oracle Payables Implementation Guide Entering Distributions in the Invoice WorkbenchThe distributions you enter for an invoice allocate the invoice line amount to various expense or asset accounts. For example, you can distribute expenses from one office supply invoice line to expense accounts for several departments. Payables uses distributions to create accounting entries for invoices. You can create distributions: In general, Tax distributions are automatically created by E-Business Tax. However, if your tax setup permits, you can enter tax distributions manually. See: . If an invoice is matched to a purchase order, Payables checks the distributions to see if they are within the tolerance you define. See: Invoice Tolerances, Oracle Payables Implementation Guide. Entering Invoice Distributions Manually in the Distributions WindowYou can enter distributions manually if you want to control how the total invoice amount is allocated to various expense or asset accounts. All manually entered distributions will automatically have a Distribution Class of Permanent. 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. To enter distributions manually in the Distributions window:
Related Topics Distribution Sets, Oracle Payables Implementation Guide Creating Distributions by Allocation in the Invoice WorkbenchYou can use the Allocations window to automatically create freight or miscellaneous distributions. The Allocations window displays when you navigate to the allocate button from invoice lines. 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. For details on Allocation, see: . If you navigate to the Allocations window through an Invoice Line (not distribution), then all the allocated lines (Freight and Miscellaneous) display. If you view in the context of a Freight or Miscellaneous line, then you can see all the invoice lines and then allocate (percentage, amount, prorate) against the invoice lines. In this case, distributions for Freight and Miscellaneous lines are generated automatically based on invoice line 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. Note: If you are matching to a purchase order shipment or receipt, then you have the option of allocating directly in the match window, without navigating to the Distributions window. If you are matching to a purchase order distribution, then allocate freight and miscellaneous charges in the Allocate window. See: . To create freight or miscellaneous distributions by allocating to item distributions:
Related Topics AllocationIf you use one of the Periodic Costing options available in Oracle Cost Management to record costs of goods that you order, then when you manually enter distributions for other charges (tax, freight, or miscellaneous), you need to record the distributions to which they are allocated. Allocation enables you to record accurately all costs associated with a receipt. If you Do Not Use Periodic CostingIf you have not installed Oracle Cost Management or do not use Periodic Costing, you do not need to record these allocations. However, you may find the Charge Allocation and Allocate windows useful for automatically creating charge distributions. If you do not use Periodic Costing, we suggest you read only the following allocation discussions: If You Use Periodic CostingIf you use Periodic Costing, then you may find all of the allocation discussions helpful: Allocate WindowUse the Allocate window to automatically create allocated tax, freight, and miscellaneous distributions when you are matching to a purchase order or receipt. Payables does not create the distributions until you choose the Match button in the matching window (Match to Receipts window, Match to Purchase Orders window, or Match to Purchase Order Distribution window). Note: You cannot adjust Adjustment and PO Price Adjustment invoices. For more information, see the Oracle Purchasing User Guide. Notice that in the matching window displays the Associated Charges region. If you want to change the allocated amounts, deselect the Freight/Misc check box to clear the amounts. You can then re-enter the allocated charge by selecting the Freight/Misc check box and re-entering the allocation information. Each tax distribution you create using the Allocate window will have the same GL Account as the distribution to which it is allocated. Note: The Allocate window replaces the Prorate window and the Charge Allocations window, which was in releases before 11i and 12. Prerequisites
Creating Charge Allocations During MatchingTo create tax, freight, or miscellaneous distributions by using the Match window:
Related Topics Allocations WindowYou can use the Charge Allocations window the following ways: If the cursor is in an Item or Line, and you choose the Allocate button, then the Allocations window displays, and you can use the Allocations window to create distributions based on the information you enter. If the cursor is on an existing tax, freight, or miscellaneous line, then the window opens and shows you any distributions that the tax, freight, or miscellaneous charge distribution is allocated to, and any distributions available for allocation. Note: You cannot access the Allocations window from the Distributions window. You can access it from the Invoice Workbench window. See: For Matching to Other Invoice Distributions OnlyUse the Charge Allocations window to allocate charges to distributions on the same invoice, not to match to receipts. If you match to receipts and you are entering a tax, freight, or miscellaneous charge invoice such as a freight invoice from a freight supplier, and you want to match that freight charge to a receipt, see: . If a tax, freight, or miscellaneous charge distribution is already matched to a receipt, then you cannot allocate it to another invoice distribution. Related Topics Allocations Window ReferenceThe top part of this window describes the charge that is allocated. The Allocations region of this window shows the distributions to which you can allocate the charge, and the amount that is allocated. Type. The type of charge: Tax, Freight, or Miscellaneous. Tax Code.
Amount. Amount of the tax, freight, or miscellaneous charge. Allocated Total. Sum of the amounts you are allocating (values in the Allocated Amount fields). To save the allocation, this amount must equal the value you entered in the Amount field. Prorate. Use this button to prorate the charge amount across all eligible lines. Applicable Lines(Check box) Indicates that a distribution is selected for allocation. Num. Distribution number of the eligible distribution. Type. Type of the eligible distribution. You can allocate Freight and Miscellaneous charges to Item distributions only. You can allocate Tax charges to Freight, Miscellaneous, Item, or Prepayment distributions. Description. Description of the eligible distribution. Amount. Amount of the eligible distribution. Allocated Amount. Amount allocated to the distribution. If you are currently allocating by proration, leave these fields empty. After you choose the OK button to allocate, Payables calculates the prorated amounts and populates these fields for you. ButtonsNew. Allocates the charge amounts to selected distributions and clears the Charge Allocations window so you can allocate new charges. This is located at the top of the application. Select/Unselect All. Selects or deselects all eligible distributions. Cancel. Discards any changes and closes the window. OK. Allocates the charge amounts to selected distributions and closes the window. Prorate. Is a button in the Allocations window. Related Topics Matching Charges to Material Receipts Complete the following steps to match an invoice for freight, tax, or miscellaneous charges to a material receipt. Note that this step is required for accurate costing data if you use Periodic Costing. When you match a freight, tax, or miscellaneous invoice to a receipt, the total cost of the goods on the receipt includes the freight, tax, or miscellaneous charges that are matched to the receipt. This kind of matching associates costs related to acquiring the goods that are on the receipt, but it does not affect the quantity and amounts billed on the purchase order shipment. If you have installed Oracle Costing, this information is then used by that product. For example, you buy a $1000 computer from Company A. You hire Company B to ship it to you for $50. You receive the computer. When you get the freight invoice from Company B, you can match that freight invoice to the receipt for the computer from Company A. This associates the $50 freight charge with the cost of the $1000 computer, making the total cost of the computer $1050. Prerequisites
To match a freight, tax, or miscellaneous invoice to a receipt:
Related Topics Recording Allocations for Periodic CostingIf you use one of the Periodic Costing options available in Oracle Cost Management to record costs of goods that you order, you need to allocate other charges (Tax, Freight, and Miscellaneous) to other invoice distributions that are matched to receipts. When a distribution is matched to a receipt, the distribution and any tax, freight, or miscellaneous distributions that are allocated to it are included in the cost of the receipt. Allocating Tax, Freight, and Miscellaneous for Periodic CostingPrerequisite
To allocate an existing tax, freight, or miscellaneous charge to another distribution:
Allocation RestrictionsCANCELLED INVOICES. You cannot modify allocations if the invoice is cancelled. PAID INVOICES. If the invoice is partially or fully paid and the Allow Adjustments to paid Invoices Payables option is not enabled, you cannot create new charges in the Allocations window. APPLIED PREPAYMENTS. If a prepayment invoice has been partially or fully applied, you cannot create new charges in the Allocations window. ITEMS MATCHED TO MULTIPLE PO DISTRIBUTIONS. You cannot allocate a single nonrecoverable tax distribution to more than one Item distribution if the distributions are matched to different purchase order distributions. ENCUMBERED TAX DISTRIBUTIONS: You cannot allocate a new Tax distribution to an Item distribution if encumbered Tax distributions already exist for the item distribution. Also, you cannot change allocations for a nonrecoverable Tax distribution if it has been encumbered and if it has already been allocated to purchase order matched Item distributions. ACCOUNTED ALLOCATIONS. You cannot adjust an allocation after you have accounted for the charge. Reviewing Allocation of Other ChargesYou can review or modify existing allocations of a Tax, Freight, or Miscellaneous distribution by selecting appropriate lines in the Invoice Lines region and choosing the Allocate button. You can make any changes in the Charge Allocations window. You cannot modify charge allocations after accounting for the invoice. See: Scheduled PaymentWhen 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:
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. For more information on the Exclude Tax from Discount Calculation Payables option, see: Exclude Tax from Discount Calculation Payables option, Oracle Payables Implementation Guide. The invoice Terms Date defaults from the supplier site Terms Date Basis option you select:
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. Related Topics Financials Options, Oracle Payables Implementation Guide Payables Options, Oracle Payables Implementation Guide Payment Terms, Oracle Payables Implementation Guide DiscountsPayables 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 RESTRICTIONSBANK CHARGES: You cannot use the Discount feature if you enable the Use Bank Charges Payables option. Related Topics Payment Terms, Oracle Payables Implementation Guide Payment Payables Options, Oracle Payables Implementation Guide Entering Invoices with Matched Purchase Orders and Receipts in the Invoice WorkbenchYou 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:
You can set up controls in your system to require you to purchase order match each invoice. You can also set an option on a purchase order shipment that controls whether invoices should match to that shipment directly or to a receipt. You set tolerances to specify the range of variance you will allow if the amounts or quantities on the invoice are greater than the amounts or quantities on the purchase order or receipt. 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. See: Invoice Tolerances, Oracle Payables Implementation Guide. 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). Receipt and purchase order matching setup and functionality is described in detail in . The following section describes how to enter and match invoices. You can match an invoice to a purchase order in different ways:
When you are matching to a purchase order, open the View PO window to have easy access to purchase order information. See: Prerequisites
Related Topics Debit Memo Notification Workflow), Oracle Purchasing User Guide Purchase Order Matching Database Tables, Oracle Payables Reference Guide Matching to Purchase OrdersYou can match to purchase orders using: Matching to Purchase Orders in the Match to Purchase Orders WindowThe simplest way to match an invoice to purchase order shipments or distributions is to use the Match to Purchase Orders Window. Payables automatically creates invoice lines and distributions based on the matched shipments and distributions. To match an invoice to purchase order shipments and distributions using the Match button:
The Distribution Account on the Lines tab is used only for defaulting. Once it has been defaulted onto the distributions and if the account on the distributions is overridden, it is not corrected or reflected on to the lines. Matching to Purchase Orders in the Invoice Workbench Lines TabYou can also match an invoice to purchase order shipments and distributions by entering information directly in the Lines tab of the Invoice Workbench. Payables automatically creates distributions based on the matched shipments and distributions. If an invoice is matched to a purchase order with multiple lines and only some of those lines have tax codes, then the invoice only populates the Tax classification code on the lines matched to a PO with tax codes as well. To match purchase order shipments and distributions in the Invoice Workbench:
Matching to Purchase Orders Using Quick MatchTo match invoices to all open, unbilled purchase order shipments, use Quick Match. Quick Match matches shipments on a first in, first out (FIFO) basis. Quick Match is convenient to use if you have:
If you have multiple shipments that are not received in chronological order, use the Match to Purchase Order Shipments window or the Lines tab in the Invoice Workbench. Payables automatically creates invoice lines and distributions based on the matched shipments and distributions. To match purchase order shipments using Quick Match:
Purchase Order Matching RestrictionsCAN'T MATCH TO PROCUREMENT CARD POs: If a purchase order will be fulfilled in the procurement card process, you can't match an invoice to it. QUANTITY INVOICED: In the Match to Purchase Orders and Match to Purchase Order Distributions windows, the Quantity Invoiced must be in the same unit of measure as the purchase order shipment. In the Match to Receipts and Match to Receipt Distributions window, the Quantity Invoiced must be in the same unit of measure as the receipt. QUANTITY INVOICED: You must enter a negative Quantity Invoiced if the invoice amount is negative, and a positive Quantity Invoiced if the invoice amount is positive. You cannot enter a negative amount that reduces the quantity invoiced to less than zero. UNIT PRICE: You cannot adjust the Unit Price if you are matching to an amount-based purchase order with a monetary unit price of 1. For example, 1 USD or 1 GBP. CONTROL/ACTUAL QUANTITY AND TOTAL: In the Match to Purchase Order Distributions window, the Control Quantity and Total must equal the Actual Quantity and Total. AMOUNTS: Credit memos and debit memos must be entered with negative amounts. All match amounts must be negative as well. Matching to ReceiptsThe process for matching to receipts, is the same as matching to purchase orders; however, to match to receipt, ensure the following prerequisites are complete:
If the Invoice Match option for the supplier site is set to receipt then the match button will default to Receipt and you can use the Match to Receipt window to match receipts to invoices. You can also match to purchase orders in the Lines tab of the Invoice Workbench. Enter a PO Number and a Receipt number to match to a receipt line. Payables automatically creates distributions for the matched to receipt lines. See: . Advances and Progressive Contract FinancingOracle Payables, Purchasing and Services Procurement provides an integrated solution to automate acquisition of complex services. Complex service contracts are characterized by:
Oracle Payables provides the functionality to release progress payments, release and recoup advances, apply retainage on invoices, and release retained funds. Advances are generally one-time prepayments made before work on a contract begins, while contract financing infuses money to the supplier as work progresses. Oracle Payables ensures that the amounts financed are recovered by automatically applying financing to subsequent invoices per the specific terms captured in the purchase order. For more information, see: Complex Work in the Procurement Suite, Oracle Purchasing User's Guide. PrerequisitesBefore you enter invoices for complex service work contracts, you must do the following:
Document StylesDocument styles are created and used in Oracle Purchasing to enable complex payment terms on a service procurement purchase order. To match a prepayment invoice created in Oracle Payables to a services procurement purchase order created in Oracle Purchasing, you must select an appropriate document style when creating the purchase order. An appropriate document style is one that has been enabled for Advances or Contract Financing. For details on creating document styles, see: Defining Document Styles, Oracle Purchasing User's Guide. Service Procurement Purchase OrderAdvances are entered on the purchase order by choosing the appropriate document style and then entering an Advance Amount in the Financing region of a purchase order line(s). The Recoupment Rate in the same region represents the percentage the supplier will be paid on subsequent invoices until the advance is fully recouped. For example, if a recoupment rate of 20% is entered, then the deploying company may pay the supplier 80% of the first progress invoice. That is, 20% of the progress invoice may be paid by recouping the advance until the advance is fully exhausted. The distribution for the advance is entered in the Distributions subtab of the purchase order. A purchase order must be approved and open before it can be matched to a prepayment. Contract financing is entered on the purchase order by choosing the appropriate document style and then adding Pay Items for each purchase order line. Distributions for each Pay Item are entered in the Distributions subtab of the purchase order. The distribution account is populated on the prepayment created in Payables when the prepayment is matched to the purchase order. A purchase order must be approved and open before it can be matched to a prepayment. For details on creating services procurement purchase orders, see: Entering Complex Work Purchase Order Pay Items, Oracle Purchasing User's Guide and Entering Complex Work Purchase Order Lines, Oracle Purchasing User's Guide. Retainage Account SetupDefine the retainage account for the operating unit in the GL Accounts region on the Accounting tab of the Financials Options window (Setup > Options > Financials Options > Accounting tab). Oracle Payables uses this account to record the distribution on progress invoices and subsequent retainage release invoices for funds withheld from suppliers. Invoice Tolerances SetupUse the Invoice Tolerances Template to define the matching tolerances policy for variances between the procurement contract or the work to date represented by the approved work confirmations. For more information on setting up invoice tolerances, see: Invoice Tolerances, Oracle Payables Implementation Guide. Supplier Terms and Controls SetupSet up supplier’s terms and control defaults using the Suppliers page. You can specify the Payables invoice management defaults, such as the invoice match option for the supplier and the retainage rates for the supplier sites. These values default on the purchase order. For more information on setting up your suppliers, see: Entering Supplier Information, Oracle iSupplier Portal Implementation Guide. Approval Management SetupOracle Approvals Management provides you the ability to configure rules for approving business transactions or activities. Although this setup is optional, Oracle recommends enabling workflow approval to automate the approval process for your complex service contracts. For more information on setting up invoice approvals, see: Setting Up Invoice Approval Workflow, Oracle Payables Implementation Guide. Entering Prepayments for Advances and Contract FinancingYou can enter prepayment invoices for complex service contracts using the:
This section includes the following topics:
For information on creating self-service invoices using the iSupplier Portal, see: . Entering Prepayment Invoices for Advances or Contract Financing in the Invoice Workbench WindowTo enter prepayment invoices for advances or contract financing in the Invoice Workbench window, perform the following steps.
For more information on the fields in the Invoice Workbench window, see: . Entering Prepayments for Advances or Contract Financing in the Quick Invoices WindowTo enter prepayment invoices for advances or contract financing in the Quick Invoices window, perform the following steps:
For more information on entering quick invoices, see: . Validating Prepayment InvoicesOracle Payables validates invoices prior to paying or creating accounting entries. For more information on validating invoices, see: . To validate a prepayment invoice, perform the following steps.
Tolerances and HoldsTolerances are used to control acceptable prepayment invoice variances of supplier invoices for price, quantity, and amount information compared with what is stipulated in the contract. The follows types of tolerances are used:
Tolerance templates are used to control tolerances across organizations for any supplier site. You can create multiple templates for invoice tolerances in the Invoice Tolerances window, but you can only assign one set of tolerances per supplier site. The Invoice Tolerances window enables you to designate the type of tolerance template as either Goods or Services. If you select the Goods template type, then holds placed for Ordered, Maximum Ordered, Received, and Maximum Received tolerances are based on quantity. Similarly, if you select the Services template type, then holds placed for Ordered, Maximum Ordered, Received, and Maximum Received tolerances are based on amount. You can create two sets of tolerances for each supplier site; one for Goods and one for Services. The tolerance templates are applied during invoice validation per invoice line depending on the PO Line Type and Pay Item Line Type. For example:
During the validation process, a matching hold is placed on prepayment invoices if the amount ordered, received, maximum ordered, maximum amount received, or milestone tolerances are violated. For details on matching holds, see: . Confirming WorkA work confirmation is information that confirms that work was delivered by a certain supplier at a specific price on a specific date as specified by a specific work confirmation number, which is associated with a purchase order number. During validation, you can use 2 or 3-way matching to verify work confirmation. If you are comfortable with a supplier's historical performance, 2-way matching with control back to the purchase order may be adequate for internal controls. On the other hand, if a supplier is new or you prefer increased control when tracking the work performed, you can optionally use 3-way matching. Advance prepayments can only be 2-way matched, that is, verifying that the purchase order and the invoice match within accepted tolerance levels, since there is no work or deliverable associated with an advance. For contract financing prepayments, you can use 2-way or 3-way matching. Three-way matching verifies that the purchase order, the invoice, and receiving information match within accepted tolerance levels. The work confirmation receipt is the only type of receipt allowed for complex service contracts. If the amount of work completed is equal to the amount billed on the invoice, then the invoice is eligible for payment. If the amount of work completed is less than the amount of work billed on the invoice, then the invoice is placed on a matching hold. Funds CheckingIf the Budgetary Control feature is enabled, the Funds Check functionality verifies that sufficient funds are available to pay an invoice. If sufficient funds are available, funds reserve occurs during validation. Oracle Payables totals distribution amounts by account and checks whether any of these totals exceed available funds for the distribution account. If a single account fails funds checking, the entire invoice fails funds checking. Funds can also be checked manually. Encumbrancing PrepaymentsIf budgetary control and encumbrance functionality are enabled, Purchasing and Payables create encumbrances and encumbrance reversals against the budgets defined in Oracle General Ledger. Encumbrances are anticipated expenditures. Advances and contract financing prepayments are always matched to a contract line pay item and recouped from an invoice delivery item for that same contract line. Note: Oracle Payables only encumbers upon delivery and not when the prepayment invoice is entered. Calculating Taxes on Advances and Contract FinancingOracle Payables integrates with Oracle E-Business Tax to provide tax services for invoices. For complex service contracts the system calculates taxes depending on the type of invoices and your configuration. This table represents how tax is calculated: Tax CalculationsStandard
PrerequisitesBefore the system can calculate taxes on your complex service invoices, you must configure tax rules in E-Business Tax. To set up taxes for complex service contracts, complete the following steps in E-Business Tax:
For more information on tax setup, see: . RetainageSupplier invoices are managed and paid as specified by the complex payment terms of the associated service procurement contract. Service procurement payment scenarios exist in numerous industries. For example, during the procurement of equipment that has a long production lead time, such as engineered-to-order items, periodic progress payments are paid to suppliers by the deploying company. The progress payments are based on the costs incurred by the supplier or upon delivery of specified milestones contained in the contract. Retainage is the act of withholding a portion of a payment until a substantial portion or all of the work is completed. It is a common practice in project-based construction and public sector service procurement contracts and is generally used in projects with a high value or with long-term contracts. A portion of a progress payment is generally withheld by the buying organization until all work in the contract is complete and accepted. The percentage withheld is negotiated, defined in the contract, and is based on the risk factors involved. These risk factors include the performance and reliability of the supplier. The retained amount is based on the contractual terms defined in the service procurement contract or purchase order line. A contract line can be associated with one or more progress payments. After performing a portion of the contractual work, the supplier sends a progress invoice to the buying organization, requesting payment against the service procurement contract line or purchase order. The progress invoices submitted by a supplier are recorded as Standard Invoices in Oracle Payables. Oracle Payables withholds a portion of a progress invoice during matching to these payment lines (2-way matching) or to the receipts of these payment lines (3-way matching). The retained amount is represented as negative distribution amounts of type Retainage to the matched invoice line. Note: No manual override or manual entry of retainage amounts is allowed. Oracle Payables supports progress invoices with the following invoice amounts:
Net of Retainage Invoice Amount ExampleThe following tables in this section illustrate an invoice amount that includes retainage as it would appear in the Invoice Workbench windows if the Net of Retainage check box is enabled in the default folder of the Invoice Workbench window. This example shows an invoice that is a progress payment of $100.00 matched to a pay item that has two distributions. The retainage rate at the contract line is 15%. Invoice HeaderINV101BVC Inc.$85.0010/01/2006YesInvoice Lines1Item$100.00CONS10111-$15.00$15.00Invoice Lines Running Totals$100.00-$15.00$85.00Since the Net of Retainage check box is selected, the invoice validation process compares $85.00, the net amount, to the invoice amount entered in the invoice header region of $85.00 to determine if the invoice should be placed on a line variance hold. Invoice Distributions11Item$50.0001-Charge1Inv101-1-1112Item$50.0001-Charge2Inv101-1-2213Retainage-$7.5001-RetainageInv101-1-11$7.5014Retainage-$7.5001-RetainageInv101-1-22$7.50Gross of Retainage Invoice Amount ExampleThe following tables in this section illustrate an invoice amount that does not include retainage as it would appear in the Invoice Workbench windows if the Net of Retainage check box in the default folder of the Invoice Workbench window is disabled. This example shows an invoice that is a progress payment of $100.00 matched to a pay item that has two distributions. The retainage rate at the contract line is 15%. Invoice HeaderINV101BVC Inc.$100.0005/01/2005NoInvoice Lines1Item$100.00CONS10111-$15.00$15.00Invoice Lines Running Totals$100.00-$15.00$85.00Since the Net of Retainage check box is disabled, the invoice validation process compares $100.00, the gross amount, to the invoice amount entered in the invoice header region of $100.00 to determine if the invoice should be placed on a line variance hold. Invoice Distributions11Item$50.0001-Charge1Inv101-1-1112Item$50.0001-Charge2Inv101-1-2213Retainage-$7.5001-RetainageInv101-1-11$7.5014Retainage-$7.5001-RetainageInv101-1-22$7.50Invoice Lines and RetainageOracle Payables retains applicable retainage on all progress payment invoices. Progress payment invoices are standard invoices matched to a service procurement purchase order or receipt. Progress payment invoices have pay items of types Rate, Milestone, or Lump Sum. During the matching process, Oracle Payables calls the Oracle Purchasing API to retrieve the amount to retain. The retainage information is stored in the matched invoice item line and the system creates negative retainage distributions prorated to the item distributions. Discarding Invoice Lines with RetainageDiscarding an invoice line means that you remove it from visibility in the Lines tab of the Invoice Workbench window, but the data remains in the database. The discard function is used to discard any lines that you do not want to include on the invoice. By discarding the entire line, all its distribution lines are reversed automatically. With the introduction of Invoice Lines, when you match a line to a PO, you cannot reverse individual distributions within the invoice line. From the Invoice Lines window, discard the entire matched line, which automatically reverses the underlying distributions. You can not reverse a distribution line once any charge is allocated to it. Once the tax is allocated to the item distribution, the system does not allow you to reverse this distribution which is also the case for the Tax distribution if it is Permanent. In such cases, you should discard the Item line and not the distribution. This automatically reverses the Item and Tax distributions as well. Then, you can create new item line and validate the invoice. If you discard an item line with retainage, the retained amount of the pay item is reduced. When the reversing distributions are created, the retainage distributions are also reversed. If the invoice amount is gross of retainage, the gross amount of the payment schedule is increased. If a line carries retainage information and some or all of the related retainage releases have been billed, then the original invoice line cannot be discarded, since the retainage release lines contain references to the original standard invoice line. Important: Discarding retainage release line leaves incorrect balances. Invoice Line Corrections with RetainagePrice, quantity, and amount corrections are allowed for a base-matched item line. If, however, an item line carries retainage, and some or the entire retained amount has been released, no corrections are allowed on the item line. Note: You cannot correct an item line with released retainage. Line-Level Matching/Corrections and Retainage ComputationAfter amount information is entered in the purchase order, the PO API is called to retrieve the amount to retain and displays it by populating the Retained Amount field in the Lines tab. Also the matching/corrections API takes the retained amount and creates the necessary retainage distributions if the Net of Retainage check box is selected. In cases where the Net of Retainage check box is disabled, the matching API also updates the payment schedules. Retainage ReleaseRetainage release is the act of releasing, or paying, that portion of a payment that was withheld until a substantial portion or all of the service procurement work is completed. The amounts retained during the life of the contract must be released and paid to the supplier or sub-contractor once all or a substantial portion of the work is completed. Retainage terms in a service procurement contract are agreed upon by the buyer and the supplier and are defined in the contract. Oracle Payables receives any required contract data from Oracle Purchasing, Oracle Projects, and Oracle Contracts. Once the release criteria are met, suppliers request a release of the retained amount by submitting a document called a Retainage Release Request. Oracle Payables uses the Retainage Release Request to create a type of invoice called Retainage Release. A retainage release invoice has lines, which are copied from the original standard progress invoices, which show an amount left to be released. Creating Retainage Release InvoicesNote: Retainage release invoices can only be entered manually in the Invoice Workbench window. Entering Retainage Release InvoicesTo create retainage release invoices, perform the following tasks:
Creating and Adjusting Payment Schedules for Invoices with RetainageWhen an invoice amount entered is net of retainage, as indicated by the selected Net of Retainage check box at the invoice header, there is no impact to the creation of the payment schedule or adjustments. When an invoice amount entered is gross of retainage, the payment schedule is adjusted. The adjustment reduces the gross invoice amount in the payment schedule and occurs at the following event points:
Discountable Basis of Payment Schedules for Invoices with RetainageWhenever payment schedules are recreated, the amounts applicable to a discount take retainage into account and are net of retainage. Tax Calculation on Invoices with RetainageTax calculation on invoices with retainage is shown in the table below. In this example, if the progress payment invoice is $100.00 and the retainage is 15%, the invoice amount will be $85.00 plus VAT (10%) of $8.50 equals a total invoice due the supplier of $93.50. Example of Tax Calculation on an Invoice with RetainageProgress Payment100.00Less Retainage15.00Amount Due85.00VAT8.50Total Due to Supplier93.50Validating Invoices with RetainageValidating invoices with retainage impacts holds, variance calculations, and withholding tax. Holds on Invoices with RetainageThe Line Variance hold is placed on an invoice when the invoice amount is unequal to the sum of all invoice lines. This hold determination considers whether the Net of Retainage check box is enabled or disabled. The following table describes the rules for determining the line variance hold for invoices with retainage. Hold Determination Rules for Invoices with RetainageEnabledInvoice Amount = Sum of all the line amounts - Sum of all the Lines Retained Amount. If this is not the case, the Line Variance hold is applied.DisabledInvoice Amount = Sum of all the line amounts. If this is not the case, the Line Variance hold is applied.Variance Calculation on Retainage Release Invoices
The following tables in this section illustrate an Exchange Rate Variance example. Assume the invoice is a progress payment for $100.00 CAD, the functional currency is USD, and the exchange rate is .1 matched to a pay item that has two distributions. The retainage rate at the contract line is 15%. Invoice HeaderINV101BVC Inc.$85.0005/01/2006YesInvoice Lines1Item$100.00CONS10111-$15.00$15.00Invoice Lines Running Total$100.00-$15.00$85.00Since the Net of Retainage check box is disabled, the Invoice Validation process compares $85.00, the net amount, to the invoice amount of $85.00 in the header to determine if the invoice should be placed on a line variance hold. Invoice Distributions11Item$50.0001-Charge1Inv101-1-1112Item$50.0001-Charge2Inv101-1-2213Retainage-$7.5001-RetainageInv101-1-11$7.5014Retainage-$7.5001-RetainageInv101-1-12$7.50Assume the retainage is released when the exchange rate is 0.2 between the CAD and USD currencies. A retainage release invoice with an Exchange Rate Variance is created as follows: Invoice HeaderINV102BVC Inc.$15.00$3.0005/01/2006Invoice Lines1Retainage Release$15.00$3.00CONS10111INV1011Invoice Distributions11Retainage$7.50$0.7501-RetainageInv101-1-112ERV$0.7501-LossInv101-1-213Retainage$7.50$0.7501-RetainageInv101-1-114ERV$0.7501-LossInv101-1-1Retainage release invoices can have Tax Rate and Tax Exchange Rate Variances. Withholding Tax on Invoices with RetainagePayables calculates withholding taxes on invoices during the invoice validation process or during the payment calculation. Invoices with retainage impact the taxable amount withheld, based on when the withholding tax is calculated. If the withholding tax is calculated during the invoice validation process, then the taxable amount withheld is the gross amount. If the withholding tax is calculated during the payment calculation, then the taxable amount withheld is net of retainage. Withholding taxes are not calculated on retainage release invoices if the calculation is done during the invoice validation process. instead, the withholding taxes are calculated during the payment calculation. Accounting for Invoices with Retainage and Retainage Releases Invoices Using Subledger Accounting (SLA)The following example illustrates the accounting entries created by Oracle Payables for retainage and retainage release invoices. The sample data includes a progress pay item in a services procurement contract for $100.00, and the retainage rate is 15%. There is a 10% tax that is 0% recoverable. The progress payment invoice is created by matching to the progress pay item. The amounts include:
The related retainage release invoice includes the following amounts:
Accrual Basis Accounting Entries for Invoices with Retainage and Retainage Release InvoicesThe tables below illustrates the accrual basis accounting entries for invoices with retainage and retainage release invoices. Invoice EntryExpense100.00Non-Recoverable Tax8.50Retainage15.00Liability93.50Payment EntryLiability93.50Cash93.50Release Invoice EntryNon-Recoverable Tax1.50Retainage15.00Liability16.50Release Payment EntryLiability16.50Cash16.50Cash Basis Accounting Entries for Invoices with Retainage and Retainage Release InvoicesThe tables below illustrates the cash basis accounting entries for invoices with retainage and retainage release invoices. Invoice Entry - no entry. Payment EntryExpense100.00Non-Recoverable Tax8.50Retainage15.00Cash93.50Release Invoice Entry - no entry. Release Payment EntryNon-Recoverable Tax1.50Retainage15.00Cash16.50Automatically Recouping Advances and Contract Financing PaymentsOracle Payables ensures that amounts financed, such as prepayments, and later automatically recouped or recovered, never exceed the allowable amounts specified by the terms in the fixed price contract. OverviewRecoupment is the automatic process of recovering prepaid amounts when invoicing for progress or for the final delivery of goods or services, based on specific terms specified in the services procurement contract. It is basically a prepayment distribution tied to an item line. Recoupment, a common business practice in Federal Government contracts, settles advances and contract financing paid to a supplier against the delivery invoice. When the supplier or contractor submits invoices for the project, any prepayments are recouped from the previous advances or contract financing. Recoupment rules present in the service procurement contract enable Oracle Payables to automatically draw against the prepayments and reduce the amount due on the delivery invoice. Automatic recoupment occurs as part of the matching process at the following event points in Oracle Payables: header-level matching, line-level matching, and the open interface import. Advances and contract financing prepayments are automatically deducted from the standard invoice delivery payments for the contract line. The advanced or financed prepayment items are matched to a specific contract line in a service procurement purchase order. They are applied to, or recouped from, the same contract line with the delivery of the item, up to the unpaid invoice amount. Recoupment amounts are automatically calculated for every standard invoice item line that is matched to a service procurement purchase order delivery pay item or shipment. It is based on the total available amount of financed pay items or shipments for that same contract line. Recoupment treats advances and contract financing prepayments differently, as the following table describes: How Recoupment Treats Advances and Contract Financing Prepayments DifferentlyAdvanceThe progress payments and the final delivery invoice are all considered progress payments. That is, each of the progress payments and the final delivery invoice are all portions of the total amount due the supplier. Progress payments can be based on a milestone, a rate, or a lump sum.Contract FinancingAll progress payments are called prepayments. The prepayments are recouped, or drawn down, against the total amount due. The final delivery invoice is for the total amount due, rather than a portion of the total amount due.Manual recoupment is unavailable. You can, however, manually change the automatically generated recouped distributions by discarding the standard invoice item line, correcting the service procurement contract line, and then re-entering the standard invoice item line. The order of a recoupment is on a first-in, first-out (FIFO) basis by the prepayment invoice payment date, with contract financing recouped first and then advances. After the recouped amounts are calculated, the payment schedules are adjusted for the amount remaining. You can view the recouped amounts in the View Prepayment Applications tab in the Invoice Workbench window. Matching Progress Invoices to Service Procurement Purchase OrdersSince a recoupment is a prepayment distribution that is tied to an item line, the recoupment distributions are created automatically as part of the matching process. Recoupment amounts are automatically calculated for every standard (progress) invoice item line that is matched to a service procurement purchase order delivery pay item or shipment and are based on the total available amount of the financed pay items or shipments for the contract line item. If prepayments are available to apply, Oracle Payables determines the maximum amount to recoup for the line item. After calculating and subtracting retainage, the available prepayments are applied on a FIFO basis according to the prepayment payment date. Matching Rules for RecoupmentIf at least one standard (progress) invoice line is matched to a service procurement purchase order actual delivery pay items, Oracle Payables performs calculations and comparisons to determine the correct amount to apply as follows:
Manually Applying and Unapplying Prepayment InvoicesYou can manually apply prepayment invoices to standard invoices by using the Apply/Unapply Prepayments window in the Invoice Workbench. This window can be accessed by navigating from the Actions button in the Invoice Workbench. Since the recouped amounts are calculated during the matching process, they are defaulted and are available upon entering this window. The amount remaining in the payment schedules is adjusted based on both the retained and recouped amounts. You can only apply the available prepayment invoices that are not matched to the financing pay items and do not total more than the amount remaining in the Apply/Unapply Prepayments window. The recouped amounts cannot be displayed or unapplied from within the Apply/Unapply Prepayments window. Calculating the Recoupment AmountOracle Payables determines how much of the prepaid amount to recoup, based on which ever is less:
Recoupment ExampleThe table below shows a recoupment example where the prepayment amount is $40.00, the recoupment rate is 80%, and the retainage rate is 15%. The invoice line amount is $10.00. Recoupment ExampleInvoice Line$10.00Retainage-$1.50$10.00 x 15% = $1.50Recoupment-$8.00Lesser of:
Adjusting Payment SchedulesCreating the header of a standard invoice generates the payment schedule for the invoice. When prepayments are applied to the standard invoice, Oracle Payables adjusts the payment schedule. Entering a progress invoice with recoupment results in an adjustment to the payment schedule and a reduction of the gross amount. Recoupment events that result in an automatic adjustment to payment schedules are the following:
Correcting Prices, Quantities, and AmountsYou can perform price, quantity, and amount corrections to reflect adjustments of unit price, quantity, and amount previously billed through a specific invoice matched to a purchase order or receipt. The corrections can be performed in the context of matching to a purchase order or receipt line. Access the Corrections window to make your corrections. If the original base-matched invoice has an amount recouped, then the corrections that result in increases to the original base-matched invoice should update the Amount Recouped information in the PO shipment in the purchase order entity. The corrections that result in decreases to the base-matched invoice do not update the amount recouped information in the PO shipment. Viewing Recouped AmountsYou can view recouped amounts from the Invoice Workbench window as follows:
CorrectionsCorrections enable you to adjust the invoiced price, quantity, or amount of previously matched purchase order shipments, distributions, or receipts. You can use a correction when a supplier sends an invoice for a change for an invoice you have already matched to a purchase order. This existing matched invoice, also known as the base-matched invoice, is the invoice that the correction is adjusting, and it represents the actual quantity, unit price, and amount being charged for the purchased goods. To record a correction enter a Standard invoice to record a price increase, or enter a Credit Memo or Debit Memo to record a price decrease. Price corrections adjust the invoiced unit price of previously matched purchase order shipments, distributions, or receipts, without adjusting the quantity billed. You can record a simple price decrease correction by entering a credit or debit memo and matching to a base-matched invoice. However, we strongly recommend that you record all price corrections by matching to a purchase order or receipt. Note: In amount matching of purchase orders, you cannot perform price corrections. See You can enter a correction only if all of the following are true:
Invoice Validation and the Weighted Average PriceWhen Invoice Validation checks whether the invoice price is within the tolerance allowed, it checks the weighted average price of the base matched invoice and all the price corrections associated with the base matched invoice. To calculate the weighted average unit price, Payables uses this equation: (quantity * unit price) + (quantity * unit price) . . . / quantity invoiced for the base-matched invoice. For example, the following table shows an invoice matched to a purchase order, and a subsequent price correction for the invoice: Base Matched Invoice101.0010.00Price Correction5.201.00The weighted average price in this example is 1.10 because (10 * 1.00) + (5 * .20) / 10 = 1.10. However, if you provide no values for the quantity and unit price then the system uses the net amount of the price correction in the equation. For example, the following table shows a price correction with a negative amount but no values for Quantity or Unit Price: Base Matched Invoice101.0010.00Price Correctionnullnull<1.00>The weighted average price is 9 because (10 * 1.00) + (-1.00) / 10 = 9. Entering the Base Matched Invoice NumberWhen you enter a correction in the Invoice Workbench or Payables Open Interface, you provide the number of the base-matched invoice when:
Recording Price, Quantity, or Amount CorrectionsUse a price correction when a supplier sends an invoice for a change in unit price for an invoice you have matched to a purchase order or receipt. To record a price, quantity, or amount corrections in the Corrections Window:
Related Topics Final Matching Invoices and Final Closing Purchase OrdersFinal matching an invoice to a purchase order indicates that no more invoices should be matched to the purchase order. To final match, select the Final Match option in the Invoice Lines region or the enable mark the Final Match check box that is available on every PO line during matching. If you select Final Match and you match to an purchase order, the system only sets the purchase orders shipment level to Finally Closed. The Header and Lines Closure status shows Closed. If you match to a purchase order shipment, the system updates the closure status of the shipment to Finally Closed when you validate the invoice. In Purchasing, you can finally close a purchase order at the following levels: header, release, line, or shipment. When you finally close at one level then all sublevels are also finally closed. No further actions can be performed against a purchase order level that is finally closed. If the Show Finally Closed POs profile option is set to No, then during invoice entry Payables does not display purchase orders that are finally closed. If the profile option is set to Yes then Payables displays these purchase orders but you can't match to them. If an invoice is matched to a purchase order shipment that then becomes finally closed before validation of the invoice, Invoice Validation applies a Finally Closed PO hold on the invoice. You cannot manually release this hold. You must reverse the match in the Distributions window and resubmit Invoice Validation to release this hold. You can then match the invoice to a different purchase order or enter distributions manually. If you final match an invoice to a purchase order and the invoice has an exception that causes Invoice Validation to place a hold on the invoice, Payables also places a Can't Try PO Close hold on the invoice. To release this hold, you must release the other holds on the invoice and resubmit Invoice Validation. If you use automated receipt accrual in Purchasing and you final match an invoice to a purchase order shipment that is not fully delivered (quantity delivered is not equal to quantity received), Payables places a Can't Close PO hold on the invoice. If you manually release the hold, Payables disables the Final Match check box for any distribution on that invoice that is matched to the shipment. If you are using encumbrance accounting and you mark an invoice distribution as a final match to a purchase order, the system creates reversing journal entries for all outstanding encumbrances on that purchase order. Note: You cannot final match to a purchase order when you are matching to receipts. Also, you cannot final match a prepayment. Prerequisite
To final match a purchase order:Note: Final Match only if you are certain this is a final match against the related purchase order. Once you validate a final matched invoice distribution, you cannot update the Final Match check box for the distribution.
Related Topics Invoice Tolerances, Oracle Payables Implementation Guide Final Match (with Budgetary Control), Oracle General Ledger User Guide Viewing Purchase Order InformationTo view purchase order information:
Related Topics PrepaymentsA prepayment is a type of invoice you enter to make an advance payment to a supplier or employee. For example, you need to pay a deposit on a lease, or pay an employee an advance for travel expenses. You can later apply the prepayment to one or more invoices or expense reports you receive from the supplier or employee to offset the amount paid to them. 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. See: . You cannot apply prepayments to standard invoices when there are no item distributions or item lines without a valid distribution set. 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. 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. 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. 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. 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. See: . 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. 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. See the window-specific documentation for details. When you apply a prepayment, Payables creates a negative amount Prepayment type distribution on the invoice, and reduces the prepayment's available applicable amount. For example, if you apply a $100 Prepayment distribution to an invoice, Payables creates a negative $100 Prepayment distribution, and reduces the Amount Available on the prepayment Item distribution by $100. The account of the Prepayment distribution on the invoice defaults from the Item distribution on the prepayment. When you apply a prepayment, in addition to updating fields in the Apply/Unapply Prepayments window, Payables updates the following fields. For Quick Invoices and Expense Reports, these values appear after import:
This discussion includes the following topics: For information on how taxes are applied to prepayments, see: . Foreign Currency PrepaymentsPayables uses the exchange rate from the invoice when it accounts for the applied Prepayment and associated tax distributions. This credits the prepaid asset account for the correct amount. Because the prepayment application pays the invoice, Payables then records any gain or loss between the functional currency amount of the payment (original prepayment) and the functional currency amount of the invoice (invoice amount that the prepayment relieved). If the exchange rate accounting causes unequal debits and credits for the transaction, Payables accounts for that difference in a rounding entry to balance the transaction. Related Topics Entering PrepaymentsYou can enter a Prepayment type invoice only in the Invoice Workbench. You cannot enter a Prepayment type invoice in the Quick Invoices window. Optional Reuirements
Related Topics Implementing Sequential Voucher Numbering, Oracle Payables Implementation Guide Applying and Releasing Holds on PrepaymentsTo 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. See: . You release holds from a prepayment just as you would for any other invoice. See: . Related Topics Paying PrepaymentsPay a prepayment just as you would any other invoice. However, you cannot partially pay a prepayment; you must fully pay it. See: , or . You must fully pay a prepayment before you can apply the prepayment to an invoice. Related Topics Applying Prepayments to Invoices and Expense ReportsYou 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. If you use Automatic Offsets then your setting for the Prevent Prepayment Application Across Balancing Segments Payables option, Oracle Payables Implementation Guide controls whether you can apply a prepayment to an invoice or expense report with a different balancing segment. Prerequisites
You can apply a prepayment in the following ways: Prepayment Application RestrictionsENCUMBRANCE: If you use encumbrance accounting, you must enter a GL date in a period that is within the latest encumbrance year. Applying Prepayments in the Invoice WorkbenchWhen 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 in the Invoice WorkbenchTo apply a prepayment to an invoice in the Invoice Workbench:
Applying Prepayments in the Quick Invoices WindowFor Quick Invoices, you specify the prepayment information when you enter the invoice record. During import Payables applies the prepayment. You can also apply prepayments to invoices in the Invoice Workbench after you import them. Note that for Quick Invoices invoice records Payables applies the prepayment during import, so the available prepayment amount is available to apply to other invoices until import. You can apply a specific prepayment or multiple prepayments to an invoice. If you enter only a prepayment amount and do not identify a specific prepayment, Payables applies available prepayments for that supplier, in order of oldest prepayment to the newest, up to the prepayment amount. You can specify the first prepayment to apply. If the prepayment amount you enter exceeds the available amount on the specified prepayment, Payables then applies other available prepayments, in order of oldest to newest, up to the remaining prepayment amount. When you enter an invoice record in the Quick Invoices window, Payables does not notify you if you have available prepayments for the same supplier. You can submit the Prepayments Status Report to get the prepayment details you need to successfully apply the prepayment. You can apply one or all prepayment Item distributions. If you do not specify a value for Prepayment Distribution, Payables applies the prepayment amount across all available prepayment Item distributions in chronological order, starting with the first prepayment Item distribution, up to the prepayment amount. You cannot apply more than the total amount of available prepayment Item distributions, and you cannot apply more than the total amount of the Standard invoice you are entering. Additional Prerequisite for Quick Invoices To apply a prepayment to an invoice in the Quick Invoices window:
Related Topics Applying Prepayments in the Payables Open InterfacePayables Open Interface Import applies prepayments. You can also apply prepayments to invoices in the Invoice Workbench after you import them. For invoice records in the Payables Open Interface, Payables applies the prepayment during import, so the available prepayment amount is available to apply to other invoices until import. You can apply a specific prepayment or multiple prepayments to an invoice. If you enter only a prepayment amount and do not identify a specific prepayment, Payables applies available prepayments for that supplier, in order of oldest prepayment to the newest, up to the prepayment amount. You can specify the first prepayment to apply in the PREPAY_NUM column. If the prepayment amount you enter exceeds the available amount on the specified prepayment, then Payables applies other available prepayments, in order of oldest to newest, up to the remaining prepayment amount. If you specify a prepayment to apply, you can apply one or all prepayment Item distributions. If you do not specify a value for PREPAY_DIST_NUM, Payables applies the prepayment amount across all available prepayment Item distributions in chronological order, starting with the first prepayment Item distribution, up to the prepayment amount. You cannot apply more than the total amount of available prepayment Item distributions, and you cannot apply more than the total amount of the invoice record. You cannot enter a number for prepayment amount that exceeds the unpaid invoice amount. After import you can view the new distributions for the Standard invoice in the Distributions window. On the Prepayment distributions you can adjust the value in the Description field. The following open interface columns are relevant to applying a prepayment in the Payables Open Interface. You must enter at least either a prepayment amount or a prepayment number. For more details on any column, see: Table Descriptions, Oracle Payables Reference Guide.
Related Topics Applying Prepayments to Expense ReportsIn 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. See: . 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. Related Topics Withholding Tax When Applying PrepaymentsIf you use automatic withholding tax, Payables creates the correct withholding tax distributions. If your Withholding Tax Payables option is set to Apply Withholding Tax at Invoice Validation Time, then you might want to time the entry of the prepayment application before the invoice is validated. If you apply the prepayment before the invoice is validated, Payables creates a withholding tax distribution net of the prepayment amount. If you validate the invoice first, Payables creates a withholding tax distribution based on the taxable invoice amount. When the prepayment is applied then you will have to manually adjust the withholding tax amount and the withholding invoice if your Withholding Tax Payables option is set to create withholding invoice at invoice validation time or at payment time. Related Topics Entering Invoices that Reference PrepaymentsYou can enter supplier invoices where the invoice amount includes prepayments. If you receive a supplier invoice, and the invoice amount has been reduced because of prepayments that the supplier has received, you need to indicate that the invoice amount includes one or more prepayments in one of two ways:
When you indicate that the invoice amount includes one or more prepayments, the following conditions are true:
Because the Distribution Total includes prepayments, you need to ensure that you have applied prepayments before you submit the invoice for Invoice Validation. Important: Since the invoice amount includes prepayments, you should not use Distributions Sets to create your invoice distributions when using the Prepayment on Invoice feature. Unapplying PrepaymentsIf you mistakenly apply a prepayment to an invoice, you can unapply it. It is then available to apply to another invoice. When you unapply a prepayment, you must unapply the full prepaid amount. Payables increases the amount available for the prepayment by the unapplied amount. Payables creates a positive amount Prepayment distribution on the invoice, with the same attributes as the existing Prepayment distribution it is reversing. Payables then updates the status of the invoice to unpaid or partially paid. You can review in the Distributions window the Prepayment distributions applied to an invoice. You unapply prepayments in the Invoice Workbench. However, if the prepayment was applied before your Payables system was upgraded to Release 11i, you unapply the prepayment by submitting the Unapply Preupgrade Prepayment program from the Submit Request window. To unapply a prepayment in the Invoice Workbench:
Unapplying Prepayments Applied Before Upgrading to Release 11iIf you applied a prepayment to an invoice before upgrading to 11i, you cannot unapply the prepayment in the Invoice Workbench. To unapply this prepayment, you must submit the Unapply Preupgrade Prepayment program from the Submit Request window. You cannot unapply more than one prepayment application at a time. Note that accounting for this is different from the procedure described for prepayment unapplication event. Because prepayments were different before Release 11i, accounting for this unapplication will be a payment adjustment on the invoice and an invoice adjustment for the prepayment. Prerequisite
To unapply a prepayment by submitting the Unapply Preupgrade Prepayment program:
Related Topics Cancelling PrepaymentsYou can cancel prepayments if they have not been paid or applied to invoices. To cancel an applied prepayment, you must first unapply the prepayment and void the payment document that paid the prepayment. To cancel an unapplied prepayment:
To cancel an applied prepayment:
Related Topics Recording a Refund of a Prepayment or AdvanceNote: We recommend that to record a refund, you enter a standard invoice and apply the prepayment to it. Then enter a debit memo and pay it with a Refund payment in the Payments window. See: Alternatively, record the refund by using the following method. Recording Refunds by Paying a Standard InvoiceYou can record a refund from a supplier that pays back an unused prepayment or part of a prepayment. When you do this, Payables reverses the prepayment so that it is no longer outstanding and so that you can no longer apply the prepayment to an invoice. The net effect is a debit to your cash (asset) account in the amount of the refund and a credit to the prepayment account in the amount of the refund. You can use exactly the same method to record a refund from an employee for an advance. Prerequisites
To record a refund of a prepayment:
Related Topics Find Invoices to Apply WindowWhen you are in the Apply/Unapply Prepayments window you can narrow your search for invoices to apply by using the Find Invoices to Apply window. To use the Find Invoices to Apply window:
Related Topics Find Prepayments to Apply WindowWhen you are in the Apply/Unapply Prepayments window you can narrow your search for prepayments to apply by using the Find Prepayments to Apply window. To use the Find Prepayments to Apply window:
Related Topics Apply/Unapply Prepayments Window ReferencePayables provides two ways to apply prepayments to an invoice. You can do either of the following:
Selecting an Invoice and Applying it to a PrepaymentWhen you select an invoice and choose the Apply/Unapply Prepayment option in the Invoice Actions window, the Apply/Unapply Prepayments window opens. It automatically displays all prepayments that have been applied to the invoice, and all available Prepayment distributions that you can apply to the invoice. Payables displays prepayment item type distributions that meet the following criteria: same supplier, and invoice currency as the invoice. The prepayment's Settlement Date is on or before today's date. The prepayment is type Temporary with a status of Available. If you use Automatic Offsets, you can set up Intercompany Accounting in Oracle General Ledger to ensure that the prepayment application is balanced by balancing segment. For more information on applying prepayments when using automatic offsets, see: . For information on setting up Intercompany Accounting, see: . Invoice Amount. Amount of the invoice. All amounts displayed in this window are in the invoice currency. Invoice Amount Unpaid. Amount of the invoice that is unpaid by payments and prepayments. You can apply remaining prepayments up to this amount. Apply. Use the Apply check box to select prepayments to apply to the invoice. Prepayment on Invoice. (check box) Enable this check box if the invoice references a prepayment (the invoice amount has been reduced by the prepayment amount and any associated tax). Amount To Apply. Enter the amount of the prepayment Item distribution you want to apply. This amount cannot exceed the amount of the Prepayment distribution that is unapplied. The total amount of prepayments you apply cannot exceed the unpaid amount of the invoice. GL Date. Accounting date of the prepayment application. Payables will default the latest GL Date used on the invoice and prepayment invoice distributions. This value will be the GL Date on the Prepayment distribution that Payables creates. Prepayment Number. Invoice number of the prepayment. Line Num. Displays the line number. Amount Available. Amount of the prepayment that you can apply. This is the original distribution amount minus any existing amounts applied to invoices. Amount of Included Tax. Displays the tax amount included. Site. Payables displays the supplier site to which the prepayment was paid. Print. To print a Prepayment Remittance Notice for the supplier when you apply a prepayment, choose this option. The Prepayment Remittance Notice is a letter notifying the supplier that you have applied a prepayment to an outstanding invoice. Payables prompts you to enter the following information for the letter signature block: Name of Sender, Title of Sender, Phone of Sender. See: . Description. Payables displays the description of the selected distribution. This value defaults to the new Prepayment distribution, and you can modify the description in the Distributions window. PO Num/Receipt Num. If the Prepayment distribution was purchase order matched, Payables displays the transaction to which it was matched. For details on how Payables builds the GL accounts for matched prepayments when the Build Prepayment Accounts When Matching Payables option is enabled, see: Build Prepayment Accounts When Matching, Oracle Payables Implementation Guide. ButtonsInvoice Overview. If you select a Prepayment record and then choose this button, Payables opens the Invoice Overview window and displays information on the prepayment. Apply/Unapply. Choose this button to apply or unapply selected prepayment amounts. You can review the updated distributions for the invoice in the Distributions window. Existing Prepayment ApplicationsThis region of the window shows all prepayment amounts you have already applied to the invoice. It shows the amount applied, the GL date and tax code on the invoice Prepayment distribution, the prepayment invoice number and distribution number, and the prepayment's supplier site. It also shows the description and account description of the prepayment Item distribution, as well as the purchase order number or receipt number if the Item distribution was matched. If you unapply a Prepayment distribution, you must unapply the full amount that you previously applied. You select the Unapply check box to identify a distribution you want to unapply. Selecting a Prepayment and Applying It to an InvoiceIf you select a prepayment and choose the Apply/Unapply Prepayment option in the Invoice Actions window, Payables displays invoices that meet the following criteria: same supplier and invoice currency as the prepayment. The invoice date is on or after the date of the prepayment. If you enable Automatic Offsets and choose Balancing Segment, you can still select prepayments and apply them to your invoices. However, you can select only one invoice at a time for prepayment application. Payables automatically applies the prepayment amount across prepayment distributions, according to the balancing segments on the invoice distributions. If you have multiple balancing segments, each time you make a prepayment application, Payables applies only those prepayment distributions that share the same balancing segment. For more information on applying prepayments when using automatic offsets, see: Prepayment Amount. Amount of the prepayment in the invoice currency. Prepayment Amount Remaining. Amount of the prepayment that is unapplied to invoices and available for application. Apply. Use the Apply check box to select invoices to which you will apply the prepayment. Amount To Apply. Enter the prepayment amount you want to apply. This amount cannot exceed the Invoice Amount Unpaid. The total amount of invoices you apply cannot exceed the Prepayment Amount Remaining. GL Date. Accounting date of the prepayment application. Payables will default the latest GL Date used on the invoice and prepayment invoice distributions. This value will be the GL Date on the Prepayment distribution that Payables creates. Invoice Number. Invoice to which you are applying the prepayment. Amount Unpaid. Amount of the prepayment that you can apply. This is the original invoice amount minus withholding tax and any existing prepayments or payments. Site. Invoice supplier site. Print. To print a Prepayment Remittance Notice for the supplier when you apply a prepayment, choose this option. The Prepayment Remittance Notice is a letter notifying the supplier that you have applied a prepayment to an outstanding invoice. Payables prompts you to enter the following information for the letter signature block: Name of Sender, Title of Sender, Phone of Sender. See: . Description. Payables displays the description of the selected invoice. Existing Prepayment ApplicationsThis region of the window shows all invoices to which the prepayment has been applied. It shows the amount applied, the GL date and tax value on the invoice Prepayment distribution, the invoice number that the prepayment has been applied to, and the invoice supplier site. It also shows the Prepayment distribution number, description and account description of the prepayment Item distribution, as well as the purchase order number or receipt number if the Item distribution was matched. If you unapply a Prepayment distribution, you must unapply the full amount that you previously applied. You select the Unapply check box to identify a distribution you want to unapply. ButtonsInvoice Overview. If you select an invoice record and then choose this button, Payables opens the Invoice Overview window and displays information on the invoice. Apply/Unapply. Choose this button to apply or unapply selected prepayment amounts. You can review the updated distributions for the invoice in the Distributions window. Related Topics Credit and Debit MemosEnter 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.
This discussion includes the following topics: Entering Credit/Debit MemosTo enter a credit/debit memo:
Related Topics Matching Credit/Debit Memos to Purchase Orders and InvoicesWhen 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 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. If the original invoice is not purchase order matched (basic invoice), you can:
If the original invoice is purchase order matched, you can:
Matching Credit/Debit Memos to InvoicesYou can match credit and debit memos to invoices only in the Invoice Workbench, not in Quick Invoices. To match a credit/debit memo to an invoice or invoice line:
When you create a Credit memo to correct an unmatched invoice, an error displays. Matching Credit/Debit Memos to Invoices Using Quick CreditUse Quick Credit to create a credit or debit to completely reverse an existing invoice record. To enter a credit/debit memo using quick credit:
Matching Credit and Debit Memos to Purchase Orders and ReceiptsEach purchase order shipment indicates whether you should match to either a purchase order or receipt. You can match only to the document type (purchase order or receipt) specified by the purchase order shipment. To match a credit/debit memo to a purchase order shipment or receipt in the Invoice Workbench:
Validating Related InvoicesThe Validate Related Invoices button validates related invoices depending on which type of invoice is selected:
To validate related invoices:
Clearing a CreditYou 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. See: . 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:
Mixed InvoicesMixed Invoices are invoices or credit/debit memos for which you can match to purchase orders and to other invoices. Mixed invoices can be either positive or negative values. However, you can only match a negative amount mixed invoice to a standard invoice. To enter a Mixed invoice: Entering Foreign Currency InvoicesWhen you enter an invoice in a currency other than your functional currency, Payables uses an exchange rate to convert the invoice and invoice distributions into your functional currency for creating journal entries. You define your functional currency during setup for your ledger. See: . To assign an exchange rate to an invoice, you can manually enter the rate when you enter an invoice. Alternatively, you can have Payables enter an exchange rate from the GL Daily Rates table either by entering a rate type and rate date during invoice entry or entering them later and then using the AutoRate program. If you match an invoice to a purchase order, Payables uses the invoice exchange rate to create invoice distributions. Payables does not use the purchase order exchange rate. If there is a difference between the rates, Payables records the exchange rate variance. Related Topics Manual Exchange Rate EntryPrerequisites
To enter a foreign currency invoice with a manually entered exchange rate:
Related Topics Payables Options, Oracle Payables Implementation Guide GL Daily Rates Table Default Exchange Rate EntryPrerequisites
To enter a foreign currency invoice with a GL Daily Rates Table default exchange rate:
Related Topics Payables Options, Oracle Payables Implementation Guide AutoRate Exchange Rate EntryPrerequisites
To enter a foreign currency invoice exchange rate with AutoRate:
Related Topics Payables Options, Oracle Payables Implementation Guide FOREIGN CURRENCY INVOICE RESTRICTIONS:CHANGING CURRENCY TYPES: Once you save your invoice, you cannot change the currency. You can use the Cancel Invoice action then re-enter the invoice with the correct currency. NO RATE HOLD: Payables will not allow you to create accounting entries an invoice in a currency other than your functional currency. Invoice Validation will put a No Rate hold on a foreign currency invoice with no rate defined. PURCHASE ORDER MATCHING: Payables will not allow you to match an invoice to a purchase order that has a different currency. WITHHOLDING TAX: Payables will not create a payment for a foreign currency invoice if the following conditions are true: the invoice has a withholding tax group assigned that is set up with either a period limit or more than one amount range. Related Topics Payables Options, Oracle Payables Implementation Guide Entering Invoices for Suppliers Subject to Income Tax Reporting RequirementsIf you set up a supplier as federally reportable and assign a default income tax type to the supplier, then that value defaults down to each invoice distribution you enter for that supplier. You can override the default Income Tax Type for an invoice distribution in the Distributions window of the Invoice Workbench. You can also use the Update Income Tax Details utility to make income tax type updates at any time before running your reports. In the United States, you must report to the Internal Revenue Service certain types of payments you make to 1099 reportable suppliers. Within Payables, you can designate suppliers as federally reportable, classify their invoice distributions by 1099 MISC Type, then at the end of the year when you submit your 1099 reports, Payables lists payments of reportable distributions made to 1099 suppliers. For example, you enter an invoice for a 1099 reportable supplier. The supplier's hourly fees are reportable for U.S. 1099 reporting purposes, but reimbursable expenses, such as travel, are not. In the Distributions window for the fee distribution you assign an Income Tax Type; however for the travel distribution, you clear the Income Tax Type field. Prerequisite To record income tax information for an invoice:
Related Topics Entering Supplier Information, Oracle iSupplier Portal Implementation Guide Updating 1099 InformationYou can update 1099 information for your suppliers. If you paid a supplier before you set up the supplier as a 1099 supplier, run the Update Income Tax Details Utility. Or, if you need to update only a few invoices, you can update the 1099 types in the Distributions window. Adjusting 1099 AmountsThe following are suggestions for adjusting transactions for 1099 suppliers. If you need to add an amount to a 1099 supplier, for example if you paid the supplier through another system, you can adjust an invoice paid during the year in the Distributions window of the Invoice workbench. Add a distribution for the amount you want to add for 1099 purposes, including the Income Tax Type. Also add an offsetting distribution with a null Income Tax Type. If you did not pay the supplier during the year using Oracle Payables, then complete the following steps: Prerequisites
To record 1099 payments made outside of Payables and from a legacy system into Payables:
Recording a Refund From a One-Time 1099 SupplierIf you get a refund from a one-time 1099 supplier, you need to record the refund in Payables so that the 1099 reports are accurate. Enter a credit memo that you match to the original invoice, and then pay it with a refund. See: . Related Topics Recurring InvoicesYou 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. With a recurring invoice template, you can do the following:
Recurring Invoices can also be used to create debit memos. PrerequisitesRecurring invoices are affected by the following prerequisites.
Creating a Recurring Invoice TemplateTo create a recurring invoice template
Related Topics Creating Recurring InvoicesIn the Control Payables Periods window, ensure that the periods you create invoices in have a status of Open, Future, or Never Opened. Prerequisites To create recurring invoices:
Related Topics Creating Recurring Credit/Debit MemosTo create recurring credit memos or debit memos:
Withholding Taxes from Recurring InvoicesTo withhold taxes from a recurring invoice:
Related Topics Withholding Tax Groups, Oracle Payables Implementation Guide RECURRING INVOICE RESTRICTIONS:SEQUENTIAL NUMBERING. You must use automatic sequential numbering for recurring invoice voucher numbers. NO REMAINING PERIODS: If the template has no remaining periods, you cannot create any invoices. CHANGING TEMPLATE FIELDS AFTER CREATING AN INVOICE: You cannot update the following fields in the recurring invoice template after you have created an invoice: Supplier Name, Number, Site, First and Next Periods, Template Number, Currency, GL Date, First Amount, Change, Number of Regular Invoices, Release Total, Amount Remaining, and Next Amount. Related Topics Recurring Invoices Window ReferenceOperating Unit - The operating unit for which the template is defined. Number of Invoices. This field is located at the bottom of the window. Enter the number of invoices you want to create, then choose the Create Invoices button to create the invoices. Supplier RegionSite. The supplier pay site for which a template is defined. This field is entered automatically if only one pay site exists for a supplier. Calendar RegionName. Calendar name representing frequency of invoice creation (e.g. Monthly). To enter a calendar name, you must first define the calendar as a Recurring Invoice type calendar in the Special Calendar window. Number of Periods. Total number of invoices to be made over the life of a template. If you change the number of periods, then this value must be less than the original number of periods. First. The first period for which a recurring invoice will be created. The period cannot be Closed or Permanently Closed. Next. Payables displays the next recurring invoice period for which an invoice can be created with a template. The First period is used as the default for the Next period until the first invoice is created. Periods Remaining. Payables displays the number of periods remaining for which you have not yet created invoices. If you change the Number of Periods value, then the system reduces the value in the Periods Remaining field by the same amount. Invoice Definition TabNumber. Template Number, which must be unique for a supplier. When you create invoices based on a template, Payables creates the invoice number for each invoice by appending the name of the recurring invoice period to the template Number. Currency. Currency for invoices created from a template. Default is the functional currency unless the supplier site has a different default. Description. Template description used as the distribution descriptions if no purchase order or Distribution Set description is available. Withholding Tax Group. The withholding tax group that will be used as a basis for withholding from invoices created from a template. This defaults from the supplier site. Accounting RegionLiability Account. Account where invoice liability will be recorded. This will be defaulted to all invoices created from a template. GL Date. Date to recognize the invoice liability. The GL Date is used as a default accounting date for each invoice. If you do not enter a GL Date, the beginning date of each invoice's period will be each invoice's default GL Date. Line Definition TabOrigin RegionSelect either Set or PO to choose whether invoice distributions are created by a Distribution Set or a purchase order. Then enter the specific source: Name. If you choose Set, enter the name of a Full Distribution Set. Num. Purchase order number. Line. Purchase order line. Shipment. Purchase order shipment. If you select a purchase order shipment, during invoice creation Payables automatically matches the invoices created to the purchase order shipment. It prorates across all purchase order distributions to create the invoice distributions. For example, you have a blanket purchase order for car leases. You enter the purchase order number, line, and shipment on a template to create lease invoices, and Payables will match each invoice created by the template to the purchase order shipment. Release. Releasing a Purchase Order. Amounts TabFirst Amount. Amount of first invoice created by a template, excluding any special payment such as a deposit. Used with the Change percentage to calculate incremental invoice amounts. Used with the Number of Regular Invoices to calculate the Control Total. Next Amount. Amount of the next scheduled recurring invoice. Change. Percent change to increase or decrease the amount per period. For example, if you pay rent once per month and your rent increases 1% per month, enter 1 here. Number of Regular Invoices. Total number of periods defined for a template. Special Invoice Amount1 / Amount2. One time special payment such as a deposit or balloon payment including the regular periodic payment. It is the only amount paid in that period. Period. Period in which you want to pay the Special Invoice. Control Total. Total amount available for creation of invoices. Payables enters this number for you if you enter the First Amount and the Number of Regular Invoices. After you create a recurring invoice, you can change the value in the Control Total field. If you change the value in this field, then the system automatically updates the values in the Released Total and Amount Remaining fields. Released Total. Sum of the invoice amounts that have been created using the template. Amount Remaining. Funds available for invoice creation using a template. Payables displays the Control Total minus the Released Total. Tax TabFor a description of the fields on this tab, see: Control TabApproval Workflow Required. If this option is enabled then when Payables creates invoices using this template it will set each invoice's approval status to Required. The invoices will then need to be approved before they can be paid. Hold. Hold name to automatically prevent the creation of invoices using a template. Release the hold by clearing this field. Expiration Date. Last day you can create invoices using a template. Before this date you can create invoices with invoice dates after the Expiration Date. Requestor. The name of the requestor. Payment TabTerms. Terms you want to use to create a scheduled payment for each invoice you create from a template. Pay Group. Pay Group name associated with a template. Default Pay Group name for all invoices created with a template. Payment Method. Payment method for invoices created from a template. Pay Alone. Pay alone invoices are paid on separate payment documents. Payment Reason. Indicates the reason for payment. Payment Reason Comments. Enter the comment for the reason. Delivery channel. Enter the mode of delivery. Remittance message 1. Enter the message o remittance. Remittance message 2. Enter the message o remittance. Remittance message 3. Enter the message o remittance. Remit to Supplier Name. Enter or accept the Remit to Supplier Name if you want to pay to the Third Party. This field is mandatory and enable you to record the Third Party supplier to whom the payments are to be made. Remit to Supplier Site. Enter or accept the Remit to Supplier Site if you want to pay to the Third Party. This field is mandatory and enable you to record the Third Party supplier to whom the payments are to be made. The Remit To Supplier Site list of values displays only those supplier sites that are attached to the selected Remit To Supplier Name for which the relationship is defined and is active as on Invoice date. Remit-To Bank Account RegionBank Account Name/Number. If you are paying your supplier electronically, then enter the supplier bank account name and number to which you will remit payment. Payables defaults the supplier site's primary account, if there is one for the payment currency. If none exists at the site level, Payables defaults the primary bank account from the supplier level, if one exists. You can change the account by choosing from the list of values another account with the same currency. If the value in the Payment Method field of the Template Definition region is Electronic, then Payables displays the bank and branch associated with the supplier bank account that you selected. Remit-To Bank RegionBank/Branch Name/Number. Payables displays the Bank and Branch associated with the supplier bank account you select. ButtonsCreate Recurring Invoices. After you have created a template and entered in the number of invoices that you want to create, click this button. This button opens the Create Invoices window where you can review invoice information before confirming that you want to create the invoices RECURRING INVOICES WINDOW RESTRICTIONS:CREATE INVOICES BUTTON: The button is enabled only if Number of Periods Remaining is greater than zero, the system date is earlier than the expiration date, and there is no hold on the recurring invoice template. UPDATES: In the Recurring Invoices window, all the fields except for Liability Account cannot be updated after the first invoice has been created. NO REMAINING PERIODS: You cannot create an invoice if a template has no remaining periods. Related Topics Special Calendar, Oracle Payables Implementation Guide Quick InvoicesYou can enter invoices in either the Quick Invoices window or the Invoice Workbench. The Quick Invoices window is the quickest way to enter most invoices. Use this window to enter a large volume of invoices that do not require extensive online validation or extensive online defaulting of values. Note: Speed up invoice record entry by customizing Quick Invoices folders. You can resize, rename, move, and hide fields to meet your needs. See: Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide. This section includes the following topics: Related Topics Quick Invoices OverviewPayables uses information you enter in the Quick Invoices window to create invoices in Payables. You enter invoice header and line information in this window. This information is stored in the Payables Open Interface tables. Because the system performs limited validation and defaulting of invoice values while you are entering invoices, you can enter invoices more quickly in the Quick Invoices window than you can in the Invoice Workbench (the Invoice Workbench is the Invoices window and its associated windows). For a text description of the previous graphic, see: Text Description of the Quick Invoices Window Graphic, Oracle Payables User's Guide. After you enter invoice records in the Quick Invoices window, you can submit a customized workflow program to automate your processes for managing invoices. For example, you can customize the workflow program to validate the cost center on all invoices before you import them. You then submit the Payables Open Interface Import Program to validate the values you entered, provide any default values, and then create invoices with distributions and scheduled payments in the regular Payables tables. After import, Payables provides a report that lists invoice records that were successfully imported and any that could not be imported because they had invalid or missing information. You can query the rejected invoice records in the Quick Invoices window, correct them, and then resubmit them for import. When you import invoice records successfully, Payables creates regular invoices that you can view, modify, and validate in the Invoice Workbench. After you successfully create invoices based on data in the invoice records, you can purge the invoice records from the Payables Open Interface tables. Related Topics Payables Open Interface Workflow, Oracle Payables Implementation Guide Payables Open Interface Tables, Oracle Payables Reference Guide Entering Invoice Records in the Quick Invoices WindowWhen you enter invoice records in the Quick Invoices window, you group the invoice records by assigning the same batch name to each invoice. When you enter a value for Quick Invoices Batch in the Quick Invoices Identification window, the system assigns that Quick Invoices Batch name to each invoice record you enter. You can use the Quick Invoices Batch name to query the group of invoice records in the Quick Invoices window, and to identify a group of invoice records that you want to import together. Note that if you use invoice batch control and you want to maintain the grouping of invoices after import, then when you submit import for the Quick Invoices batch, you can assign an Invoice Batch name to the group of invoices that Payables creates. You can then use the Invoice Batch name to query the same group of invoices in the Invoice Workbench. Entering a Basic Invoice Record in the Quick InvoicesPrerequisites
To enter a basic invoice record in the Quick Invoices window:
Related Topics Entering Purchase Order Matched Invoice Records in the Quick Invoices WindowWhen you enter a purchase order matched invoice record, the import process automatically creates invoice distributions for you based on your match. You can match to a purchase order receipt, and you can match to a purchase order at different levels: purchase order header, purchase order line, purchase order shipment, purchase order distribution. Tip: When you are matching to a purchase order, also open the View PO window to have easy access to purchase order information. Note: During import, the system does not check quantity or unit price tolerances. If the invoice exceeds the tolerances you have set in the Invoice Tolerances window, Payables applies a system hold on the invoice at Invoice Validation time. Matching to a Purchase Order at the Quick Invoices Header LevelPrerequisites
To enter a purchase order matched invoice record at the header level:
Matching to a Purchase Order Shipment or Distribution in the Quick InvoicesPrerequisite
To enter a purchase order matched invoice record at the shipment or distribution level:
Matching to Receipts in the Quick InvoicesYou can match to a receipt associated with a purchase order shipment. Specify the purchase order number and the receipt to which you want to match. Prerequisite
To enter a receipt matched invoice record:
Related Topics Entering Price Corrections in the Quick InvoicesYou use a price correction when a supplier sends you an invoice for a change in Unit Price. You can record a price correction when you match a Credit or Standard invoice record to a previously matched purchase order and adjust the invoiced unit price. Tip: We strongly recommend that you use the Invoice Workbench, rather than the Quick Invoices window to enter price corrections in this version of Payables. Entering in the Invoice Workbench allows you to specify more detailed information, so Invoice Validation can properly validate that the price is within the appropriate tolerance. For more information, see: . Prerequisite
To record a price correction in the Quick Invoices window for a purchase order shipment or distribution:
Related Topics Finding Invoice Records in the Quick Invoices WindowYou can query any invoice record in the Quick Invoices window if you entered it in the Quick Invoices window and you have not yet purged the invoice record from the Payables Open Interface tables. If you have successfully imported the invoice record, we recommend that you view it in the Invoice Workbench, where you can see the new distributions, scheduled payments, and defaults that were assigned during import. To find invoice records that are in the same Quick Invoices batch, you can use the Quick Invoices Identification window. Or, to find invoice records regardless of Quick Invoices batch, you can perform a query directly in the Quick Invoices window. For example, to see all invoice records that have been rejected in all batches, you can query all invoices with the Status of Rejected. If you entered invoices in the Payables Open Interface from other sources such as e-Commerce Gateway or your credit card enterprise and you want to view or modify them, do not use the Quick Invoices window. Use the Open Interface Invoices window instead. Prerequisites
To find invoice records using the Quick Invoices Identification window:
To find invoice records by performing a query in the Quick Invoices window:
Related Topics Modifying Invoice Records in the Quick Invoices WindowIn the Quick Invoices window, you can modify any invoice record you entered in the Quick Invoices window but have not successfully imported. If you have successfully imported an invoice record and want to modify it, you must use the Invoice Workbench. When correcting problems with invoice records rejected during import, you can find the rejection reason by looking at the Payables Open Interface Import Report, or you can query the record in the Quick Invoices window and choose the Rejections button to see the rejection reason in the Rejections window. For a more detailed explanation of the rejection, see: . Prerequisites
To modify an invoice record in the Quick Invoices window: Related Topics Adding Invoice Records to an Existing Quick Invoices BatchYou can add invoice records to a Quick Invoices Batch at any time. Either query an existing batch and add invoice records to it, or add invoice records to an existing batch by using the same Source and Batch Name when you enter new invoice records. Prerequisite
To add an invoice records to an Quick Invoices batch:
Related Topics Creating Invoices From Quick Invoices Invoice Records (Import)The Payables Open Interface Import Program creates invoices using the invoice records you entered in the Quick Invoices window. Once import creates invoices in Payables, you can view and modify them in the Invoice Workbench. You can also pay the invoices after you validate them. There are two ways you can submit Payables Open Interface Import for invoice records you have entered in the Quick Invoices window: Use the Create Invoices window, or submit the Payables Open Interface Import Program from the Submit Request window. If you submit import from the Submit Request window, you can optionally specify only the Source, and not the Quick Invoices Batch Name (Group parameter). To submit the request from the Submit Request window, see: . Prerequisite
To create Payables invoices by using the Create Invoices window:
Related Topics Quick Invoices Identification Window ReferenceWhen you navigate to the Quick Invoices window, the Quick Invoices Identification window opens. Use this window to assign Source and Batch names to the invoice records. You can then use these values to identify invoice records for queries, and for import. When you enter invoice records, the Source and Quick Invoices Batch name values default from the values currently in the Quick Invoices Identification window. Source. Enter Quick Invoices, or enter a value that you defined in the Oracle Payables Lookups window. If you enter a user-defined source, then use it only for one particular source type. For example, if you define a source name that you use for Quick Invoices invoice records, do not use it for any other method of entering data in the Payables Open Interface tables. At import time, the Source differentiates between invoice records you enter in the Quick Invoices window; credit card records from your credit card issuer; lease invoices from Property Manager; lease invoices from Oracle Assets, and invoice records you load using Oracle e-Commerce Gateway or SQL*Loader. Quick Invoices Batch. A Quick Invoices Batch is used to group invoice records that you enter in the Quick Invoices window. You can add invoice records to a batch at any time. You can use the batch name to specify a group of invoice records you want to query, import, or purge together. You can import data in concurrent processes for the same Source by specifying a unique group (batch) for each request. This reduces the processing time of your import. For example, if you enter 200 invoice records, instead of submitting import for a single batch of 200 invoices, you can submit two batches at the same time for faster processing. Note that if you use batch control for your invoice batches (the AP: Use Invoice Batch Controls profile option is enabled) and you want to maintain the grouping of invoices after import, then when you submit import for the Quick Invoices batch, you can assign an invoice batch name to the group of imported invoices. You can then query the invoice group in the Invoice Workbench by using the Invoice Batch name. Status. Use this field to query invoice records with a particular status. You can query Rejected or Processed invoice records by specifying those statuses. If you provide no value for Status when you perform a query, the system retrieves invoice records regardless of status.
Related Topics Quick Invoices Window ReferenceEnter invoice header and line information in this window. When you submit Payables Open Interface Import, Payables creates invoices with distributions and scheduled payments based on the invoice records you enter in this window. After an invoice record is imported successfully, you can view, modify, and validate it in the Invoice Workbench. You can modify invoice records in the Quick Invoices window if they have not been imported or purged. After you purge an invoice record from the Payables Open Interface tables, you can no longer query or modify the invoice record in the Quick Invoices window. Fields that are validated online have the following designation in this document: (LOV). This indicates that you can select from a list of valid, active values. Also, if you enter an invalid or inactive value in one of these fields, then the list of values will appear automatically. For information on the validation that Payables performs during the import process, see the , and see the validation information in the column descriptions of the Payables Open Interface Table Descriptions, Oracle Payables Reference Guide. Tip: Customize your Quick Invoices folder forms to prevent yourself from entering values that could cause rejection of the invoice during import. Quick Invoices Header RegionEnter the invoice header information in this region. The following information is required: Supplier Site, Invoice Amount, and either Supplier Number or Supplier Name. Date Invoice Received. The date you receive an invoice. If your Terms Date Basis Payables option is set to Invoice Received, and you provide a value, Payables will use this value as the Terms Date. If you don't provide a value here, then the invoice will be rejected. Description. Description of goods and services listed on the invoice. During import, this value is the default for invoice header description. The description appears on the payment document remittance, and you can include it when you transfer journal entries to your general ledger. Discountable Amount. Invoice amount applicable to discount. If you don't enter a value, during import Payables defaults the Invoice Amount as the Discountable Amount value. Document Category. (LOV) Payables uses the document category to assign a unique voucher number to an invoice. Enter a document category only if all of the following conditions are true. If one or more of the following conditions are not true, then the invoice record will be rejected during import.
If you enter a value for Document Category, then Payables will ignore any value you enter for Voucher Number in this window. Payables predefines a document category for each invoice type. The predefined document category will default to the invoice during import if you use automatic sequential voucher numbering, you do not enter a value in this Document Category field, and the Sequential Numbering profile option is set to Always. If you do not use voucher numbering (your Sequential Numbering profile option is set to "Not Used"), then do not enter a value, or import will reject the invoice. Exchange Date/ Exchange Rate. Foreign currency rate information that Payables uses to convert a foreign currency invoice amount to your functional currency. If a rate is available based on the Exchange Rate Type and Exchange Date that you enter, then the Quick Invoices window will display it. Do not overwrite any value that the system provides in this window or the invoice record will be rejected during import. If you have enabled the Require Exchange Rate Entry option in the Financials Options window and the exchange rate type is User then you must enter a value for Exchange Rate or the invoice record will be rejected. See: and . Exchange Rate Type. (LOV) Type of exchange rate between the invoice and your functional currency. If you have entered a foreign currency invoice record and do not enter a value for Exchange Rate Type, then during import Payables defaults the exchange rate type from the Exchange Rate Type field in the Payables Options window.
GL Date. The default GL Date for the distributions for this invoice. Must be in an open or future period. During import, Payables looks for a GL Date value to assign to the invoice distribution. Payables assigns a value from the first source it finds, and it searches the following sources in the following order: 1) GL Date field in invoice record line, 2) GL Date field in invoice record header, 3) GL Date parameter from import submission, 4) GL Date Basis Payables option. If the system searches at the GL Date Basis level, the following occurs: If the GL Date Basis option is set to Goods Received/Invoice Date, then Payables uses the Goods Received Date, if it is populated. If not, then Payables uses the Invoice Date. If the GL Date Basis option is set to Goods Received/System Date, then Payables uses the Goods Received Date, if it is populated. If it is not, then Payables uses the system date at time of import. If the Use PO Encumbrance option is enabled in the Financials Options window, then the date must be in the current encumbrance year. Date Goods Received. The date you receive goods for invoice records. If your Terms Date Basis Payables option is set to Goods Received, then if you provide a value, Payables will use this value as the Terms Date, and if you don't provide a value here, Payables will reject the invoice. Invoice Amount. Total amount of the invoice. If you enter a Credit invoice, the amount must be a negative number. If you enter a Standard invoice, the amount must be zero or greater. Invoice Curr. (LOV) The currency of the invoice. The Quick Invoices window defaults the supplier site currency. You can override this value. After you import your invoice, you cannot change the currency. You can use the Invoice Actions window to cancel the invoice, then re-enter the invoice with the correct currency. If you enter a currency other than your functional currency, then you must provide exchange rate information. Invoice Date. Date on the invoice. If you do not enter a value, then import uses the system date at the time of import as the default. Payables may use the Invoice Date as the Terms Date and GL Date for an invoice, depending on your system setup. If your GL Date Basis is Invoice Date, then the Invoice Date must be in an open or future period. Invoice Num. The invoice number provided by the supplier on the invoice. This value must be unique for the supplier. If you do not enter a value, then during import, Payables uses the system date at the time of import as a default. If you enter more than one invoice for a supplier, you must enter a unique value for the invoice number. Invoice Type. (LOV) The type of invoice. Standard and Credit are the only invoice types you can enter in this window. If you do not enter a value for this field then a value will be assigned during import based on the amount of the invoice.
Liability Account. (LOV) Account for the invoice liability. Payables uses this account when you create accounting entries for your invoices if you use accrual basis accounting. Payables credits an amount equal to the sum of your invoice distributions. You cannot enter more than one Liability account for an invoice. The Quick Invoices window provides the supplier site Liability account as a default. You can override this value. Payables defaults this value to invoice distributions during import. Pay Alone. A Pay Alone invoice is paid with its own payment document without including other invoices for the supplier. The Quick Invoices window defaults to each record the Pay Alone value for the supplier site. You can override this value. Payment Curr. (LOV) If the Invoice Currency is not a fixed-rate currency, then the Payment Currency will be the same as the Invoice Currency and you cannot enter a value in this field. If the payment currency is a fixed-rate currency, such as euro or another EMU currency, you can change it to an associated currency. For fixed-rate currencies, the payment currency value defaults from the supplier site. If the supplier site has no default payment currency, the value defaults from the Invoice Currency. If you change the Invoice Currency then the value for Payment Currency will change to the value for Invoice Currency. Pay Group. (LOV) Use Pay Group to group in a payment batch invoices from multiple suppliers. The Quick Invoices window defaults the supplier site's Pay Group. You can override this value. Payment Method. (LOV) The payment method you use to pay the supplier site. The Quick Invoices window defaults the supplier site's Payment Method to this field. You can override this value. During import Payables defaults this Payment Method to all scheduled payments of the invoice. Payment Rate. If you are making a payment in a different currency than the invoice, and both currencies are associated fixed-rate currencies, Payables displays the fixed cross rate. You cannot update this value in this window. Payment Rate Date. The date the Payment Rate is effective. If the payment currency and invoice currency are associated fixed-rate currencies, then when you enter the Invoice Date, Payables enters the invoice date value as the payment rate date. Payment Rate Type. If the Payment Currency is different from the Invoice Currency and both are fixed-rate currencies, Payables displays EMU Fixed. PO Number. (LOV) If you are matching the entire invoice record to a purchase order, then enter the number of a valid, open purchase order that has not been final matched. The purchase order must be for the supplier site you entered. The list of values displays all available purchase orders for the supplier site you specified. If you match to a purchase order, then during import Payables uses purchase order information to create invoice distributions. If you want to override the account default that the purchase order provides, then see: Account Overlay in Payables Interface Import, Oracle Payables Reference Guide. If you do not enter a value for PO Number at the header, then you can still enter a PO Number for any line. However, if you want the invoice to use terms from a purchase order, you must enter the purchase order here. Payables uses terms from the purchase order you identify in this field if you match to a purchase order and do not enter a value for terms on the invoice record. Prepay Apply Amt. If you are applying prepayments, the maximum currency amount of the prepayments you want to apply to an invoice. If you specify a prepayment number and leave this field blank, then Payables enters the unapplied prepayment amount up to the amount of the invoice. Payables ensures that the prepayment amount does not exceed the invoice amount. Note: The prepayment is not actually applied until the import process. Therefore, to prevent overapplication of an prepayment, you cannot select a prepayment number that has been applied to another invoice record that has not yet been imported. Prepayment Distribution. (LOV) Distribution number of a specific Item distribution on the specified prepayment that you want to apply. Leave this field blank to apply all available prepayment Item distributions, starting with the lowest distribution number first, up to the amount of the invoice. This field is enabled after you enter a valid value for the Prepayment Number field. Prepayment GL Date. Accounting date for the application of the prepayment. This will be the GL date on the new Prepayment type distribution on the imported invoice. Prepayment on Invoice. (check box). Enable this check box if you are entering an invoice that references a prepayment that the supplier received, and the invoice amount is reduced by the amount of the prepayment and any associated tax. See: Prepayment Number. (LOV) Invoice number of a specific prepayment you want to apply. Leave this field blank if you do not want prepayments applied to the invoice. Requester. Person who requested the goods or services on the invoice. If you use Invoice Approval Workflow, you can define rules that use this value to generate a hierarchical list of approvers for the invoice. Site. (LOV) The supplier site address to which you want to remit payment. This site must be a pay site. If you print checks, Payables prints this address on the check. The Quick Invoices window defaults this value if you enter a supplier with only one active pay site. Supplier. (LOV) Supplier Name. You must specify a valid supplier in either the Supplier field or the Supplier Number field. Supplier Num. (LOV) Supplier number. You must specify a valid supplier in either the Supplier field or the Supplier Number field. Remit to Supplier Name. Enter or accept the Remit to Supplier Name if you want to pay to the Third Party. This field is mandatory and enable you to record the Third Party supplier to whom the payments are to be made. Remit to Supplier Site. Enter or accept the Remit to Supplier Site if you want to pay to the Third Party. This field is mandatory and enable you to record the Third Party supplier to whom the payments are to be made. The Remit To Supplier Site list of values displays only those supplier sites that are attached to the selected Remit To Supplier Name for which the relationship is defined and is active as on Invoice date. Terms. (LOV) Payment terms. This value defaults from the supplier site. You can overwrite that value. If you're matching to a purchase order and want to use the purchase order's terms, then make sure this field is blank. The import process uses the invoice amount, payment terms, and terms date to create one or more scheduled payments for each invoice record. You define terms in the Payment Terms window. See also: Payment Terms, Oracle Payables Implementation Guide. Transaction Code. USSGL Transaction Code. The import program imports any USSGL information that you enter in this field. Voucher Num. Manual voucher number assigned to the invoice for internal tracking purposes. This value will be validated for uniqueness. If you use automatic sequential numbering (your Sequential Numbering profile option is set to "Partial" or "Always"), then during import, Payables ignores any value you enter here. Do not enter a value with more than 9 digits or Payables will have problems processing the invoice. Withholding Tax Group. (LOV) Enter a value if you want to apply multiple withholding taxes to this invoice. This value defaults from the supplier site. You can also enter a value for Withholding Tax Group at the invoice line level. Any value you enter in the Withholding Tax Group field for an invoice line will override any value you enter here in the header. Workflow Status. If you use Oracle Open Interface Workflow, this field shows you the workflow status of the invoice record.
[] (Descriptive Flexfield). You use descriptive flexfields to record custom data. The flexfield you use in this window will provide values to the invoice descriptive flexfield in Payables. Therefore, the structure of the information you enter in these columns (datatypes, value sets) must match the structure of the descriptive flexfield segments you have defined in the Invoices window or you will experience validation problems when you try to access this information in the Invoice Workbench. [ ] (Localization Descriptive Flexfield). If you are using a localization, you must enter appropriate values in this flexfield or the invoice will be rejected. For more information see your localization guide. Display Only RegionInvoice Total. Payables displays the value you entered for Invoice Amount so you can compare it to the line total. Lines Total. The sum of the amounts in the Lines region for this invoice record. The sum of the invoice lines does not need to equal the Invoice Total when you submit import. For example, you may have a $10 tax line with a VAT tax that has an offsetting tax. The tax amount will be zero after the invoice record is imported and validated, but the lines will not equal the invoice total when you save the record in the Quick Invoices. Source. Source identifier used by Payables Open Interface Import. The value should be either Quick Invoices, or a source name you defined in the Oracle Payables Lookups window. Quick Invoices Batch. Name of the Quick Invoices Batch that you assigned in the Quick Invoices Identification window. Request ID. If you have submitted Payables Open Interface Import for this record, then the system displays the concurrent request ID. In the Requests window, you can use the request ID to query the status and results of the import process. Status. The Payables Open Interface Import status of the invoice record.
Quick Invoices Lines RegionUse this region to enter line information for an invoice. Enter at least one invoice line per invoice. The following fields are required in this region: Line Type and Amount. When Payables imports the invoice record it creates one or more distributions for the invoice based on the information you enter in this region. Payables uses distributions to create accounting entries for invoices. An invoice can have an unlimited number of distributions. You can create distributions by entering lines, or you can create them automatically by using Distribution Sets, proration of charges, or purchase order matching. Tip: Customize your Quick Invoices folder window to hide fields for features you don't use. This will prevent you from entering values that could cause rejection of the invoice during import. 1099 Type. Income tax type, for 1099 reporting purposes. If you do not use a Distribution Set to create invoice distributions, then Payables uses the supplier site's income tax type as the default value. If you use a Distribution Set to create invoice distributions, then Payables uses the default income tax type from the Distribution Set as the default value. You can enter or adjust this field regardless of whether the supplier is defined as a 1099 supplier. Payables uses this information when you submit the 1099 Payments Report and the 1099 Form Reports. See also: . You can update this field of the imported invoice in the Distributions window even after you have posted a distribution. You can use the Update Income Tax Details Utility to make adjustments to many distributions at once. See: . Account. (LOV) This value is the complete account (including balancing segment, cost center, and account) to charge when you create accounting entries for this distribution. Usually an expense or asset account. Do not enter a value for account if you provide account information by using any of the following: Distribution Set, proration, matching to a purchase order, or providing Projects information. If you have defined a Distribution Set at the supplier site level and you do not enter account information here, then the Distribution Set account information from the supplier site will default to the invoice during import. If you have Oracle Projects installed and you enter Projects information, do not enter a value here. The Quick Invoices window will build the account for you after you save the invoice record. Note that if you enter values for any of the following, during import they will override one or more segments of this account field: Overlay GL Account, Account Segment, Cost Center Segment, Balancing Segment. See: Account Overlay in Payables Open Interface Import, Oracle Payables Reference Guide. Account Segment. If you want import to override the account segment of the account for this line, then enter the overriding value. See: Account Overlay in Payables Open Interface Import, Oracle Payables Reference Guide. Import will reject the invoice record if you use a Skeleton Distribution Set and use the Prorate feature for the same line. Amount. Amount to charge to the general ledger account. If this is a foreign currency invoice, enter the amount in foreign currency and enter exchange rate information. Since this window does not format your amounts according to currency, be sure not to exceed the precision of your currency. For example, if you are entering US dollars, do not enter more than 2 numbers after the decimal. Payables does not support Extended Precision when calculating amounts. Balancing Segment. If you want to override the balancing segment of the account for this line during import, then enter the overriding value. See: Account Overlay in Payables Open Interface Import, Oracle Payables Reference Guide. Cost Center Segment. If you want to override the cost center of the accounting segment of the account for this line during import, then enter the value. See: Account Overlay in Payables Open Interface Import, Oracle Payables Reference Guide. Description. Description of the distribution. If you do not enter a value and you match to a purchase order, then during import, Payables assigns to the invoice the description from the purchase order line. Distribution Set. (LOV) Used to create invoice distributions automatically when invoice is not matched to a purchase order or when you do not want to enter invoice distribution information manually. If you want to use a Distribution Set, you must enter one before you import the invoice record. You can provide account information from only one of the following sources or the invoice will be rejected during import: Distribution Set, purchase order, Account field, allocation of a non-Item type line, Projects information. Import will reject the invoice record if you use a Skeleton Distribution Set and use the Allocate feature for the same line. See: Account Overlay in Payables Open Interface Import, Oracle Payables Reference Guide Final Match. You can enable this option only if the line is matched to a purchase order, and the Allow Final Matching Payables option is enabled. For detailed information, see: . Important: Enable only if you are certain this is a final match to the purchase order. Once you validate a final matched invoice distribution, you cannot update the Final Match check box in the Distributions window. GL Date. Payables uses the GL Date as the accounting date for the invoice. The date must be in an open or future period. During import, Payables looks for a GL Date value to assign to the invoice distribution. Payables assigns a value from the first source it finds, and it searches the following sources in the following order: 1) GL Date on invoice record line, 2) GL Date on invoice record header, 3) GL Date parameter from import submission, 4) GL Date Basis Payables option. The following occurs if the system searches at the GL Date Basis level: If the GL Date Basis option is set to Goods Received/Invoice Date, then Payables uses the Goods Received Date, if it is populated. If not, then Payables uses the Invoice Date. If the GL Date Basis option is set to Goods Received/System Date, then Payables uses the Goods Received Date, if it is populated. If it is not, then Payables uses the system date at time of import. If the Use PO Encumbrance Financials option is enabled, then the date must be in the current encumbrance year. Includes Tax. If the supplier site uses Line or Tax Code level automatic tax calculation, and you are not matching to a purchase order, then you can check this check box to indicate if a distribution amount includes a non-Use type tax (Sales, user-defined, etc.) If you check this check box, then during Invoice Validation of the imported invoice, Payables will use the line amount and Tax Code value to create tax distributions with the appropriate tax codes and tax amounts. Payables then subtracts the calculated tax from the distribution amount. For detailed information on automatic tax calculation, see: . Income Tax Region. (LOV) Income tax region for the distribution. Do not enter a value here unless you also enter a value for 1099 Type, or import will reject the record. Payables orders distributions by income tax region on the 1099 Form reports. If you enable the Combined Filing Program Payables option, 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. If you enable the Use Pay Site Tax Region option in the Payables Options window, the default for this field during import is the supplier site's state. If you choose instead to enter a tax region in the Income Tax Region field in the Payables Options window, the default for this field during import is the tax region you entered. See also: . Line Number. Unique line number for the invoice. If no value is entered, then import will assign numbers during import. Match Option. This option indicates whether you are matching to a purchase order or a receipt. Note that the match option on the purchase order shipment controls whether you can match to receipts or purchase order. Oracle Projects Project (LOV) /Task (LOV) /Expenditure Organization (LOV)/ Expenditure Type (LOV). If Oracle Projects is installed, enter values in these fields to associate an invoice with a project. Note: The values that you enter for Project, Task, and Expenditure Organization correspond to internal IDs in the Payables Open Interface tables. For example, the Project value that you select from the list of values corresponds to the Project ID in the AP_INVOICE_LINES_INTERFACE table. The information you enter creates an account that defaults to the invoice distribution. You can override this project information in the Distributions window, after you import the invoice. Note: If you enter project information, you must enter a value for Task unless you have matched to a purchase order with project information with a null task ID. A purchase order can have a null task ID only if its destination is Inventory or Shop Floor. If the destination is Inventory or Shop Floor, the project information is used by Project Manufacturing. Overlay GL Account. Enter a value if you want to replace any or all segments of the complete account (for example, balancing segment, cost center, and account) for this line. If you enter a value here, it will replace any account created from a Distribution Set, purchase order matching, prorating non-Item type lines, or entering Projects information. You must use the account flexfield structure of your organization. See: Account Overlay in Payables Open Interface Import, Oracle Payables Reference Guide. If you match to a purchase order distribution (or a purchase order shipment with one distinct account), then after you save the record, the Quick Invoices will display the purchase order distribution account in this field. You can overwrite that value and perform the match with the new value you enter. If you are matching, the Payables option Allow Matching Account Override must be enabled. PO Item Description. (LOV) To match to a purchase order line with a unique item description, enter the item description exactly as it appears on the purchase order. If the purchase order has more than one line with the same item description, then the invoice record will be rejected. PO Distribution Number. (LOV) If you want to match an Item type invoice line to a purchase order distribution, then enter the purchase order distribution number. PO Line Number. (LOV) If you want to match an Item type invoice line to a purchase order line, then enter the purchase order line number. PO Number. (LOV) To match an Item type invoice line to a purchase order for the same supplier site, enter the purchase order number. You must specify the PO Number if you want to match in greater detail to a purchase order shipment, line, or distribution. If you are matching to a receipt, you can enter a value here to limit the list of values for the receipt. If you enter both PO Number and Receipt Number, then the match will be to the receipt only. Note that the match option on the purchase order shipment controls whether you can match to receipts or purchase order. PO Shipment Num. (LOV) If you want to match an Item type invoice line to a purchase order shipment, then enter the purchase order shipment number. PO Unit of Measure. (LOV) If you are matching an Item type invoice line to a purchase order item, you can specify the item by entering a unit of measure. For example, each, square feet, or months. This value is not required, but may be helpful during purchase order matching. PO Unit Price. If you are matching an Item type invoice line to a purchase order distribution, then enter a value for either PO Unit Price or Quantity Invoiced. If you are performing a price correction, enter the incremental amount of the price correction in this field. During import, Payables calculates the value you do not enter (Quantity Invoiced x Unit Price = Match Amount). Price Correction. You use a price correction when a supplier sends you an invoice for a change in unit price. You can record a price correction when you match a Credit or Standard invoice to a purchase order. Adjust the invoiced unit price of a previously matched purchase order shipment by matching a price correction to it. To record a price increase, match a Standard invoice record to a purchase order shipment or distribution. To record a price decrease, match a Credit invoice record to a purchase order shipment or distribution. Check the price correction check box, and enter the Unit Price for the incremental amount of the price correction. Enter either Quantity Invoiced or Match Amount. Payables will calculate the remaining field (Quantity Invoiced x Unit Price = Match Amount). Tip: We strongly recommend that you use the Invoice Workbench, rather than the Quick Invoices window to enter price corrections in this version of Payables. Entering in the Invoice Workbench allows you to specify more detailed information, so Invoice Validation can properly validate that the price is within the appropriate tolerance. Projects Quantity. Enter a value if you have installed Oracle Projects and you want to record a project quantity for the distributions that import creates from this line. Prorate Across. Enable this check box to prorate tax, freight, or miscellaneous charges across lines with the same Prorate Group. Or, if you do not assign a Prorate Group, then Payables will prorate the cost to all lines during import. Payables prorates only Tax, Freight, or Miscellaneous lines. Do not enable this check box if the line is purchase order matched or if you are automatically calculating tax. For other line in the prorate group, import creates a charge distribution and records the allocation. The new charge distribution has the same GL account as the line to which you allocate it. After Payables creates the distribution you can update the account any time before the invoice is accounted. Prorate Group. If you want to prorate a charge to a group of lines, enter the same value to identify the Item lines in the group and the non-Item line you are allocating. For example, if you want to allocate tax to two Item lines, then enter the same line group number for the two Item lines and the Tax line. If you do not assign Prorate Groups, and you use the Prorate Across check box for a non-Item line, then Payables will allocate the cost to all lines during import. Quantity Invoiced. Quantity Billed value you enter during a purchase order match. If you are matching an Item type line to a purchase order distribution, then enter a value for either Quantity Invoiced or Unit Price. During import, Payables calculates the value you do not enter (Quantity Invoiced x PO Unit Price = Amount). If the distribution is not matched to a purchase order distribution, Payables leaves the field blank. If this is a price correction, this value will be zero. Receipt Num. (LOV) If you want to match the line to a receipt, then enter the receipt number. The list of values for this field can be limited by values you enter in other fields such as PO Number. The list of values for this field gives additional information, such as the packing slip number to help you select the correct line. Note that the Quantity in the list of values is the original quantity on the receipt, not the adjusted quantity. Receipt Line Number. If you want to match the line to a receipt, then enter a Receipt Number and receipt line number. To ensure that you are matching to the correct receipt, you should also enter: PO Number, PO Line Number, and PO Shipment Number. Recoverable. This check box indicates that the amount of a tax line is recoverable. Recovery Rate. If you record recoverable tax, this is the rate at which tax is recoverable for this line. Ship-To Location. If you want to match an Item type invoice line to a purchase order shipment, enter a value if exactly one shipment on the purchase order has the Ship-To location you specify. Or you can match to a purchase order shipment by entering a value for PO Shipment Num. Statistical Quantity. Statistical quantity based on the unit of measure. For example, if your unit of measure is barrels, you can enter the number of barrels here. Track as Asset. If you enable this check box, Payables transfers this distribution to Oracle Assets when you submit the Create Mass Additions for Oracle Assets Program. You can then create assets in Oracle Assets from the imported distribution information. If the distribution has an asset account, Payables enables this option during import and you cannot adjust it. If the account is an expense account, Payables does not enable the check box, but you can enable it in at anytime before the invoice accounting entries are transferred to general ledger. For more information see: . Transaction Code. USSGL Transaction Code. Payables Open Interface Import imports any USSGL information that you load into the interface tables and assigns the information to the invoices it creates. Type. (LOV) Line Type is a required field. Valid line type values in this window are: Item, Tax, Freight, or Miscellaneous. Payables uses Type to differentiate between item, tax, freight, and miscellaneous charges. You can include purchase order information for a line only if the type is Item. During import, Payables may create more than one distribution for each line and the distribution types may not match the line type you enter here. For example, if you enter a tax inclusive item line, during import, Payables will create an Item and a Tax distribution.
Withholding Tax Group. (LOV) Withholding Tax Group for the line. Enter a value if you want to apply multiple withholding taxes to this invoice line. If you do not enter a value, then during import, Payables will default the invoice header withholding tax group, if you entered one. For more information, see: Withholding Tax Groups, Oracle Payables Implementation Guide. [ ] (Descriptive Flexfield). You use descriptive flexfields to record custom data. The flexfield you use in this window will provide values to the invoice descriptive flexfield in Payables. Therefore, the structure of the information you enter in these columns (datatypes, value sets) must match the structure of the Descriptive Flexfield segments you have defined in the Invoices window or you will experience validation problems when you try to access this information in the Invoice Workbench. [ ] (Localization Descriptive Flexfield). If you are using a localization, you must enter appropriate values in this flexfield or the invoice will be rejected. For more information see your localization guide. Display Only RegionButtonsRejections. Choose this button to navigate to the Quick Invoices Rejections window. This window displays for the current record the reason that the record was rejected during its last submission to Payables Open Interface Import. This is the same rejection that appears on the Payables Open Interface Import Report. For more information on the rejection, see: . Create Invoices. Choose this button to open the Create Invoices window. You can use this window to submit import which will validate your invoice records and create invoices from them. For more information see: . Save and Next. Save the data and move to the next invoice. Related Topics Distribution Sets, Oracle Payables Implementation Guide Payables Open Interface ImportYou can use the Payables Open Interface Import program to create Payables invoices from invoice data in the Payables Open Interface tables. You can populate the Payables Open Interface tables with invoice data from the following sources:
Note: Use Expense Report Export to export expense report data from Oracle Internet Expenses into Payables. See: . This section includes the following topics: Related Topics Payables Open Interface Tables, Oracle Payables Reference Guide Submitting the Payables Open Interface Import ProgramUse Payables Open Interface Import to create invoices from invoice records in the Payables Open Interface tables. During the import, the program checks the supplier site to determine which invoice tolerance template to use when checking invoices with a source of Oracle e-Commerce Gateway. If no value for the Invoice Tolerances field is found at the site level then tolerance checking is not performed. Otherwise, the tolerances defined at the site level at import time will be used. The import program checks the specific invoice tolerance template stored in the Invoice Tolerances window to determine if the invoice falls within the defined tolerances. Payables validates invoice records and rejects invoice records that have insufficient or invalid data. Successfully imported invoices have distributions and scheduled payments, and can be queried, modified and validated in the Invoice Workbench. Tip: Set up your system to submit Payables Open Interface Import after each business day so you don't use system resources while users are online. For a text description of the previous graphic, see: . Importing e-Commerce Gateway Invoice RecordsIf you are importing invoices through the Oracle e-Commerce Gateway, you can submit the e-Commerce Invoice Inbound set. This program set submits both the e-Commerce Gateway Program, which populates the Payables Open Interface Tables with the electronic invoice records your supplier provides, and the Payables Open Interface Import Program, which transfers the invoice data from the interface tables into the invoice tables in Payables. To submit the e-Commerce Invoice Inbound transaction, see: Running the e-Commerce Invoice Inbound Program (Oracle e-Commerce Gateway User's Guide). The discussion below describes how you can submit the Payables Open Interface Program separately. You may need to submit Payables Open Interface Import separately if you have had rejections that you have fixed and want to import corrected e-Commerce invoice records. Payables supports the outbound application advice (824/APERAK) for e-Commerce invoices. When you submit the Payables Open Interface Outbound Advice, Payables creates a notification for invoices that were successfully imported and those that failed import, and you can send this notification to your e-Commerce trading partners via the e-Commerce Gateway. Importing XML Invoice RecordsIf your supplier is transmitting invoices through the XML Gateway, you can submit the P2P Inbound Process Request set. This request set populates the Payables Open Interface Tables with electronic invoice records from your supplier. It then submits the Payables Open Interface Import Program that transfers invoice data from the interface tables into the invoice tables in Payables. Important: The Payables Open Interface Import Program needs to be run for each operating unit if you have a multi-org implementation. The request set then submits the Payables Validation and Accounting processes and automatically generates an output file of supplier invoice rejections that is sent to a Confirmation User Email id that is specified in the Define Bank window. This output file includes the number of invoices that had holds applied during Invoice Validation and any invoices that are not included in the accounting process. You need to resolve all issues and then validate any corrected invoices before they can be selected for payment. Additionally, data problems that your system administrator needs to address will be automatically sent to an AP Administrator Email id that is defined in the Define Bank window. You may need to submit Payables Open Interface Import separately if you have had rejections that you have fixed and want to import corrected XML Gateway invoice records. Importing Quick Invoices RecordsWhen you enter invoice records in the Quick Invoices window, you can choose the Create Invoices button to submit the Payables Open Interface Import program from the Create Invoices window. Alternatively, you can submit the import program from the Submit Request window, as described below. Prerequisites
Additional Prerequisites for e-Commerce (810/INVOIC) Invoices
Additional Prerequisites for XML Gateway Invoices
Additional Prerequisites for Invoices You Transfer Using SQL*Loader
Additional Prerequisites for Invoices You Transfer Using the Create Procurement Card Issuer Invoice Additional Prerequisites for Invoices You Transfer from Oracle Property Manager
Additional Prerequisites for Invoices You Transfer from Oracle Assets
To submit Payables Open Interface Import:
Related Topics Payables Options, Oracle Payables Implementation Guide Defining Financials Options, Oracle Payables Implementation Guide Account Overlay in Payables Open Interface Import, Oracle Payables Reference Guide Payables Open Interface Import ParametersSource. Choose the source of the invoices from the list of values.
Group. To limit the import to invoices with a particular Group ID, enter the Group ID. The Group must exactly match the GROUP_ID in the Payables Open Interface tables. You can import data in concurrent processes for the same source by specifying a unique Group for each request. This reduces the processing time of your import. Payables Open Interface Import imports data with the source and group combination you specify. If you are importing invoice records from the Quick Invoices window, enter the Quick Invoices Batch name. If you did not enter a value for Quick Invoices Batch name during entry, then no value was assigned to Quick Invoices Batch Name (GROUP_ID). If you do not specify a Group during import, Payables imports invoice records for all Quick Invoices batches that match the Source name you specify. Invoice Batch Name. You can enter a batch name only if you have enabled the AP: Use Invoice Batch Controls profile option. Payables groups the invoices created from the invoice records you import and creates an invoice batch with the batch name you enter. If you use a batch name and some invoices are rejected during the import process, you can import the corrected invoices into the same batch if you enter the exact Invoice Batch Name during the subsequent import. If you are importing invoice records that you entered in the Quick Invoices window, you may want to enter the Quick Invoices Batch name for consistency. If the AP: Use Invoice Batch Controls profile option is enabled and if you provide no value for this parameter then the system provides a value for you. The value the system provides is the concatenation of the Source and a unique sequential number. For example, ERS: 1234. Hold Name. If you want to apply a hold to all invoices that the invoice process creates, enter an invoice hold name. You can define your own holds in the Invoice Hold and Release Names window. Hold Reason. Payables displays the invoice hold reason description. GL Date: To assign a GL Date to any invoice in the batch that does not already have a GL Date at the line or header level, enter a value for the GL Date parameter. If you do not enter a value here, or at the line or header level, then during import the system assigns a GL Date based on the GL Date Basis Payables option. Important: If you are using encumbrance accounting, you must enter a GL Date in a period that is within the latest open encumbrance year. See also: . Purge. Enter Yes if you want Payables to delete from the Payables Open Interface tables all successfully imported invoice records that match the Source and Group ID of this import. Payables does not delete any invoice data for which it has not yet created invoices. If you want to purge later, you can use the Payables Open Interface Purge Program. Summarize Report. If you want to summarize the audit portion of the Payables Open Interface Import Report, enter Yes. If you do not select this option and you are importing a large number of invoice records, this report could be very long. Related Topics Payables Open Interface Import TroubleshootingYou may experience two types of errors while trying to import invoices: incorrect data or program failure. Incorrect DataThe Payables Open Interface Import Report lists invoices that were not imported correctly. If a problem exists at the invoice level, the invoice is rejected without further validation. Examples of these fatal errors are:
If the invoice level information is correct, Payables validates all values at the line level, and the rejections report lists all line level problems. If a distribution is rejected, the whole invoice is rejected. An example of this type of error is:
Correct the data in one of the following ways:
Program ErrorsIf a failure occurs in the e-Commerce Gateway Program or the Payables Open Interface Import program, you can query the program in the Requests window. Read about errors in the log file. Payables Open Interface Import commits in cycles of 1000. For example, if an error stops the import program when it is validating the 350th invoice record, the system will have already committed the first 300 invoices. Related Topics Open Interface Invoices WindowUse this window to update records in the Payables Open Interface tables. Note that this window performs no validation. The field names in this window correspond to the table columns. For detailed descriptions of the columns in the interface, see: Payables Open Interface Tables, Oracle Payables Reference Guide. The Open Interface Invoices window now contains four additional fields, Remit To Supplier Name, Remit To Supplier ID, Remit To Supplier Site Code, and Remit To Supplier Site ID to use with Third Party payment. The Open Interface Invoice window includes Original Invoice Amount and Dispute Reason options for Dispute Resolution functionality. These fields are hidden. Use Show Fields folder option to display these fields. Changes to the Payables Open Interface Import Program Payables Open Interface Import API imports Invoices from external sources including invoices from OTM. Two new fields, Original Invoice Amount and Dispute Reason, are added. The API for Payables Open Interface Import is enhanced to capture and process the values introduced for the Dispute Resolution functionality. Important: We recommend that you use the Quick Invoices window to update any invoice records you entered in the Quick Invoices window. Related Topics Payables Open Interface Purge ProgramUse the Payables Open Interface Purge Program after you submit the Payables Open Interface Import program. This program purges records from the Payables Open Interface tables (AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE). Purge only invoices that you successfully imported, or enter Yes for Purge All to purge all records in the table that match the Source and Group program parameters you enter. Report SubmissionYou submit this program from the Submit Request window. See: . Selected Report ParametersSource. Choose the source of the invoices you want to purge from the list of values. Use e-Commerce Gateway, Credit Cards, Quick Invoices, Oracle Property Manager, or a Source type lookup you defined in the Oracle Payables Lookups window. The source must exactly match the Source in the Payables Open Interface tables. This parameter is required. Group. (Optional) To limit the purge to invoices with a particular group, enter the GROUP_ID. If you entered the invoices in the Quick Invoices window, enter the Quick Invoices Batch name. The Group must exactly match the value in the GROUP_ID column in the Payables Open Interface tables. You can purge data in concurrent processes for the same source by specifying a unique Group for each request. This reduces purge process time. The Payables Open Interface Purge Program purges data with the Source and Group combination you specify. Purge All. Enter Yes to purge all records in the Payables Open Interface tables that match the Source and Group you enter above. These records include successfully imported records, records rejected during import, and records that you have not tried to import yet. Enter No to purge only records that have been successfully imported. Related Topics Payables Open Interface Outbound AdviceThis program creates notification data about e-Commerce invoices processed during Payables Open Interface Import. If you choose either the Rejected or All parameter, the advice includes the same exceptions that are identified on the Payables . You can send this notification to your supplier via the e-Commerce Gateway. See: Outbound Application Advice (824/APERAK) (Oracle e-Commerce Gateway Implementation Manual). Program SubmissionYou submit this program from the Submit Request window. See: . Selected Program ParametersSource. Choose e-Commerce Gateway because you are creating a notification about e-Commerce Gateway transactions. Group. (Optional) Choose the Group of the invoices for which you want to submit this report. Status.
Related Topics Payables Open Interface Import ReportUse this report to review detailed information for each invoice Payables imports during Payables Open Interface Import. The report has two sections, the Payables Open Interface Audit Report and the Payables Open Interface Rejections report. The Audit section lists the invoices that Payables has successfully imported. If you choose to summarize the report when you import, then the Audit section will list only the number of invoices selected for import, and the number of successfully imported invoices. The Rejections section lists invoices that Payables was not able to import and lists the rejection reasons. If the import program finds a reason to reject the invoice record at the invoice header level, it will record that reason on the report and will not process the invoice record further. Therefore, even if the invoice record has more than one error, the report may list only the first error the import program finds. Report SubmissionPayables automatically generates this report when you submit the Payables Open Interface Import process. See: . Report HeadingsSource. The source of the invoices you entered as a parameter when you submitted the report.
Group/Invoice Batch Name/GL Date/Purge/Summarize Report. Payables displays the values you entered for these parameters when you submitted Payables Open Interface Import. Batch Name. Payables displays the value you entered when you submitted Payables Open Interface Import. If you didn't enter a value and you use batch control then the system assigns a value for you by concatenating the source with a unique sequential number. For example, ERS: 1234. Hold Name. If you entered a Hold Name parameter when you submitted Open Interface Import, Payables prints the Hold that was applied to the invoices. Hold Reason. If you entered a Hold Name parameter when you submitted Open Interface Import, Payables prints the Hold Reason for the Hold. Payables Open Interface Audit Report -- Selected Report HeadingsInvoice Number/Date/Currency/Amount. Number, date, currency, and amount of the invoice Payables created during Payables Open Interface Import. Dist Number. Number assigned to the invoice distribution. Dist Amount. Amount of the invoice distribution. Accounting Date. GL Date for the invoice. Total Invoices Imported. Total number of invoices that the Payables Open Interface Import Program imported. Total Functional Currency Invoice Amount. Sum of all invoices displayed in your functional currency. Payables Open Interface Rejections Report -- Selected Report HeadingsInvoice Number. Payables prints the number of the invoice that could not be imported. Invoice Level/Line Number. The report prints Invoice if the problem is at the invoice level. If the problem is with a line of the invoice, the report prints the line number. Total Invoices Rejected. Total number of invoices that the Payables Open Interface Import Program rejected. Reason/Description. The report lists the reason the invoice could not be imported and prints a brief explanation of the problem.
Related Topics Financials Options, Oracle Payables Implementation Guide Payables Options, Oracle Payables Implementation Guide Voucher Numbers, Oracle Payables Implementation Guide Defining Ledgers, Oracle General Ledger Implementation Guide Site Locations, Oracle Human Resources User's Guide Payment RequestsPayables 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. Using payment requests you can:
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:
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. A payment request must be paid in full. You cannot partially pay a payment request and then create a debit memo to write off the remaining, which you can do with other types of invoices. Once you enter a payment request, you cannot delete payment request or update payment request fields. Reporting on Payment RequestsUse the following reports to view information about your payment requests: Setting Up Payment RequestsThere 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
Oracle Payments
Oracle Payables
Oracle Approvals Management
Self Service InvoicesOracle Payables integrates with Oracle iSupplier Portal to enable suppliers to create, submit, and view self service invoices. Suppliers with an iSupplier Portal account can create invoices for:
Suppliers can also use iSupplier Portal to enter credit memos against a fully billed purchase order. See: Submitting Invoices, Oracle iSupplier Portal User Guide. Depending on the supplier setup, suppliers can use iSupplier Portal to view self service invoices, including any retainage and recoupment information for Contract Financing Invoices. See: Viewing Invoice Information, Oracle iSupplier User Guide. In addition, iSupplier Portal also allows suppliers to request advances. Suppliers can only request advances if the advances were pre-approved on the purchase order. Even if you don't implement Oracle iSupplier Portal, you can also allow internal users to enter self service invoices using the Invoice Actions page. Entering Self Service Invoices Matched to Purchase OrdersTo enter a self service invoice that is matched to a purchase order, enter the following information:
After you submit the invoice, it is considered a liability and can be updated and validated in Payables. For complete instructions on how to enter self service invoices, see: Submitting Invoices, Oracle iSupplier Portal User Guide Entering Self Service Invoices Matched to ReceiptThe process for entering self service invoices that are matched to receipt is the same as entering self service invoices that are matched to purchase orders; however, if the Invoice Match Option for the shipment is Receipt, then you will only be able to enter an invoice for the shipments that have been received. For example, if you ordered 50 items, but have received only 35 items, then you will only be able to create an invoice for the 35 items you have received. Entering Self Service Invoices Not Matched to a Purchase OrderIf you are entering a self service invoice that is not matched to a purchase order, that invoice must be approved using the Invoice Approval Workflow. When you enter self service invoices that are not matched to a purchase order, follow the same steps for entering an invoice that is matched to a purchase order, but, optionally, enter a Requestor. The Requestor is the person who may be responsible for approving the invoice in Payables. Once you submit the invoice, it is entered in Payables as a “Standard Invoice Request”. Payables automatically initiates the Invoice Approvals Workflow even if you set the Require Validation Before Approval Payables Option to No. During the workflow, the requestor and other approvers can enter in accounts and distribution amounts. The requestor and approvers can approve or reject the invoice, or they can request that the supplier enter into negotiation. See: . Self service invoices that are not matched to a purchase order not considered a liability and cannot be updated in Payables until they are approved. Once the invoice is approved, the invoice type changes from Standard Invoice Request to Standard Invoice and you can update the invoice in Payables. Entering Self Service Invoices - Internal UserTo grant internal users access to the Invoice Actions page to enter self service invoices, grant the user the Payables Request responsibility. You do not need to implement iSupplier Portal to grant this responsibility to users. Users with the Payables Request responsibility can only create invoices in the Invoice Actions page. In addition, the internal user will only have access to the suppliers that are part of the Organization that the internal user belongs to. For example, if the user is in the North American organization, he will only have access to suppliers assigned to that organization, and not to suppliers assigned to other organizations such as Europe or Africa. Flexfields on Self Service InvoicesYour system administrator can set up descriptive flexfields to capture any additional information your enterprise needs for invoice processing. Setting Up Self Service InvoicesPrerequisites
To set up self service invoices:
Special Issues for Self Service Invoices
Related Topics ValidationBefore you can pay or create accounting entries for any invoice, the Invoice Validation process must validate the invoice. Invoice Validation checks the matching, tax, period status, exchange rate, and distribution information for invoices you enter. It checks the supplier site to determine which invoice tolerance template to use. The Matching Payables Options tolerances take effect if there are no tolerances templates associated to each individual supplier site. If there are no tolerances templates associated to each individual supplier site, then the Matching Payables Options tolerances take effect. 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. Authorized users can always correct an invoice, even if you have validated, approved, paid, or created accounting entries for the invoice. See also: . 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. 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. You can submit an invoice for validation in one of the following ways: 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, see . Validation ExampleFor 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. Related Topics Payables Options, Oracle Payables Implementation Guide Using Oracle Alert for Exception Reporting, Oracle Payables Implementation Guide Submitting Online Invoice Validation for InvoicesPrerequisite
To submit online Invoice Validation for invoices:
Submitting Online Invoice Validation for Invoice BatchesPrerequisite
To submit online Invoice Validation for invoice batches:
Related Topics Selecting Multiple Records, Oracle E-Business Suite User's Guide Invoice Validation ProgramThe Invoice Validation process checks the matching tax, period status, exchange rate, and distribution information for invoices you enter and automatically applies holds to exception invoices. If an invoice has a hold, you can either manually release the hold (if allowable) or correct the exception that caused Invoice Validation to apply the hold and then resubmit Invoice Validation. You can schedule regular submission of the Invoice Validation program when you define your submission options for the Invoice Validation program in the Submit Request window. You can specify the intervals in which you want to submit Invoice Validation, and Payables will submit Invoice Validation using the parameters that you specify up until the End Resubmission date you specify. See also: . Invoice Validation Program ParametersOption.
Invoice Batch Name. Invoice Validation reviews invoices that are in the invoice batch you select. You can enter a value in this field only if you have enabled the AP: Use Batch Controls profile option. See Profile Options in Payables, Oracle Payables Implementation Guide. Start/End Invoice Date. If you want Invoice Validation to review invoices that have an invoice date in a range you specify, then enter a date range. Supplier Name. If you want Invoice Validation to review invoices for a specific supplier, then enter the supplier. Pay Group. If you want Invoice Validation to review invoices for a specific pay group, then enter the pay group. Invoice Number. If you want Invoice Validation to review a specific invoice, then enter the invoice number. Entered By. If you want Invoice Validation to review all invoices entered by a specific person, then enter the userid of that person. Related Topics Using Oracle Alert for Exception Reporting, Oracle Payables Implementation Guide Approving InvoicesOracle Payables integrates with Oracle Approvals Management and Oracle Workflow to approve invoices. The Invoice Approval Workflow process uses Oracle Approvals Management and Oracle Workflow to enable you to define business rules to determine who approves invoices and how they will be routed for approval to different approvers. The requester, who initiated the purchase of the line item, is one way of identifying the starting approver in the approval hierarchy using the business rules defined in Oracle Approvals Management. For information on defining rules in AME, refer to the Oracle Approvals Management User Guide. You can define the approval rules in Oracle Approvals Management in one of the following ways:
Approving Invoices at the Line-LevelLine-level approval is the approval of one specific line or set of lines within an invoice, rather than approving the entire document. Approvers have access to the Notification Detail and Interactive Line Details pages to review the invoice details. The pages display only the appropriate level of information for the approver to view. That is, approvers view only the information that they can approve or reject. Furthermore, no additional login or privileges are required for the approver to approve. The self-service login that an approver uses to view the notifications is sufficient to review the invoice information. The system does not initiate document level approval until all lines have been approved. If an approver rejects one line, the remaining line level approvals continue to go through approval. This allows the continuation of the line level approval process while the rejected line is being resolved. However, the system does not continue to document level approvals unless all lines are approved. Note: Invoice approval workflow is required for self service invoices that are not matched to a purchase order. These invoices are entered in Oracle iSupplier Portal or using the Payables Request responsibility. To approve invoices at the line-level:
Approving Invoices at the Document-LevelTo approve invoices at the document-level:
Invoice Approval Workflow OverviewThe Invoice Approval Workflow automates your invoice approval process. Based on rules you define, the workflow determines if an entire invoice (document) or invoice lines need approval, who the approvers are, and in what order approvers should approve payment of the invoice. If you use Invoice Approval Workflow, then every invoice and invoice line that require approval must be approved before you can pay it. Payables indicates that an invoice requires approval by setting the value in the Approval status field in the Invoices window to Required. The approval status is derived from the approval status of the document maintained at the invoice header and the approval status of the invoice lines. For example, if the invoice lines require approval and the document does not, the system sets the approval status for the invoice lines to Required, the approval status for the document to Not Required, and the derived approval status to Required. Note: Line-level approval is only available for self service invoices that are matched to a purchase order. Note: Invoice approval workflow is required for self service invoices that are not matched to a purchase order. These invoices are entered using Oracle iSupplier Portal or the Payables Request responsibility. When you use this feature, all invoices require approval, with the following exceptions. Payables sets the Approval status of the following invoices to Not Required:
You can set up your system to request and receive approval through the approver's e-mail, through the approver's Oracle Workflow Notifications Workflow web page, or both. Approvers can approve or reject the invoice document or invoice line. If both invoice lines and document need to be approved, all the lines of the invoice requiring approval must be approved before the invoice document can be approved. The following scenario assumes that only invoice document approval is required. However, the same process applies to approving invoice lines.
An approver can delegate approval requests, approval reminders, and escalated approval requests. If a notification is delegated to an approver outside the approval chain, the system continues with the original approval chain. For example, the approval chain consists of approvers A > B > C. Approver A delegates to approver X. Once approver X approves the invoice, the system notifies approver B. If the delegated approver does not respond within the time you specify, the system sends a reminder to the delegated approver. If the delegated approver still does not respond, the system rejects the invoice approval and does not escalate it. The Invoice History Approval and Invoice Lines Approval History windows track the approval process, including the delegated approvers' actions. If an approver rejects an invoice or invoice line, you can perform one of the following actions:
For more information on invoice approval actions, see You can review the approval status of an invoice that has started the Invoice Approval Workflow in the following ways: Oracle iSupplier Portal and Payables Request Invoice ApprovalsInvoice approval workflow is required for self service invoices that are not matched to a purchase order. These invoices are created using Oracle iSupplier Portal or the Payables Request responsibility. The system initiates the approval process automatically when the invoices are submitted. At this point, the invoice becomes an invoice request. The approval workflow must be complete before the invoice becomes a standard invoice. Once the invoice becomes a standard invoice, the system validates it and the invoice is susceptible to holds. The requester name on the iSupplier Portal can be the first approver in the approval chain. Invoice Selection CriteriaYou can submit the Invoice Approval Workflow for an invoice either from the Invoice Actions window, or from the Submit Request window. An invoice must meet all of the following criteria to be processed:
Note: The system automatically initiates invoice approval workflow for self service invoices that are not matched to a purchase order and that come from iSupplier Portal or the Payables Request responsibility. Approval and ValidationThe order of the Invoice Validation process and Invoice Approval Workflow Program is based on the Approval Processing Sequence Payables option. Options include:
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. Handling ExceptionsYou are provided with the following actions for handling invoice document and invoice line approvals:
Related Topics Setting Up Invoice Approval Workflow, Oracle Payables Implementation Guide Invoice Approval Workflow ProgramThe Invoice Approval Workflow automates your invoice approval process. Based on rules you define, the workflow determines if an entire invoice or invoices lines need approval, who the approvers are, and in what order approvers should approve payment of the invoice. The workflow then sequentially asks each approver in the approval list to approve invoices online. If both invoice lines and the invoice need to be approved, all the lines of the invoice requiring approval must be approved before the invoice can be approved. For example, you can define rules so invoice lines over $10,000 require CFO approval, and invoices over $100,000 require CEO approval as well. For more information, see: . When you start this program, it updates the approval statuses of the invoice, document, and invoice lines to Initiated. The invoice is then placed in the WF_DEFERRED queue. The next time the Workflow Agent Listener runs, the system initiates Invoice Approval Workflow for the invoice. Prerequisites Before you can use the approval process for an invoice or invoice lines, you must:
Each invoice must meet all selection criteria to be processed by the Invoice Approval Workflow. See: . To submit the Invoice Approval Workflow Program from the Invoices window:
To submit the Invoice Approval Workflow Program using the Submit Request window:
To schedule automatic submission of the Invoice Approval Workflow Program:
Invoice Approval Workflow Program ParametersSupplier Name. If you want to process invoices for a specific supplier, then enter the supplier name. If you do not enter a supplier name, then the program will process eligible invoices for all suppliers. Invoice Number. If you want to process a single invoice, then enter the invoice number. If you do not enter an invoice number, then the program will process all eligible invoices. From/To Invoice Date. If you want the Invoice Approval Workflow to process only invoices with invoice dates in a specified date range, then enter the date range. Related Topics Setting Up Invoice Approval Workflow, Oracle Payables Implementation Guide Invoice Approval HistoryUse the Invoice Approval History window to review the approval progress of any invoice that has started or completed the Invoice Approval Workflow process. This window shows you all the approvers for an invoice in the order that the workflow requests approval from them. You can see who has reviewed the invoice, whether the approver approved or rejected it, the response date, what the invoice amount was when the approver reviewed it, and any comments the approver entered. You also see who the pending approver is and who the planned approvers are. If an invoice is force approved, then you see the username of the person who approved the invoice. You can also review the approval progress of any invoice resubmitted to the Invoice Approval Workflow process. Since this window does not automatically update, you should requery the window to see up-to-date information on an invoice. Future approvers in this window are based on whatever rules are currently defined in Oracle Approvals Management (AME). However, this future approver list can potentially change within the lifecycle of the approval process. For example, an invoice might be rerouted because of an escalation, or planned approvers are removed from the list when an invoice is force approved. If you submit an invoice to the Invoice Approval Workflow that does not require a person to approve it, then the Invoice Approval History window will be blank for that invoice. If an invoice is cancelled it no longer appears in this window, even if it has completed the workflow. If an invoice amount is changed, then a Needs Reapproval record is displayed in the Invoice Approval History window. For details on what invoices are selected for approval and how approvers are selected to approve an invoice, see: . Invoice Lines Approval HistoryUse the Invoice Lines Approval History window to review the progress of any invoice line that has started or completed the Invoice Approval Workflow process. This window displays approval history for all lines within an invoice when you access it through the Invoice Approval History window, or approval history for one specific invoice line when you access it through the Invoices or Invoice Overview windows. The system displays similar approval information for an invoice line in this window as it does for an invoice in the Invoice Approval History window. To review invoice or invoice line approval history information:
Related Topics Invoice Approval History Window ReferenceApproval Context. Displays Invoice Approval or Invoice Line Approval. Action Date. Date that the approval action occurred. For example, the date an approver rejected the invoice. Action. The window shows the action associated with each approver.
Approver. Name of the approver who is assigned to perform an action in response to a request for approval notification or escalation notification. You set up approvers in Oracle Approvals Management (AME). If an invoice was force approved, this field shows the username of the accounts payable processor who force approved the invoice. If an invoice amount was changed, then the Approver field remains blank. Amount Reviewed. Invoice total at the time of approval, rejection, or resubmission. This field serves as an audit trail because the invoice amount can change between approvers. Comments. As an invoice goes through the Invoice Approval Workflow process, the approver can enter comments about the approved or rejected invoice. If the invoice is force approved then this field is blank. If an invoice amount is changed, then this field shows the username of the payables processor who changed the amount. Related Topics Oracle Approvals Management User Guide Taxes on InvoicesOracle Payables integrates with Oracle E-Business Tax, the Oracle Applications tax engine, to provide tax services for invoices. With this integration, E-Business Tax provides a central repository for your invoice tax requirements. E-Business Tax does not provide tax services for Withholding Taxes or 1099 Income Taxes. For information on these taxes see: or . E-Business Tax provides tax services for the following categories of Payables invoices:
Each of these categories maps to an event class in E-Business Tax. E-Business Tax uses your tax setups as well as information from the invoice header and line level (the tax drivers) to determine the applicable taxes, tax statuses, tax rates, taxable basis, calculations, rounding, and tolerance for each invoice. The tax drivers E-Business Tax uses to calculate taxes can differ depending on the category of invoice and the parties involved. For example, for a Standard invoice in the U.S., the Location ID and Place of Supply on the invoice are used to determine the applicable State and County Sales Taxes. For a list of tax drivers, see: . When you enter an invoice and click Calculate Tax, E-Business Tax calculates the following tax amounts. Invoice Header Tax Amounts
Invoice Line Tax Amounts
When you validate an invoice, E-Business Tax recalculates the tax and places any tax-related holds on the invoice. If you update a tax driver on a validated invoice, you must revalidate it. In general, E-Business Tax automatically calculates all applicable tax amounts for invoices except in the following instances:
Setting Up Taxes on InvoicesTo set up taxes for invoices, complete the following setup steps in E-Business Tax:
For more information on setting up taxes, see: Setting Up Taxes in Oracle E-Business Tax, Oracle E-Business Tax User Guide. Entering Manual Tax Lines on InvoicesTo enter manual tax lines on invoices, enable the following manual tax options in E-Business Tax. You can set these options at the Event Class, Configuration Owner, or Tax level. Setting these options at the Event Class level is the most generic; the Configuration Owner is more specific; and the Tax level is the most specific. The more specific settings override the more generic settings.
You can only enter manual tax lines in Payables if:
When you enter a manual tax line, enter an amount in the Tax Control Amount field in the invoice header. E-Business Tax uses the Tax Control Amount to prorate automatically calculated tax amounts. For example, if you enter a Tax Control Amount of $10 and E-Business Tax calculates a total tax amount of $12, then E-Business Tax will prorate the calculated tax amounts so the total tax amount matches the Tax Control Amount you entered. See: Entering a Manual Tax Line, Oracle E-Business Tax User Guide Updating Tax Lines on InvoicesTo update tax lines on invoices, enable the Allow Override for Calculated Tax lines tax option in E-Business Tax. You can set this option at the following levels:
Setting this option at the Event Class level is the most generic setting; Configuration Owner is more specific; and Tax level is the most specific. The more specific settings override the more generic settings. If your suppliers can enter invoices using Oracle iSupplier Portal, then set the Allow Override for Calculated Tax lines tax option for the supplier as well. See: When you enable the this option, you can update the taxes that were calculated by E-Business Tax. For example, you can update the rate or amount. You can also make a tax inclusive or self-assessed. See: . You can only update detailed tax lines if you do not make any changes to tax lines in the Tax Lines Summary window. See: Changing Existing Tax Line Information, Oracle E-Business Tax User Guide. If you override the tax amount and it falls outside of the tolerances specified, then a hold will be placed on the invoice. See: Defining Tax Tolerances, Oracle E-Business Tax User Guide. Excluding Taxes from DiscountsIf you do not want to include taxes in your discounts, then enable the Exclude Tax From Discount Calculation Payables Option. Note that if you enable this option, you cannot set the Discount Distribution Method Payables Option to Prorate. At validation, E-Business Tax calculates the total tax for the invoice. Next, Payables calculates the discountable amount, which is Invoice Amount minus the Total Tax Amount. Then, if the invoice has scheduled payments, Payables updates those payments accordingly. Payment schedules are not updated if there are changes to taxes after validation, because the taxes were not considered when calculating the discount. Payables can only calculate the discountable amount if the invoice is not paid (partially or fully paid). If an invoice is paid, you must manually adjust the payment schedules as required. The only exceptions to this are:
Self-Assessed Taxes on InvoicesTo implement self-assessed taxes on invoices, enable the Set for Self Assessment/Reverse Charge option when you define the tax registration information for the Party Tax Profile for any First Party Legal Entity or First Party Legal Establishment. You can enable this option at the following levels:
Setting the Self Assessment/Reverse Charge option at the Regime level is the most generic; Regime, Tax is more specific; and Regime, Tax, Tax Jurisdiction level is the most specific. Any specific settings override the more generic settings. See: Setting Up Parties for Self Assessment, Oracle E-Business Tax User Guide. You can also enable self assessment for Third Parties. If you enable self-assessed taxes for Third Parties, then the taxes will only be assessed for the supplier at the level specified and not for other suppliers in that tax regime, tax, or jurisdiction. The following example illustrates how E-Business Tax applies self-assessed taxes to invoices. Assume you enter an invoice from a supplier for $1000.00. The supplier did not charge tax on the invoice; however, assume that according to tax rules, as the purchaser you are liable to pay a 5% tax on the item to your tax authority. Standard Invoice1000.000.000.00When you click Calculate Tax or validate the invoice, E-Business Tax uses the tax drivers on the invoice, such as Ship To, Product Type, Primary Intended User, Business Category and Product Fiscal Classification to calculate taxes and determines if any self-assessed tax should be applied. In this case, provided the tax setup allows, a Self-Assessed Tax Amount of $50.00 is applied to the invoice. The Self Assessed Tax Amount field in the Invoice Header is updated to reflect the amount of self-assessed tax due. This field is for reference only; it has no impact on the amount due to the supplier. Note that the Tax Amount for the supplier's invoice is $0.00 and the Invoice Amount is $1000.00. Standard Invoice - Calculated Self-Assessed Tax1000.000.000.0050.00You can view the self-assessed tax details in the Tax Lines Summary window. You can also use the View Accounting report to see how the self-assessed tax amounts are accounted. The following table illustrates the accounting for this self-assessed tax. Accounting - Self-Assessed TaxVision Operations01-580-7740-0000-000Item Expense1000.00Vision Operations01-000-2210-0000-000Liability1000.00Vision Operations01-580-7740-0000-000Self Assessed Tax50.00Vision Operations01-000-2340-0000-000Self Assessed Tax50.00In this accounting example, the credit is the self-assessed tax liability and the debit is the non-recoverable self-assessed tax amount. You cannot use the Distributions window to view self-assessed tax amounts, because they are not represented on the supplier's invoice. Depending on your E-Business Tax setup, you can use the Tax Lines Summary window to update calculated tax lines and mark them as self-assessed or to manually enter self-assessed tax lines. If you update a calculated tax line and mark it as self-assessed, the invoice will be updated to remove the calculated tax line from the invoice line and the distribution details. Also, the Self Assessed Tax Amount field in the invoice header will be updated with the self-assessed tax amount, as shown in the previous example. See: , or . To report on self-assessed taxes, use the following Subledger Accounting reports:
If you are using Offset or Use taxes, see: Setting Up Offset Taxes, Oracle E-Business Tax User Guide. Taxes with Deferred RecoverabilityIn some cases, recoverable taxes can only be accrued and accounted for after the invoice is paid; this is known as deferred recoverability. You can set up taxes with deferred recoverability by enabling the following options at the Tax Regime, Tax, Tax Status, or Tax Rate levels in E-Business Tax. Tax Regime is the most generic level; Tax Rate is the least specific. If you set the options at the Tax Rate level it will override any settings at a more generic level.
The default account for recoverable taxes in Subledger Accounting is Accounts Payable deferred. You can change this account if necessary. The following example illustrates how deferred recoverability works in Payables. Assume you have an invoice for $1100.00, with a total tax amount of $100.00. Assume that the tax is 55% recoverable. Standard Invoice1100.00100.00After the invoice is validated, the recoverable portion of the tax is placed in an interim tax account until the invoice is paid. Accounting - Deferred Recoverable Tax Before Invoice is PaidVision Operations01-580-7740-0000-000Item Expense1100.00Vision Operations01-000-2210-0000-000Liability1100.00Vision Operations01-000-2800-0000-000Recoverable Tax55.00Vision Operations01-000-7740-0000-000Non-Recoverable Tax45.00Once the invoice is paid, the deferred tax amount is credited and debited to deferred recoverable tax. Accounting - Deferred Recoverable Tax After Invoice is PaidVision Operations01-000-2210-0000-000Liability1100.00Vision Operations01-000-1110-0000-000Cash Clearing1100.00Vision Operations01-000-2800-0000-000Deferred Recoverable Tax55.00Vision Operations01-000-2520-0000-000Deferred Recoverable Tax55.00If you were entering a Credit Memo with deferred recoverable taxes, then these entries would be reversed. Accounting - Deferred Recoverable Tax on Credit MemoVision Operations01-000-2210-0000-000Liability1100.00Vision Operations01-000-1110-0000-000Cash Clearing1100.00Vision Operations01-000-2800-0000-000Deferred Recoverable Tax55.00Vision Operations01-000-2520-0000-000Deferred Recoverable Tax55.00Taxes on Prepayment InvoicesPrepayments have the following special considerations related to tax. Taxes can be set up for Prepayments in general, or for specific types of prepayments such as contract financing, advances and automatic and manual prepayment applications. Taxes are not always applied to Prepayments. If you want to apply taxes to Prepayments, enable the Allow Tax Applicability option for the Prepayment Event Class in E-Business Tax. See: Managing Event Class Settings, Oracle E-Business Tax User Guide. Define tax rules to set up specific tax rates for different types of prepayments. For example, to tax Contract Financing prepayments but not Advances, you can create a tax rule which will look specifically for line classes of P2P Advance or P2P Contract Financing to assign a specific tax rate. See: Tax Rules in E-Business Tax, Oracle E-Business Tax User Guide Tax rules also affect how taxes are applied to a prepayment. In particular, it is affected by how you set the Applied Amount Handling option for the tax. You can set this option to either Recalculated or Prorate. The following examples illustrate how the Applied Amount Handling option affects Prepayments. Recalculated Examples If the the Applied Amount Handling option is Recalculated, when a Prepayment is applied to a Standard Invoice the tax is recalculated and, if there is a difference in tax rates no liability remains. Assume that you enter a Prepayment for $240.00, with a 20% Tax Rate. Prepayment Invoice240.000.2040.00After the prepayment is paid, the tax rate changes from 20% to 25%. Next, assume you enter a Standard Invoice for $250.00, the 25% tax rate is automatically applied to the invoice. Standard Invoice250.000.2550.00When you apply the Prepayment to the Standard Invoice, the system applies the Prepayment at the current tax rate, leaving no liability. However, if you view the accounting, the difference of $10.00 is credited to the Tax Difference Account. Accounting - Recalculated PrepaymentVision Operations01-580-7740-0000-000Item Expense200.00Vision Operations01-580-7740-0000-000Non-Recoverable Tax50.00Vision Operations01-000-2210-0000-000Liability250.00Vision Operations01-000-2210-0000-000Liability250.00Vision Operations01-000-1340-0000-000Prepaid Expense240.00Vision Operations01-000-7826-0000-000Tax Difference Account10.00In another example, assume you enter a prepayment of $100.00, with 10% tax and the tax is 60% recoverable. In that case $6.00 is recoverable and $4.00 is non-recoverable. If the tax rate changes to 15%, then the recoverable tax amount is 9.00 and the non-recoverable tax amount is 6.00. A tax different of 2.00 is credited to the tax difference account. The accounting for this scenario is shown in the following table. Accounting - Recalculated PrepaymentVision Operations01-000-1340-0000-000Item Expense100.00Vision Operations01-000-1340-0000-000Non-Recoverable Tax6.00Vision Operations01-000-1340-0000-000Recoverable Tax9.00Vision Operations01-000-2210-0000-000Liability115.00Vision Operations01-000-2210-0000-000Liability115.00Vision Operations01-000-1340-0000-000Prepaid Expense100.00Vision Operations01-000-1340-0000-000Prepaid Expense4.00Vision Operations01-000-1340-0000-000Prepaid Expense9.00Vision Operations01-000-7826-0000-000Tax Difference Account2.00Prorate Example If the Applied Amount Handling option is Prorate, then the tax is applied at the Prepayment rate and the difference between the tax on the Prepayment and the Standard Invoice is a liability. This example uses the same assumptions as the Recalculated example and illustrates what happens when there is a tax rate increase. Prepayment Invoice240.000.2040.00Standard Invoice250.000.2550.00Standard Invoice After Prepayment is Applied - Prorate10.0010.0010.00In this case, the difference between the Prepayment Tax Amount and the Standard Invoice Tax Amount is accounted in the Tax Difference Account and Liability has a credit balanced of $10.00. Accounting - Recalculated PrepaymentVision Operations01-000-1340-0000-000Prepaid Expense240.00Vision Operations01-000-2210-0000-000Liability240.00Vision Operations01-000-2210-0000-000Liability240.00Vision Operations01-000-1110-0000-000Cash Clearing240.00Vision Operations01-580-7740-0000-000Item Expense200.00Vision Operations01-580-7740-0000-000Non-Recoverable Tax50.00Vision Operations01-000-2210-0000-000Liability200.00Vision Operations01-000-2210-0000-000Liability50.00Vision Operations01-000-2210-0000-000Liability250.00Vision Operations01-000-1340-0000-000Prepaid Expense240.00If the Applied Amount Handling option is Prorate, and the tax rate decreases, then when you apply the prepayment to the invoice the result is a credit balance. To avoid a tax decrease from causing a credit balance, unapply the prepayment and enter a lesser prepayment, so the invoice total after the prepayment is applied is 0. If you anticipate that tax decreases will occur and do not want to unapply and reapply prepayments as described, then consider setting up inclusive taxes in E-Business Tax. It is easier to partially apply prepayments that have inclusive taxes; therefore, it is easier to manage prepayments when tax decreases occur. Tax VariancesA tax variance occurs when there is a difference between the tax on the invoice and the tax on the PO matched to the invoice. When you match a PO to an invoice, there are three tax-related variances that can occur:
In addition, Tax Quantity Variance (TQV) is calculated, but is shown as a non-variance distribution. Variances are calculated for all taxes that are enabled in E-Business Tax. The following example illustrates how variances are determined. Purchase Order1100.00CAD0.80.00100.00Assume that the purchase order shown above is matched to the invoice shown below. Invoice100.00CAD1.1100.0020.00120.00Note that the exchange rate and tax amounts differ between the PO and the Invoice. The distributions for the invoice show a Tax Exchange Rate Variance of 0.3 and a Tax Rate Variance of $20.00. To illustrate an Invoice Price Tax Rate Variance, assume that the invoice is the same as as above, but the Unit Price changes from $100.00, as shown on the Purchase Order, to $200.00. The Tax Amount also changes as a result of the change in Unit Price. Invoice100.00CAD1.1200.0040.00120.00Tax Tolerances and Releasing Tax HoldsTo define tax tolerances, enabled the Allow Override for Calculated Tax Lines option in E-Business Tax. Tax Tolerances can be defined for any combination of Event Class and Configuration Owner. Tax Tolerances determine when Tax Holds are placed on an invoice. E-Business Tax places a hold on an invoice when a calculated tax line is updated and the updated tax amount exceeds the specified tolerance. Use E-Business Tax to release a tax hold. For more information on tax tolerances and tax holds, see: Defining Tax Tolerances, Oracle E-Business Tax User Guide. Tax Drivers on InvoicesThe following tax drivers appear on the invoice header and are used to determine tax applicability and calculate taxes for invoices:
The following tax drivers appear on the invoice lines and are used to determine tax applicability and calculate taxes for invoices:
Ability to Change Inclusion or Exclusion of TaxesYou can change the tax from inclusive to exclusive or vice versa on the transaction. Payables provide an ability to make the taxes applicable as inclusive or exclusive while entering the invoices, depending on the business practice and after looking at the physical invoice available. You can decide whether a tax is inclusive or exclusive on the fly for a transaction. You can override the Inclusive Flag in Tax details page for the system generated tax line. The inclusive flag depends on the setup done for that particular tax in E-Business Tax. From the document (Payables Uptake of E-Business Tax) and other references, it has been noted that the behavior was changed in R12 Payable Invoices with a purpose. You can override the tax inclusion flag at the Invoice level. In the UK Tax Regime, the law is that the supplier can issue Retail invoices, if the individual supply is more then £250, VAT should be shown as inclusive or exclusive values depending on his business practice. For Invoices less then £250, the invoice should show exclusive values. They further mentioned that freight invoices also commonly show inclusive and exclusive line items depending on the Customer's business practice. The details of the VAT laws applicable in UK is available on this link. You can now override Inclusive flag at the Invoice workbench level before the calculation of taxes. When the tax engine used to return inclusive taxes, AP would subtract the item dist amount (net off inclusive taxes) and store tax distributions as exclusive. No more changes were allowed after this point. On the Tax Details window, you set the taxes applicable on invoice to be inclusive or exclusive, by selecting the Includes tax option that can be overridden in the Tax Details window. The following Business Rules apply: You can override the Includes tax option in the Tax Detail window based on the setup in the EB Tax and before the invoice is undergone any of these changes:
You cannot override the Includes Tax option in the Tax Summary window. For Tax Only Line on an invoice, the Includes Tax option is not editable. For Expense Reports, the Includes tax option is not editable on Tax Summary window. The Taxes for expense reports will always be Inclusive. For PO or Receipt Matched Invoices, the Includes tax option in the Tax Detail window is disabled. For Inter-company Transactions and Manual Tax Lines entered in the Invoice Workbench, you cannot override the Inclusive Tax value. For Self Assessed Tax lines and Offset Tax lines as well, the Inclusive Tax option cannot be overridden. For manual tax lines entered in the tax details window, you can select the Inclusive Tax option to includes tax only at the time of entering the tax line. Once the tax line is saved, you cannot override it. Special Inclusive tax handling is not supported. Only Standard Inclusive Handling is supported. For the Quick Credit Memo transaction type, Applied Credit Memo and Applied Debit Memo (created using corrections or Create Debit Memo From RTS transactions), which are created by copying the data from the Invoice, the Inclusive Tax option cannot be overridden. Once an inclusive tax is calculated, you cannot split the item distributions. If you want to modify the distributions, then discard the item line. For upgraded Invoices, you cannot override the Inclusive Tax option. When setting up taxes, if you selected the Applied Amount Handling option as Recalculated, then for such taxes the Inclusive Tax cannot be overridden for the Prepayment type Invoices. For Cancelled Tax lines, you cannot override the Inclusive taxes. In the tax details window, for a tax already calculated, if you change the inclusive option and also other values such as tax rate, tax status, then the calculation is done based on the tax percentage and the most recent value of the Inclusive tax as specified on the item line before the values were modified. For example,
If you change the Include Tax value in the Tax Details window and change the Tax Rate to 15%, then the application ignores the modified tax rate of 15%. The tax rate is calculated based on the value specified on the Item line prior to change which is 10% Inclusive on 100$ that comes to 9.09. Note: For an Invoice, if a Prepayment is applied, then you cannot override the inclusive tax. You can override the Inclusive Tax option when you unapply the prepayment. For an already paid Invoice, you cannot override the inclusive tax option. However, if you void the payment, then you can override the override the inclusive tax option. HoldsHolds that you apply manually or that Payables applies, prevent payment and, in some cases, creation of accounting entries for an invoice. You can remove holds that you apply, and you can manually release certain holds that Payables applies during Invoice Validation. In addition to manually releasing holds, Oracle Payables integrates with Oracle Workflow to provide a resolution of user releasable holds through workflow. Holds resolution workflow is initiated during Invoice Validation. Payables provides some generic invoice holds for you to use, and you can define your own, based on your invoice validation needs. You can also prevent payment of supplier invoices by placing a hold on the supplier rather than on each individual invoice. This discussion on holds includes the following topics: Related Topics Invoice Hold and Release Names, Oracle Payables Implementation Guide Applying HoldsThere are three types of holds you can use to prevent payment of an invoice:
Payables automatically applies certain holds to exception invoices during Invoice Validation. You cannot manually apply these system holds. For example, if the sum of an invoice's distribution amounts does not equal the Invoice Amount, Payables will apply a Distribution Variance hold to the invoice during Invoice Validation. Applying a Hold to an InvoicePrerequisite
To apply a hold to an invoice:
Supporting Engineering and Construction Subcontractor Payment ManagementEngineering and Construction firms have unique requirements regarding subcontractor management, subcontractor payment, and customer billing. It is a common practice in the Engineering and Construction industry to hire a Subcontractor by a General contractor to perform specific portions of work as part of the overall construction project. Improvements in Payment management of Subcontractor are considered to be a top priority to the Engineering and Construction industry in recent years, considering Subcontractor role in successful completion of the project. To synergize the efforts of Subcontractor in overall success of project it is very important to do timely payments to place appropriate controls in the Payment process. Payables Department must have efficient and effective controls on payments. Payables department must ensure that suppliers are paid only when they are supposed to be paid as per the terms defined. Till then the suppliers should be held for any payment. The Business Process related to Engineering and Construction usually includes the Pay when Paid terms and other deliverable required from the Subcontractor Pay When Paid is a payment term common in the Engineering and Construction Industry where subcontractors are not paid until the customer pays the general contractor. PO Deliverable are documents required to be submitted or renewed by the subcontractor. If this is not done as per the terms, the payments are held for the supplier. For details on the Business process, refer to Oracle Projects User Guide. Payables supports automatic Payment Holds and Releases in following scenarios:
You define the Hold and Reasons on the Holds tab on the Invoices Workbench window. Two new types of Invoice Hold Names, Pay when paid scenario and PO Deliverable, and two new Invoice Release reasons, Project Manager release and Automatic Release, are included. This lets you hold the payment if pay when paid term is enabled or if Deliverable is not received from tbe subcontractor Pay When Paid Scenario To support pay when paid scenario, you must first enable these terms in the Purchase Order. Whenever invoices are validated (online or through the Concurrent Process), if the invoice is matched to Purchase order or receipt, and any of the matched PO has Pay When Paid marked as Yes, the invoice is put on hold with hold reason as Pay when Paid hold. You can release the Pay When Paid Hold:
Refer to the Oracle Projects User Guide for more details. To support payment control with regard to PO deliverable, whenever invoices are validated (online or through the Concurrent Process), if the PO Deliverable are not received or renewed as per the terms and set up, the invoices are put on PO Deliverable Hold. The hold is released when the PO Deliverable are received. PO Deliverable Hold can be released in the following ways:
Refer to Oracle Projects and Oracle Procurement User Guides for more details. Applying a Hold to a Scheduled PaymentPrerequisite To apply a hold to a scheduled payment:
Applying Supplier Site HoldsPrerequisite
To apply supplier site holds:Prevent payment of multiple supplier invoices by applying a hold to the supplier site rather than on each individual invoice. There are several types of supplier related holds (also known as vendor holds) that you enable for a supplier site. Payables also provides these options at the Supplier level, but Payables only uses these values to provide defaults for new supplier sites that you enter. The options you enable at the Supplier Site control Payables processing:
APPLYING HOLDS RESTRICTIONS:PAYMENT BATCH SELECTED INVOICES: You cannot apply holds to an invoice you have selected for payment in a payment batch. Related Topics Selecting Multiple Records, Oracle Applications User's Guide Releasing HoldsRelease holds from invoices to allow payment and accounting entry creation for the invoices. You can view the holds on an invoice in either the Invoice Overview window or the Invoice Holds tab. You can see the number of invoice holds on an invoice in the Holds display only region of the Invoices window. Identify invoices on hold with the Invoices On Hold report and the Matching Hold Detail report. These reports aid you in releasing holds from invoices. After you release all holds from an invoice it is not necessary for you to resubmit Invoice Validation before you can pay or create accounting entries for it. Invoice Validation will not place an invoice on the same type of hold that you manually released. You must manually release all holds that you apply manually. Payables does not automatically release holds that you apply to invoices. During Invoice Validation, Payables automatically releases system holds (anything other than the user defined holds you define) from invoices with corrected exception conditions. For example, you fix a distribution variance on an invoice, resubmit Invoice Validation, and Payables automatically releases the Distribution Variance hold. If you release a manually releasable hold that Payables applied during Invoice Validation, the next time you submit Invoice Validation, Payables will not reapply the same hold. Payables applies some holds that you cannot release. You can use the Invoice Holds tab to view invoices with these holds, but you cannot manually release these holds. You must correct the exception that caused Invoice Validation to place the hold on the invoice, then resubmit Invoice Validation to release the holds. You can correct exceptions by updating the invoice or the purchase order or by changing your Invoice Tolerances. There are three types of holds you can manually release:
Note: You can also use Oracle Workflow to release holds through workflow. See: . It is recommended that you do not use Accounting at the same time as the Hold Release as it is results in a significant performance issue. After releasing holds, run the Create Accounting process. You can still use the concurrent process too. Related Topics Releasing Holds From an InvoicePrerequisite
To release holds from an invoice:
Releasing Holds from Multiple InvoicesPrerequisite
To release holds from multiple invoices:
Releasing Scheduled Payment HoldsPrerequisite
To release scheduled payment holds:
Releasing Supplier HoldsTo release supplier holds:
Releasing Holds Through WorkflowHolds resolution workflow is initiated during Invoice Validation when:
Note: If the Approvals Manager setup does not provide a valid approver, the workflow terminates without further processing. PrerequisitesPrior to releasing holds through workflow, you must:
To release holds through Workflow:
For non-PO matched invoices, the approver can Release or Acknowledge the hold. The approver does not have the option to negotiate the hold. Note: The non-PO matched invoice negotiation is initiated during the invoice approval process. For more information on invoice approval, see: . Hold Resolution WorkflowThe Hold Resolution workflow allows you to release holds through workflow. As a part of the holds resolution, for non-purchase order matched invoices, it allows negotiation between the internal Payables clerk and the supplier. Releasing the holds on an invoice allows it to be eligible for validation and approval. All holds are available as attributes in AME. You define conditions for the hold attributes that you are using workflow to resolve. Once your Conditions and Approver Groups are finalized, you can create your Approval Rules. You create an approval rule for your purchase order matched invoices and one for your unmatched invoices. See: Approvals Management Implementation Guide for more details. Holds resolution workflow runs during validation when the:
If the Approvals Manager setup does not set up a valid approver, then the workflow terminates without further processing. PO Matched FlowThe holds resolution workflow uses the following process for PO matched invoices. An initial Workflow notification is sent to Internal Approver who is derived from the Approvals Management Engine (AME) setup. The Internal Approver can choose the following actions:
Non-PO Matched FlowThe only difference between the PO Matched and the Non-PO Matched flow is that the Internal Approver does not have the option to negotiate. An initial Workflow notification is sent to the Internal Approver. The Internal Approver can do the following:
The workflow waits for specific amount of time setup at the Hold type level, and checks again if the hold is really released. And then the workflow ends. If the hold has still not been released, then the notification is sent again. This is repeated until the hold is resolved. Related Topics Invoice Tolerances, Oracle Payables Implementation Guide Selecting Multiple Records, Oracle Applications User's Guide Hold Release Restrictions:FIND WINDOW. When you use the Find window to locate invoices from which you want to release holds, Payables releases only the holds that match your invoice find criteria. SYSTEM HOLDS. Payables applies some holds that you cannot manually release. You can use the Invoice Holds tab of the Invoice Workbench to view invoices with these holds, but you cannot release these holds. You must fix the problem that caused Invoice Validation to place the hold on the invoice then resubmit Invoice Validation to release the holds. You cannot release the following holds:
Invoice NoticesGenerate a standard invoice notice to send to a supplier to inform them about one or more invoices you have entered. For credit/debit memos, the notice informs the supplier of outstanding credit or debit memos that you will apply to future invoices. You can print an invoice notice in two ways: Payables generates one type of notice for a Standard invoice, and another type for Credit and Debit Memos. You can use Oracle Reports to change the boilerplate text of either letter. See: Customizing Your Supplier Letters, Oracle Payables Implementation Guide. If you use multiple languages in your Payables installation, then Payables will group the notices by language and submit the report once for each group. You specify a language for the supplier at the supplier site. The following is the introductory text of the invoice letters that come with Payables:
The invoice notice then lists the following information:
If the invoice is purchase order matched, the notice also lists the following information:
The invoice notice ends with a signature block with the Sender Name and Sender Title you enter as parameters when you print an invoice notice. See also: Customizing Your Supplier Letters, Oracle Payables Implementation Guide Printing Invoice Notices from the Invoice WorkbenchTo print notices from the Invoice Workbench:
Related Topics Reviewing InvoicesThis section includes the following topics: Finding Invoice BatchesYou can find invoice batches in the Invoice Workbench either by using the Find Invoice Batches window, or by entering query criteria directly into the Invoice Batches window. If you want to find invoices contained in a particular invoice batch, query the invoice batch in the Invoice Batches window, then choose the Invoices button. In the Find Invoice Batches window, you can search for a batch by entering ranges for invoice batch names and dates. You then choose Find to navigate to the Invoice Batches window, where Payables displays all invoice batches that match your Find criteria. To find invoice batches using the Find Invoice Batches window:
Related Topics Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide Finding InvoicesYou can find invoices to respond to supplier inquiries, including questions regarding invoice payment status, invoice payment date, reasons an invoice has not been paid, and total balance due for a supplier or supplier site. You can also find invoices to make adjustments to them or to perform actions on them, such as validation or cancellation. You can find invoices in the Invoice Workbench either by using the Find Invoices window or by entering query criteria directly into the Invoices window. In the Find Invoices window, you can enter a greater variety of criteria, including invoice status and ranges for invoice amounts, invoice dates, and voucher numbers. You then choose Find to navigate to the Invoices window, where Payables displays all invoices that match your Find criteria. From the Invoices window, you can review or adjust information about an invoice, and you can navigate to other windows to review or adjust scheduled payments, distribution holds, related payments, and more. If you want to find invoices contained in a particular invoice batch, you can also find the invoice batch, then choose the Invoices button in the Invoice Batches window. See: . If you want to review in one window a wide variety of high level information about a single invoice, use the Invoice Overview window. See: . You can quickly open an invoice you have saved as an icon on your Navigator. When you have the invoice open, select Place on Navigator from the Actions menu. Later, if you choose the icon in the Documents region of your Navigator, then Payables will automatically open the Invoice workbench and query the invoice. See also: Using the Navigator's Documents Region, Oracle Applications User's Guide. To find an invoice using the Find Invoices window:
Related Topics Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide Reviewing InvoicesYou can review invoices in either the Invoice Workbench or the Invoice Overview window. If you want to be able to enter complex query criteria, review multiple invoices, or review all details about invoices, use the Invoice Workbench. If you just want to review high level invoice information for a single invoice, such as invoice status, active holds, scheduled payments, and actual payments, use the Invoice Overview window. See: . Note: You can view the detail accounting lines for the transaction in the form of a balanced accounting entry (i.e., debits equal credits). You can also choose to view the detail accounting as t-accounts. See: To review invoices in the Invoice Workbench:
Reviewing Invoice BatchesPrerequisite
To review invoice batches:
Reviewing Invoice DistributionsDistributions WindowFrom the Distributions window, you can use the Find Invoice Distributions window to search for distributions for one invoice that match criteria you select. For example, if you have an invoice with a large number of distributions, you can view only distributions that meet criteria you specify. You can search by accounted status, GL date range, amount range, and account range. To find invoice distributions in the Invoice Workbench:
View Accounting Lines WindowIf you want to search for accounted distributions outside of the context of the invoice, you can use the View Accounting Lines windows to identify them and see which invoices they belong to. For example, you can search for all accounted distributions that have a particular account. In the Find Accounting Lines window, you can search by any combination of the following criteria: supplier name, currency, transfer to GL status, account range, and accounting date range. Payables then shows all accounting lines that match your inquiry in the View Accounting Lines window. See: . Related Topics Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide Reviewing Payment Information in the Invoice WorkbenchUse the Payments tab of the Invoice Workbench to get quick payment information for a selected invoice. To use the window, select an invoice in the Invoices window and choose the View Payments tab. The Payments window displays payment documents that you have used to pay the selected invoice. For further information, you can then choose the Payment Overview button or the Scheduled Payments tab. Note: This tab is separate from the Payments window in the Payments Workbench, which you use to create single payments. Calculating a Supplier or Supplier Site BalanceThe Calculate Balance Owed window shows how much you owe a supplier and how many unpaid invoices you have in the system for the supplier. Use the Find Invoices window and choose the Calculate Balance Owed button to see how much you owe a supplier and how many unpaid invoices you have in the system for the supplier. To calculate the balance owed, Payables subtracts available prepayments from the unpaid invoice amount. Payables does not use unpaid prepayments when it calculates the balance. If you have foreign currency invoices that do not yet have exchange rates, you can calculate the balance with an exchange rate you enter in the window. The exchange rate you enter will not update the invoices; you are still required to submit AutoRate or enter an exchange rate in the Invoices window. To calculate a supplier or supplier site balance:
To calculate a supplier or supplier site balance in a foreign currency:
Related Topics Calculate Balance Owed Window ReferenceThis window shows a supplier balance for the invoices that match the criteria you enter in the Find Invoices window. Default Exchange Rate: If you have foreign currency invoices that do not yet have exchange rates, you can calculate the balance with an exchange rate you enter in the window. The exchange rate you enter will not update the invoices; you are still required to submit AutoRate or enter an exchange rate in the Invoices window. Take Discount: If you want Payables to reduce the balance by available discounts, then check this check box. Include Outstanding Future Dated Payments: If you want to include in the Balance Owed the amount in the Future Dated Payments field, then enable this check box, then choose the Calculate button. Unpaid Amount: Sum of unpaid, validated and unvalidated invoices. This number includes negative amount invoices but does not include unpaid prepayments. Future Dated Payments: Sum of all outstanding (issued but not matured) future dated payments. If you do not want this amount included in the Balance Owed, then uncheck the Include Outstanding Future Dated Payments check box and then choose the Calculate button. Less Available Prepayments: Available prepayments (the sum of Temporary, paid, unapplied prepayments) include prepayment Item distributions and the associated tax. Payables does not use unvalidated or unpaid prepayments when it calculates the balance because they are not available for application. Balance Owed: Unpaid invoice amount minus available prepayments. If you have enabled the Include Outstanding Future Dated Payments check box, then Payables also subtracts the sum of any outstanding (issued but not matured) future dated payments Number of Invoices: Number of unpaid invoices, not including unpaid prepayments. Number of Prepayments: Number of available prepayments. Related Topics Supplier Customer Netting Report, Oracle Receivables User Guide Identifying Duplicate InvoicesYou can periodically audit your invoices to prevent duplicate payments of the same invoice. Although Payables prevents you from entering an invoice with exactly the same invoice number for the same supplier, you may have entered the same invoice twice with different supplier names, or invoice numbers with different case (abc123 and ABC123). Tip: You may want to use an invoice numbering convention that minimizes the risk of separate entries of the same invoice under different invoice numbers. For example, if you consistently enter all letters in upper case you would enter an invoice number only as ABC123, and not also as abc123. The following reports to help you identify duplicate invoices in your Payables system:
Related Topics Resolving Duplicate InvoicesTo resolve duplicate invoices when you have overpaid:
To resolve duplicate invoices when you have not overpaid:
Invoice Overview WindowIn the Invoice Overview window, you can review the status of an invoice and some high-level information. This window is particularly helpful for reviewing information quickly when a supplier calls you to inquire about the status of an invoice. This window also serves as a bridge between the Payment and Invoice Workbenches. This window displays summary information for the invoice:
This is a display-only window. If you are in entry mode, then choose the Invoices button to navigate to the Invoices window to adjust the invoice. For more detailed information regarding the invoice or related attributes, choose the Invoices, Supplier, View PO, View Receipt, or Payment Overview button. If your query retrieves more than one invoice, Payables orders and displays queried invoices by the latest invoice date. To see the next queried invoice, press [Next Screen]. Note: You can view the detail accounting lines for the transaction in the form of a balanced accounting entry (i.e., debits equal credits). You can also choose to view the detail accounting as t-accounts. See: Note: For invoice approval, the Notification Detail and Interactive Line Details pages display only the appropriate level of information for the approver to view. The approver can approve or reject the invoice or invoice lines using these pages. Adjusting InvoicesAdjustment ChartsInvoice Adjustment ChartThe following chart shows for each field in the Invoices window the conditions under which you cannot adjust the value in the field. Because the paid status and accounted status are common reasons you cannot adjust an invoice, we have provided separate columns for those reasons for easy reference. Note: When you change the following fields, which are marked with an asterisk, Payables recalculates the scheduled payment: Discountable Amount, Payment Method, Terms Date, Terms. AmountInvoice is a prepayment anda) is encumbered, or b) is applied. Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is selected for payment. Invoice is paid with a positive amount discount taken and the Allow Adjustments to Paid Invoices Payables option is disabled. Unaccounted invoice payments that do not have a corresponding void on the same GL Date exist. You cannot adjust the invoice amount to less than the amount you have already paid on an invoice. NONOApproved AmountInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice currency has no value. NONOApproval DescriptionInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. YESYESApproval StatusInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. NONODate Invoice/Goods ReceivedInvoice is cancelled.Invoice has an unaccounted void payment. YESYESDescriptionInvoice is fully or partially paid and Allow Adjustments to Paid Invoices Payables option is disabled.YESYESDescriptive FlexfieldInvoice is fully or partially paid and Allow Adjustments to Paid Invoices Payables option is disabled.YESYESDiscountable Amount *Currency field has no value.Invoice is a prepayment and is encumbered. Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. NONODistribution SetInvoice is saved.NONODocument Category NameInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is saved. Sequential numbering is not enabled or the allow document category option is not enabled. NONOExchange DateInvoice is in the functional currency.Invoice is a prepayment and is encumbered. Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. NONOExchange Rate, TypeInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Exchange rate type is not user-defined or has no value. Invoice is encumbered. Invoice has accounted or partially accounted distributions. NONOFreight AmountInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Currency or GL Date has no value. NONOFunctional Curr AmountThe Payables option Calculate User Exchange Rate is not enabled and if the exchange rate type is not User.NONOGL DateInvoice is cancelled.YESYESInvoice CurrMultiple currencies are not used.Invoice is fully or partially paid or a prepaid amount exists for the invoice. Invoice is cancelled. NONOInvoice DateInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is purchase order matched. Sequential numbering is enabled. NONOInvoice NumberAllow Adjustments to Paid Invoices Payables option is disabled and the invoice is paid or partially paid.Invoice is a prepayment and is encumbered. Invoice is cancelled. Invoice has an unaccounted void payment. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is purchase order matched. Sequential document number present. Invoice is a prepayment. NONOLiability AccountInvoice is a prepayment and is encumbered.You use encumbrance and any of the distributions are validated.YESNOOracle Projects Project, Task, and Expenditure InformationInvoice is a prepayment and is encumbered. Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Projects is not installed. Invoice is not Projects-related. NONOPay AloneInvoice type is Mixed with a negative invoice amount.Invoice has been selected for payment. Invoice is cancelled. Invoice is a Credit or Debit Memo. YESYESPay GroupInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment . Invoice is cancelled. Invoice has withholding tax distributions. Invoice has prepayment applied to it. Invoice is selected for payment. YESYESPayment CurrNOYESPayment Method*(can change at scheduled payment)Invoice is a prepayment and the invoice is encumbered. Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is selected for payment. NONOPayment PriorityRecord is queried.Payment schedule is fully paid. Any payment schedules for the invoice are selected for payment. YESYESPrepayment PO NumberInvoice is not a prepayment or Supplier has no value.Invoice is cancelled. Prepayment is applied. YESYESPrepayment TypeInvoice is not a prepayment.Invoice is cancelled. Prepayment has been applied. YESYESSettlement DatePrepayment type is not Temporary.Invoice is cancelled. Prepayment has been applied. YESYESSupplier NameInvoice has an unaccounted void payment.Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is purchase order matched. Invoice is validated. Invoice is a prepayment and is purchase order matched. NONOSupplier NumberInvoice has an unaccounted void payment.Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is purchase order matched. Invoice is validated. Invoice is a prepayment and is purchase order matched. NONOSupplier SiteInvoice is cancelled.Invoice has an unaccounted void payment. Invoice is fully or partially paid and Allow Adjustments to Paid Invoices is disabled. Invoice has withholding tax lines. NOTax AmountInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Tax Code has no value. Tax type is Use. NONOTax CalculationInvoice is saved.Automatic tax calculation override is disabled. Automatic tax calculation option in Payables options window is disabled. Tax type is Use. Invoice amount has no value. YESYESTax CodeInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Tax:Allow Tax Code Override profile option is disabled. NONOTerms Date *Invoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is selected for payment. NONOTerms*Invoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is selected for payment. Invoice is fully or partially paid and invoice payments exist. NOYESTypeInvoice is a prepayment anda) is encumbered, or b) is applied. Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is purchase order or receipt matched. Sequential numbering is enabled. NONOUser Rate TypeInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice currency is the same as the base currency. User rate type is EMU Fixed. Exchange rate type is not User. Encumbered distributions exist. NONOVoucher NumberInvoice is a prepayment and is encumbered.Invoice has an unaccounted void payment. Invoice is cancelled. Invoice has withholding tax distributions. Invoice has a prepayment applied to it. Invoice is selected for payment. Invoice is saved and sequential numbering is enabled. NONOWithholding Tax GroupInvoice is prepaid and is withheld at payment time.Invoice is validated and is withheld at validation time. Invoice is cancelled and has withholding tax lines. Invoice has unaccounted void payments. Invoice is fully or partially paid and Allow Adjustments to Paid Invoice is disabled. Use Withholding Taxes Payables option is disabled. Supplier site option to use withholding taxes is disabled. YESNO* When you change this field, Payables recalculates your scheduled paymentRelated Topics Invoice Distribution Adjustment ChartThis section discusses the fields and restrictions on the invoice distribution adjustment chart. General RestrictionsYou cannot update, reverse, or delete a distribution if:
You cannot delete a distribution if:
Fields Without Other RestrictionsOther than the above rules, there are no restrictions to updating the following distribution fields:
Display Only FieldsThe following fields are display only, and cannot be updated:
The following chart shows for each field in the Invoices window the conditions under which you cannot adjust the value in the field. Because the accounted status is a common reason you cannot adjust an invoice distribution, we have provided a separate columns for that reason for easy reference. AccountDistribution is purchase order matched anda) the Allow Matching Account Override Payables option is disabled, b) the invoice is Final Matched, c) the Accrue On Receipt flag is enabled or set to Done, d) encumbrance is enabled. Encumbrance is enabled and distribution Projects is installed, distribution is project-related, and the PA: Allow Override of PA Distributions in AP/PO profile option is disabled. Distribution is an automatically created withholding tax distribution. NOAccounting DateEncumbrance is enabled and distributiona) is part of a reversal pair, or b) is encumbered.NOAmountEncumbrance is enabled and a) the distribution is part of a reversal pair, or b) the distribution has been encumbered (validated). Distribution is purchase order matched. NODescriptionYESDescriptive FlexfieldInvoice is fully or partially paid and Allow Adjustments to Paid Invoices Payables option is disabled.YESFinal MatchMatch Status flag is set to Yes.Final Match flag is set to Done. Allow Final Matching Payables option is disabled. Distribution is not purchase order matched. YESGL DateEncumbrance is enabled and distributiona) is validated, or b) is part of a reversal pair. Distribution has been validated. NOIncludes Tax CheckboxAllow Override (of Distribution Amount Includes Tax) Payables option is disabled.Use Automatic Tax Calculation Payables option is disabled. Tax calculation level is not Line or Tax Code. Distribution is purchase order or receipt matched. Tax has already been calculated for the distribution. Distribution is type Tax. YESIncome Tax RegionIncome Tax Type has no value.YESLine NumberDistribution is encumbered (validated)Invoice is a Prepayment type invoice. NOProjectsProjects is not installed or project does not have a name.Encumbrance is enabled. Distribution: Invoice is Final matched. Distribution is purchase order matched and If the invoice has been fully or partially paid, you have taken a discount for it, and your Discount Distribution Method Payables option is anything other than System, you will be unable to update the Project field in the Distributions window. YESRecoverableEnable Recoverable Tax Payables option is disabled.Encumbrance is enabled and distribution Distribution is an automatically created withholding tax distribution. Distribution type is not Tax. NOStatistical Quantity/UnitNo defined unit of measure exists for the account.Record is queried. Distribution is validated. Distribution is part of a reversal pair. NOTax CodeEncumbrance is enabled and distributiona) is encumbered (validated), or b) is part of a reversal pair. Distribution is an automatically created withholding tax distribution. Tax Code field has value; or Tax Code field has no value but is not required, and the Tax:Allow Tax Code Override profile option is disabled. Encumbrance is enabled and distribution Distribution is an automatically created withholding tax distribution. Distribution type is Tax or Automatic Withholding Tax. Tax:Allow Override of the Tax Recovery Rate profile option is disabled. Distribution is validated. Distribution is purchase order matched and a tax line is associated with it that is encumbered. NOTrack As AssetIf the account type is Asset, you cannot disable this check box.YESTypeRecord is saved.Distribution is purchase order or receipt matched. Encumbrance is enabled and distribution: Distribution is a prepayment distribution. Distribution has existing allocations. Invoice is a prepayment and prepayment distribution is partially or fully applied. Invoice has a voucher number. Invoice is paid and you have taken a discount. Distribution is an automatically created withholding tax distribution. NOWithholding Tax GroupInvoice is already paid and you withhold at payment time.Invoice is already validated and you withhold at validation time. Distribution is not a withholding tax distribution. Record is saved. NOUSSGL Transaction CodeThe following section is applicable to customers who use transaction codes. Transaction codes are typically used by US Federal Government customers to produce both proprietary and budgetary entries for a given transaction. USSGL option is disabled.Encumbrance is enabled and distribution Related Topics Adjusting InvoicesFor most invoice types, authorized users can make adjustments to invoice details, distributions, and scheduled payments, even if the invoice has been accounted or paid. After you make an adjustment to an invoice, you may need to submit Invoice Validation before you can pay it. If you adjust payment terms or any scheduled payment information on a validated invoice, you do not need to resubmit Invoice Validation. For detailed information on adjusting different types of invoices and invoice distributions, and under which conditions you can adjust values in specific invoice and distribution fields, see: ; ; and . Remember that some invoice values, such as the withholding tax group, distribution set, and projects information, are used when you create new invoice distributions. If you change these values at the invoice header level, they do not affect any existing invoice distributions. If you want to change this information on the invoice distribution, then you must change it in the Distributions window. Note: If Payables automatically withholds tax at Invoice Validation time, it withholds only the first time you submit Invoice Validation for an invoice. If you adjust an invoice after Payables calculates withholding tax, you need to make appropriate adjustments manually. If and invoice is unpaid you can cancel it. After you cancel an invoice, however, you can make no changes to it. Adjusting Purchase Order Matched InvoicesIf you accidentally matched to the wrong purchase order document (purchase order, shipment, distribution, or receipt), you can reverse matched distributions and/or 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 Payables will place holds on the invoice during Invoice Validation. You can adjust the GL Date, Income Tax Type, and Account fields of a purchase order matched invoice distribution. For details on when you can update any field, see: If a supplier sends an 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. See: . When Adjustments to Paid Invoices Can Cause Accounting ProblemsWarning: Certain Adjustments to Paid Invoices Can Result in Incorrect Accounting If you have enabled the Allow Adjustments to Paid Invoices Payables option, you can adjust certain information on a paid invoice. Usually the desired adjustment is to the invoice distributions to correct account information. In certain cases, adjustments you make to invoice distributions will cause incorrect accounting because Payables cannot automatically make corresponding adjustments to related accounts. Payables warns you when you try to adjust a distribution in these cases. If you still want to make adjustments, then create a manual journal entry in your general ledger to correct the other accounting. Adjusting an invoice in the following situations can cause accounting errors:
Related Topics Adjusting Invoice AmountsTo adjust the amount of an invoice:
Related Topics Adjusting Invoice Exchange RatesYou can change the Exchange Rate of an invoice at any time before you pay it or create accounting entries for it. You can change the exchange rate in two ways:
Adjusting GL DatesYou can change the GL Date of any invoice in the Invoices window but the new GL Date will default only to new invoice distributions you create. If you want to adjust the GL Date on existing invoice distributions, change the GL Dates in the Distributions window. Payables uses the GL Date as the invoice accounting date. You cannot change the GL Date of a distribution once it has been validated. If you are allowed by your accounting rules, you can use the Unaccounted Transactions Sweep program to transfer all unaccounted invoice and payment transactions from one accounting period to another. You can submit this program when you need to close a period that has unaccounted invoices or payments in it. Related Topics Adjusting Invoice BatchesTo adjust an invoice batch:
To delete an invoice batch:
Related Topics Invoice and Invoice Batch Adjustment Restrictions:The following are general restrictions for adjusting invoices. For restrictions for adjusting particular fields, see: REVERSING DISTRIBUTIONS AND ENCUMBRANCE ACCOUNTING: If you use encumbrance accounting and you reverse a validated invoice distribution, Payables automatically creates an encumbrance reversal entry that reverses the invoice distribution encumbrance entry created when you validated the invoice. You cannot update the reversed invoice distribution because Payables will use it to create the reversing encumbrance entry. ADJUSTING DISTRIBUTIONS ON INVOICES THAT CROSS BALANCING SEGMENTS: If Automatic Offsets is enabled and the invoice contains distributions that are charged to more than one balancing segment, you cannot add, delete, reverse, or update distributions once the invoice is paid or partially paid. CANCELLED INVOICES: If you have cancelled an invoice, you cannot adjust any invoice or invoice distribution information for that invoice. However, under certain conditions, you can delete it. FINAL MATCHED: You cannot adjust an invoice that has distributions marked as Final Matched. You can disable the distribution's Final Match check box if you have not submitted Invoice Validation for the invoice. After you submit Invoice Validation for a final matched invoice and Payables validates the invoice, you cannot make adjustments to the invoice or reopen the purchase order. INTEREST INVOICES: You cannot adjust an interest invoice if the payment that paid it has been accounted. INVOICES SELECTED FOR A PAYMENT BATCH: You cannot adjust an invoice that has been selected for payment in a payment batch. You can wait until the payment batch completes and then adjust the paid invoice. REVERSING DISTRIBUTIONS WITH INVALID ACCOUNTS: You cannot reverse an invoice distribution that has an invalid account. WITHHOLDING TAX: If you have enabled withholding tax and you choose to have Payables automatically create invoices to a tax authority, you cannot modify the distributions of that invoice. DELETING DISTRIBUTIONS. If you have reversed a distribution, you cannot delete it or the associated reversal line. If a distribution line has been encumbered, you cannot delete it. Adjusting Invoice DistributionsIf you have not yet created accounting entries for an invoice distribution, you can update most of the invoice distribution details, including Description, GL Date, Income Tax Type, Withholding Tax Group, and Income Tax Region. If you have not yet created accounting entries for the distribution and the distribution has an expense type account, you can also adjust the Track as Asset check box. For more information on changing a particular field, see the . For Prepayment type distributions, the only fields you can adjust are Tax Code and Description. You cannot reverse or delete Prepayment distributions. However, you can unapply them. You cannot adjust invoice distributions for a paid invoice if you disable the Allow Adjustments to Paid Invoices Payables option. If you add or reverse distributions or if you change a distribution amount, you must submit Invoice Validation again before you can pay the invoice. Invoice Validation recalculates the invoice scheduled payments. Invoice Validation also reallocates any Tax, Freight, or Miscellaneous charges that are not already fully allocated, or that were allocated to reversed distributions. If the charge is not fully allocated, Invoice Validation removes any existing allocations and prorates the charge across all eligible distributions. Many factors affect whether you can adjust invoice distributions. For a complete list of restrictions, see: . For a chart that shows each field and when you can adjust it, see: . Purchase Order Matched DistributionsYou can adjust the GL Date, Income Tax Type, and, under some circumstances, the Account fields of a purchase order matched invoice distribution. You can change the Account only if you have not yet accounted for the invoice and if you have enabled the Allow Matching Account Override Payables option. If the invoice is purchase order matched, you cannot directly adjust fields that are defaulted by the matched purchase order, such as Amount. You can, however, reverse purchase order matched distributions at any time, then create new invoice distributions by rematching. Updating Invoice DistributionsPrerequisite
To update invoice distributions:
Related Topics Adding New Invoice DistributionsPrerequisites
To add invoice distributions to an existing invoice.
Reversing Invoice DistributionsPrerequisites
To reverse invoice distributions:
Related Topics Selecting Multiple Records, Oracle Applications User's Guide Adjusting Scheduled PaymentsYou can make any adjustments you need to an invoice's scheduled payments if the invoice is not fully paid. You can add as many new payments as you want, and you can alter unpaid scheduled payments. You can defer payment by adjusting due dates on schedules or by applying holds to selected scheduled payments. Important: Payables recalculates and overwrites scheduled payments if you adjust the invoice Payment Terms. Invoice Validation recreates scheduled payments if the Exclude Tax from Discount Calculation Payables option is enabled and updates have been made to the tax amount, or if the Scheduled Payment Recalculation Payables option is enabled. If you manually adjust scheduled payments and Payables subsequently recalculates the scheduled payments, you will need to reenter your changes, including any holds that you have placed on scheduled payments. To adjust scheduled payments for an invoice:
Scheduled Payment Adjustment Restrictions:INVOICES IN PAYMENT BATCHES: You cannot update a scheduled payment for an invoice that has been selected for a payment batch. You must cancel the payment batch before you can adjust the invoice. Related Topics Adjusting PrepaymentsIf you have not paid or applied a prepayment, you can make changes to it in the same way that you make changes to an invoice. You can cancel a prepayment after you create accounting entries for it, but not if it is paid or applied to an invoice. Related Topics Cancelling InvoicesYou can cancel only unpaid invoices. You can cancel any unvalidated invoice, or a validated invoice that does not have any effective payments or accounting holds. If an invoice has a hold that prevents accounting, you must release the hold before you cancel the invoice. You cannot cancel an invoice that is selected for payment in a payment batch. You can cancel an invoice that was paid with a payment that is now voided, if the invoice status is now Unpaid. A cancelled invoice does not show up in your invoice liability reports and you cannot pay or adjust a cancelled invoice. You can cancel single invoice distributions by reversing them. See: . When Payables cancels an invoice, it sets the invoice amount to zero, sets all scheduled payments to zero, and reverses all invoice distributions and any matches to purchase order shipments and distributions. Payables also submits Invoice Validation for the invoice and, if there are no accounting holds on the invoice, updates the status of the invoice to Cancelled. Note: If you want to make a zero-amount payment on an invoice, you should not cancel the invoice. Instead, you can change to zero the invoice amount for the invoice and pay the invoice using a payment batch, manual payment or Quick payment. See: . If you cancel an invoice with an associated withholding tax invoice, Payables automatically creates an invoice for the tax authority supplier to offset the amount of the withholding tax invoice. Payables saves the original invoice amount for audit and reference purposes. Note: If you cancel an invoice with manually entered withholding tax, you should check to see if any invoices for the tax authority were created manually to reflect the amount withheld. If such invoices exist, they will not be cancelled automatically, and you might want to cancel them manually. To cancel an invoice:
Cancelling Invoice Restrictions:INVOICES TO WHICH YOU HAVE APPLIED PREPAYMENTS: You cannot cancel an invoice that you have applied a prepayment to. You must first unapply the prepayment. INVOICES YOU HAVE MATCHED TO PERMANENTLY CLOSED PURCHASE ORDERS: If you use encumbrance accounting, you cannot cancel an invoice that you matched to a permanently-closed purchase order. PREPAYMENTS: You cannot cancel a prepayment that you have applied to an invoice. You must first unapply any prepayments and void the payment that paid the prepayment. You can then cancel the prepayment. GL DATE: You cannot change the GL Date if you use Encumbrance and the distribution has been encumbered or is part of a reversal pair. CAN'T REDUCE QUANTITY BELOW ZERO: You cannot cancel an invoice if cancelling it reduces the quantity billed on a purchase order below zero. Related Topics Selecting Multiple Records, Oracle Applications User's Guide Deleting InvoicesYou can delete an invoice if it is not accounted, and at least one of the following is true:
You cannot delete an invoice in the following conditions:
For more information, see: . Related Topics Oracle Assets IntegrationYou can enter invoices for asset items in Oracle Payables and then import specified distributions into an interface table in Oracle Assets. You can then create assets from the distributions in Oracle Assets. For detailed information see: Create Mass Additions from Invoice Distributions in Oracle Payables, Oracle Assets User Guide. You can also use Payables to make payments for capital leases that you record in Oracle Assets. In Oracle Assets, you enter lease payments and create lease payment schedules that are exported to Payables through the Export Lease Payments to Payables Process. This process loads invoice information into the Oracle Payables Open Interface and you can run the Payables Open Interface Import to create your invoices. For detailed information see: Exporting Lease Payments to Oracle Payables (Oracle Assets User Guide or online help) and . Prerequisites
To record an invoice distribution as an asset:
Related Topics Create Mass Additions from Invoice Line Distributions in Oracle Payables, Oracle Assets User Guide Oracle Assets User Guide, Oracle Assets User Guide Oracle Projects IntegrationIf you install Oracle Projects, you can record project information on supplier invoices and employee expense reports. For each transaction, Payables records the project name, task, and expenditure information. The Account Generator creates a charge account for each invoice distribution that has project information. Project-related transactions are interfaced back to Projects where the transactions are recorded and associated with particular projects. Note: Project fields appear in the Invoices window and Distributions window only if you have installed Oracle Projects. This document includes the following topics: Entering Project-Related Invoices and Expense ReportsThis discussion gives a brief overview of the ways in which you can add project information to expense reports and invoices. For detailed information on Payables Integration with Projects, see the "Integration with Other Oracle Applications" chapter in the Oracle Project Costing User Guide. You can enter project information on supplier invoices. These transactions are interfaced to Oracle Projects as supplier invoices. You can use the Payables Open Interface Import program to import project-related invoices from Quick Invoices and other sources. You can also enter project information on supplier invoices in the following ways:
You can enter project information on expense reports. These transactions are interfaced to Oracle Projects as expense reports. You can enter project information on expense reports in the following ways:
The PA: Default Expenditure Item Date for Supplier Cost profile option controls how Payables and Purchasing determine expenditure item dates for supplier invoices and receipt accruals. Payables uses this profile option to determine the expenditure item date for supplier invoices distribution lines. See: Profile Options, Oracle Projects Implementation Guide. Entering Project-Related Invoices and DistributionsWhen you enter a project-related invoice, you enter the project information either manually in the projects fields, or by entering a project-related Distribution Set for the invoice. These project values default to the Distributions window. In the Distributions window you can add a value for Quantity. Creating Project-Related Recurring InvoicesWhen you set up a recurring invoice template, assign a project-related distribution set or purchase order to the template. All invoices created by the template will have the project information. You can override these values in the Distributions window after Payables creates the recurring invoice. Entering Project-Related Expense Reports in Internet ExpensesThis section gives you an overview of the process of entering project-related expense reports using Internet Expenses. Each step refers you to documentation where you can find more information on the step.
Entering Project-Related Expense Reports in PayablesThe Expense Reports window has no project fields. You can enter project-related expense reports in the Invoice Workbench. Enter an invoice with the invoice type of Expense Report, enter an employee's name as the supplier, and enter project information, either by using a project-related Distribution Set, or by manually entering project information. The system automatically builds the charge account for the distribution based on the project information on the distribution. Related Topics Oracle Internet Expenses Implementation and Administration Guide. Implementing Oracle Payables for Projects Integration, Oracle Projects Implementation Guide Creating a Project Related Distribution Set, Oracle Payables Implementation Guide Adjusting Project-Related InvoicesIf the project-related invoice is not accounted, then in Payables you can make the same adjustments that you can to any other unaccounted invoice. See: . However, you cannot update the account if the PA: Allow Override of PA Distributions in AP/PO profile option is disabled. If the invoice has already interfaced to Oracle Projects, you can no longer adjust the total amount of the invoice. After interfacing the invoice to Projects, to make a change to an invoice distribution, you should add a reversing distribution with the incorrect information, and then add a new distribution with the correct information. For example, if you entered a distribution for $500, with cost center 444 in the charge account, and you want to change the cost center to 445. Choose the Reverse button to create a new distribution with the same information as the distribution you want to replace, including cost center 444, but an amount of -$500. Then add a new distribution for $500 with cost center 445. For more information see: Adjustments to Supplier Costs, Oracle Project Costing User Guide. If you have interfaced the invoice from Payables to Projects, then from Projects, you can make net-zero adjustments to supplier cost expenditure items. Projects generates accounting events for the adjustments and creates accounting for the accounting events in Oracle Subledger Accounting. In Payables you can cancel an invoice after interfacing it to Projects. Viewing Adjustments Made in Oracle ProjectsYou can access Expenditure Inquiry in Projects from the Invoice Workbench to view any adjustments to the invoice that users made in Projects. On the Invoice Workbench, select View Project Adjustments option from the Tools menu to open the Find Expenditure Items window. This option is context-sensitive. Oracle Payables automatically enters find criteria based on whether your cursor is on the invoice header, an invoice line, or an invoice distribution line. You can optionally revise the find criteria before you search for the expenditure items. Adding or Modifying Project Information on InvoicesIn the Distributions window, you can update or add project information on invoices, or expense reports that you have entered in Payables. After you validate the invoice and create accounting for the invoice, you can interface the invoice to Projects. Adjusting Charge Account InformationThe Account Generator generates a charge account for each distribution that has project information. If you change the project information on an invoice distribution, the Account Generator rebuilds the account based on the new project information. You can make changes to project information either in Payables, or in Projects if the invoice has already been interfaced to Projects. For detailed information, see: Accounting Transaction Created by the Account Generator, Oracle Project Costing User Guide, Implementing Accounting for Project-Related Supplier Costs and Expense Reports, Oracle Projects Implementation Guide, and Integrating with Oracle Purchasing and Oracle Payables, Oracle Project Costing User Guide. You cannot override the charge account on a project-related distribution if the PA: Allow Override of PA Distributions in AP/PO profile option is disabled. The PA: Allow Override of PA Distributions in AP/PO profile option controls whether the Account Generator generates an account when a user enters or updates project information and the account on an invoice. The following chart shows different actions a user might perform on an invoice and how the setting of this profile option determines whether the Account Generator generates or regenerates an account. enters a new project-related invoice and enters an account.does not generate account.overrides user-entered account and generates account.enters a new project-related invoice but does not enter an account.generates account.generates account.updates a project-related invoice. User changed project information but did not change the account.generates account, and the system displays a message that the account was automatically updated.regenerates account.updates a project-related invoice. User does not change project information and tries to change the account.does not generate account, and the system allows the user to change the account.does not generate account, and the system does not allow the user to change the account.updates an invoice. User changed from a project-related invoice to a nonproject-related invoice, but did not change the account.does not generate account.does not generate account.updates an invoice. User changed from a nonproject-related invoice to a project-related invoice, but did not change the account.generates account, and the system displays message that the account was automatically updated.generates account.updates an invoice. User changed from a nonproject-related invoice to a project-related invoice, and changed the account.does not generate account.generates account.Oracle Purchasing IntegrationPayables fully integrates with Purchasing and other purchasing systems. This allows you to access your purchasing information online and match invoices to purchase orders or purchase order receipts. You can use many options in Payables to control purchase order and receipt matching. You can define invoice tolerances which Payables uses when validating your purchase order or receipt matched invoices. If you use a purchasing system other than Oracle Purchasing and you want to match invoices, you must provide that purchasing information in several Purchasing tables in order to perform the matches. See: Purchase Order Matching Database Tables, Oracle Payables Reference Guide. If you want assistance from Oracle to integrate your purchasing system with Payables, contact Oracle Consulting Services at your local Oracle office. This discussion includes the following topics: Integrated Supplier and Purchasing InformationIntegrated information in Payables and Purchasing ensures consistency of information between applications and avoids the necessity of having to enter the information more than once. Payables shares suppliers with Purchasing. You can enter a supplier in either application and use that supplier to create requisitions and purchase orders in Purchasing. Then, within Payables, you can create invoices for the same supplier and match the invoices to one or more purchase order shipments, purchase order distributions, or purchase order receipts. In addition, Payables and Purchasing share the lookup values that you use during supplier entry. You can create values for the following lookup types in the Oracle Payables Lookups window:
You can create values for the following lookup types in the Oracle Purchasing Lookups window:
For more information, see: Lookups, Oracle Payables Implementation Guide. Purchase Order and Receipt MatchingPayables shares purchase order information from your purchasing system to enable online matching with invoices. When matching based on quantity, match your billed (invoice) items to the original purchase orders or receipts to ensure that you pay only for the goods or services you ordered. If you are billed for an item in excess of the amount and quantity tolerances you define in the Invoice Tolerances window, Invoice Validation applies a hold to the invoice, which prevents payment. Note: To prevent overbilling when amount matching, enable the Shipment Amount tolerance and set it to zero. You can match a single invoice to multiple purchase order shipments and distributions, or you can match multiple invoices to a single purchase order shipment or distribution. Payables ensures that when you match an invoice to a purchase order that the invoice and purchase order have the same supplier and currency. When you match an invoice to a purchase order or receipt, Payables creates invoice distributions using the purchase order distribution accounting information. You cannot delete invoice distributions created through matching. If you incorrectly match an invoice to a purchase order, you may either cancel the invoice, or reverse the individual distributions which are incorrectly matched. Related Topics Purchase Order Shipment and Distribution MatchingYou can match to purchase order shipments, purchase order distributions, and purchase order shipments for receipt transactions. A purchase order shipment may have multiple distributions. If you are billed for only a portion of a shipment, you may want to match at the distribution level to ensure you charge the correct account If you choose not to match to the distributions, Payables prorates the match amount across the available distributions for that shipment. You may want to record a price correction for a purchase order shipment if you receive an invoice from the supplier that is an adjustment to the unit price of an invoice you previously matched to that purchase order shipment. You can record price corrections without adjusting the quantity billed on the purchase order. Note: When matching based on amount, price or quantity correction is not applicable. You can reverse purchase order matches in the Distributions window of the Invoice Workbench. You can cancel invoices matched to purchase orders in the Invoice Actions window of the Invoice Workbench. If you cancel an invoice matched to a purchase order, in addition to creating reversing distributions, Payables reverses the match to the purchase order by cancelling the invoiced quantity and amount of the original invoice distributions. Payables reduces the billed quantity and billed amount on the matched purchase order distributions by the amount of the cancelled or reversed invoice distributions. You can then match these purchase order shipments and distributions to other invoices. Related Topics Two-, Three-, and Four-way ApprovalTwo-way approval verifies that purchase order and invoice information match within your tolerances as follows:
Three-way approval adds a third criterion to verify that receipt and invoice information match with the quantity tolerances you define:
Four-way approval adds a fourth criterion to verify that acceptance documents and invoice information match within the quantity tolerances you define:
When you match to a purchase order, Payables automatically performs two-way approval. In the Purchasing Options window you can choose to additionally use three-way or four-way approval. You can change the Match Approval Level option at the supplier and purchase order shipment levels. If the invoice and purchase order do not match within the tolerances you define for quantity and price, Invoice Validation places a matching hold on the invoice. You must release the hold before you can pay the invoice. Related Topics Amount-Based Matching of Purchase OrdersUse amount-based matching of purchase orders to match supplier invoices for services based on the invoice amount. Purchasing specifies Amount as the match basis. You can perform amount matching on the following kinds of invoices: Credit Memo, Debit Memo, Expense Report (from Invoice Workbench only), Mixed, Prepayment, Recurring, and Standard. When matching invoices based on amount, match your billed (invoice) amount to purchase order shipments or receipts to ensure that you pay only for the rate or value of the services. You enter invoices and create invoice distributions similar to quantity matching. However, you provide an amount, rather than quantity and unit price, as the basis to create distributions. You can further match a distribution to a purchase order by clicking on the Distribute button, selecting each purchase order distribution, and entering the applicable amount. If you have not distributed while selecting a shipment, Payables prorates the appropriate purchase order distribution. In some instances, you may enter an invoice against a service shipment with different rates for regular and overtime hours. If you want to match to the service shipment and also track the regular and overtime hours differently, you match to the same shipment twice and enter the appropriate amount each time. You can optionally enter the hours worked in the Quantity Invoiced field and the rate in the Unit Price field. You can also allocate charges during matching by specifying the tax, freight, and miscellaneous charges. Invoice validation is similar to quantity matching except if the accrue on receipt option is set to No, Payables calculates the amount variance, which is the excess amount invoiced and expensed during accounting. Payables does not have a separate accounting entry for this but records it separately for encumbrance. In addition to the entries recorded by Payables in encumbrance accounting, Payables creates amount variance encumbrance entries if the PO and Invoice Encumbrance types are different and reverses any amount variance during invoice accounting in accrual basis and during payment accounting in cash basis. Since quantity-related and price-related validations are not applicable, Payables does not check tolerances related to quantity and price. Invoice tolerances specified for the quantity and price are also not applicable. Instead, Payables validates the invoice only on the following applicable holds when matched to a service order or receipt: Final Matching, Currency Difference between Invoice and PO, PO Approval, Receipt Exception, Shipment Exception, Shipment Amount, Total Amount, and Exchange Rate Amount. Payment on ReceiptIf you have installed Oracle Purchasing, you can increase the efficiency of your procurement cycle by generating payments to suppliers based on receipt transactions. These receipts include Advance Shipment Notices (ASNs) and Advance Shipment and Billing Notices (ASBNs) that you receive electronically in Purchasing. See: Advance Shipment Notice (ASN/ASBN), Oracle Purchasing User's Guide. You can set up your suppliers to be paid either on receipt or delivery, and you can choose the level of invoice consolidation: packing slip, receipt, or supplier pay site. After receipt or delivery transactions are created, you can submit the Pay on Receipt AutoInvoice Program to automatically import invoices that are matched to corresponding purchase orders. After the Payables Open Interface Import process completes, you can then validate and pay these purchase order matched invoices using standard Payables payment processing functionality. See: Payment on Receipt, Oracle Purchasing User's Guide. If you enable the supplier site option, Create Debit Memo from RTS Transaction, then when you enter RTS (Return to Supplier) transactions in Purchasing, the system automatically creates unvalidated debit memos in Payables that are matched to the purchasing document specified on the purchase order shipment. Invoice VariancesIf you use accrual basis accounting, and have Oracle Purchasing installed, then Payables records variances when you validate and create accounting entries for an invoice distribution matched to either a purchase order or receipt. Variances are the differences between the purchase order and invoice in price, quantity, and, for foreign currency transactions, exchange rate. Invoice variances include nonrecoverable tax. Variance is calculated based on the invoice amount, not including any prepayment distributions. The following formulas show how Payables calculates the invoice amount, purchase order amount, and the variance amounts. Purchase Order AmountPO Qty x PO Price x PO/Receipt RateInvoice Distribution AmountInvoice Qty x Invoice Price x Invoice RateExpense or Accrual AmountAll in functional currency if this is a foreign currency transaction.Invoice Distribution Amount - (Invoice Price Variance + Exchange Rate Variance)Invoice Price Variance (IPV)Invoice Qty x (Invoice Price - PO Price) x Invoice RateQuantity Variance(Invoice Qty - PO Qty) x PO Price x PO RateExchange Rate Variance (ERV)Invoice Qty x PO Price x (Invoice Rate - PO/Receipt Rate) Note: The balancing entry to encumbrances is the reserve for encumbrances. The associated encumbrances use the same formulas; for example, the encumbrance for a purchase order is calculated according to the formula PO Qty x PO Price x PO Rate. During Invoice Validation, Payables applies holds to purchase order matched invoices that exceed tolerances you defined for price, quantity, and exchange rate differences in the Invoice Tolerances window. Related Topics Invoice Tolerances, Oracle Payables Implementation Guide Accounting Methods, Oracle Payables Implementation Guide Variance AccountsThe accounts to which Payables records invoice distributions and any related variance distributions depend on your accrual method (receipt or period end), and the item type (expense or inventory). If you use the receipt accrual method, (also known as perpetual accrual), the system automatically records an accrual when you record an item as received in Oracle Purchasing. When you create accounting entries for the invoice, Payables reverses this accrual and records the AP liability. If you use period end accruals, you run the Accrual Process for Period End Accruals and enter a reversing manual journal entry for the AP accrual. When you create accounting entries for the invoice, Payables records the expense and the AP liability. For inventory items you must use the receipt accrual method. For expense items you select your Accrue Expense Items Purchasing option, either On Receipt or Period End. If you use Period End Accrual, and if the CCID segments are the same, then the system summarizes IPV and ERV expenses with the distribution and nonrecoverable tax expenses in a single expense entry. Any lines with different CCIDs appear as separate entries. Payables creates all variance distributions at invoice validation time. Expense ItemsThe following table shows the variance accounts used for expense items: On ReceiptExpense AP Accrual AccountExpense AP Accrual AccountCharge AccountCharge AccountPeriod EndCharge AccountCharge AccountCharge AccountCharge AccountInventory ItemsThe following table shows the variance accounts used for inventory items: On ReceiptInventory AP Accrual AccountInventory AP Accrual AccountInvoice Price Variance AccountExchange PO Rate Variance Gain or Loss AccountDefining Accrual and Variance AccountsYou define accounts in different windows of different products. To see which windows inherit accounts you define, see: . Exchange PO Rate Variance Gain/Loss Account. Accounting Region of the Financials Options window in Payables or Purchasing. See: Defining Financials Options, Oracle Payables Implementation Guide. Expense Accounts Payable Accrual Account. Defining Accrual Options Region of the Purchasing Options window in Purchasing. See: Defining Accrual Options, Oracle Purchasing User's Guide. Inventory Accounts Payable Accrual Account. Organization Parameters window in Oracle Inventory. See: Organization Parameters Window, Oracle Inventory User's Guide. Invoice Price Variance Account. Organization Parameters window in Inventory. See: Organization Parameters Window, Oracle Inventory User's Guide. Related Topics Invoice Tolerances, Oracle Payables Implementation Guide Overview of Receipt Accounting, Oracle Purchasing User's Guide Defining Purchasing Options, Oracle Purchasing User's Guide Reconciling A/P Accrual Accounts Balance, Oracle Purchasing User's Guide Accrual Write-Offs, Oracle Purchasing User's Guide Receipt Accruals - Period End Process, Oracle Purchasing User's Guide Retroactive Price Update on Purchasing DocumentsIf your enterprise uses Oracle Purchasing's Retroactive Price Update on Purchasing Documents feature, your purchasing department can retroactively adjust the price of a previously invoiced items and in Payables. The following text applies only if your purchasing department uses this optional feature. Important: In certain countries, unless you receive special dispensation from the fiscal authorities, this feature may not be appropriate because it automatically generates invoices without first receiving a corresponding invoice document from a supplier. If your Oracle Purchasing system is set up to use this feature, when an Oracle Purchasing user updates the price on an item that has already been invoiced, and then the user submits the Create Adjustment Documents in Payables program, the program adjusts the total invoiced amount to the final negotiated purchasing price. The two types of adjustment invoices are:
These adjustment invoices can be positive, negative, or zero amount. When the original invoice and its related adjustment documents are paid, the net effect is as if the original invoice had always had the new price. The supplier is paid the appropriate amount, and the accounting is adjusted accordingly. You cannot manually enter these types of invoices, nor can you adjust or cancel them. You can view, report on, validate, account for, and pay them. If you want to effectively cancel one of these invoices, the Purchasing user can set the price back to the original price on the purchase order and resubmit the Create Adjustment Documents in Payables program. This will generate new adjustment documents to net to zero any outstanding adjustment documents.
More Information
Because this is an Oracle Purchasing feature, most documentation for this feature resides in the Oracle Purchasing user guide and online help. Related Topics Retroactive Price Update on Purchasing Documents, Oracle Purchasing User Guide Closing Purchase OrdersPayables closes a purchase order when the quantity billed and the quantity received (if you require receipt on the purchase order shipment) against the purchase order are both greater than or equal to the quantity ordered less the quantity cancelled on the purchase order. Payables displays a warning message if you try to match to a closed purchase order, but you can still complete the match unless the shipment is finally closed. When you submit Invoice Validation, Payables applies the appropriate matching hold(s). You can reopen a closed purchase order in Purchasing by adding a new shipment, over-receiving within your tolerance, or changing the quantity for a shipment. Payables closes a purchase order shipment when the quantity billed and the quantity received (if you require receipt on the purchase order shipment line) against the purchase order shipment are both greater than or equal to the quantity ordered less the quantity cancelled on the purchase order shipment. In Oracle Purchasing, you can manually close a purchase order at the header, release, line, and shipment levels and also enter a Closed Reason, which is displayed in the Match to Purchase Order and Match to Receipts windows. This indicates that the record was intentionally closed and should not be matched. For detailed information, see: Oracle Purchasing User Guide. Note: The Finally Closed status of a purchase order indicates that the purchase order is permanently closed and no further actions can be performed against it in either Purchasing or Payables. Related Topics Receipt AccrualPurchasing provides you with a number of windows and reports to support receipt accrual for purchase orders you match to. You can report on the balance of the receipt accrual accounts and manually write off any accrual transactions. You can then report on the transactions you chose to write off. If goods receipt accruals are enabled, either using the perpetual or Period-end method, and the Enable Recoverable Tax option is enabled, then the receipt accruals will be accounted inclusive of nonrecoverable tax to reflect the liability on the receipt of goods. See: . Related Topics Accrual Reconciliation Report, Oracle Purchasing User's Guide Accrual Write-Off Report, Oracle Purchasing User's Guide Overview of Receipt Accounting, Oracle Purchasing User's Guide Holding Invoices With Invalid Purchase Order NumbersIf a supplier sends you an invoice that is either missing a purchase order number, or has an invalid purchase order number, then you can manually apply the Invalid PO hold to the invoice to prevent payment of it. You can then submit the Invalid PO Supplier Notice to automatically generate a notice that informs the supplier that you require a valid purchase order number. See: . Purging Payables and Purchasing InformationPayables maintains all invoice, purchase order, and related records you enter in Payables and Purchasing. You may want to delete these records periodically to limit the amount of space required for your Payables and Purchasing tables. You can use the Purge feature to delete all invoices and payments in Payables, and all requisitions, purchase orders, and receipts in Purchasing. You can also delete inactive suppliers. When you purge payables and purchasing information, Payables maintains summary records of all purged information for reference and audit purposes. Related Topics Oracle Property Manager IntegrationYou can use Payables to make payments for leases that you record in Oracle Property Manager. In Property Manager, you abstract a lease, authorize payment, and then export the lease payment information to Payables by using the Export Payments to Payables window in Property Manager. This loads the invoice information into the Payables Invoice Open Interface table. To import this information into Payables and create Payables invoices, use the Source of Oracle Property Manager when you submit the Payables Open Interface Import program. You can then query, validate, and pay the lease invoices in Payables. Related Topics Oracle Property Manager User's Guide Oracle Grants Accounting IntegrationIf you install Oracle Grants Accounting, you can record an award ID in the following windows:
If you enter an award ID in the Invoices window, it defaults to invoice distributions. You can also add award ID information to Distribution Sets to default the award ID to distributions. In the Distributions window you can add a value for award ID to any imported invoice distributions. Oracle Inventory IntegrationTo comply with the European Union's Intrastat requirements, you might need to record information associated with the movement of goods between statistics-gathering countries. If you install Oracle Inventory, and want to comply with Intrastat reporting requirements, you can record statistics for invoices. For details, see: Collecting and Reporting Movement Statistics, Oracle Inventory User's Guide Invoice Window ReferencesMatch to Purchase Orders Window ReferenceThe Match to Purchase Orders window is a customizable folder in which you can move, resize, and hide fields in the window. See: Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide. Accounting Date. Date accounting entries are created. Associated Charges Freight/Misc. Total of associated Freight or Miscellaneous charges. Award. If you use Oracle Grants Accounting, the award number of the project. Allocate. Check the Allocate check box for the shipments for which you want to prorate tax, freight, or miscellaneous. For detailed information see: . Buyer. Buyer who created the purchase order associated with this purchase order shipment. Closed Code. Indicates whether a purchase order shipment has been closed for invoicing. Closed Reason. The reason the purchase order line or shipment was closed. Deliver To. Person who submitted the purchase requisition for the item. Distribution Total. Payables displays the sum of the distributions for the invoice you are matching to the purchase order. This number includes Match Amounts that you have not yet saved. Final Match. Check the Final Match check box only if you are certain this is a final match against the related purchase order. Once you validate a final matched invoice distribution, you cannot update the Final Match field for the distribution or match other invoices to this shipment. For detailed information, see: . Freight/Misc. Check this check box for the shipments that you want to prorate to freight or miscellaneous lines. For detailed information see: . Invoice Amount. Payables displays the amount of the invoice you are matching to the purchase order. Item Category. Item category from the purchase order shipment line. Item Description. Description of an item from the purchase order shipment line. Item Num. Payables displays the item number from the purchase order shipment line. Use this information to compare items ordered on a purchase order shipment line with items billed on your invoice. Last Receipt. Last date someone entered receiving information for a purchase order shipment in Purchasing. Line. Payables displays the purchase order shipment line number. You can match an invoice to one or more purchase order shipment lines. Match. Check this check box to select a shipment and to enter matching data for it. Note that when you check this box the information in the Shipment Qty display only region shows the shipment information for the selected shipment line. Match Amount. Total currency amount you want to match. If you enter Quantity Invoiced, Payables calculates and enters this value. (Quantity Invoiced x Unit Price = Match Amount). Match Basis. Basis on which invoices are matched to purchase orders. Options include: Price Correction, Quantity Correction, Invoice Line Correction, Invoice Line Matched to Purchase Order, Invoice Line Matched to Receipt, Other Charge Invoice Line Matched to Receipt, or Not Matched. You can also define custom match types in the Invoice Line Match Type lookup. Need-By Date. The need-by date, as specified in the purchase order shipment. Payment Type. The payment type as specified on the purchase order. PO Number. Payables displays the purchase order number of the shipment. Purchase Order Payment Terms. Payment terms associated with the purchase order shipment. Purchase Order Freight Terms. Freight terms associated with the purchase order shipment. Project/Task/Expenditure. If you have Oracle Projects installed, a project to charge the expenditures on an invoice to a specific project, task, or organization. The system uses the project information you enter to create an account that defaults to the invoice distribution. You can override this project information at the invoice distribution. If you change these values at the invoice header level, then the values will not affect any existing distributions. Note: If you enter project information, you must enter a value for Task unless you have matched to a purchase order with project information with a null task ID. A purchase order can have a null task ID only if its destination is Inventory or Shop Floor. If the destination is Inventory or Shop Floor, the project information is used by Project Manufacturing. Quantity Invoiced. Number of units invoiced. This value defaults from the unbilled purchase order shipment quantity. If you enter Unit Price and Match Amount, Payables calculates and enters this value. (Quantity Invoiced x Unit Price = Match Amount). Release. Payables displays the Release associated with a blanket purchase order. Ship-To Location. Payables displays the shipment location of the item from the purchase order shipment line. Shipment Item Description. The description of the item as it appears on the purchase order shipment. Shipment Num. Number of the purchase order shipment. Supplier Item. Supplier item number from the purchase order shipment line. Unit Price. Price per unit. This value defaults from the purchase order shipment unit price. You can update this value at the shipment level only. If you enter Quantity Invoiced and Match Amount, Payables calculates and enters this value. (Quantity Invoiced x Unit Price = Match Amount). If you are recording a price correction, you can adjust the price without affecting the quantity. You cannot adjust the Unit Price if you are matching to an amount-based purchase order shipment with a Unit Price of 1, for example, a purchase order for labor service charges where the Unit Price is 1 and the labor service amount is entered in the Quantity Invoiced field. Display Only RegionInvoice Amount. Payables displays the amount of the invoice you are matching to the purchase order. Line Total. The total of the invoice lines. Shipment Quantity. Payables displays for the currently selected purchase order shipment the following information:
Payment Terms. Payment terms associated with the purchase order shipment. Freight Terms. Freight terms associated with the purchase order shipment. Freight/Misc. If you have used the Freight/Misc. check box, the amounts you have allocated for Freight or Miscellaneous charges. ButtonsView PO. Choose this button to view the purchase order. Distribute. Choose this button to navigate to the Match to Purchase Order Distributions window. Match. Choose this button to complete the match. Related Topics Match to Receipts Window ReferenceThis window is a customizable folder. Note that in the default folder, many of the fields listed below are hidden. You can create custom folders by unhiding, hiding, moving, resizing, and renaming fields in this window. See: Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide. Accounting Date. Date accounting entries are created. Award. If you use Oracle Grants Accounting, the award number of the project. Allocate. Check the Allocate check box for the shipments for which you want to prorate tax, freight, or miscellaneous. For detailed information see: . Bill of Lading. Bill of Lading for the purchase order receipt. Buyer. Buyer who created the purchase order associated with this purchase order shipment. Closed Code. This indicates whether a purchase order shipment has been closed for invoicing. Closed Reason. Reason the purchase order line or shipment was manually closed. Container. Number of the shipping container in which the received goods arrived. Deliver To. Person who submitted the purchase requisition for the item. Distribution Total. The sum of the distributions of the invoice you are matching to the purchase order. This number includes Match Amounts that you have not yet saved. Freight Carrier. Freight carrier (for example, Rail). Freight/Misc. Check the Allocate check box for the shipments for which you want to prorate tax, freight, or miscellaneous. For detailed information see: . Item Category. Item category from the purchase order shipment line. Item Description. Item description from the purchase order shipment line. Item Num. Item number from the purchase order shipment line. Inventory Org. Inventory organization to which the received item belongs. Invoice Amount. Payables displays the amount of the invoice you are matching to the purchase order receipt. Item Num. Item number from the purchase order shipment line. Item Category. Item category from the purchase order shipment line. Item Description. Item description from the purchase order shipment line. Match. Check this check box to select a receipt and to enter matching data for it. Note that when you check this box the information in the Receipt Qty display only region shows the shipment information for the selected shipment line. Match Amount. Total currency amount you want to match. If you enter Quantity Invoiced, Payables calculates and enters this value. (Quantity Invoiced x Unit Price = Match Amount). Match Basis. Basis on which invoices are matched to purchase orders. Options include: Price Correction, Quantity Correciton, Invoice Line Correction, Invoice Line Matched to Purchase Order, Invoice Line Matched to Receipt, Other Charge Invoice Line Matched to Receipt, or Not Matched. You can also define custom match types in the Invoice Line Match Type lookup. Need-By Date. The need by date as specified in the purchase order shipment. PO Line. Purchase order line number. PO Number. Number of the purchase order shipment. Packing Slip. Packing slip number entered for the receipt. Payment Type. The payment type specified on the purchase order shipment. Project, Task, Expenditure. If you have Oracle Projects installed, associate an invoice with a project to charge the expenditures on an invoice to a specific project, task, or organization. The system uses the project information you enter to create an account that defaults to the invoice distribution. You can override this project information at the invoice distribution. If you change these values at the invoice header level, then the values will not affect any existing distributions. Note: If you enter project information, you must enter a value for Task unless you have matched to a purchase order with project information with a null task ID. A purchase order can have a null task ID only if its destination is Inventory or Shop Floor. If the destination is Inventory or Shop Floor, the project information is used by Project Manufacturing. Qty Invoiced. The unbilled quantity or number of units invoiced. This value defaults from the receipt shipment quantity. If you enter Unit Price and Match Amount, Payables calculates and enters this value. (Quantity Invoiced x Unit Price = Match Amount). Receipt Date. The date of the receipt. Receipt Line Num. The receipt shipment line number. You can match an invoice to one or more receipt shipment lines. Receipt Num. The receipt number of the shipment. Release Number. Release number of the blanket purchase order shipment. Ship To Location. Location where the items are being shipped. Shipment Item Description. The description of the shipment item, as it appears on the purchase order. Shipment Num. Purchase order shipment number. Shipment Type. The shipment type from the purchase order shipment line. Shipped Date. Date the items were recorded as shipped. Supplier Item. Supplier item number from the purchase order shipment line. Transaction Date. The date the goods were recorded as reviewed. UOM. Unit of measure that was entered on the receipt shipment line, for example, Each, Days, or Dozen. You can compare the unit of measure on a receipt shipment line to the unit of measure on your invoice. The quantity invoiced must be in the same unit of measure as the quantity ordered on the receipt. Unit Price. Price per unit. This value defaults from the receipt shipment unit price. You can update this value at the shipment level only. If you enter Quantity Invoiced and Match Amount, Payables calculates and enters this value. (Quantity Invoiced x Unit Price = Match Amount). If you are recording a price correction, you can adjust the price without affecting the quantity. You cannot adjust the Unit Price if you are matching to an amount- based receipt shipment with a Unit Price of 1, for example, a receipt for labor service charges where the Unit Price is 1 and the labor service amount is entered in the Quantity Invoiced field. Waybill Airbill Num. The waybill/airbill number. Display Only RegionInvoice Amount. Payables displays the amount of the invoice you are matching to the purchase order receipt. Line Total. The total of the lines on the invoice. Purchase Order. Payables displays purchase order information for the currently selected receipt:
Receipt Quantity. Payables displays receipt quantity information for the currently selected receipt:
Associated Charges. If you have used the Freight/Misc. check box and window to allocate freight or miscellaneous charges, Payables displays the amounts you have prorated for Freight or Miscellaneous charges. ButtonsMatch. Choose this button to complete the match. Distribute. Choose this button to navigate to the Match to Receipt Distributions window. Invoice Overview. Choose this button to view the invoice in the Invoice Overview window. View Receipt. Choose this button to view the receipt. Invoice Batches Window ReferenceYou use the Invoice Batches window to set defaults for a group of invoices you enter in an invoice batch. If you change an invoice batch default, the change will apply only to invoices you subsequently enter in the invoice batch. For example, if you enter half a batch with the Standard invoice Type default and then change the batch invoice Type default to Prepayment, only the invoices you enter after the change will get Prepayment as a default invoice type. After you enter invoices in a batch, you can review them in the Invoices window. If you are reviewing batch invoices in the Invoices window and want field references, see: . All amounts in the Invoice Batches window are in the invoice currency. This window is a customizable folder. Note that in the default folder, many of the fields listed below are hidden. You can create custom folders by unhiding, hiding, moving, resizing, and renaming fields. See: Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide. Actual Invoice Count. Payables displays the number of invoices you have entered in the batch. Actual Invoice Total. Payables displays the cumulative sum of the invoice amounts of the invoices you have entered in the batch. Batch Name. Name of the invoice batch. Control Amount. Enter the sum of the invoice amounts in the batch. Control Count. Enter the number of invoices in the batch. Currency. The default currency for all invoices in the batch. After you save an invoice, you cannot change the Currency. You can use the Invoice Actions window to cancel the invoice. You can then re-enter the invoice with the correct currency. Date. Invoice batch date. Document Category. Payables uses the document category to assign a unique voucher number to each invoice if you assign an automatic sequential numbering sequence to the document category. You can enter a value in this field if you enable the Document Category Override Payables option. If you do not enable your Sequential Numbering profile option, Payables provides no default for this field and you cannot enter a value. GL Date. The default GL Date for each invoice in the batch and its distributions. Must be in an open or future period. If you do not provide a batch default, the default for each invoice is the invoice date, goods received date, or system date, depending on your GL Date Basis Payables option. Hold Name. Hold you want to apply to each invoice. Hold Reason. Payables displays the Hold description if you have entered a Hold Name. Invoice Count Difference. Payables displays the Control number minus the Actual number. Invoice Total Difference. Payables displays the Control amount total minus the Actual amount total. Liability Account. Account for the liability of each invoice. If you do not enter a batch default, Payables uses the supplier site Liability Account as a default for each invoice. Payables uses the liability account when you create accounting entries for your invoices if you use accrual basis accounting. Payables credits an amount equal to the sum of your invoice distributions. You cannot enter more than one liability account for an invoice. If you enable the Automatic Offsets Payables option, Payables automatically allocates the invoice liability across multiple balancing segments, rather than using one liability account. See: . Pay Group. Use Pay Group to group invoices from multiple suppliers in a payment batch. Payment Currency. Payables enters the Invoice Currency as the default. If the Invoice Currency is not a fixed-rate currency, you cannot update the value. If the Invoice Currency is a fixed-rate currency such as Euro or an EMU national currency, you can change the Payment Currency value to an associated fixed-rate currency. Payment Priority. A number, between 1 (high) and 99 (low), that represents the priority of a payment. If you do not enter a batch default, then the default payment priority for each invoice will be from the supplier site. You can enter a payment priority range as a criteria for selecting invoices for a payment batch. Payment Terms. Payment terms Payables uses to create one or more scheduled payments for an invoice. If you want the terms to default from the purchase order, then leave this field blank. Type. The type of invoice you select determines which processing options Payables makes available to you.
ButtonsInvoices. Choose the Invoices button to navigate to the Invoices window to enter the invoices in the batch. Payables automatically defaults the invoice batch defaults you entered to each invoice you enter. You can override any invoice batch defaults. Validate. After you have entered invoices in an invoice batch, choose the Validate button to submit Invoice Validation for each invoice in the batch. In the Invoice Holds tab, you can review any invoice holds and releases that Payables applies during Invoice Validation. Create Accounting. After you have entered invoices in an invoice batch, choose the Create Accounting button to create accounting entries for each invoice in the batch. See: . Related Topics Invoices Window ReferenceThe Invoices window is a customizable folder. Note that in the default folder, many of the fields listed below are hidden. You can create custom folders by unhiding, hiding, moving, resizing, and renaming fields in this window. See: Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide. In the Invoices window, all values are displayed in the invoice currency, except for the Amount Paid, which is displayed in both the invoice and payment currency. Supporting Dispute Resolution Two new fields, Original Invoice Amount and Dispute Reason, are introduced in the invoice workbench for dispute resolution. These are Display Only fields and are hidden and use Show Fields folder option to display these fields. Actual Total. If you are entering or reviewing an invoice batch, Payables displays the cumulative total of the invoice amounts in the batch. Approved Amount, Approval Status, Approval Description. Use these fields for your reference. For example, you might want to use these fields for future reference when you force approve an invoice that was manually approved for payment outside of the Invoice Approval Workflow, for example, by a hardcopy signature. These fields are not populated by Payables or used by Payables in any way. Award Number. If you use Oracle Grants Accounting, enter the award number of the project. Batch Actual Total. If you are entering or reviewing an invoice batch, Payables displays the cumulative total of the invoice amounts in the batch. Batch Control Total. If you are entering or reviewing an invoice batch, Payables displays the number you entered in the Control Total field of the Invoice Batches window. Batch Name. If you entered this invoice in an invoice batch, Payables displays the batch name. Business Category: A tax driver field used by E-Business Tax to determine and calculate applicable taxes. Cancelled By / Date / Amount. The name of person who cancelled an invoice, date of cancellation, and original amount of cancelled invoice. Create Freight Distribution. Check this check box to open the Freight window. Payables automatically creates a freight distribution from information you enter in the Freight window. If you have enabled the Automatically Create Freight Distribution Payables option and have entered a default Freight Account, Payables automatically checks this check box and enters a default freight account in the Freight window. You can override this account. Credited Invoice. The invoice being credited, when the Quick Credit check box is enabled. Date Invoice, Goods Received. Payables enters the Terms Date as default if you have set Invoice Received or Goods Received as the terms date basis for the supplier site. If you change the default, Payables automatically updates the Terms Date and recalculates your scheduled payment. Description. A description (up to 240 characters) of the goods and services listed on the invoice. Used as the default for distributions. Description appears on the payment document remittance. Discountable Amount. Invoice amount eligible for discount. The default value for positive and negative amount invoices is the invoice amount, and the default value for invoices on which you have withheld tax is the adjusted invoice amount. If your supplier discount does not apply to tax, enable the Exclude Tax from Discount Payables option to subtract the tax amount from the invoice amount when calculating the default Discountable Amount. However, Payables will not subtract Offset type taxes. You can manually change the Discountable Amount field. 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. For example, you are applying a $100 prepayment that has a $10 discount. Before the system creates the scheduled payments, you should subtract $100 from the Discountable Amount. However, we recommend that you do not modify this amount to reduce it by the tax amount if your Exclude Tax From Discount Calculation Payables option is enabled. See also: . Distribution Set. Used to automatically create invoice distributions when invoice is not matched to a purchase order or when you do not want to enter invoice distributions manually. Payables enters the supplier site default Distribution Set, if one exists. If you want to use a Distribution Set, you must enter one before you navigate to the Distributions window. Distribution Total. Sum of the Item, Freight, and Miscellaneous Invoice distributions in the Distributions window. This total does not include Tax, Withholding Tax, or some Prepayment type distributions. When you enter an invoice that references a prepayment, the distribution total will include Prepayment distributions and any associated tax distributions that have the Prepayment on Invoice check box enabled. If the Distribution Total does not match the Invoice Amount, Payables will apply a hold to your invoice during Invoice Validation. Document Approval Status. The status of the entire invoice (document) with respect to the Invoice Approval Workflow program. For more information on the approval status, see: . Document Needs Reapproval. Indicates that the invoice needs to be processed by the Invoice Approval Workflow again. Selecting this check box updates the Document Approval Status field to Needs Reapproval. Document Category Name. Default document category for an invoice. Payables predefines a document category for each invoice type. If you enable the Sequential Numbering profile option, this document category defaults to an invoice during entry. Payables uses the document category to assign a unique voucher number to an invoice if you assign an automatic sequential numbering sequence to the document category. If you do not enable your Sequential Numbering profile option, Payables provides no default for this field and you cannot enter a value. Document Sequence. Sequence name assigned to an invoice, based on the document category of the invoice. Your system administrator defines the sequential numbering sequences used by Payables and assigns them to a document category, Exchange Rate, Exchange Date. Foreign currency rate information Payables uses to convert a foreign currency invoice amount to your functional currency. See: and . Note that if the Invoice Currency and your functional currency are different associated fixed-rate currencies, such as Euro and an EMU national currency, Payables displays the fixed rate and you cannot update this value. If you are entering an exchange rate between a National Currency Unit of the European Monetary Union (EMU), and a non-EMU currency, then Payables can calculate the exchange rate if you provide the exchange rate between the non-EMU currency and the euro. See: . Fiscal Classification. A tax driver used by E-Business Tax to determine and calculate applicable taxes. Freight Amount. The freight amount you want Payables to exclude when Payables calculates the default discountable amount for an invoice, if your Exclude Freight from Discount option is enabled for the supplier site. Ledger Currency. Currency of your ledger. Ledger Curr Amount. If you enter a foreign currency invoice and have provided an exchange rate for the invoice currency, rate type, and rate date, then Payables automatically calculates and displays the functional currency of the invoice. You can enter a value in this field only if the Payables option Calculate User Exchange Rate is enabled, if you use the exchange rate type User, and if the invoice is not yet accounted. GL Date. The default GL Date for the distributions for this invoice. Must be in an open or future period. The default is the invoice date, system date, or goods received date depending on your GL Date Basis Payables option. If you change the date it will not affect existing distribution GL Dates, but it will default to any new distributions you enter. Internal Recording Date. The date the invoice was recorded. Invoice Amount. The invoice amount including tax, freight, and miscellaneous charges. This amount does not include the Prepaid Amount (Prepayment distributions) or Withheld Amount (Withholding Tax distributions). Invoice Curr. The currency of the invoice. After you save your invoice, you cannot change the currency. You can use Invoice Actions to cancel the invoice, then re-enter the invoice with the correct currency. Invoice Date. Date on an invoice. Payables uses the system date as a default. Payables may use the Invoice Date as the Terms Date and GL Date for an invoice, depending on your system setup. If your GL Date Basis is Invoice Date, the Invoice Date must be in an open or future period. Invoice Num. The invoice number provided by the supplier on the invoice. Must be unique for the supplier. Payables uses the system date as a default. Liability Account/Description. Account for the invoice liability. Payables uses the supplier site Liability Account as a default. Payables uses this account when you create accounting entries for your invoices if you use accrual basis accounting. Payables credits an amount equal to the sum of your invoice distributions. You cannot enter more than one Liability account for an invoice. If you enable the Automatic Offsets Payables option, Payables automatically allocates the invoice liability across multiple balancing segments, rather than using one liability account. See: . Also, if you enable Automatic Offsets but do not use encumbrance accounting, if you update the liability account for an invoice, you must resubmit Invoice Validation before you can pay the invoice. (Payables sets the unaccounted distributions to Needs Revalidation so you need to resubmit Invoice Validation). Match Action. The match level: Purchase Order, Invoice, Receipt. These fields default from the supplier site you had set up. If the invoice is finally matched to a PO that requires matching to a receipt, then the value is not changed. Operating Unit. The operating unit for the invoice. Pay Alone. A Pay Alone invoice is paid with its own payment document without including other invoices for the supplier. You cannot choose this option if the invoice is partially paid, has been selected for payment in a payment batch, or has one or more withholding distributions. Payment Amount. Invoice amount displayed in payment currency. Payment Curr. If the Invoice Currency is not a fixed-rate currency, then the payment currency will be the same as the Invoice Currency and you cannot enter a value in this field. If the payment currency is a fixed-rate currency, such as Euro or another EMU currency, you can change it to an associated currency. For fixed-rate currencies, the payment currency value defaults from the supplier site, or, if you are using batch control, it defaults from the batch. If you aren't using batch control and the supplier site has no default payment currency, the value defaults from the Invoice Currency. If you change the Invoice Currency then the value for payment currency will change to the value for invoice currency. Pay Group. Use Pay Group to group invoices from multiple suppliers for a payment in a payment batch. Payment Method. The payment method by which you pay the supplier site. Payables defaults the Payment Method to all new scheduled payments of the invoice. Payables enters the supplier site default Payment Method, if one exists. Note that if you change the payment method after Payables has calculated scheduled payments for the invoice, Payables will recalculate the scheduled payments and you will need to re-enter any manual changes you have made to scheduled payments, including scheduled payment holds. Payment Rate. If you are making a payment in a different currency than the invoice, and both currencies are associated fixed-rate currencies, Payables displays the fixed cross rate. You cannot update this value in this window. Payment Rate Type. If the Payment Currency is different from the Invoice Currency and both are fixed-rate currencies, Payables displays EMU Fixed. Payment Rate Date. The date the Payment Rate is effective. If the payment currency and invoice currency are associated fixed-rate currencies, then when you enter the Invoice Date, Payables enters the invoice date value as the payment rate date. PO Number. The purchase order you are matching the invoice to. Enter this field when creating or adding lines to an invoice. Prepaid Amount. The sum of prepayment amounts that have been applied to an invoice. This is the sum of the invoice's Prepayment type distributions. Prepayment Type.
If you are not sure which Type you want, you can change from Permanent to Temporary at any time, and you can change from Temporary to Permanent if you have not applied the prepayment to an invoice. Prepayment PO Number. Associate a prepayment with an open purchase order for the same supplier. If you later apply the prepayment to an invoice, it must be to an invoice matched to this purchase order. Note: Even if you match a prepayment to a purchase order, you are not restricted to the value you enter in this field. You can leave this field blank or you can enter a different purchase order number. Project/Task/Expenditure information. If you have Oracle Projects installed, associate an invoice with a project to charge the expenditures on an invoice to a specific project, task, or organization. The system uses the project information you enter to create an account that defaults to the invoice distribution. You can override this project information at the invoice distribution. If you change these values at the invoice header level, then the values will not affect any existing distributions. Note: If you enter project information, you must enter a value for Task unless you have matched to a purchase order with project information with a null task ID. A purchase order can have a null task ID only if its destination is Inventory or Shop Floor. If the destination is Inventory or Shop Floor, the project information is used by Project Manufacturing. Quick Credit. Enable this check box to create a quick credit from this invoice. See: Rate Type. Type of exchange rate between invoice and functional currency. See: . Ready for Approval. Indicates that an invoice is ready to be processed by the Invoice Approval Workflow. The Invoice Approval Workflow will not process an invoice if this check box is unchecked. If you want to delay an invoice from being selected for approval, then uncheck this check box. This check box is enabled by default for all invoices, even if you don't use the Invoice Approval Workflow feature. See: . Related Invoice. The invoice that is associated with the selected invoice. For example, a prepayment that is applied to a standard invoice. Release Amount Net of Tax. Remit To Bank Account Name. The supplier site's remit-to bank account for the invoice currency. If there is no primary bank account for the supplier site, Payables defaults the primary bank account for the supplier. Remit To Bank Account Number. The supplier site's remit-to bank account for the invoice currency. If there is no primary bank account for the supplier site, Payables defaults the primary bank account for the supplier. Requester. Person who requested the goods or services on the invoice. If you use Invoice Approval Workflow, you can define rules that use this value to generate a hierarchical list of approvers for the invoice. Self Assessed Tax Amount. Tax that was not charged by a supplier but that you are liable for paying to your tax authority. See: . Settlement Date. The date after which you can apply a temporary prepayment. Payables adds your Settlement Days Payables option to the system date for employees, and uses the system date for all other suppliers. Site. The supplier site address to which you want to remit payment. If you print checks, Payables prints this address on the check. If you designate a primary pay site for a supplier then that pay site defaults to this field for all invoice types during invoice entry. Supplier. Name of the supplier to which you want to remit payment. Supplier Num. Identification number for a supplier in your system. Supplier Tax Invoice Date.The date on the which the supplier charged tax, as shown on the purchase order. Supplier Tax Invoice Exchange Rate. Customs Location Code.. Displays the Custom location code. Remit to Supplier Name. Enter or accept the Remit to Supplier Name if you want to pay to the Third Party. This field is mandatory and enable you to record the Third Party supplier to whom the payments are to be made. Remit to Supplier Site. Enter or accept the Remit to Supplier Site if you want to pay to the Third Party. This field is mandatory and enable you to record the Third Party supplier to whom the payments are to be made. The Remit To Supplier Site list of values displays only those supplier sites that are attached to the selected Remit To Supplier Name for which the relationship is defined and is active as on Invoice date. Taxation Country. The country where tax is applicable Tax Amount. Amount of tax on an invoice. Tax Control Amount. The total amount of tax for the invoice, if you are manually entering tax lines. Enter a tax control amount if you are manually entering tax lines. The total amount of tax lines must equal the Tax Control Amount or the invoice is placed on hold. Terms. Payment Terms that Payables uses to create one or more scheduled payments for an invoice. You define terms in the Payment Terms window. See also: Payment Terms, Oracle Payables Implementation Guide. If you want to ensure that the payment terms default from the purchase order, then enter a PO Number. You can change the invoice payment terms in the Invoices window. Payables uses the invoice payment terms to schedule invoice payment unless the Recalculate Scheduled Payment option is enabled in the Payables Options window. If that option is enabled, Payables uses the more favorable payment terms between the purchase order and the invoice. Terms Date. Beginning date from which Payment Terms start when Payables calculates the scheduled payment(s) for an invoice. Can be the invoice date, invoice received date, goods received date, or invoice entry date depending on the Terms Date Basis for the supplier site. If the Terms Date Basis is invoice or goods received date, Payables prompts you to enter that date here and copies the value to the field of the same name. Trading Partner. Name of the supplier or payee to whom you want to remit payment. Transaction Code. Codes that your bank uses to identify different types of transactions on its statements. You can define these values in Oracle Cash Management. Type. The type of invoice you select determines which processing options Payables makes available to you.
Voucher Number. Assign a manual voucher number to an invoice for internal tracking purposes. Payables assigns a unique, sequential number during invoice entry. You cannot update a voucher number assigned by Payables. Withheld Amount. Payables displays the amount withheld from the invoice based on automatic withholding tax calculations. Withholding Tax Group. Withholding tax group that Payables will use to calculate the Amount Withheld for an invoice. Payables enters the supplier site default Withholding Tax Group, if one exists. If you change this value at the invoice header level, then the change will not affect any existing distributions. ButtonsActions. Opens the Invoice Actions window for a selected invoice(s) which you can use to perform actions such as validating, approving, cancelling, or printing. Distributions. Opens the Distributions window for a selected invoice. Match. Allows you to start one of the following matches, based on the transaction you select. Select the transaction you want to match to from the poplist, then choose the Match button. If you enter a positive amount invoice, then Payables defaults either Purchase Order or Receipt, based on the Invoice Match option of the supplier site.
Quick Match. Automatically matches invoice to open, unbilled purchase order lines for the specified supplier. Tax Details. Opens the Tax Lines Summary window, which displays the tax lines on the invoice. See: . General TabAccounted. Payables displays Yes, No, or Partial to indicate if the accounting entry for the invoice has been successfully created. If the status is Partial, then you have created accounting entries for some but not all of the invoice distributions. Amount Paid. Amount you have paid on the invoice. This amount includes applied prepayments and related tax distributions that do not have the Prepayment on Invoice check box enabled. If the invoice has a payment currency, then it is displayed with the invoice currency above and payment currency below. To see detailed information on the invoice payment(s), select the invoice and choose the Payments tab. Approval. The derived status of an invoice with respect to the Invoice Approval Workflow program. The approval status is derived from the approval status of the document and the approval status of the invoice lines. For more information on the approval status, see: If you want to review the status of an invoice in the Invoice Approval Workflow or want to see the approval history then see: , and .
Description. Payables displays the invoice description. Distribution Total. Sum of the Item, Freight, and Miscellaneous Invoice distributions in the Distributions window. This total does not include Tax, Withholding Tax, or some Prepayment type distributions. When you enter an invoice that references a prepayment, the distribution total will include Prepayment distributions and any associated tax distributions that have the Prepayment on Invoice check box enabled. If the Distribution Total does not match the Invoice Amount, Payables will apply a hold to your invoice during Invoice Validation. Freight. The amount of freight lines on the invoice. Holds. If the invoice has an invoice hold, Payables displays the number of invoice holds. Payables does not include the Hold All Payments or scheduled payment holds in this field. To see detailed invoice hold information, choose the Holds tab. To see detailed information on all hold types, submit the Invoice on Hold report. See also: . Items. The total amount of Item lines on the invoice. Miscellaneous. The total amount of Miscellaneous lines on the invoice. Pending Approver. Displays the name of the person to whom workflow notification has been sent but has not yet responded. Prepayments Applied. The amount of prepayment applied to the invoice. Retainage. The amount retained for advances and contract financing. Scheduled Payment Holds. Number of holds on schedule payments. Subtotal. The total of the Item lines, Retainage, Prepayments, and Withholding Tax on the invoice. Status. Status of an invoice.
Total. The invoice total including tax. Withholding. The amount of tax withheld. Lines TabUse the Lines tab to enter item line information to enable you to perform the following tasks:
If a field defaults to the line from the header region, the definitions for these fields are provided in the Header Region. Account Segment. One of up to 30 different sections of your Accounting Flexfield, which together make up your general ledger account combination. Specify an account segment if you want to overlay a specific account segment in place of the segment derived from the template, matching or default accounts. The segment is ignored if the invoice line:
The segment is validated against list of possible values for Account Segment in GL for the appropriate Chart of Accounts. It cannot be updated if the line cannot add any more distributions, or if the line has GENERATE DISTRIBUTIONS set to N (No) or D (Done). See: Amount. Line amount. The line amount is the Quantity Invoiced * Unit Price. Approval Status. Line amount. The approval status of an invoice line within the Invoice Approval Workflow process. For more information on the approval status, see: . Assessable Value. The deemed price at which a product is valued, by a tax authority, for tax calculation purposes. The same product can have more than one assessable value, as given by different tax authorities. Asset Book. This field is used to default to the distributions if the Track as Asset check box is enabled. The default Asset Book is the ledger, if only one ledger exists. Asset Category. This field is used to default to the distributions if the Track as Asset check box is enabled. Defaults in based on the Inventory Item. Award Number. If you use Oracle Grants Accounting, enter the Award number of the project. If you have a default value in this field, it is from either the invoice header or Distribution Set. Balancing Segment. An Accounting Flexfield segment that you define so that General Ledger automatically balances all journal entries for each value of this segment. Specify a balancing segment if you want to overlay a specific balancing segment in place of the segment derived from the template, matching or default accounts. This segment is ignored if the invoice line:
The balancing segment is validated against list of possible values for Balancing Segment in GL for the appropriate Chart of Accounts. It cannot be updated if the line cannot add any more distributions, or if the line has GENERATE DISTRIBUTIONS set to N (No) or D (Done). See: Business Category. The business category is a tax driver used by E-Business Tax to determine and calculate the applicable taxes. Cancelled. Invoice cancelled by Oracle Payables. Control Amount. A feature used to specify the total amount available for payment of a recurring payment. When you generate invoices for a recurring payment, Oracle Payables uses the control amount and the total number of payments to determine the invoice amount. Corrected Invoice. Corrected invoice number. Corrected Invoice Line Number. If the invoice line is a correction, the invoice number the line is correcting. Correction. Possible Correction types are: Price Correction, Amount Correction (Quantity), or null. This field is populated if the line represents a correction. Price Corrections are only available for Standard, Mixed, Credit Memo, or Debit Memos. Price and Amount Corrections are only available for Item lines. Invoice Line Corrections can be entered for Item, Freight, and Miscellaneous lines, but not for Tax lines. Cost Center SegmentAn Accounting Flexfield segment that you define so that General Ledger automatically balances all journal entries for each value of this segment. Specify a cost center segment if you want to overlay a specific cost center segment for the distributions in place of the segment derived from the template, matching or default accounts. The cost center segment is ignored if the invoice line:
The cost center segment is validated against list of possible values for Cost Center Segment in GL for the appropriate Chart of Accounts. It cannot be updated if the line cannot add any more distributions, or if the line has GENERATE DISTRIBUTIONS set to N (No) or D (Done). See: Default Account DescriptionThe default account for distributions generated for the line in the absence of a specific account, specified by a Distribution Set. Deferred End Date, Number of Periods, Deferred Option, Period Type, Start Date. Used to generate deferred accounting entries. Description. Item description. Discarded. Invoice line discarded by Oracle Payables. Distribution SetUsed to generate distributions for the line. The distribution set is automatically validated to ensure that all accounts specified in the set are valid. If a distribution is specified at the header level, then the value defaults into this field for the line. You can update the distribution set for the line as necessary. Encumbrance Status. The status of the invoice line in the Encumbrance process. Expenditure Item Date. This date defaults in based on the site-level “PA: Default Expenditure Item Date for Supplier Cost” profile option. Final Match. Enter Yes only if this is the last invoice line you want to match to the purchase order and you are sure you want to final match. See: .
Important: Enter Yes only if you are certain this is a final match against the related purchase order. Once you validate a final matched invoice distribution, you cannot update the Final Match field for the distribution. Fiscal Classification. A classification used by a tax authority, which is further divided into: party fiscal classification, party site fiscal classification, product fiscal classification, transaction fiscal classification, and document fiscal classification. Included Tax Amount. The amount of tax, both recoverable and non recoverable, included in the line total. This field is for reference only. Income Tax Region. The region or state you assign to paid invoice distribution lines for a 1099 supplier. Income Tax Type. A type of payment you make to 1099 suppliers. You can assign an income tax type to each paid invoice distribution line for a supplier. The Internal Revenue Service (IRS) requires that you report, by income tax type, payments made to 1099 suppliers. For purchase order matched invoices, this value always defaults from the purchase order, (even if the purchase order value is null and the supplier has a value). If this happens and you want to use the supplier value, you can enter it here manually or use the Update Tax Details Utility. You can update this field even after you have posted a distribution. You can use the Update Income Tax Details Utility to make adjustments to many distributions. Inventory Item. Inventory item identifier. This field is only available for Item lines that are matched to purchase orders or receipts. Invoice Includes Prepayment. If this check box is enabled, the prepayment is referenced on the supplier invoice and the invoice amount includes the amount of the prepayment and any associated tax. Distributions with the Prepayment on Invoice check box enabled are included in the Distributions Total and are not included in the Amount Paid for the invoice. Item Description. Item description. This description defaults from the PO or Receipt if the invoice is matched. For PO matched invoices, this is the PO Shipment; for Receipt matched invoices, this is the receipt line. Line Source. Source of the invoice line. For example, Open Interface or Manual lines. Manufacturer. Name of the manufacturer of the item. This field is only available for Item lines. Match Basis. Basis on which invoices are matched to purchase orders. Options include: Price Correction, Quantity Correction, Invoice Line Correction, Invoice Line Matched to Purchase Order, Invoice Line Matched to Receipt, Other Charge Invoice Line Matched to Receipt, or Not Matched. You can also define custom match types in the Invoice Line Match Type lookup. Model. Model number of the item. This field is only available for Item lines. Nonrecoverable Tax Amount. The part of the tax amount, that is included in the line amount, that cannot be recovered. Num. Line number of the invoice line. Overlay Account. Allows null values for some segments so not all account segments need to be provided. PO Distribution Number. Purchase order distribution line number, if the invoice is matched to a purchase order. PO Line Number. Purchase order line number, if the invoice is matched to a purchase order. PO Number. Purchase order number, if the invoice is matched to a purchase order. PO Release Number. Purchase order release number, if the invoice is matched to a purchase order. PO Shipment Number. Purchase order shipment number, if the invoice is matched to a purchase order. Prepayment Invoice Number, Line Number, PO Number. Populated when you apply or unapply a prepayment to the invoice. Primary Intended Use. A tax driver used by E-Business Tax to determine and calculate the applicable taxes for the line. Product Category. A type of product fiscal classification that is non-Inventory based. Product Fiscal Classification. A tax classification used by a tax authority to categorize a product. Product Type. A tax driver used by E-Business Tax to determine and calculate the applicable taxes for the line. Project, Task, Expenditure Information. If you have Oracle Projects installed, the project to charge the expenditures on an invoice to a specific project, task, or organization. The system uses the project information you enter to create an account that defaults to the invoice distribution. You can override this project information at the invoice distribution. If you change these values at the invoice header level, then the values will not affect any existing distributions. Note: If you enter project information, you must enter a value for Task unless you have matched to a purchase order with project information with a null task ID. A purchase order can have a null task ID only if its destination is Inventory or Shop Floor. If the destination is Inventory or Shop Floor, the project information is used by Project Manufacturing. Project Quantity. Project Quantity defaults in based on the quantity invoiced. Prorate across All Item Lines. Available only for Freight and Miscellaneous lines. Enable this check box if you want to prorate the Freight or Miscellaneous line across all Item lines. Tax is always prorated across all Item lines. You cannot update this check box if the line has allocation rules associated with it, is already distributed, or if the line is matched by Receipt. Receipt Line Number. The receipt and receipt line information, if the invoice line is matched to receipt. Quantity Invoiced. Quantity of items for matched invoice lines, price corrections, quantity corrections, or non-matched invoice lines. Receipt Required. Indicates whether the invoice line is receipt matched and if a receipt is required (3-way match). Receipt Verified. Indicates whether the invoice line receipt was verified (4-way match). Recoverable Tax Amount. The part of the tax amount, that is included in the line amount, that can be recovered. Requester. (Optional) Person who initiated the purchase of the line item. This may be the person who is responsible for approving the invoice line if you are using the Invoice Approval Workflow. Serial Number. Serial number of the item. This field is only available for Item lines. Ship to. A tax driver used by E-Business Tax to determine and calculate the applicable taxes for the line. Tax, Classification Code, Jurisdiction, Rate, Rate Name, Regime, Status. Tax drivers used by E-Business Tax to determine and calculate the applicable taxes for the line. Track As Asset. If you enable this check box, Payables transfers this distribution to Oracle Assets when you submit the Create Mass Additions for Oracle Assets Program. You can then create assets in Oracle Assets from the imported distribution information. If the distribution has an asset account, Payables enables this option and you cannot adjust it. If the account is an expense account, Payables does not enable the check box, but you can enable it at any time before the invoice accounting entries are transferred to general ledger. Type. Type of invoice line. Possible types are: Item, Freight, Miscellaneous, Prepayments, Tax, or Withholding Tax. Prepayment lines are automatically generated when you apply or unapply a prepayment. You can only enter Tax lines if your tax setup permits. You can only enter a Withholding Tax if your withholding tax setup permits. Unit Price. Unit price of the item. UOM. Unit of measure for quantity invoiced. Warranty Number. Warranty number of the item. This field is only available for Item lines. Withholding Tax Group. You can assign one or more Withholding Tax type tax names to a withholding tax group. Assign a withholding tax group to an invoice or distribution line and use Oracle Payables to automatically withhold tax for expense reports and supplier invoices. Holds TabUse the Invoice Holds tab to apply manual holds to an invoice and to remove holds from an invoice. You can release a single hold by entering a Release Name in the Release Name field, or you can release multiple holds at once by using the Release button. For more information, see: , and . Held By. Displays who placed the hold. Hold Date. Displays the date on which the hold was placed. Hold Name. If you or the system has placed a hold, Payables displays the name of the hold. If you want to manually apply a hold, enter the hold name here. Hold Reason. The hold reason associated with the hold. Release Name. If this is a manually releasable hold, enter the release name to release the hold. You can select from all invoice hold names defined with the type Invoice Invoice Release Reason. If this is not a manually releasable hold, Payables will notify you if you try to enter a value in this field. Release Reason. The release reason associated with the Release Name. Purchase Order Number, Reason, Line, Ship To. If the invoice is purchase order matched, Payables displays the purchase order information for this invoice. You can choose the View PO button to view purchase order details. Receipt Number, Line, Date. If the invoice is receipt matched, Payables displays the receipt information for this invoice. Release By. Displays who released the hold. Release Date. Displays the date on which the hold was released. WF Status. The status of the hold in the workflow. View PO (button). Navigates to the View PO window. You can select this only if the invoice is purchase order matched. Release..(button). To release multiple holds at once, select the holds you want to release. Choose the Release button and select a Release Name. You can select from all invoice hold release names defined with the type Invoice Quick Release Reason. When you save your work, Payables automatically assigns the release name to all releasable holds. Choose OK. View Payments Tab[] (Descriptive Flexfield). Payables displays any values from the Payment's descriptive flexfield. If you use a local version of Payables, consult your county-specific documentation for more information on this flexfield. Discount Taken. If you realized a discount when you created the payment, Payables displays the amount of the discount. Document Number. Payment document number, for example, check number. GL Date. Payment GL Date. Payment Amount. Amount of the payment. Payment Date. The GL Date for the payment lines and the date on the payment document. The date must be in an open accounting period. Payment Method.
Payment Overview. Navigates to the Payment Overview window which displays additional payment information. From this window you can navigate to the Payments Workbench, the Banks window, or the Suppliers window. Void. Payables enables this check box if you have voided the payment. Scheduled Payments TabAll amounts in the Scheduled Payments tab are displayed in the payment currency, except for the Gross Amount, which is displayed in the invoice currency. Amount Paid. Invoice amount minus the gross amounts of the remaining payments. The Amount Paid does not reflect discounts you realize on payments. It shows the actual amount disbursed. For example, for a 100 invoice, if you paid 90 and realized a 10 discount, then Payables displays 90 in the Amount Paid field. If you check the Prepayment on Invoice check box when applying prepayments, then your Prepayment and associated Tax distributions will not be included in the Amount Paid calculation. For example, you receive a 500 invoice that references a 100 prepayment. Your invoice looks like this: Services500(less Prepayment received)(100)Total Amount Due400When you enter this invoice, you check the Prepayment on Invoice check box to apply the 100 prepayment that is referenced on the invoice. You make a 300 payment and Payables displays 300 in Amount Paid. You still owe the supplier 100, so you apply an additional 100 prepayment distribution. You do not check the Prepayment on Invoice check box when applying the 100 prepayment distribution because this prepayment is not referenced on the invoice. In this case, the 100 prepayment application is included in the Amount Paid field so Payables now displays a total of 400 in Amount Paid. See: Amount Remaining. Payables displays the unpaid amount of a selected scheduled payment line. Remit to Supplier Name. Displays the Remit to Supplier Name to pay to the Third Party. Remit to Supplier Site. Displays the Remit to Supplier Site to pay to the Third Party. Bank Account Name. Name of the account from which a scheduled payment will be made. Bank Account Number. Number of the account from which a scheduled payment will be made. Discount Amount Remaining. Payables displays the first discount amount available on the unpaid amount of a scheduled payment line. Payables displays the discount amount you would realize if you paid the scheduled payment today. Discount, Second Discount, Third Discount Date, Amount. Payables displays the discount amount you are eligible to subtract from the gross amount if you pay the invoice before the corresponding discount date. For example, you enter a $100 invoice with a payment terms date of January 1, 2002, and your payment terms allow you to take either a 10% discount if you pay within 10 days, or a 5% discount if you pay within 20 days. When you select Discount, the date is January 10, 2002, and the amount is $10.00. You select Second Discount, and the date is January 10, 2002, and the amount is $5.00. If you make the payment on or before eligible discount dates, you choose between paying the gross amount of the invoice or taking the most favorable discount option. Due Date. Payables calculates the date the invoice is due based on the invoice Terms Date and invoice Payment Terms. For example, if the terms date is January 1, 2002, and the invoice payment terms are Net 30, the Due Date is January 30, 2002. If you enable the Recalculate Scheduled Payment Payables option, then during Invoice Validation the system recalculates the due date based on your most favorable available payment terms and start dates, unless you have manually entered or updated any scheduled payments. Payables does not default Due Dates for scheduled payments you add manually. Gross Amount Total. Sum of the scheduled payment Gross Amounts. This must equal the Invoice Amount. Gross Amount. Gross amount due for the scheduled payment, displayed in the invoice currency. Payables subtracts the discount amount, automatic withholding amount, and prepayment amount from the gross amount to calculate the payment amount. Hold. Enable this check box if you want to apply a payment hold on the scheduled payment line. If a scheduled payment has a payment hold, Payables will not create a payment for that scheduled payment until you disable the check box. See: . You cannot enable this hold if the scheduled payment line has already been paid. Invoice Amount. Amount of the invoice, displayed in the payment currency. If this is a prepayment, Payables displays the amount of the prepayment that remains unapplied. Pay..(button). Opens the Payments window so you can pay selected scheduled payments. See: . Payment Method. Payables defaults the payment method from the invoice (Check, Electronic, Wire, or Clearing). Payment Priority. A number, between 1 (high) and 99 (low), that represents the priority of payment. The value for this field defaults from the invoice batch if you specified one in the Invoice Batches window. Otherwise it defaults from the supplier site. You can enter a payment priority range as a criteria for selecting invoices for a payment batch. Split Schedule. If you want to automatically create an additional scheduled payment, select a scheduled payment and update the amount. Choose Split Schedule to have Payables create an additional scheduled payment with the net amount due. For example, select a $100 scheduled payment and change the gross amount to $40. Choose Split Schedule to have Payables create a new $60 scheduled payment. If you use the Split Schedule button to update default scheduled payments then no payment schedule recalculation will be performed during Invoice Validation, even if the Recalculate Scheduled Payments Payables option is enabled. System Hold Reason. The reason the payment is on hold, as determined by the system based on specified tolerances. View Prepayment Applications TabThe View Prepayment Applications tab displays the prepayments applied to the invoice. Amount Applied. Amount of prepayment applied to the invoice. PO Num, Receipt Num. Payables populates these fields for prepayments related to a purchase order. INVOICE ENTRY RESTRICTIONS:INVOICE DATE NOT IN OPEN PERIOD. If you enter a date in a future period, Payables displays a warning message. When you submit Invoice Validation, Payables applies a Future Period hold to the invoice. This hold prevents payment and creation of accounting entries for the invoice. You need to open the period and resubmit Invoice Validation to pay or create accounting entries for the invoice. If you enter a date that is more than one year old, Payables displays a warning message. This warning message helps you detect data entry errors. LIABILITY ACCOUNT. If you use encumbrance accounting and Automatic Offsets, and an invoice is fully validated, you cannot update the Liability Account for the invoice. If you use encumbrance accounting and Automatic Offsets, and there is at least one unvalidated invoice distribution, then you can update the Liability Account. Related Topics Distributions Window ReferenceThis window is a customizable folder. Note that in the default folder, many of the fields listed below are hidden. You can create custom folders by unhiding, hiding, moving, resizing, and renaming fields in this window. See: Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide. Use this window to enter, review, or adjust distributions for an invoice. Payables uses distributions to create accounting entries for invoices. You can enter an unlimited number of distributions for an invoice. You can enter distributions manually, or you can create them automatically by using Distribution Sets, allocating, or by Purchase Order Matching. When you query distributions in this window, Payables displays distributions by Type in the following order: Item, Tax, Freight, Miscellaneous, Prepayment, Withholding. You can find detailed information on entering, reviewing and adjusting distributions throughout the Invoices chapter. Account. Account to charge when you create an accounting entry for this distribution. Usually an expense or asset account. Accounted. Payables displays Yes or No to indicate if accounting entries have been created for the distribution. Amount. Amount to charge the general ledger account. If this is a foreign currency invoice, enter the amount in foreign currency. The sum of the distribution amounts must equal the invoice amount. Description. Description of the distribution. This description appears on the payment document remittance. For manually entered distributions, the default value is the invoice description. For tax distributions, the default value is the tax code. For distributions created by Distribution Sets, the default is the Description of the Distribution Set line. For distributions created by purchase order matching, the default value is the description of the purchase order line. Functional Amount. Invoice amount displayed in your functional currency. GL Date. Payables uses the GL Date as the accounting date. The date must be in an open or future period. This value defaults from the Invoices window. Important: If you change the GL Date in the Invoices window, Payables does not change the GL Date for existing invoice distributions. If you want to update the GL Date for an invoice, use the Distributions window to change the GL Date for each invoice distribution. You cannot change the GL Date after the invoice has completed Invoice Validation. If the GL Date of an invoice is in a future period in Payables, you cannot pay the invoice. Income Tax Region. Income tax region for the distribution. Payables orders distributions by income tax region on the 1099 form reports. If you enable the Combined Filing Program Payables option, when you submit the 1099 tape, Payables will produce K records for all tax regions participating in the Combined Filing Program that have qualifying payments. If you enable the Use Pay Site Tax Region option in the Payables options window, the default for this field is the supplier site's state. If you choose instead to enter a tax region in the Income Tax Region field in the Payables Options window, the default for this field is the tax region you entered. If you do not enter an income tax type for a distribution, you cannot enter an income tax region. See also: Income Tax Type. Income tax type, for 1099 reporting purposes. If you do not use a Distribution Set to create invoice distributions, Payables uses the supplier's income tax type as the default value. If you use a Distribution Set to create invoice distributions, Payables uses the default income tax type from the Distribution Set as the default value. You can enter or adjust this field regardless of whether the supplier is defined as a 1099 supplier. Payables uses this information when you submit the 1099 Payments report and the 1099 form reports. See also: . For purchase order matched invoices, this value always defaults from the purchase order, (even if the purchase order value is null and the supplier has a value). If this happens and you want to use the supplier value, you can enter it here manually or use the Update Tax Details Utility. You can update this field even after you have posted a distribution. You can use the Update Income Tax Details Utility to make adjustments to many distributions. See: . Num. Unique number for the distribution. You can override Payables default if the number you enter is unique for the invoice. PO Number. Purchase order to which the distribution is matched. PO Distribution Number. Purchase order distribution to which the distribution is matched. Project/Task/Expenditure information. If you have Oracle Projects installed, associate an invoice with a project to charge the expenditures on an invoice to a specific project, task, or organization. The system uses the project information you enter to create an account that defaults to the invoice distribution. You can override this project information at the invoice distribution. Note: If you enter project information, you must enter a value for Task unless you have matched to a purchase order with project information with a null task ID. A purchase order can have a null task ID only if its destination is Inventory or Shop Floor. If the destination is Inventory or Shop Floor, the project information is used by Project Manufacturing. Expense Receipt Date. Used to record VAT on expense reports. Date of the receipt or invoice that included the VAT charge. For example, receipt date of hotel bill that included a VAT charge. Status. Validation status of the distribution:
Tax Regime.Tax regime associated with the distribution. See: Tax. Tax associated with the distribution. See: . Type. Payables uses Type to differentiate between charges on an invoice.
Unit of Measure. Payables displays a statistical unit if you have defined one for the distribution's account in General Ledger. For example, you can use a unit of Square Feet for an office rent purchase order. Display Only RegionTotal. Sum of the invoice or line amounts. Distribution Total. Sum of the distribution amounts excluding withholding and some prepayment type distributions. Status. Validation status of the selected invoice distribution. (See above) Accounted. Indicates whether accounting entries have been created for the distribution. PO Number. Purchase order number that is matched to the distribution. Account Description. Description of the selected distribution. ButtonsTax Distributions. Choose this button to view the tax distributions calculated by E-Business Tax. See: . View PO. If you have Oracle Purchasing installed and the selected distribution is purchase order matched, choose the View PO button to Navigate to the Purchase Order Distributions window. View Receipt. If you have Oracle Purchasing installed and the selected distribution is matched to a receipt, then choose the View Receipts button to navigate to the Receipt Transactions Summary window. Which is available on vendor invoice?Vendor invoices include the amounts owed, sales taxes, freight and delivery charges, the date by which the payment should be made, and where to send the payment.
When the vendor payment is made the general ledger is updated for the cash receipts?When the vendor payment is made, the general ledger is updated for the cash disbursement. The vendor invoice triggers the "establish payable" process. The vendor sends a confirmation to establish the payable.
Which of the following is designed to reflect the formal approval of the voucher for payment?A disbursement voucher is designed to reflect formal approval of the voucher for payment and to provide such added data as the account distribution and the amounts to be debited.
Which document typically notifies the purchaser of his or her obligation to pay?A debit note, or a debit memo, is a document issued by a seller to a buyer to notify them of current debt obligations. You'll commonly come across these notes in business-to-business transactions — for example, one business may supply another with goods or services before an official invoice is sent.
|
The vendor invoice master data is a repository of all unpaid vendor invoices.
zusammenhängende Posts
Urheberrechte © © 2024 paraquee Inc.
