Get ready to pass the 1Z0-1055-24 Exam right now using our Oracle Cloud Exam Package [Q19-Q43]

March 2, 2026 admin 0 Comments

Rate this post

Get ready to pass the 1Z0-1055-24 Exam right now using our Oracle Cloud Exam Package

A fully updated 2026 1Z0-1055-24 Exam Dumps exam guide from training expert TopExamCollection

Oracle 1Z0-1055-24 Exam Syllabus Topics:

Topic	Details
Topic 1	Processing Expenses: This section evaluates the capabilities of Auditors in managing expense-related tasks156. It covers entering expense reports, managing expense approvals, processing expense reimbursements, managing corporate cards, auditing expense reports, and setting up expenses within the system. These skills ensure compliance with expense policies and accurate reimbursement processes.
Topic 2	Configuring Payables and Payments: This section assesses the skills of Implementation Consultants in configuring payables and payments within Oracle Financials Cloud156. It covers managing withholding and transaction taxes, configuring payables and payments, managing business units, managing sub-ledger accounting, and managing invoice and payment approvals1. These skills are vital for setting up and customizing the system to meet specific business requirements.
Topic 3	Managing Payables Invoices: This section measures the skills of Accounts Payable Administrators and explains invoice imaging and recognition solutions, creating and accounting for invoices, and managing suppliers within Oracle Financials Cloud156. These skills are fundamental for efficiently handling invoice processing and supplier relationships.

NO.19 MANAGE EXPENSE REPORT TEMPLATE
Task 1:
Create an Expense Report Template for the US1 Business Unit, where:
a. The effective start date is the current date.
b. The hotel expense type requires itemization and should include Internet, Room Rate, and Dinner.
c. The expense type is associated with the respective account
d. Card Expense Type Mapping is not enabled.
e. Company policy states that receipts
f. Users can indicate receipts are missing in their expense report and a warning should be displayed for any missing receipts.
g. All Expense Fields are optional.

NO.20 As an Expenses Administrator, you can control which expense values you do not want to automatically populate on the Create Expense Item page. You have therefore created the profile option EXM_DFLT_FROM_PREV_EXPENSE at the user level and set it to N (No).
Which three values will no longer populate from a previous expense item when a user enters a new expense item?

Expense Location

Template

Currency

Project and Task Number

NO.21 An installment meets all the selection criteria of a Payment Process Request, but it still does not get selected for payment processing.
What are the two reasons for this?

The pay-through date is in a future period.

The pay-through date is in a closed Payables period.

The invoice needs re-validation.

The invoice requires approval.

The invoice has not been accounted.

NO.22 While processing an expense report, the system placed a payment hold on the expense report. What are the two ways to release payment holds?

The expense auditor can manually release the payment hold in a discretionary manner.

The employee can manually release the hold from the notification.

Expenses automatically releases holds when receipts are received or waived.

The employee’s supervisor can manually release the hold from the notification.

Payables Manager can release payment holds in Payables.

NO.23 Which reference data sharing method can you use for Payables Payment Terms when working with reference data sets in Payables?

Assignment to one set only; no common values allowed

Assignment to multiple sets with common values allowed

Assignment to multiple sets; no common values allowed

