Skip to main content

AutoAccounting in Oracle Apps Receivables AR R12

AutoAccounting

AutoAccounting is a powerful feature in Oracle Apps Receivables which is used to default the Accounting Flexfield Structure (Chart Of Account Structure) / General Ledger  (GL) accounts for the transactions entered either manually or imported using Autoinvoice. AutoAccounting defaults Accounting Flexfield segments only for transactions (eg:- Invoices, Debit Memo, Credit Memo, Chargeback, Deposit, Guarantee ) and not for receipts. Account for receipts is simply taken from the Bank Accounts defined in receipt class.

The below table shows the sources from which a segment in the below accounts can take a value .


Now, let us know the use of various accounts and when it is used :

Autoinvoice Clearing Account : This account hits when there is a difference between the revenue recognized and Selling Price times the Quantity invoiced. For this account to hit, enabling this feature in transaction batch sources is required.


Freight Account : This is the freight account capturing the carrying costs related to transactions.

Receivable Account :  This account hits when invoicing of the transaction takes place.

Revenue Account : This account hits when a sale is recognized. For Accrual basis of accounting, Revenue is recognized when the items/services have been delivered and not when payment is received.

Tax Account: This account hits when a tax has been applied on the transaction which needs to be accounted/recorded.

Unbilled Receivable: This account hits when the Invoicing rule used is Bill in Arrears (Transaction is invoiced after revenue is recognized).

Unbilled Revenue: This account hits when Invoicing rule used is Bill in Advance (Transaction is invoiced before the revenue of it is recognized).


Comments

Post a Comment

Popular posts from this blog

Prepayments in Oracle Receivables R12

When you determine that a prepayment is required, you record the payment information in your feeder system (eg: OM) , and the information is passed to Oracle Receivables. . When the order is later sent to Receivables for invoicing, AutoInvoice creates an invoice that is marked as prepaid. Setups :   1. In OM:System parameters set 'Allow Multiple Payments' to 'Yes'. 2. Create a Customer Bank Account. 3. Assign the Customer bank Account to Customer Site. 4. Create a Payment Method and assign an internal bank account (Receipt Method in Receipt Class         window). 5. Create a document sequence for the Payment method.  6. Create or Update a Payment term by checking Prepayment checkbox. 7. Create a Prepayment Receivable Activity. Process :  1. Book a Sales Order in OM responsibility.  2. Go to Action in Sales Order header and select Payments.  3. Select Payment Type as Cash , 100% (Percent amount of sales order t...
Post a Comment
Read more

Oracle Apps AR R12 Interface Tables and Information

RECEIVABLE INTERFACE TABLES Transactions RA_INTERFACE_LINES_ALL This table acts as an intermediate storage of data between your external sytem, oracle subledgers and oracle receivables. You must enter all mandatory columns and columns required as per the transaction in this table (using a custom feeder program) alongwith the required oracle setups, so that Autoinvoice Master Program (AMP) can validate the information without any errors. Once data is validated, Autoinvoice Import Progra m (AIP) triggered by AMP imports data for various receivable batch sources (One AIP for each batch is trigerred) and creates oracle receivable transactions. Depending on the transaction you would create, populate the below transaction flexfields in the columns of this table :  Line Transaction Flexfield - Use when creating invoice lines.  interface_line_context interface_line_attribute1 to interface_line_attribute15 ( Use any as per requirement ). Reference Transaction...
Post a Comment
Read more