The steps in bold italics are required. To create accounting setups, complete the General Ledger prerequisites, such as defining a chart of accounts and accounting calendar. To use additional subledger accounting methods other than Standard Accrual or Standard Cash, define them using Subledger Accounting. When defining ledgers in Accounting Setup Manager, assign a subledger accounting method if planning to use Subledger Accounting to integrate data from transaction sources.
Note: Subledger Accounting Options. The Accounting Setup Manager provides the following pages:. Create new legal entities and assign specific balancing segment values to legal entities to help identify legal entities during transaction processing and reporting.
You can take full advantage of all of the legal entity-related features, such as Intercompany Accounting. Note: Legal Entities Overview. Identify the associated primary ledger for any legal entity, ledger, operating unit, and reporting currency. After creating an accounting setup structure, update the accounting options immediately after creating the structure or later. The following table describes the steps to create accounting setups using Accounting Setup Manager.
Each required setup step must be completed before you can complete your accounting setup. Note: If you plan to use jurisdictions that do not come seeded, you can define your own jurisdictions using Legal Entity Configurator before you define legal entities. A jurisdiction is the intersection of the physical territory and type of legislation within which judicial authority may be exercised. The jurisdiction is used to assign a territory to a legal entity.
Note: Creating Accounting Setup Structures. Note: Reporting Currencies. Note: Intercompany Accounts. Note: Intracompany Balancing Rules. Note: Primary to Secondary Ledger Mapping. Note: Completing Accounting Setup. Define one or more legal entities using Accounting Setup Manager's Legal Entities tab if planning to assign legal entities to accounting setups.
You can also define legal entities using Legal Entity Configurator. The only difference is that you can assign balancing segment values to legal entities using Accounting Setup Manager. Assigning balancing segment values to legal entities is optional; however, it is strongly recommended that you assign specific balancing segment values to each legal entity to help identify legal entities during transaction processing and reporting.
This is particularly important for accounting setups that use the accounting setup where multiple legal entities share the same primary ledger. By assigning balancing segment values to legal entities, you can also take advantage of all of the legal entity accounting features available, such as intercompany accounting. If you do not assign any balancing segment values to your legal entities, then all balancing segment values will be available for transaction processing.
Note: If using multiple value sets for the balancing segment across charts of accounts, be sure to assign the correct value set to the legal entity. Once assigned, you cannot remove the value set from legal entities.
However, there is no harm in assigning the wrong value set or assigning balancing segment values for the wrong value set; the system will ignore it during transaction processing. Tip: If you are unsure about the value set to assign to each legal entity, allow Accounting Setup Manager to do it. When assigning a legal entity to an accounting setup, Accounting Setup Manager automatically assigns the correct value set associated with the legal entity's primary ledger and secondary ledger, if used.
Any balancing segment values assigned to a legal entity are automatically assigned to the legal entity's ledger when completing the accounting setup. When entering transactions using Oracle subledgers, use only the valid balancing segment values that are assigned to the legal entity. When entering journals in General Ledger, use only the valid balancing segment values assigned to the ledger's legal entities and the ledger itself.
If no balancing segment values are assigned to the legal entities or ledgers, then all balancing segment values will be available to enter transactions and journal entries.
Special Note for Disabling Legal Entities: If disabling a legal entity by entering an end date, also enter end dates for all assigned balancing segment values to prevent the use of the balancing segment value. If you have an accounting setup with multiple legal entities assigned and specific balancing segment values assigned to legal entities, you cannot complete the accounting setup if the following violations exist:.
Note: Accounting Setup Manager does not check for overlapping balancing segment values assigned to legal entities in different accounting setups. Therefore, ensure that the correct balancing segment values are assigned to legal entities in all accounting setups. Note: Before the accounting setup is complete, delete and add balancing segment values to legal entities at any time. After completing the accounting setup, you cannot delete balancing segment values from legal entities; you can end date the balancing segment value to prevent the use of it.
It is recommended that you designate the balancing segment of the chart of accounts as the legal entity or company segment.
If there are multiple legal entities that use different charts of accounts, limit the number of value sets you define for the balancing segment to ease maintenance efforts.
This allows you to share value sets across multiple charts of accounts and assign unique balancing segment values for each legal entity that is consistent across charts of accounts. Use the Create Legal Entity page to create legal entities. The following prerequisites are required only if planning to assign balancing segment values to legal entities:. Click Apply or click Save and Add Details to enter additional information for the legal entity that includes the following:.
Note: Adding this additional information is not required for creating an accounting setup. Note: You can quickly create legal entities when creating an accounting setup. Select one or more balancing segment values to assign to this legal entity. You cannot assign parent values. Note: Be sure to assign unique balancing segment values to each legal entity.
You cannot complete the accounting setup if multiple legal entities assigned to the same accounting setup have overlapping balancing segment values assigned or only some of the legal entities have balancing segment values assigned. Note: Once you add a legal entity to an accounting setup and complete the accounting setup, you cannot remove balancing segment values from legal entities.
You can only disable balancing segment values by entering an end date. Update the balancing segment value assignments for the legal entity in one of the following pages:. Assign a legal entity to an accounting setup to automatically assign the value set associated with the legal entity's ledger. If you accidentally assign the wrong value set that is not associated with any of the legal entity's ledgers, the invalid value set will be ignored during transaction processing.
If the legal entity is assigned to a complete accounting setup, you cannot remove its balancing segment values. You can disable them by entering an end date.
The value set associated with one or more of the legal entity's ledgers will be automatically assigned. If multiple value sets are assigned to the legal entity, assign the same balancing segment value across value sets.
The accounting setup structure defines the framework or skeleton of an accounting setup. The following table lists the prerequisites for accounting setup manager. Creating an accounting setup includes the following steps:. Assigning legal entities to accounting setups is optional. Assign legal entities if you are planning to use Oracle financial subledgers that require a legal entity context for transaction processing.
Also, assign legal entities if you are planning to use legal entity specific features, such as intercompany accounting. If creating legal entities from the Assign Legal Entities page, you are not creating a complete definition of your legal entity. Complete the definition of the legal entity later from the Legal Entities tab. Specify the ledger attributes for the primary ledger. The primary ledger acts as the primary accounting representation. To maintain additional currency representations of primary or secondary ledgers, assign reporting currencies to them.
Note: Add secondary ledgers and reporting currencies to accounting setups at any time. Before completing the accounting setup, you can delete secondary ledgers and reporting currencies.
After completing the accounting setup, you can only disable the conversion of reporting currencies and secondary ledgers.
Note: You cannot assign a calendar if it contains gaps between periods or it does not have a full fiscal year defined. Optionally assign a subledger accounting method if planning to use Subledger Accounting to integrate data from Oracle financial subledgers or external feeder systems. Note: Once you assign a subledger accounting method, you must always have a subledger accounting method assigned.
You can change the subledger accounting method at any time. Note: To define a subledger level secondary ledger, assign a subledger accounting method to both the primary ledger and to this secondary ledger.
Note: To define an adjustments only secondary ledger, the chart of accounts, accounting calendar, and currency must be the same as the primary ledger. If you only want to use the Adjustments Only secondary ledger for manual adjustments in General Ledger, do not assign a subledger accounting method. To use the Adjustments Only secondary ledger for both manual and automated adjustments from Subledger Accounting, assign a subledger accounting method to both the primary and secondary ledger.
Note: Data Conversion Levels. If assigning a balance level secondary ledger that uses a different currency from the primary ledger, a balance level reporting currency is automatically assigned to the primary ledger if you did not create one. For example, if the primary ledger's currency is EUR and you assign a balance level secondary ledger whose currency is CAD, the system automatically creates a balance level reporting currency for the CAD currency.
This reporting currency is used as the source representation when transferring CAD balances to this secondary ledger. In the Add Reporting Currency page, enter a currency and one of the following currency conversion levels:. Note: The currency of the balance level reporting currency cannot be the same currency as its source ledger. Journal : maintains journals and balances in the reporting currency using the General Ledger Posting program. Subledger: maintains a currency representation of the source ledger's subledger journals, General Ledger journals, and balances using both Subledger Accounting and the General Ledger Posting program.
Note: The subledger level reporting currency requires a subledger accounting method to be assigned to the primary ledger. Note: You cannot assign subledger level reporting currencies to secondary ledgers. Carefully review and save the accounting setup structure to finish creating the framework of the accounting setup before proceeding to the Accounting Options. The Accounting Options page is displayed in a checklist format to complete the relevant setup steps to make the accounting setup ready for entering transactions and journals.
Before entering transactions, complete all of the required setup steps for each accounting setup. If using secondary ledgers, complete all of the required setup steps for the primary ledger before completing the setup steps for the secondary ledgers. Query an existing accounting setup from the Accounting Setups page, and then select the Update Accounting Options icon. The Legal Entities region of the Accounting Options page allows you to do the following:.
Once the accounting setup is complete, you cannot remove any of its legal entities. To disable a legal entity, end-date it. Once you end-date a legal entity, you cannot enter new subledger transactions against the legal entity. You can use the legal entity's balancing segment values to enter manual journal entries in General Ledger.
This allows you to enter adjusting entries during the accounting close. If you end-date a legal entity, end date its balancing segment value to prevent the use of the balancing segment value for journal entries. Note: If you use balancing segment values to represent legal entities, do not assign the same balancing segment values to multiple legal entities that are assigned to different accounting setups.
Accounting Setup Manager will not prevent you from assigning the same values to legal entities in different accounting setups. You can only remove balancing segment values before the accounting setup is complete. A balancing segment value removed from one legal entity can be assigned to another legal entity within the same or different accounting setup. Note: If the accounting setup is complete, you cannot remove any balancing segment values from the accounting setup's legal entities.
To disable the balancing segment value, end-date it. You can end-date balancing segment values at any time. If you end-date a balancing segment value, you cannot enter new transactions with dates after the end-date.
You can query historical transactions and report on the end-dated balancing segment value. Note: If you end-date a legal entity, end-date the balancing segment values that are assigned to the legal entity. This prevents users from entering transactions using a balancing segment value that is associated with an inactive legal entity.
The primary ledger setup steps are as follows:. Note: Accounting Setup Manager Checklist. The same setup steps for the primary ledger also apply to secondary ledgers. The following setup step applies only to secondary ledgers:.
Note: Add secondary ledgers at any time after completing the ledger options for the primary ledger by clicking Add Secondary Ledgers. A ledger determines the chart of accounts, accounting calendar, currency, subledger accounting method, and ledger processing options for each company, legal entity, or group of companies and legal entities.
Each accounting setup requires a primary ledger that acts as the main record-keeping ledger for none or one or more legal entities that use your main chart of accounts, accounting calendar, subledger accounting method, and currency to record and report on all of your financial transactions. When creating an accounting setup structure, specify the ledger attributes for the primary ledger and optionally one or more secondary ledgers. The ledgers assigned when creating the accounting setup structure are not completely defined; complete the ledger options for each ledger to complete the ledger definition.
Assign the ledger to the GL Ledger Name profile option for each Subledger responsibility to grant access to ledgers used by Oracle Subledgers. Assign the appropriate data access set to the profile option GL: Data Access Set for each General Ledger responsibility to grant access to ledgers used by General Ledger. If enabling average balance processing for the ledger, General Ledger tracks and maintains average and end—of—day balances. Note: You can only enable average balances or average balance consolidation for your secondary ledger if average balances or average balance consolidation is also enabled for its primary ledger.
Note: You cannot enable average balances if your ledger is enabled for secondary segment tracking. Recommended for Subledger Accounting Rounding Differences account to use a specific account to track small currency differences during currency conversion.
This account captures the net activity of all revenue and expense accounts when calculating the average balance for retained earnings. Recommended for Subledger Accounting Entered Currency Balancing Account to use Subledger Accounting to balance foreign currency subledger journals by the entered currency and balancing segment value. Ledger Currency Balancing Account to use Subledger Accounting to balance subledger journals by the ledger currency and balancing segment value. Required for Average Balances Define transaction calendars to use average balance processing.
Transaction calendars ensure journal entries created in General Ledger and Oracle Subledger Accounting, if used, are only booked on valid business days. Query an existing accounting setup from the Accounting Setups page and then choose the Update Accounting Options icon. Note: You can enter journal batches for a future enterable period, but you cannot post the batches until a period is opened. Tip: Minimize the number of future enterable periods to prevent users from accidentally entering journal entries in an incorrect period.
Note: A rounding differences account is recommended for Subledger Accounting. Note: Subledger Accounting offers features for controlling how the accounting program deals with rounding differences. Note: For accounting setups with multiple legal entities, enabling intracompany balancing enables both intercompany and intracompany balancing for a journal that includes multiple legal entities. Note: When you enable Journal Approval, only journal entries that use actual amounts and the Manual journal source will automatically have Journal Approval enabled.
To require journal approval for budget or encumbrance journals or for journals using a source other than Manual, you must select the Require Journal Approval check box for the appropriate journal source in the Journal Sources window in Oracle General Ledger. Note: The rate types specified for the ledger are used to assign default rate types for any balance level reporting currencies assigned to this ledger.
You can override the default rate types for each balance level reporting currency. Net Income Account: Captures the net activity of all revenue and expense accounts when calculating the average balance for retained earnings.
Rate Type: Enter any daily conversion rate type except User for translating average balances. General Ledger automatically translates period-average-to-date balances. You can also choose to have translation maintain end-of-day, quarter-average-to-date, and year-average-to-date balances by selecting the appropriate check boxes. Transaction Calendar: Ensures that journal entries created in General Ledger and Subledger Accounting are posted only to valid business days; not required for average balance consolidation ledgers.
Note: You can only enable average balance processing for those ledgers that require it. This ensures that you incur no additional overhead unless you need average balance processing enabled. Note: You can only enable average balances for a secondary ledger if its primary ledger has average balances or average balance consolidation enabled. Note: You can only enable average balance consolidation for a secondary ledger if its primary ledger has average balances or average balance consolidation enabled.
Click Next to review your ledger options and then click Finish to complete your ledger definition. To navigate to the ledger definition pages, click the Update icon for the ledger; or click the ledger name link and then the Update button. For example, the USD primary ledger balances can be expressed in CAD or Yen by assigning a balance level reporting currency to the primary ledger.
Unlike secondary ledgers, reporting currencies can only differ by currency from their source ledger. Subledger: Maintains a currency representation of your subledger journals, General Ledger journal entries, and balances.
When using the subledger level reporting currency, you must define subledger accounting rules using Subledger Accounting. These rules provide instructions on how to convert subledger data entered into the source ledger to one or more subledger level reporting currencies. You must also define journal conversion rules. General Ledger Posting uses the journal conversion rules to automatically replicate specific journals, such as manual journal entries, to one or more subledger level reporting currencies.
Note: Subledger level reporting currencies can only be assigned to primary ledgers, not secondary ledgers. Journal: Maintains General Ledger journal entries and balances in another currency representation. Journal level reporting currencies are maintained using the General Ledger Posting Program. Every time a journal is posted in the source ledger, the journal is automatically converted to the respective journal level reporting currency based on the journal conversion rules defined.
The General Ledger Translation program is used to convert balances from the source ledger to the balance level reporting currency. When you run Translation in your primary or secondary ledger and specify a target currency, the translated balances are reflected in the balance level reporting currency.
Note: If a balance level reporting currency is not assigned to the ledgers in the accounting setup, a balance level reporting currency is automatically created the first time Translation is run. The name of the balance-level reporting currency is the same as its source ledger except its currency code, such as USD , is appended to the end of its name.
Note: The subledger level and journal level reporting currencies act similarly to ledgers. You must open and close the periods for these reporting currencies before you can enter transaction and journal entries. You can also enable journal approval for these reporting currencies if planning to enter manual journal entries directly to these reporting currencies.
If reporting currencies are assigned to ledgers when creating an accounting setup structure, the status for the Reporting Currencies step is In Process. To complete the accounting setup, update the reporting currency and complete the conversion options for all reporting currencies that are assigned.
If no reporting currencies are assigned to the ledgers when creating the accounting setup structure, the Reporting Currencies step is not required and the status is Not Started. Note: Adding Reporting Currencies. The following table describes selected options for journal and subledger level reporting currencies. Note: Disabling the Conversion of Reporting Currencies.
Warning: Any changes you make to the Rounding Differences Account in the source ledger will automatically be applied to all of its journal and subledger level reporting currencies. If you have a different rounding differences account assigned to your reporting currencies and you change the rounding differences account for the source ledger, such as removing one, changing one, or adding one, be sure to also update the rounding differences account for each of the reporting currencies.
To require journal approval for budget or encumbrance journals or for journals using a source other than Manual, you must mark the Require Journal Approval check box for the appropriate journal source in the Journal Sources window in Oracle General Ledger. If Yes is selected, then the conversion rate type used to enter the transaction in the source ledger will be retained when converting the same transaction from the transaction currency amount to this reporting currency.
Note: If the original transaction rate type is User or EMU Fixed, the default rate type assigned to the reporting currency will always be used. If No is selected, then the default rate type specified in the Default Rate Type field will be used to convert transactions to this reporting currency.
An EMU fixed rate relationship exists between the transaction currency and the currency of the reporting currency. In this case, the EMU Fixed conversion rate type is used. The transaction currency is the same as the currency of the source ledger, such as the primary or secondary ledger. In this case, a conversion rate type does not exist for the transaction and the default rate type is used. The transaction currency is the same as the currency of the reporting currency. In this case, the User conversion rate type is used with a default rate of 1.
A User rate is used for the transaction. In this case, the User conversion rate type is used. The reporting currency conversion is completed in two steps via the default rate type assigned to the reporting currency.
Note: If the Account Type Specific Conversion is enabled, you can determine whether Accounting Setup Manager should inherit the conversion type used in the source ledger. If Report an Error is selected, the system will report an error and prevent a transaction or journal from being posted in the source ledger; a conversion rate will need to be specified to successfully convert data entered in the source ledger to this reporting currency.
If Use Last Rate is selected, the system will use the last rate defined for a particular rate type if it cannot find a currency conversion rate; if enabled, specify a number for the Number of Days to Find the Last Rate. Select Yes to retain the person who entered the journal in the source ledger as the Created By user. General Ledger Posting uses the journal source and category conversion rules to determine the journals based on journal source and category combinations to automatically convert to this reporting currency.
Journal sources identify the origin of journal entry transactions, such as Purchasing or Payables. Journal categories describe the purpose of journal entries, such as purchase requisitions or purchase orders. Specifying a journal source and category combination and selecting Yes in the Convert Journals to this Reporting Currency field instructs the General Ledger Posting program to automatically convert those journals to this reporting currency when they are posted in the source ledger.
The journal source and category Other represents all other journal sources and categories other than those explicitly defined. To convert the majority of journals to this reporting currency, specify Yes for the Other journal source and category and then select No for the journal source and category combinations that you do not want converted.
If you do not want the majority of the journals to be automatically converted to this reporting currency, specify No for the Other journal source and category and then selectively add those journal source and category combinations that you do want converted.
This means that if you use Mass Maintenance to move or merge balances between accounts in the source ledger, the same accounts are moved or merged in the reporting currency.
For subledger level reporting currencies, the journal sources for all transaction sources that use Subledger Accounting must be set to No in the Convert Journals to this Reporting Currency field. Any journal source that uses Subledger Accounting to generate its accounting entries must not be converted to the reporting currency using General Ledger Posting because Subledger Accounting automatically performs the conversion for these subledger journals. Warning: If you incorrectly choose Yes in the Convert Journals to this Reporting currency field for any transaction sources that use Subledger Accounting, the journal will be double counted; once by Subledger Accounting and once by General Ledger Posting.
You will need to reverse the journal in General Ledger. Note: To find all transaction sources that integrate with Oracle Subledger Accounting, query them in the Subledger Application form that is accessed from the Subledger Accounting Setup menu.
Note: If integrating with transaction sources that do not use Subledger Accounting and you want to maintain journals from these subledgers in the subledger level reporting currency, do not use Oracle's seeded journal sources. For example, if you use a non-Oracle Receivables application, you should create your own journal source for that application instead of using the seeded source Receivables that is reserved for Oracle sources.
If you use the seeded source to import data from third party systems, those journals will not be converted to a subledger level reporting currency when you post them in the primary ledger. This section describes examples that illustrate how journals are converted based on different journal conversion rules.
It also shows that no conversion takes place if there is not a match with any of the defined conversion rules. The following shows an example of matching a journal source but not a category; and another example of matching a journal category but not a source. The rule for the source always overrides the rule for the category. Change the journal source and category conversion rules at any time. Caution: It is strongly recommended that you do not change the conversion rules once you begin entering transactions.
Doing so may result in inconsistent transaction amounts and account balances between your source ledger primary or secondary ledger and its reporting currencies. Add reporting currencies to primary or secondary ledgers at any time.
If adding journal level or subledger level reporting currencies to existing ledgers that have periods opened, you must initialize the beginning balances for your reporting currency and optionally choose to convert historical data from the source ledger to the reporting currency. Historical Conversion refers to converting the historical transactions of the source ledger to the journal level or subledger level reporting currency. Note: Historical Conversion does not apply to reporting currencies that are assigned to new accounting setups.
Note: Before adding journal or subledger level reporting currencies, carefully review the information in the Implementation Considerations section of the Journal or Subledger-Level Reporting Currencies chapter of the Oracle General Ledger User Guide. Note: If you allow users to make adjustments in Oracle Projects to expenditure items that represent receipts, receipt non-recoverable tax, or exchange rate variances, then Oracle Projects does not perform accounting for adjustments in reporting currencies and subledger level secondary ledgers if the secondary ledger currency differs from the primary ledger currency.
You can only assign subledger level reporting currencies to primary ledgers that have subledger accounting methods assigned. If assigning a reporting currency to a secondary ledger, the currency conversion level of the reporting currency must be equal to or less than the Data Conversion Level of the Secondary Ledger. The following table lists the types of reporting currencies that can be assigned to Secondary Ledgers. Note: : Secondary ledgers cannot have subledger level reporting currencies assigned.
To initialize beginning balances and convert historical transactions or journals to this reporting currency, enter Data Conversion Initialization options as described in the following table.
Note: Reporting currencies can only be deleted before the accounting setup is complete. If the reporting currency acts as the source representation for a secondary ledger, delete the secondary ledger before deleting the reporting currency. After the accounting setup is complete, you cannot delete reporting currencies; you can disable the conversion of subledger and journal level reporting currencies.
Define remit-to addresses to inform your customers where to send payments. Associate each remit-to address with one or more state, country, and postal code combinations. For example, if you want your customers in California and Nevada to send their payments to a specific address, enter the remit-to address and associate the states CA and NV with this address.
Remit-to addresses are assigned based on the bill-to address on the transaction. Context: Define remit-to addresses for each installation. For each operating unit, associate each remit-to address with a state and country. Tip: It is a good idea to set up a default remit-to address, even if you have other remit-to addresses defined, because Receivables can use this address if the bill-to location on the transaction is not covered by any other remit-to address assignment.
This may happen, for example, when you create transactions for a new customer. Define customer relationships to enable customers to apply receipts to related customer transactions.
To restrict receipt application to only related customers, define relationships between your customers and set the system option Allow Payment of Unrelated Invoices to No. Receivables lets you define one way and reciprocal relationships between your customers.
If you want to provide one party with access to another party's accounts and transactions, then define party paying relationships. To import receipts from a bank file using AutoLockbox, define lockboxes. For each lockbox, enter the lockbox number, bank name, batch source, bank account, bank origination number and cash account. If you use AutoLockbox to import receipts, define a transmission file format.
Transmission formats specify how data in your lockbox bank file is organized so it can be successfully imported into the Receivables interface tables.
Receivables provides several standard transmission formats you can modify to meet your needs. Proceed to the next step if you defined units of measure classes while setting up another Oracle Applications product.
Use the Units of Measure Classes window to define and update groups of units of measure with similar characteristics for example, Volume or Length. A class consists of a base unit of measure and other assigned units of measure. Use this window to define the base unit of measure for each class.
Proceed to the next step if you defined units of measure while setting up another Oracle Applications product. Use the Units of Measure window to define one or more units of measure.
Each item that you define in Receivables must have a primary unit of measure that you will have defined in this window. The number of units of measure that you define in this window depends on the variety of physical characteristics of your organization's inventory. Define standard memo lines to enter predefined lines for debit memos, on-account credits, and invoices.
When you define standard memo lines, you can specify whether a line is for charges, freight, line, or tax. Receivables also lets you define one chargeback and one debit memo reversal line. If your organization needs to apply receipts to transactions in different currencies, set up Receivables for cross currency receipts. To do this, define a cross currency rounding account in the System Options window, and define a suspense account in Oracle General Ledger.
Oracle E-Business Tax provides a tax vendor extension that integrates external tax calculation programs with Oracle Applications. This extension performs complex tax calculations to create and store tax data. By assigning unique numbers to documents, you can account for each transaction you enter and the document that accompanies it. To enable sequential numbering, set the Sequential Numbering profile option to either 'Always' or 'Partially Used'.
You must then define and assign categories and sequences for each transaction type, receipt method, adjustment, and late charge activity that you use. Context: Define categories and sequences for each installation. Assign sequences to categories for each ledger. Use balance forward billing to print a single bill that includes all of a customer's transactions for the billing period and any balance carried forward from the previous billing period.
This lets you send one consolidated bill to a customer, instead of a separate invoice for each transaction. You can calculate late charges against past due debit items for each customer, account, or site. Late charges are calculated according to your organization's late charge policy.
Your late charge policy indicates if you assess late charges against your customers and, if so, how those late charges are calculated. Set Up Underlying Oracle Applications Technology In addition to the setup steps that follow, be sure to set up underlying Oracle Applications technology, including: performing systemwide setup tasks such as configuring concurrent managers and printers managing data security, which includes setting up responsibilities to allow access to a specific set of business data and complete a specific set of transactions, and assigning individual users to one or more of these responsibilities.
Step 1 Define Ledgers Required If you previously defined your ledger or ledgers while setting up a different Oracle Applications product, proceed to the next step. You need to define at least one ledger before you can implement and use Receivables. Step 2 Decide How to Use the Account Generator Required The Account Generator ensures that Receivables substitutes the correct balancing segment values during various accounting activities against transactions and receipts.
Context: Perform this step for each ledger. Context: Perform this step for each installation. Step 4 Define Flexfields For Receivables, you need to define both key and descriptive flexfields. Define Key Flexfields Required You can use the Territory flexfield for recording and customized reporting on your territory information. Define Descriptive Flexfields Optional Define a descriptive flexfield if you want to capture information that is not otherwise captured in a Receivables form.
See: Descriptive Flexfields. Context: Perform this step for each business group. See: Organizations. See: AutoCash Rule Sets. Step 7 Define Receivables Lookups Optional Receivables provides several default lookups which are used throughout the application to provide validated default values and list of values choices.
See: Defining Receivables Lookups. Step 8 Define Demand Class Lookups Optional Demand classes are categories you can use to segregate scheduled demand and supply into groups, so that you can track and consume the groups independently.
See: Demand Class Lookups. Step 9 Define Invoice Line Ordering Rules Optional If you are using AutoInvoice, define invoice line ordering rules to specify how you want to order and number transaction lines after AutoInvoice groups them into invoices, debit memos, and credit memos. See: Grouping Rules. Step 12 Define System Options Required Define your accounting, discount, and invoice system options to control how Receivables works.
Context: Perform this step for each operating unit. See: Defining Receivables System Options. Step 13 Set Up Flexible Address Formats Optional To enter customer, supplier, bank, check, and remit-to addresses in country-specific formats, set up flexible address formats.
See: Setting Up Flexible Addresses. Step 14 Maintain Countries and Territories Optional Use the address style field to assign address styles to countries if you want to use the Flexible Address Formats feature. Step 15 Define Payment Terms Required Define payment terms to determine the payment schedule and discount information for customer invoices, debit memos, and deposits. See: Payment Terms. Step 17 Define Accounting Rules Optional If your accounting method is Accrual, define accounting rules to create revenue recognition schedules for your invoices.
See: Accounting Rules. Step 18 Open Accounting Periods Required Open or close periods in your accounting calendar to control the recording of accounting information for these periods. Step 19 Define AutoAccounting Required Define AutoAccounting to specify the general ledger accounts for transactions that you enter manually or import using AutoInvoice.
See: AutoAccounting. Step 22 Define Transaction Types Required Define the transaction types that you assign to invoices, debit memos, commitments, chargebacks, credit memos, on-account credits, and bills receivable. See: Transaction Types. Step 23 Define Transaction Sources Required Define the transaction sources that you assign to invoices, debit memos, commitments, credit memos, on-account credits, and bills receivable.
See: Transaction Batch Sources. Step 24 Define Collectors Required Define collectors to assign to your customers through credit profile class assignments. See: Collectors. Step 25 Define Approval Limits Required Define approval limits to determine whether a Receivables user can approve adjustments or credit memo requests.
See: Approval Limits. Proceed to the next step if you already defined your remittance banks in Oracle Cash Management. See: Defining Internal Banks. Step 27 Define Distribution Sets Optional Define distribution sets if you enter non-invoice related receipts and you want to use a predefined revenue distribution set. See: Distribution Sets. Step 28 Define Receivables Activities Required Define Receivables Activities to provide default accounting information when you create adjustments, discounts, late charges, miscellaneous cash transactions, and bills receivable.
See: Receivables Activities. Step 29 Define Receipt Programs Optional To create Automatic Receipts, define additional receipt or remittance format programs that you use to send paper and electronic documents to your customers and remittance banks.
See: Automatic Receipt Programs. Step 30 Define Receipt Classes Required Define receipt classes to specify whether receipts are created manually or automatically. See: Receipt Classes. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Skip to content 1. Define Your Chart of Accounts 2. Define Conversion Rate Types and Conversion Rates to Support Multiple Currencies optional : — Conversion Rate Types : Define the conversion rate types you want to use to maintain daily exchange rates and to enter foreign currency journals.
Share this: Twitter Facebook. Like this: Like Loading Post navigation Previous Post Reconciling Receivables. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. Follow Following. Oracle Apps Reference Join 99 other followers. Sign me up. Already have a WordPress. Log in now.
0コメント