Comprehensive and Detailed In-Depth Explanation:
In Oracle Fusion Applications, reference data sharing (also known as SetID) enables organizations to share common configuration data across various organizational units, such as business units, without unnecessary duplication. This approach streamlines maintenance and ensures consistency of reference data across the enterprise.
Payment Terms in Oracle Payables define the conditions under which a company pays its suppliers. These terms can vary between business units based on factors like regional practices or supplier agreements. To accommodate this variability, Oracle Payables employs a specific reference data sharing method for Payment Terms.
Reference Data Sharing Methods:
* Assignment to One Set Only; No Common Values Allowed:
* Each reference data object instance is assigned to a single set exclusively.
* No sharing of values across multiple sets.
* Example: Asset Prorate Conventions are defined and assigned to only one reference data set.
* Assignment to One Set Only, with Common Values:
* Reference data objects can be assigned to one set, but there’s a common set whose values are accessible to all business units.
* Example: Receivables Transaction Types are assigned to a common set that’s available to all business units.
* Assignment to Multiple Sets; No Common Values Allowed:
* A reference data object instance can be assigned to multiple sets.
* There’s no common set; each set operates independently.
* Example: Payables Payment Terms use this method, allowing each payment term to be assigned to one or more sets.
For Payables Payment Terms, the applicable method is “Assignment to multiple sets; no common values allowed.” This means that each payment term can be associated with one or more reference data sets, but there’s no overarching common set that includes all payment terms. This flexibility allows organizations to define payment terms specific to certain business units while also sharing others across multiple units as needed.
Practical Application:
* Shared Payment Terms: If multiple business units operate under similar payment conditions, a single payment term (e.g., “Net 30”) can be assigned to multiple reference data sets corresponding to those units.
* Specific Payment Terms: For unique business units with distinct payment agreements, specific payment terms (e.g., “Net 15”) can be created and assigned exclusively to the relevant reference data set.
This approach ensures that each business unit has access to the payment terms relevant to its operations without unnecessary proliferation of identical terms across the system.
References:
* Reference Data Sets and Sharing Methods
* Payment Terms

NO.24 You have been asked by the cloud customer to create some user-defined account derivation rules for Payables invoices that were imported from lease accounting.
Which two lease accounting source attributes are predefined and can be used in rule creation?

DFF values on the Asset tab

DFF values on the Schedule tab

Lease preparer

ROU Flag value

Lease location

Comprehensive and Detailed In-Depth Explanation:
In Oracle Lease Accounting, integration with Oracle Payables allows for the seamless import of lease-related invoices. To ensure accurate financial reporting, it’s essential to configure account derivation rules that map specific lease attributes to the appropriate general ledger accounts. Oracle provides a set of predefined source attributes that can be utilized in creating these rules.
Key Predefined Lease Accounting Source Attributes:
* DFF Values on the Asset Tab (Option A):
* Explanation: Descriptive Flexfields (DFFs) on the Asset tab capture additional, user-defined information related to leased assets. These fields can store bespoke data pertinent to an organization’s reporting requirements. When configuring account derivation rules, these DFFs can be referenced to derive specific accounting treatments based on the custom attributes recorded.
Reference: Accounting Configuration for Lease Accounting Invoices
ROU Flag Value (Option D):
Explanation: The Right-of-Use (ROU) flag indicates whether an asset is recognized as a right-of-use asset under lease accounting standards. This distinction is crucial for determining the appropriate accounting treatment for lease-related transactions. In account derivation rules, the ROU flag can be used to route transactions to the correct accounts, ensuring compliance with accounting standards.
Reference: Accounting Configuration for Lease Accounting Invoices
Other Options Analysis:
DFF Values on the Schedule Tab (Option B):
Explanation: While Descriptive Flexfields on the Schedule tab may capture additional information related to payment schedules, they are not explicitly listed among the predefined source attributes available for account derivation rule creation in Oracle Lease Accounting.
Lease Preparer (Option C):
Explanation: The individual who prepares the lease (Lease Preparer) is not a predefined source attribute available for configuring account derivation rules. Accounting rules typically rely on attributes directly impacting financial transactions rather than user-specific data.

NO.25 While creating the setup for employee bank accounts, you have the profile option CE_USE_EXISTING_BANK_BRANCH set to Yes.
What can the users now search for by default?

Bank Branch identifier

Bank Branch only

Bank and Bank Branch

NO.26 A Payables user creates a manual invoice, and a Withholding Tax Classification Code defaults on the invoice line when the invoice is saved. Where does this Withholding Tax Classification Code default from?

From the Site Assignments of the Supplier Site

From the Party Tax Profile of the Third Party Site

From the Ship-to Location selected on the invoice

From the Site Assignments of the Supplier Site (Correct Answer)

