1z0-1107-2 Exam Dumps : Oracle Financials Business Process Foundations Associate Rel 2

These are two true statements about creating case folders within the Customer Statement to Collections business process. A case folder is a collection of billing transactions that are related to a specific issue or dispute with a customer. You can create case folders to track and resolve issues that prevent customers from paying their invoices on time. You can also assign case owners, statuses, and priorities to each case folder1. Some facts about creating case folders are:

• Billing transactions can belong to multiple case folders, which means that a single invoice can be part of more than one issue or dispute.
• Billing transactions can be of multiple currencies, which means that you can include invoices with different currencies in the same case folder.
• Billing transactions must belong to the same bill-to customer, which means that you cannot mix invoices from different customers in the same case folder.
• Billing transactions must be of the same currency conversion type, which means that you cannot mix invoices with different conversion methods, such as corporate or spot rate, in the same case folder. References: Oracle Financials Business Process Certified Foundations Associate Rel 1

These are three attributes that can be captured on an Invoice Header while recording a supplier invoice in the Payables application. An Invoice Header is a section of an invoice that contains general information about the invoice, such as supplier details, invoice amount, invoice number, invoice date, payment terms, or description1. Some examples of these attributes are:

• Supplier Details: These are the details of the supplier who issued the invoice, such as supplier name, site, contact person, address, or tax registration number.
• Invoice Amount: This is the total amount of the invoice that is payable to the supplier, including taxes and charges.
• Invoice Number: This is the unique identifier of the invoice that is assigned by the supplier or by the system. References: Oracle Financials Business Process Certified Foundations Associate Rel 1

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