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 used as selection criteria when submitting a payment process request. A payment process request is a request to pay one or more invoices or other payments within a single payment batch. You can use various attributes to filter and select the invoices or payments that you want to include in the payment process request2. Some of these attributes are:

• Invoice Type: This attribute allows you to select invoices based on their type, such as standard, credit memo, debit memo, prepayment, or interest.
• Pay Through Date: This attribute allows you to select invoices based on their due date or discount date. Only invoices that are due or eligible for discount on or before the pay through date are selected.
• Pay Groups: This attribute allows you to select invoices based on their pay group, which is a grouping of invoices that share common payment attributes, such as payment method, payment priority, or payment terms. 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

These are three additional attributes that are considered for duplicate invoice check when the Additional Duplicate Invoice Check feature is enabled. The Additional Duplicate Invoice Check feature is a feature that enables you to perform a more comprehensive check for duplicate invoices in Oracle Payables. The feature compares the invoice number, supplier name, supplier site, invoice amount, invoice date, and invoice type of the invoices and flags any potential duplicates1. References: Oracle Financials Business Process Certified Foundations Associate Rel 1

These are three predefined sources that you can choose to create the Cash Positioning report by using the system transactions. The Cash Positioning report is a report that shows your cash inflows and outflows for a given period and bank account. You can use various sources to populate the report with system transactions, such as AR Invoices, AP Invoices, AP Payments, AR Receipts, GL Journals, or Cash Forecasting1. References: Oracle Financials Business Process Certified Foundations Associate Rel 1

These are the four factors that are responsible for calculating taxes on Receivables transactions. Products are the goods or services that are sold, and they may have different tax rates or exemptions. Plans are the pricing or discounting schemes that may affect the taxable amount. Processes are the business flows or events that trigger tax calculation, such as invoicing, adjusting, or crediting. Parties are the entities involved in the transaction, such as customers, suppliers, or legal entities, and they may have different tax statuses or registrations. Places are the locations where the transaction occurs or where the products are delivered, and they may have different tax jurisdictions or rules1. References: Oracle Financials Business Process Certified Foundations Associate Rel 1