The Withholding Tax Classification Code can be assigned at the supplier site level in Oracle Financials Cloud.
When a supplier site has a predefined withholding tax classification, this automatically defaults onto the invoice line when an invoice is created for that supplier site.
This setup ensures that consistent withholding tax is applied to transactions related to that supplier.
According to Oracle documentation:
“For supplier sites that use withholding tax, the withholding tax classification that you define at the supplier site assignment level is used to populate the default tax classification on the invoice.” (Oracle Financials Cloud Payables Guide) B: From the Party Tax Profile of the Third Party Site (Incorrect Answer) The Party Tax Profile contains tax-related settings for a supplier or third-party entity, including tax registration details.
However, it does not directly default the Withholding Tax Classification Code onto invoice lines.
Instead, the Party Tax Profile provides high-level tax configurations that may influence tax calculations but does not assign the default withholding tax classification.
C: From the Ship-to Location selected on the invoice (Incorrect Answer) The Ship-to Location on an invoice is used for logistics and sales tax calculations based on where goods are delivered.
It does not impact withholding tax, which is typically linked to the supplier or supplier site.
Therefore, the Withholding Tax Classification Code does not default from the Ship-to Location.
Final Conclusion:
The correct source of the default Withholding Tax Classification Code on an invoice line is the Supplier Site Assignment.
This ensures that withholding tax is consistently applied to transactions involving that supplier, reducing errors in tax calculations.
Reference:
Oracle Financials Cloud Documentation – Withholding Tax Classifications in Payables (Oracle Documentation Link) Explanation:
Comprehensive and Detailed In-Depth Explanation:
In Oracle Financials Cloud, when a Payables user creates a manual invoice, the Withholding Tax Classification Code can default onto the invoice line from various sources depending on the system configurations. The correct source for defaulting this code is from the Site Assignments of the Supplier Site.
Explanation of Each Option:

NO.27 You have enabled Payment Approval for your Payment Process Requests (PPR). At what stage of the PPR is the payment approval process automatically triggered?

Review Proposed Payments

Create Payment Files

Review Installments

Build Payments

NO.28 Your company asks you to build new Payables reports. You will be using Oracle Transactional Business Intelligence (OTBI) and deep links. Deep links allow you to directly drill down from OTBI reports to purchase orders and view the related purchase order details. Which three predefined job roles allow you to use this drill-down feature?

Accounts Payable Analyst

Accounts Payable Manager

Account Payable Invoice Supervisor

Accounts Payable Agent

Accounts Payable Specialist

NO.29 MANAGE POLICIES BY EXPENSE CATEGORY
The US1 Business Unit has an expense policy on meals that allows an employee to claim 30 USD per day for an evening meal, regardless of their role and location.

NO.30 Oracle Cloud currently offers two invoice scanning solutions: Integrated Imaging and Intelligent Document Recognition (IDR). Both solutions function similarly.
In which two ways do these invoice scanning solutions operate in the cloud?

Customers scan the invoice on-premises and email the images.

Customers ask suppliers to send electronic invoices.

Customers ask their suppliers to scan and email the invoice.

Customers scan and store the invoice images on-premises and attach them during invoice entry.

Customers cannot use invoice imaging in the Cloud.

Comprehensive and Detailed In-Depth Explanation:
Oracle Cloud’s Integrated Imaging and Intelligent Document Recognition (IDR) solutions streamline the processing of supplier invoices by automating data extraction and invoice creation. These solutions support multiple methods for capturing and importing invoice images into the cloud system.
A: Customers scan the invoice on-premises and email the images.
Organizations that receive paper invoices can digitize them by scanning the documents on-premises. Once scanned, these images are emailed to a designated address provided by Oracle Cloud. The Integrated Imaging or IDR system retrieves these images from the email inbox, processes them to extract relevant data, and automatically creates invoices within the Payables module. This method ensures that paper-based invoices are efficiently integrated into the cloud system without manual data entry.
docs.oracle.com
C: Customers ask their suppliers to scan and email the invoice.
To enhance efficiency, customers can request that their suppliers scan physical invoices and send the digital images directly via email. These emailed invoice images are received by the designated email account associated with the customer’s Oracle Cloud instance. The Integrated Imaging or IDR solutions then process these images, extracting the necessary invoice data and creating corresponding entries in the Payables system.
This approach reduces processing time and minimizes potential errors associated with manual data entry.
docs.oracle.com
B: Customers ask suppliers to send electronic invoices.
While encouraging suppliers to send electronic invoices (such as XML or EDI formats) is a best practice for streamlining invoice processing, this method does not involve the Integrated Imaging or IDR solutions, which are specifically designed for processing scanned invoice images. Electronic invoices are typically processed through different channels within Oracle Cloud, such as the Supplier Portal or electronic data interchange systems.
blogs.infosys.com
D: Customers scan and store the invoice images on-premises and attach them during invoice entry.
In this scenario, customers manually scan and store invoice images on their local systems and then attach these images during manual invoice entry into the Oracle Cloud Payables module. This process does not utilize the automated capabilities of the Integrated Imaging or IDR solutions, which are designed to handle the import, recognition, and processing of invoice images sent via email.
docs.oracle.com
E: Customers cannot use invoice imaging in the Cloud.
This statement is incorrect. Oracle Cloud provides robust invoice imaging solutions, namely Integrated Imaging and Intelligent Document Recognition, enabling customers to process scanned invoices efficiently within the cloud environment.
docs.oracle.com
By leveraging these solutions, organizations can automate the extraction of invoice data from scanned images, reduce manual intervention, and improve the accuracy and efficiency of their accounts payable processes.

