R 12: Payables Reconciliation:

Reconciling Payable Activity:

Use the following reports to reconcile your posted invoices and payments to your Accounts Payable Trial Balance to ensure that your Trial Balance accurately reflects your accounts payable liability:

• Posted Invoice Register
• Posted Payment Register
• Accounts Payable Trial Balance (last period and current period)

Note: Before you run your reports, transfer the journal entries to General Ledger for all transactions in the period that you are reconciling.

Note: When reviewing your Accounts Payable Trial Balance report, you may notice that the remaining amount for a given invoice is less than you expect or even negative. This may be caused by recording invoice payments in a GL period that precedes the GL period used to record some or all of your invoice distributions.

For example: You enter an invoice with one distribution of $200 that uses a GL date of 04-JAN-2001. You pay the full invoice, and the payment date is 20-DEC-2000. If you submit the Accounts Payable Trial Balance report as of 31-DEC-2000, then the invoice will correctly show an amount remaining of <-$200>.

In the reports parameter, if you do not enter an as of date, then the report shows all paid and unpaid invoices from the start date.

Payables allows the payment date to precede the invoice GL date to support certain accounting methods (e.g. recording prepaid items).

To reconcile your Accounts Payable Trial Balance for a given period:

• Add the current period's posted invoices (total invoice amount from the Posted Invoice Register) and subtract the current period's posted payments (total cash plus discounts taken from the Posted Payments Register) from the prior period's Accounts Payable Trial Balance. This amount should equal the balance for the current period's Accounts Payable Trial Balance.

For example, you are closing your accounting period for April and you have just posted your final invoice and payment batches to your general ledger system. To reconcile your accounts payable activity for April, make the following calculation:

March Accounts Payable Trial Balance

+ April Posted Invoice Register

- April Posted Payment Register

= April Accounts Payable Trial Balance

Reconciling Payables Activity to General Ledger

Use the Accounts Payable Trial Balance report to reconcile your accounts payable liability in your general ledger. Compare the Accounts Payable Trial Balance to the accounts payable balance in your general ledger system for a given period.

Because the Trial Balance presents the outstanding accounts payable liability information, it is only valid for an accrual ledger.

Posted Invoice Register:

Use the Posted Invoice Register to review accounting lines for invoices that have been transferred and posted to your general ledger. Because it presents amounts that have been charged to liability accounts, this report is valid only for an accrual ledger.

The Posted Invoice Register is primarily a reconciliation tool. Use this report along with the Posted Payment Register and the Accounts Payable Trial Balance Report to reconcile balances between Payables and your general ledger. To make their output easier to read, each of these reports can be generated for a single liability account. For example, if you are using Automatic Offsets and the liability for your invoices is allocated across multiple balancing segments, then you can use the Liability Account parameter to limit your reports to a single balancing organization.


You can generate the report in summary or in detail. When generated in detail, the report displays invoices charged to liability accounts and the accounting information that has been transferred to the general ledger. Also included is the supplier and amount information for each invoice listed. Payables displays the total invoice amount in the invoice currency, and the transferred distribution amount in both the invoice currency and accounted currency for easier reconciliation with your general ledger.


Note: The posted distribution amount only includes distribution lines that have been transferred to general ledger.

When generated in summary, the report lists totals for each liability account and does not include any invoice detail.

The report always sorts first by liability account. If the report is submitted in detail, it then sorts in the following order:

·   The report sorts using the Order By parameter, either Journal Entry Batch or Entered Currency. The default value is Entered Currency, and you can change the parameter value only if the report includes journal entry batch names (the Include Journal Entry Batch parameter is Yes).

·    The report then sorts by supplier name, invoice number, and invoice date.

Posted Payment Register:

Use the Posted Payment Register to review accounting lines for payments that have been transferred and posted to general ledger. Because it presents amounts that have been charged to liability accounts, this report is valid only for an accrual ledger. You can submit the Posted Payment Register for one payment journal entry batch or all payment journal entry batches.


