1z0-1107-2 VCE Exam Download

These are three components that will be useful for the automatic reconciliation of bank statements with system transactions. Automatic reconciliation is a feature that enables you to reconcile bank statement lines with system transactions without manual intervention. You can use various components to define the criteria and conditions for automatic reconciliation1. Some of these components are:

• Transaction Grouping Rules: These are rules that determine how system transactions are grouped together for reconciliation purposes. You can group transactions by attributes, such as bank account, currency, transaction type, or payment method.
• Tolerance Rules: These are rules that define the acceptable differences between bank statement lines and system transactions for reconciliation purposes. You can define tolerances by amount or percentage, and by bank account or currency.
• Matching Rules: These are rules that specify how bank statement lines and system transactions are matched for reconciliation purposes. You can match transactions by attributes, such as transaction number, amount, date, or reference number. References: Oracle Financials Business Process Certified Foundations Associate Rel 1

Statistical Currency is the currency that you should use to create the journal entry to load the headcounts. Statistical Currency is a special currency that is used to record non-monetary values, such as headcounts, units, or hours. You can use Statistical Currency to create allocation journals based on non-monetary bases or drivers1. References: Oracle Financials Business Process Certified Foundations Associate Rel 1

These are four true statements about an effective subledger period close. A subledger period close is a process that ensures that all transactions and adjustments in a subledger application, such as Projects, Payables, Fixed Assets, or Receivables, are accounted and transferred to General Ledger for a given period. To perform an effective subledger period close, you need to follow a recommended sequence of steps and dependencies among different subledger applications1. Some of these steps and dependencies are:

• Projects must be closed before Fixed Assets, which means that you need to ensure that all project-related transactions and adjustments are accounted and transferred to General Ledger before creating or adjusting any assets from projects in Fixed Assets.
• Payable must be closed before Projects, which means that you need to ensure that all supplier invoice and payment transactions and adjustments are accounted and transferred to General Ledger before creating or adjusting any project expenditures from Payables in Projects.
• Fixed Assets must be closed before Payables, which means that you need to ensure that all asset addition, depreciation, adjustment, and retirement transactions and adjustments are accounted and transferred to General Ledger before creating or adjusting any supplier invoices from assets in Payables.
• Fixed Assets must be closed before Receivables, which means that you need to ensure that all asset-related transactions and adjustments are accounted and transferred to General Ledger before creating or adjusting any customer invoices from assets in Receivables. References: Oracle Financials Business Process Certified Foundations Associate Rel 1

Process Category is an optional parameter that can be selected while submitting the create accounting job to generate accounting entries on a periodic basis. It helps you to restrict the events selected for accounting and it is useful for segmenting events based on processing volumes. For example, you can create different process categories for high-volume and low-volume transactions, or for different subledger applications2. References: Oracle Financials Business Process Certified Foundations Associate Rel 1