NO.31 Which reference data sharing method can you use for Payables Payment Terms when working with reference data sets in Payables?

Assignment to one set only; no common values allowed

Assignment to multiple sets with common values allowed

Assignment to multiple sets; no common values allowed

Comprehensive and Detailed In-Depth Explanation:
In Oracle Fusion Applications, reference data sharing (also known as SetID) enables organizations to share common configuration data across various organizational units, such as business units, without unnecessary duplication. This approach streamlines maintenance and ensures consistency of reference data across the enterprise.
Payment Terms in Oracle Payables define the conditions under which a company pays its suppliers. These terms can vary between business units based on factors like regional practices or supplier agreements. To accommodate this variability, Oracle Payables employs a specific reference data sharing method for Payment Terms.
Reference Data Sharing Methods:
Assignment to One Set Only; No Common Values Allowed:
Each reference data object instance is assigned to a single set exclusively.
No sharing of values across multiple sets.
Example: Asset Prorate Conventions are defined and assigned to only one reference data set.
Assignment to One Set Only, with Common Values:
Reference data objects can be assigned to one set, but there’s a common set whose values are accessible to all business units.
Example: Receivables Transaction Types are assigned to a common set that’s available to all business units.
Assignment to Multiple Sets; No Common Values Allowed:
A reference data object instance can be assigned to multiple sets.
There’s no common set; each set operates independently.
Example: Payables Payment Terms use this method, allowing each payment term to be assigned to one or more sets.
For Payables Payment Terms, the applicable method is “Assignment to multiple sets; no common values allowed.” This means that each payment term can be associated with one or more reference data sets, but there’s no overarching common set that includes all payment terms. This flexibility allows organizations to define payment terms specific to certain business units while also sharing others across multiple units as needed.
Practical Application:
Shared Payment Terms: If multiple business units operate under similar payment conditions, a single payment term (e.g., “Net 30”) can be assigned to multiple reference data sets corresponding to those units.
Specific Payment Terms: For unique business units with distinct payment agreements, specific payment terms (e.g., “Net 15”) can be created and assigned exclusively to the relevant reference data set.
This approach ensures that each business unit has access to the payment terms relevant to its operations without unnecessary proliferation of identical terms across the system.
Reference:
Reference Data Sets and Sharing Methods
Payment Terms

NO.32 A company has assigned a withholding tax classification to an invoice line to withhold two taxes, each tax withheld at different rates and remitted to different tax authorities.
Tax A has a withholding tax rate of 5% with compounding precedence of 1 Tax B has a withholding tax rate of 10% with compounding precedence of 2 What are the withholding tax amounts computed for the two taxes when the withholding taxable amount is
100$?

Tax A:5%, Tax B:$10.5

Tax A:4.5%, Tax B:$10

Tax A:5%, Tax B:$10

Tax A:5%, Tax B:$9.5

NO.33 Your Company is considering using BI publisher to create additional reports. They want to know about the various features and benefits of this tool.
Which are two benefits of BI publisher customize feature?

Report output is sent to an e-commerce site

Writing code is not required

You do not need any special roles to access this feature

A backup copy of the report is automatically saved in my folders