The Posted Payment Register is primarily a reconciliation tool. Use this report along with the Posted Invoice Register and the Accounts Payable Trial Balance Report to reconcile balances between Payables and your general ledger. To make the output easier to read, each of these reports can be generated for a single liability account. For example, if you are using Automatic Offsets and the liability for your invoices is allocated across multiple balancing segments, then you can use the Liability Account parameter to limit your reports to a single balancing organization.


You can generate the report in summary or in detail. When generated in detail, the report displays payments that relieve liability accounts and that have had their accounting information transferred to the general ledger. Also included is the supplier and amount information for each payment listed. Payables displays the payment amount in the entered currency and the liability amount relieved in the accounted currency. In detail mode, the report also displays the payment document and disbursement type for each batch of payments. It provides a report total and subtotals for each payment document and bank account.

When generated in summary, the report lists totals for each liability account and does not include any payment detail.

The report always sorts first by liability account. If the report is submitted in detail, it then sorts in the following order:

·         The report sorts using the Order By parameter, either Journal Entry Batch or Bank Account. The default value is Bank Account, and you can change the parameter value to Journal Entry Batch only if the report includes journal entry batch names (the Include Journal Entry Batch parameter is Yes).

·         The report then sorts by payment number, payment date, and supplier name.

Accounts Payable Trial Balance Report:


Use the Accounts Payable Trial Balance Report to verify that total accounts payable liabilities in Payables equal those in the general ledger. To reconcile these balances you can compare the cumulative total liability provided by this report with the total liability provided by your general ledger.
The Accounts Payable Trial Balance report is a Payables-specific version of the Open Account Balances Listing report. By running this report from Payables, you can run this report for a specific operating unit. In the reports parameter, if you do not enter an as of date, then the report shows all paid and unpaid invoices from the start date.

Accounts Payables Trial Balance Rebuild

If you are unable to add a new code combination, the Accounts Payable Trial Balance report does not display any invoices that use the liability account. You can run the Accounts Payables Trial Balance Rebuild concurrent program. This concurrent program is applicable only for new accounting data created in E-Business Suite release 12 and not for migrated data.

The Accounts Payables Trial Balance Rebuild program inserts liability accounting and report definition setup data into the tables on which the Accounts Payable Trial Balance report is based.

The program has the following input parameters:

·         Report Definition – Enter the report definition code.

·         Start Date and End Date – Enter the accounting date range.

·         Account From and To – Enter the range of account combinations.

·         Preview Only – Select Yes or No.

All Payables journals that match the specified parameters and are accounted in SLA but are not present in the trial balance tables are processed.


If the Preview Only is set to Yes, then the system displays the balances that would be inserted. When the parameter is set to No, then only the actual balances are updated.

R12: Payables - Closing Period Process

Closing is the process of accounting for all transactions at the end of each period so all supporting information is transferred to the General Ledger. Subledgers cannot be closed if the required transactions in that period are not processed. Subledgers are E-Business Applications that post (transfer accounting records) to the General Ledger: for example, Payables, Receivables, Inventory, etc.

You should close a period when no one is entering any invoices or payments. 

In Payables you close the accounting period after you have completed accounting for transactions for the period and you have transferred the accounting entries to general ledger.

    To complete the close process in Payables:

1.      Validate all invoices.

2.      Confirm or cancel all incomplete payment batches (Payment Process Requests).

3.      If you use future dated payments, submit the Updated Matured future Dated Payment status Program. This will update the status of matured future dated payments to Negotiable so you can account for them.

4.      Resolve all unaccounted transactions. Submit the Create Accounting program to account for all unaccounted transactions. Review the Unaccounted transactions Report. Review any unaccounted transactions and correct data as necessary. Then resubmit the Create Accounting program to account for transactions you corrected. Or move any unresolved accounting transactions exceptions to another period (optional).

5.      Transfer invoices and payments to the General Ledger and resolve any problems you see on the output report.

6.      In the Control Payables Periods window, close the period in Payables.

7.      Reconcile Payables activity for the period. To perform reconciliation of payables activity, you will need the following reports:

i.                    Accounts Payable Trial Balance Report

