Skip to main content

Accounting information in Procure to Pay Cycle

Flow of accounting information in Procure to Pay Cycle

If you are implementing the Procure to Pay Cycle in Oracle Apps, you might have come across the following accounting activities:
1. Run the Create Accounting program after creating an invoice to post entries to the General Ledger
2. Run the Create Accounting program after making payments to post entries to the General Ledger.
As a newbie consultant, I always used to wonder why someone would have run the accounting entries twice. If you are one of the professional consultants or belong to the Chartered Accounting fraternity, you may already know the answer.
Else, read on..
1. The reason for creating accounting entries after creating an invoice is to ensure that the General Ledger is updated with the correct accounting information for the following 2 types of accounts:
a) Accounts Payable A/C
b) Merchandise A/C (incase of goods purchased) or Expense A/C (in case of expense)
When a supplier invoice is created, the business is liable to pay for the invoice and hence, the Accounts Payables A/C is credited. Since the invoice is raised for purchasing goods or for an expense, the corresponding Merchandise A/C or Expense A/C is debited.
AccountDrCr
Merchandise A/C or Expense A/C
100

Accounts Payable A/C
100
2.  The reason for creating accounting entries after making a payment is to ensure that the General Ledger is updated with the correct accounting information for the following 2 types of accounts:
a) Cash A/C or Bank A/C
b)Accounts Payable A/C 

When the invoice is paid, the payment is made in Cash. Hence the Cash A/C or Bank A/C is credited. Since the payment reduces the amount that the company owes to the Supplier, the Accounts Payable A/C is debited to the same extent.
AccountDrCr
Accounts Payable A/C100
Cash A/C100
Labels:

Comments

Post a Comment

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

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

Public API’s for FA Transactions

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

AP Table Relation Oracle Apps

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