Patches do not override report customizations

NO.34 Your company will be utilizing the Campaign Management for Early Payment Discount Offers feature to maximize early payment discounts. This feature allows companies to send email-based campaigns offering suppliers the opportunity to enroll in an early payment discounts program. There is a predefined list of response options that suppliers can choose from, and such supplier responses are then automatically processed and applied in the system.
Which two are predefined response options available to suppliers?

Accept All Offers

Decline the Offer

Enroll in a Standing Offer

Comprehensive and Detailed In-Depth Explanation:
In Oracle Financials Cloud, the Campaign Management for Early Payment Discount Offers feature enables organizations to send email campaigns to suppliers, inviting them to participate in early payment discount programs. Suppliers receiving these offers have predefined response options that are automatically processed by the system.
Predefined Supplier Response Options:
Accept a One-Time Offer:
Suppliers can choose to accept a discount offer for specific invoices that are currently eligible for early payment. This action applies the discount to the selected invoices, and they are processed for early payment accordingly.
Enroll in a Standing Offer:
By selecting this option, suppliers agree to participate in an ongoing early payment discount program. All future invoices that meet the agreed-upon criteria will automatically be eligible for early payment discounts without the need for individual acceptances.
Decline the Offer:
Suppliers may opt to decline the current early payment discount offer. Declining does not prevent them from receiving future offers; it simply indicates that they are not interested in the present offer.
Unsubscribe:
If a supplier chooses to unsubscribe, they will no longer receive email notifications regarding early payment discount offers from the campaign. This action effectively removes them from the current and any future campaigns.
Analysis of the Provided Options:
A . Accept All Offers:
There is no predefined response option that allows suppliers to accept all past and future offers in a single action. Acceptance is either for a specific one-time offer or through enrollment in a standing offer for future invoices.
B . Decline the Offer:
This is a valid predefined response. Suppliers can choose to decline the current offer, indicating they are not interested in the proposed early payment discount for the specified invoices.
C . Subscribe:
While suppliers can unsubscribe from receiving future offers, there isn’t a specific “Subscribe” option. Suppliers are considered participants by default and can choose to enroll in standing offers or accept individual offers.
D . Enroll in a Standing Offer:
This is a valid predefined response. Suppliers can enroll in a standing offer, agreeing to early payment discounts on all future eligible invoices automatically.
Conclusion:
The correct predefined response options available to suppliers are B. Decline the Offer and D. Enroll in a Standing Offer. These options provide suppliers with the flexibility to manage their participation in early payment discount programs effectively.
Reference:
Oracle Help Center: Early Payment Discount Offers
Oracle Help Center: Email Campaigns

NO.35 Your company asks you to build new Payables reports. You will be using Oracle Transactional Business Intelligence (OTBI) and deep links. Deep links allow you to directly drill down from OTBI reports to purchase orders and view the related purchase order details. Which three predefined job roles allow you to use this drill-down feature?

Accounts Payable Analyst

Accounts Payable Manager

Account Payable Invoice Supervisor

Accounts Payable Agent

Accounts Payable Specialist

NO.36 During an expense audit, the auditor marks an expense item, which is missing a receipt, to be Short Paid. The auditor chooses to complete the audit and warn the user.
Given that the Expense Report Audit Approval is set to After Manager Approval, what are the two valid results of the auditor’s action?

The approved part of the expense report is not eligible for expense reimbursement.

A new expense report containing disallowed expense items is not created until the manager approves the short payment.

The approved part of the expense report is eligible for expense reimbursement.

A new expense report containing disallowed expense items is immediately created.

NO.37 You implemented the service provider model for Payables payments, where your United Kingdom (UK) headquarters works solely as an outsourced payment processing unit on behalf of your other UK business units.
What is this type of payment service provider model known as?

Self-Service

Dedicated

Dedicated and Self-Service

Procurement

NO.38 Which two invoice types can have a status of Incomplete?

Supplier Portal Invoices which are saved but not yet submitted

Scanned Invoices with invalid or missing data

Scanned Invoices which are rejected during import

Prepayment Invoices which are fully paid but not applied against any invoice