ii.                  Posted Invoice Register

iii.                Posted Payment Register

8.      If you use oracle Purchasing, accrue uninvoiced receipts.

9.      If you use Oracle Assets, run the Mass Additions Create Program to transfer capital invoice line distributions from Oracle Payables to Oracle Assets.

10.   Post journal entries to general ledger and reconcile the trial balance to the General Ledger.

Therefore, you cannot close a period in Payables if any of the following conditions exists:

i.          Outstanding payment batches

ii          Future dated payments for which the Maturity Date is within the period but still have

            a status of issued.

iii.                Unaccounted transactions

iv.                Accounted transactions that have not been transferred to GL

R12: Payables Period close Analyzer (Doc ID 1489381)

What are Analyzers?

Oracle Analyzers are designed by Support to proactively assist you to better diagnose and maintain your Oracle Application environments.

The analyzer is a self-service health-check script that helps identify transactions which may stop the period close within your payables application. In addition, you can also run the data validation report to check for data integrity issues in that period. This will help the production support and payables teams in resolving the period close show stoppers and keeping your system ready for period close without missing any deadlines.

You should always run this script prior to logging a Service Request when you are not able to close the period or if you simply want to proactively verify the data integrity of your transactions to keep the system ready for period close.

Your application data is not altered in any way when you run this analyzer. This is a non-invasive script – the analyzer does not perform any INSERTs, UPDATEs or DELETEs to your data; it simply reports on it.

The Analyzer identifies known issues and provides solutions and recommended actions to be performed for the specific instance it was run on and can be run at any time.

For production instances, you should first apply any recommended actions or solutions to a recent clone to ensure an expected outcome.

The Payables Period Close Analyzer can be run via SQL*Plus or as a Concurrent Request. 

To download the EBS Payables close Analyzer Latest version please click on the following link:

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=472610917582932&id=1489381.1&displayIndex=3&_afrWindowMode=0&_adf.ctrl-state=12j6irxd28_126#aref_section11

Registering the Payables Period Close Analyzer as the Concurrent Program (Doc ID 1489916.1)

Registering the Payables Period Close Analyzer as the concurrent program allows you to schedule and run a concurrent process which will scan all transactions in a particular period within specified operating units for potential transaction that may stop period close.

You can register it in one of two methods.

Method 1 – FNDLOAD:

The simplest and quickest method for defining these concurrent processes in your instance is to upload the definition from the files using the FNDLOAD link below.

• Period Close Analyzer: AP_PCLOSEAZ.ldt

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=473387384633001&parent=DOCUMENT&sourceId=1489381.1&id=1489916.1&_afrWindowMode=0&_adf.ctrl-state=12j6irxd28_175

These files can then be used to upload the concurrent program definitions using the following FNDLOAD command substituting in the correct password:

FNDLOAD apps/<appspw> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct AP_PCLOSEAZ.ldt CUSTOM_MODE=FORCE

WARNING: As with applying any change to your system, this process should first be thoroughly tested on a test instance prior to applying the files to any production system.

Method 2:

The concurrent process registration can also be completed manually through the applications front-end. The excel file below contains the front end data for the various elements that need to be created and entered in order to register these concurrent programs.  It can be used to enter the data manually as described below, or to validate the results of using Method I by comparing the data to the values resulting from the FNDLOAD upload.

Programs_Data_PH.xls

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=473387384633001&parent=DOCUMENT&sourceId=1489381.1&id=1489916.1&_afrWindowMode=0&_adf.ctrl-state=12j6irxd28_175

The steps below are all performed in the "System Administrator" responsibility.

Step 1: Create Value Sets

1. In the applications (System Administrator responsibility) navigate to Application > Validation > Set.
2. Use the data in the "Value Sets" worksheet of Programs_Data.xls to enter the required value set definitions.
3. For value sets with "Independent" validation, after saving the value set, navigate to Application > Validation > Values.  Use the "Name" field to query up the new value set, and enter the values for the value set as indicated in the "Value Sets" worksheet.
4. For "Table" validated value sets, after saving the value set, click the "Edit Information" button and enter the data as provided in the "Table Validations" worksheet of the file.

Step 2: Create the Executables

1. Navigate to Concurrent > Program > Executable
2. Use the data in the "Executables" worksheet of the file to enter the executables for each of the programs

Step 3: Register the Programs

1. Navigate to Concurrent > Program > Define
2. Use the data provided in the "Programs" worksheet of the file to enter the main concurrent program data for the process.
3. For each program after entering the main information click the "Parameters" button and use the data in the "Parameters" worksheet of the file to enter the parameter information for the corresponding program.

NOTE:  if the payables responsibility you use, is not assigned to a report group which includes all payables programs you may have the additional step of adding these processes to the responsibility report group. To determine what report group your responsibility uses navigate to Security > Responsibility > Define. Under “Request Group” note down the name and query up this request group in Security > Responsibility > Request. If there is no entry with Type = Application and Name = Payables, then you may need to add an entry for these programs here.

R12: Payables Invoice Holds

Why are Invoice Holds applied?

The process of invoice validation checks the PO matching, tax on invoice, period status (open or closed), exchange rate, and distribution information for invoices entered.

In addition, Invoice Validation checks,

i.                     The supplier site to determine which invoice tolerance template to use

ii.                   If no invoice tolerance is specified, tolerance checking is not performed

iii.                  If an invoice tolerance template is specified, invoice validation will check against the specific invoice tolerances stored in the Invoice tolerances window to determine if the invoice falls within the defined tolerances and automatically applied 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 PO, or changing the invoice tolerances. Then resubmit Invoice Validation to release the holds.

In addition, in the invoice holds tab, you can manually release certain invoice holds, even if you have not resolved the matching error condition.

How to Remove Invoice Holds?

Account Holds

Payables uses holds with this type to identify invoices with invalid or incorrect accounts. An invalid account prevents payment of an invoice and prevents Payables from creating accounting entries for an invoice or payment.

• Dist Acct Invalid:
  Invoice distribution distributed to invalid account. To release the holds you must correct account and resubmit invoice validation.

• ERV Acct Invalid:
  Payables created invalid Exchange Rate Variance account for invoice distribution. Used only if you enable Automatic Offsets. To release the holds you must correct account and resubmit invoice validation.

For both account holds accounting is not allowed and user cannot release these holds manually.

Funds Holds

Payables applies these holds only if you use budgetary control and if either there are insufficient funds for an invoice distribution or Payables cannot perform funds checking.

• Funds Check:
  This hold can be caused by 3 reasons:
• No budget exists for the account in the accounting period on the invoice. To remove it create a budget in General Ledger and resubmit invoice validation.
• Invoice account is not equal to the purchase order account. Enter different account for
  invoice distribution and resubmit invoice validation.
• Detail account not assigned to a parent account. Assign detail account to parent account and
  resubmit invoice validation.

For this hold accounting is not allowed and user cannot release these holds manually.

• Insufficient Funds:
  Invoice distribution amount is more than the funds available. There are different ways to remove this hold:
• Enter different account for invoice distribution and resubmit invoice validation.
• Transfer funds to account budget and resubmit invoice validation.
• In General Ledger, enable a user to override funds control and user resubmit invoice
  validation.
• Manually release in the invoice holds tab.

For this hold accounting is not allowed.

Invoice Holds

Payables applies holds with this type to invoices. You can manually apply as many of these holds to an invoice as you require when you enter or adjust the invoice.

• Amount:
  Invoice amount is more than the invoice amount limit you specify for a supplier site. There are different ways to remove this hold:
• Adjust invoice amount and resubmit invoice validation.
• Change invoice amount limit option for supplier site and resubmit invoice validation.
• Manually release in the invoice holds tab.

For this hold accounting is allowed.

• Invalid PO:
  You apply this hold when a supplier does not provide a valid purchase order number for matching.
  Manually release it in the Invoice Holds tab. (Note: you can submit the Invalid PO Supplier Notice to request a valid PO from the supplier).

For this hold accounting is not allowed.