Comprehensive and Detailed In-Depth Explanation:
In Oracle Financials Cloud, the “Incomplete” status is assigned to invoices that require additional information or actions before they can be fully processed. This status ensures that incomplete or erroneous invoices are identified and addressed promptly.
A: Supplier Portal Invoices which are saved but not yet submitted
When suppliers create invoices through the Supplier Portal, they have the option to save their progress without submitting the invoice for approval or payment. These saved invoices are assigned an “Incomplete” status, indicating that the supplier has not yet finalized and submitted them. This allows suppliers to review and modify invoice details before formal submission.
support.oracle.com
B: Scanned Invoices with invalid or missing data
Invoices processed through Integrated Imaging or Intelligent Document Recognition (IDR) are scanned and imported into the system. If these scanned invoices contain invalid or missing data-such as incorrect invoice numbers, missing line items, or unreadable fields-they are assigned an “Incomplete” status. This designation prompts accounts payable personnel to review and correct the discrepancies before the invoices can proceed through the payment process.
docs.oracle.com
C: Scanned Invoices which are rejected during import
Invoices that are rejected during the import process due to significant errors or mismatches are typically not assigned an “Incomplete” status. Instead, they are marked as “Rejected” or “Error,” indicating that they require substantial correction before reprocessing. Therefore, this option is not associated with the
“Incomplete” status.
D: Prepayment Invoices which are fully paid but not applied against any invoice Prepayment invoices represent advance payments made to suppliers and are recorded as such. Once a prepayment is made, the invoice reflects a “Paid” status. The application of this prepayment to subsequent invoices is a separate process and does not revert the original prepayment invoice to an “Incomplete” status.
Thus, this option does not correspond to the “Incomplete” status.
Understanding the scenarios that lead to an “Incomplete” status helps organizations efficiently manage and rectify invoice issues, ensuring a smooth accounts payable workflow.

NO.39 You need to issue an off-cycle, single payment for a supplier before the next scheduled payment run. The invoice you need to pay has been uploaded into the system, yet it is not available for selection on the Create Payment page.
Select two potential reasons for this:

The invoice is not validated.

The invoice is not yet due.

The payment supplier site you selected is different from the supplier site on the invoice.

The invoice is not accounted.

NO.40 You have created an approval rule as follows:
* Rule 1: If the invoice amount > $1000, route it to User 1.
* Rule 2: If the invoice amount < $1000, auto-approve it.
What will happen if a user creates an invoice for $1000 and routes it for approval?

The initiate option is greyed out for the invoice.

Invoice will be sent to User 1 for approval.

Invoice will be auto-approved.

The workflow will fail once approval is initiated, and the invoice will not get processed.

NO.41 Your company has set certain entertainment daily limits in its Entertainment Policy to restrict employee entertainment expenses. Oracle Expenses supports the requirements within your entertainment policy where you can configure and define daily sum limits, along with single instance limits and yearly limits that depend on your policy requirements.
What are three considerations when enabling and defining daily limits in entertainment policies?

The limits defined in the policy will be enforced per attendee regardless of whether the policy has rate determinants set up.

The limits apply only to company employees and excludes nonemployees.

This policy can be associated with both travel and entertainment policies.

Use the entertainment policy to define single or multiple daily limits that need to be enforced per attendee or group of attendees.

The limits defined in the policy will be enforced per attendee only if the policy has rate determinants set up.

This policy can be associated only with entertainment policies.

Use the entertainment policy to define single, daily, or yearly limits that need to be enforced per attendee.

NO.42 You have been managing the procure to pay process related to a construction project for one of your customer. You are using retainage feature to ensure that a certain percentage of payment is held back until the project is completed , and all requirements are fulfilled according to the contract.
A portion of the work has been completed and retainage release invoices?

Retainage release by Invoice schedule

Retainage release by Invoice Lines

Retainage release by PO Schedule

Retainage release by Invoices

Retainage release by PO Line

NO.43 You need to issue an off-cycle, single payment for a supplier before the next scheduled payment run. The invoice you need to pay has been uploaded into the system, yet it is not available for selection on the Create Payment page.
Select two potential reasons for this:

The invoice is not validated.

The invoice is not yet due.

The payment supplier site you selected is different from the supplier site on the invoice.

The invoice is not accounted.