• Natural Account Tax:
  You assigned a tax code to an expense or asset account in the Tax Options window, and you enabled the Enforce Tax From Account Payables option. The tax code on the invoice does not
  match the tax code assigned to the account. There are different ways to remove this hold:
• Change the tax code on the invoice to match the tax code assigned to the account.
• Disable the Enforce Tax From Account in E-Business Tax Defaults and Controls: Configuration Owner Tax Options tab.
• In the Tax Options window in General Ledger, change the tax code association.
• Manually release the hold in the invoice holds tab.

For this hold accounting is not allowed.

• Supplier:
  You enabled the hold unvalidated invoices option for a supplier site in the Suppliers Sites window.
  You can manually release in the Invoice Holds tab. To prevent future Supplier holds, disable
  the hold unvalidated invoices supplier site option.

For this hold accounting is allowed.

• Withholding Tax:
  Payables cannot perform automatic withholding of tax. Correct error that caused automatic
  withholding of tax to fail. For example, you may need to set up a period in the withholding
  tax special calendar.
  
  For this hold accounting is not allowed and user cannot release these holds manually.

Matching Holds

Payables applies holds with this type to an invoice if the invoice violates predefined matching criteria.

• AMT ORD:
  Amount Billed is greater than Amount Ordered * (1 + % Ordered tolerance). There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Holds tab.

For this hold accounting is allowed.

• AMT REC:
  Amount Billed is greater than Amount Received * (1 + % Received tolerance). There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Holds tab.

For this hold accounting is allowed.

• MAX AMT ORD:
  Amount Billed is greater than the sum of Amount Ordered and Maximum Amount Ordered
  Tolerance Amount. There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Holds tab.

For this hold accounting is allowed.

• MAX AMT REC:
  Amount Billed is greater than the sum of Amount Received and Maximum Amount Received
  Tolerance Amount. There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Holds tab.

For this hold accounting is allowed.

• MILESTONE:
  Quantity or Amount Billed is not equal to the total Quantity or Amount Ordered. This is a System hold - Correct PO or invoice and resubmit Invoice Validation or release the hold manually.

For this hold accounting is allowed.

• Can't Close PO:
  Online receipt accrual enabled in Purchasing and Purchase order quantity delivered is not equal to
  the quantity received. Resolve purchase order delivery information in Purchasing and resubmit
  Invoice Validation or release the hold manually. 

For this hold accounting is allowed.

• Can't Try Final Close:
  Invoice (final matched to purchase order) placed on hold during Invoice Validation. Release hold that caused invoice to be placed on hold and resubmit Invoice Validation.

For this hold accounting is not allowed and user cannot release it manually.

• Final Matching:
  Invoice is matched to a purchase order that was final matched by another invoice. Reverse the distribution and resubmit Invoice Validation to remove the Final Matching hold.
  
  For this hold accounting is not allowed and user cannot release it manually.

• Matching Required:
  You have enabled the Hold Unmatched Invoices option in the Supplier Sites window, and
  the invoice is not matched to purchase order or receipt. Match invoice to purchase order or
  receipt and resubmit Invoice Validation or release the hold manually.
  
  For this hold accounting is allowed.

• Max Qty Ord:
  Quantity billed more than the sum of (quantity ordered plus the tolerance amount). There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Max Qty Rec:
  Quantity billed is more than the sum of (quantity received plus the tolerance amount). There are different ways to remove this hold:
• Correct invoice or receipt and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Max Rate Amount:
  Exchange rate variance exceeds amount tolerance limit. There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Max Ship Amount:
  Variance between invoice and shipment amount exceeds amount tolerance limit. There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Max Total Amount:
  Sum of invoice and exchange rate variances exceeds amount tolerance limit. There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Price:
  Weighted average price of all distributions on the matched invoice and all price corrections related to the invoice is more than [purchase order unit price (1 plus % tolerance)]. There are different ways to remove this hold:
• Correct PO, invoice, or price corrections and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Qty Ord:
  Quantity billed is more than [quantity ordered (1 plus % tolerance)]. There are different ways to remove this hold:
• Correct PO or invoice and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Qty Rec:
  Quantity billed is more than [quantity received (1 plus % tolerance)]. There are different ways to remove this hold:
• Enter receipt in Purchasing and resubmit Invoice Validation.
• Adjust tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Quality:
  Quantity billed is more than quantity accepted. Enter acceptance in Purchasing and resubmit
  Invoice Validation or release the hold manually. 

For this hold accounting is allowed.

• Rec Exception:
  Purchase order receipt indicates exception. Please note this hold is not set at invoice validation time. It's created manually in Purchasing. You can release it manually in the Invoice Holds tab.

For this hold accounting is allowed.

• Tax Difference:
  Invoice tax code value is not equal to the purchase order tax code. Invoice tax code value =
  purchase order tax code value, but taxable flag set to No for PO shipments. Correct PO or
  invoice and resubmit Invoice Validation or release the hold manually.
  
  For this hold accounting is allowed.

Variance Holds

Payables applies holds with this type as follows. 

Payables applies the Dist Variance hold to an invoice if the total of the invoice distributions does not equal the invoice amount.
Payables applies the Tax Variance and Tax Amount Range holds by verifying that the invoice's distribution tax amount matches the calculated tax for the Tax Code within the amount tolerance or percentage tolerance or both that you define.
If the variance exceeds a percentage tolerance, Payables applies the Tax Variance hold.
If the variance exceeds an amount tolerance, Payables applies the Tax Amount Range hold.

• Dist Variance:
  Invoice line amount is not equal to the related sum of invoice distribution amounts. Adjust invoice distributions or invoice amount and resubmit Invoice Validation. If adjustment is not possible reverse distribution line and re-enter a new one or discard line.

For this hold accounting is not allowed and user cannot release it manually.

• Line Variance:
  Sum of invoice line amounts is not equal to the invoice header amount. Add an invoice line, adjust invoice lines or invoice amount and resubmit Invoice Validation. If adjustment is not possible discard line and re-enter a new one.

For this hold accounting is not allowed and user cannot release it manually.

• Prepaid Amount:
  The prepaid amount including tax exceeds the invoice amount. Unapply the prepayment and apply a lower amount. 

For this hold accounting is allowed but user cannot release it manually.

• Tax Amount Range:
  Tax amount is less than [(tax rate taxable dist line total) - tolerance amount] or Tax amount
  is more than [(tax rate taxable dist line total) + tolerance amount]. There are different ways to remove this hold:
• Adjust tax rate for tax code and resubmit Invoice Validation.
• Change tax code or tax group on invoice distributions and resubmit Invoice Validation.
• Adjust tax tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

• Tax Variance:
  Tax amount is less than [(tax rate taxable dist line total) (1 - % tolerance)] or Tax amount
  is more than [(tax rate taxable dist line total) (1 + % tolerance)]. There are different ways to remove this hold:
• Adjust tax rate for tax code and resubmit Invoice Validation.
• Change tax code values on invoice distributions and resubmit Invoice Validation.
• Adjust tax tolerance and resubmit Invoice Validation.
• Manually release in the Invoice Holds tab.

For this hold accounting is allowed.

Miscellaneous Holds

Miscellaneous predefined Hold that Payables uses to apply holds to invoices.

• No Rate:
  No exchange rate for foreign currency invoice. Enter exchange rate and resubmit Invoice
  Validation or submit AutoRate and resubmit Invoice Validation.

For this hold accounting is not allowed and user cannot release it manually.

• All Payments:
  You enabled the Hold All Payments option for the invoice's supplier site. Disable the Hold All
  Payments option in the Supplier Sites window and Payables allows you to select the supplier site's invoices for payment if they are validated  (and approved, if the invoice requires invoice approval) or create a manual payment for any of the held invoices.

For this hold accounting is allowed.

• Supplier:
  Hold all unvalidated invoices for a supplier. Remove the hold in the Invoice Holds tab, or use the Actions button. To disable completely, disable the Hold Unvalidated Invoices option at the supplier site.
  
  For this hold accounting is allowed and user can release these holds manually.