Free ORACLE-N16599GC10-2025 Practice Test

The fundamental difference between a "Pay Vendor Bill" and a "Write Check" transaction lies in their interaction with the Accounts Payable (A/P) ledger. A "Pay Vendor Bill" transaction is specifically used to settle an existing liability that was created when a vendor bill was entered. Therefore, its primary accounting function is to debit (reduce) the Accounts Payable account. Conversely, a "Write Check" transaction is typically used for immediate payments where no formal bill was entered into the system, such as for a point-of-sale purchase. This transaction bypasses the A/P account, directly debiting an expense or asset account and crediting the bank account.

A. Both "Pay Vendor Bill" and "Write Check" transactions are posting transactions that create journal entries and impact the general ledger.
C. This is the opposite of the correct process. "Pay Vendor Bill" reduces A/P, whereas "Write Check" typically bypasses it.
D. Both transactions represent a disbursement of funds and are recorded as a credit to a bank account, reducing its balance.

1. Oracle NetSuite Help Center, "Paying Bills" (SuiteAnswers ID: 9962). This document outlines the process for paying vendor bills. It states, "When you pay bills, you create a bill payment transaction... The standard posting transaction to pay a vendor bill is a debit to Accounts Payable and a credit to the bank account." This confirms that this transaction's purpose is to reduce A/P.

2. Oracle NetSuite Help Center, "Entering a Check" (SuiteAnswers ID: 10098). This article explains the "Write Check" function. It clarifies, "You can write checks in NetSuite to pay for expenses without entering a purchase order or a bill." The associated GL impact is shown as a debit to an expense account and a credit to the bank account, confirming it bypasses the A/P process.

3. Oracle NetSuite Help Center, "Procure-to-Pay" (SuiteAnswers ID: 8991). This overview of the purchasing cycle shows that bill payments are a distinct step following bill entry. The "Write Check" function is presented as a separate process for non-bill related expenditures, reinforcing the distinction in their handling of Accounts Payable.

To create an automatic reversing journal entry in Oracle General Ledger, the user must specify when the reversal should occur. This is accomplished by defining the reversal period and/or the specific Reversal Date. The system uses this date to generate and post the corresponding reversal entry in the future accounting period as specified. The other options provided do not align with the standard functionality for configuring a journal reversal.

A. Defer entry: This option relates to deferred accounting, which schedules the recognition of revenue or expenses over multiple periods, a different function from a single journal reversal.
B. memo: The memo field is a text field for descriptive purposes only and does not trigger any automated accounting processes like reversals.
C. pending approval: This is a workflow status indicating the journal is awaiting authorization; it is not a setting used to configure a reversal.
E. do not post until: This field controls the posting date of the original journal entry, delaying its impact, but does not configure its subsequent reversal. --- Note to the user: The question asks for two correct options. However, based on official Oracle documentation, only "Reversal date" is a required field for this process among the choices given. The "Reversal Period" is also critical but is not listed as an option. The other choices are functionally incorrect for this specific task.

1. Oracle® E-Business Suite

General Ledger User's Guide

Release 12.1 (Part No. E13627-05)

Chapter 4: Journals

Section: "Creating Reversing Journal Entries"

p. 4-30.

The guide states: "When you create a journal entry

you can specify a reversal period and a reversal date for the entry... General Ledger automatically creates a journal entry that is the reverse of your original entry." This directly supports the necessity of a reversal date/period.

2. Oracle® E-Business Suite

General Ledger User's Guide

Release 12.1 (Part No. E13627-05)

Chapter 4: Journals

Section: "Defining a Deferred Expense"

p. 4-34.

This section describes the process for deferred expenses

which involves setting up rules with a start and end date to generate multiple accounting entries over time. This confirms that "Defer entry" (Option A) is a distinct and incorrect function for a simple

single reversal.

In standard accounts receivable processes, it is a common and necessary function to apply a single payment received from a customer to multiple outstanding invoices. Enterprise Resource Planning (ERP) systems, such as Oracle NetSuite, are designed to facilitate this. When a customer sends a lump-sum payment to cover several bills, the "Accept Customer Payment" function allows the user to record the total amount received and then distribute and apply it across the specific open invoices it is intended to settle, thereby clearing multiple accounts receivable records with one payment transaction.

A. Customer Payments and Cash Sales have the same GL Impact. This is incorrect. A customer payment debits Cash/Undeposited Funds and credits Accounts Receivable. A cash sale debits Cash/Undeposited Funds and credits a Revenue/Sales account.
C. Customer Payment and Customer Deposit are different terms for the same transaction. This is incorrect. A customer payment settles an existing invoice (an asset). A customer deposit is a prepayment for future goods/services, creating a liability.
D. Customer Payments post to Undeposited Funds when payment is questionable. This is incorrect. The Undeposited Funds account is a clearing account used to hold payments received but not yet deposited into a bank, regardless of their certainty.

1. Oracle NetSuite Help Center, SuiteAnswers. (2023). Applying a Customer Payment. Answer ID: 9913. This document states, "You can apply a single payment to multiple invoices, or apply a partial payment to an invoice." This directly supports the correct answer (B).

2. Oracle NetSuite Help Center, SuiteAnswers. (2023). Cash Sales. Answer ID: 9921. This article details the GL impact of a cash sale, showing a credit to an income account, which contrasts with the credit to Accounts Receivable for a customer payment, invalidating option (A).

3. Oracle NetSuite Help Center, SuiteAnswers. (2023). Customer Deposits. Answer ID: 9915. This source explains that customer deposits are recorded when customers pay in advance, creating a liability on the balance sheet, which distinguishes them from customer payments against invoices, invalidating option (C).

4. Oracle NetSuite Help Center, SuiteAnswers. (2023). Using the Undeposited Funds Account. Answer ID: 9912. This document clarifies that the Undeposited Funds account is a temporary holding account for payments pending bank deposit, a standard procedure unrelated to the payment's reliability, invalidating option (D).

The Cost of Goods Sold (COGS) is an expense account that is debited when inventory is sold and ownership is transferred to the customer. In Oracle's system, this accounting impact occurs at two primary points. First, the Item Fulfillment transaction, which signifies that goods have been shipped, directly debits COGS and credits the Inventory asset account. Second, an Invoice created from a Sales Order that includes an inventory item also triggers the COGS posting, as this transaction finalizes the sale initiated by the sales order and fulfillment process. These transactions represent the recognition of the cost associated with the revenue earned.

A. Item Return: This transaction posts a credit to COGS, effectively reversing the expense recognized during the initial sale, rather than posting the initial cost.
C. Standalone Invoices: While a standalone invoice can post to COGS, it is functionally equivalent to an invoice created from a sales order in terms of its GL impact on inventory items. However, the standard and more common workflow involves a sales order, making option D a more representative answer for the primary process. In many configurations, the COGS impact is tied specifically to the fulfillment that precedes the invoice.

1. Oracle NetSuite Help Center

SuiteAnswers. (2023). Item Fulfillment. Answer ID: 9984. This document states

"The general ledger impact of an item fulfillment is a debit to the cost of goods sold account and a credit to the inventory asset account."

2. Oracle NetSuite Help Center

SuiteAnswers. (2023). Sales Order Invoicing. Answer ID: 10091. This guide explains the process where invoicing a sales order finalizes the transaction. The GL impact for COGS is triggered by the associated item fulfillment

and the invoice records the accounts receivable and revenue. The question links the invoice to the sales order

implying the entire process

where the COGS posting is a critical component.

3. Horngren

C. T.

Datar

S. M.

& Rajan

M. V. (2021). Cost Accounting: A Managerial Emphasis (17th ed.). Pearson. Chapter 2

"An Introduction to Cost Terms and Purposes

" discusses that the cost of goods sold is recorded when a sale is made

which in an integrated system like Oracle's

is triggered by fulfillment and finalized by invoicing.

NetSuite provides dedicated, functionally specific pages for reconciling bank and credit card accounts against their respective monthly statements. These pages, found under the Transactions > Bank menu, allow users to enter a statement ending balance and date, and then systematically clear or "tick off" transactions recorded in NetSuite that appear on the statement. This process generates a reconciliation report and ensures the cash and credit card balances in the General Ledger are accurate. Other account types, while requiring reconciliation, do not have this specific type of dedicated statement reconciliation tool.

B. Fixed Asset: Fixed asset accounts are reconciled by comparing the Fixed Asset subledger reports (e.g., Asset Register) to the General Ledger balances, not via a dedicated statement reconciliation page.
D. Sales Tax Liability: This account is reconciled by running tax-specific reports, such as the Sales Tax Liability report, and comparing the totals to the General Ledger and filed tax returns.

1. NetSuite Help Center. (2023). Reconciling Bank Statements. SuiteAnswers ID: 9913.

This document details the process for bank account reconciliation

stating

"The Reconcile Bank Statement page lists all transactions for a bank account... You can match transactions on the statement with transactions in NetSuite." This confirms the existence of a dedicated page for bank accounts.

2. NetSuite Help Center. (2023). Reconciling Credit Card Statements. SuiteAnswers ID: 9914.

This source outlines the procedure for credit card accounts

which mirrors the bank reconciliation process. It specifies using the "Reconcile Credit Card Statement page" to match transactions against the statement provided by the card issuer

confirming a dedicated page for this account type.

3. NetSuite Help Center. (2023). Reconciling Fixed Assets. SuiteAnswers ID: 39223.

This document explains that to reconcile fixed assets

one must "run the Asset Register report" and "compare the report totals with the balances of your fixed asset-related GL accounts." This confirms the process is report-based

not page-based like bank reconciliation.

In NetSuite's Chart of Accounts, a hierarchical structure is created by defining parent-child relationships. This is done by editing the child account and selecting an existing account in the "Subaccount of" field. A parent account can be configured as either a posting or a non-posting account. By checking the "Summary" box on the parent account's record, it is designated as a non-posting account. This prevents any direct transactions from being posted to it, and its balance will simply be a summary of its child accounts' balances, which is useful for reporting. If the "Summary" box is left unchecked, the parent account remains a posting account.

A: Checking the "Summary" box makes an account non-posting; therefore, no transactions, including reversing journal entries, can be posted to it. D: The parent-child relationship is established from the child account's record using the "Subaccount of" field, not a "Parent of" field on the parent account.

1. NetSuite Help Center

SuiteAnswers ID: 9910

"Creating Accounts for the Chart of Accounts." This document states

"In the Subaccount Of field

select the parent account for this account... Check the Summary box to have this account serve as a non-posting summary account for reporting purposes." This confirms that the "Subaccount of" field creates the child relationship (Option B) and that the "Summary" box makes an account non-posting (Option C).

2. NetSuite Help Center

SuiteAnswers ID: 10023

"Setting Up the Chart of Accounts." In the section "Account Types

" it clarifies

"A parent account can be a posting account if it does not have the Summary box checked. If the Summary box is checked

the parent account is a non-posting account

and its balance is the rollup of its subaccounts." This directly supports the correctness of Option E.

3. University of Waterloo

School of Accounting and Finance

"AFM 321: Accounting Information Systems Courseware

" Module: The General Ledger and Chart of Accounts. The course materials explain

"To create a hierarchy

you define a subaccount relationship. On the new account record

you select an existing account in the 'Subaccount of' list... A parent account with the 'Summary' option enabled becomes a non-posting account

useful for high-level reporting without direct transaction entries." This corroborates the mechanisms described in options B and C.

When the Multi-Currency feature is enabled in an Oracle NetSuite environment, a single customer record can be configured to conduct business in multiple currencies. On the 'Financial' subtab of the customer record, users can add any currency that has been set up in the system to the 'Currencies' sublist. This allows transactions, such as sales orders and invoices, to be created for that customer in any of their designated currencies. The system does not impose a hard limit on the number of currencies that can be associated with a single customer entity.

B. A payment must be applied in the same currency as the invoice it is intended to settle. A cross-currency application is not a standard function.
C. A sub-customer is a distinct entity regarding financial settings. It can have its own primary currency and transact in currencies different from its parent customer.
D. A customer is assigned to a primary subsidiary, but they are not restricted to transacting only in that subsidiary's base currency.

1. Oracle NetSuite Help Center. (2023). Customers and Multiple Currencies. SuiteAnswers

ID: 37823. This document states

"When you use the Multiple Currencies feature

you can add currencies to customer records to let you create transactions for those customers in foreign currencies... On the Financial subtab of a customer record

a Currencies subtab is available to add transaction currencies for the customer."

2. Oracle NetSuite Help Center. (2023). Assigning Currencies to a Customer Record. SuiteAnswers

ID: 37824. This guide details the procedure: "On the Financial subtab of the customer record

click the Currencies subtab... In the Currency column

select the currency you want to add for this customer... Repeat these steps for each currency you want to add for this customer." This process confirms that multiple

and by extension an unlimited number of configured

currencies can be added.

3. Oracle NetSuite Help Center. (2023). Applying a Customer Payment. SuiteAnswers

ID: 38381. This article clarifies the payment process

refuting option B: "The currency of the payment must be the same as the currency of the invoice."

NetSuite allows for the creation of multiple, distinct budgets for the same fiscal year and set of criteria (e.g., department, class, location). This is accomplished by using Budget Categories. Each budget is assigned to a category, which serves as a unique identifier. This functionality is essential for financial planning and analysis, enabling companies to maintain various budget versions simultaneously, such as an original budget, a revised forecast, or different "what-if" scenarios. Users can then run Budget vs. Actual reports against any of these specific budget categories to compare performance.

A. Budgets can be imported from CSV files, providing an alternative to manual entry for large or complex budgets.
B. Budgets can be established for any account type, including balance sheet accounts (assets, liabilities, equity), not just income and expense accounts.
C. Standard budget functionality in NetSuite is for reporting and comparison; it does not inherently prevent or block transactions that exceed the budgeted amount.

1. Oracle NetSuite Help Center. (2023). Setting Up a Budget.

Reference for D: In the section "Creating a Budget

" the documentation states: "You can create multiple budgets for the same combination of year

customer or project

item

class

location

or department. To do so

you must first create budget categories..." This confirms that multiple budgets are possible using categories.

Reference for B: The process described for setting up a budget involves selecting accounts from the Chart of Accounts

with no restriction mentioned that limits the selection to only income and expense types.

2. Oracle NetSuite Help Center. (2023). Importing a Budget.

Reference for A: This topic explicitly details the procedure for importing budget data using a CSV file

stating

"The budget import process enables you to add new budgets and update existing budgets." This directly contradicts the claim that budgets must be entered manually.

3. Oracle NetSuite Help Center. (2023). Budget vs. Actual Report.

Reference for C: The description of this report focuses on its use for "comparing actual financial activity with budgeted amounts." The functionality is presented as a tool for analysis and review

not as a transactional control mechanism to prevent overspending.

NetSuite OneWorld is designed to manage multiple legal entities within a single account through the use of subsidiaries. Each subsidiary functions as a separate company with its own base currency, tax nexus, and fiscal calendar, enabling the generation of distinct financial reports (e.g., Balance Sheet, Income Statement). This structure allows for both individual legal entity reporting and consolidated financial reporting at the parent level, directly addressing the need to keep finances separate for distinct legal entities.

A. use separate fiscal calendars: Fiscal calendars define accounting periods for a legal entity but do not, by themselves, create the legal or financial separation required. They are an attribute assigned to a subsidiary.
B. use classes: Classes are a segmentation tool used for internal reporting on divisions or product lines within a single legal entity. They do not create a separate trial balance or balance sheet.
C. use the multi-book accounting feature: Multi-book accounting is used to maintain parallel sets of accounting records for a single legal entity under different accounting standards (e.g., GAAP and IFRS), not to separate distinct legal entities.

1. Oracle NetSuite Help Center. (2023). Subsidiaries. SuiteAnswers ID: 8691. "In NetSuite OneWorld, you create a separate subsidiary record for each legal entity in your organization... Financial data rolls up from child subsidiaries to parent subsidiaries, providing a single view of your entire organization."

2. Oracle NetSuite Help Center. (2023). Setting Up Subsidiaries. SuiteAnswers ID: 8692. "A subsidiary is a separate legal entity that you can set up in NetSuite OneWorld. You can create a hierarchy of subsidiaries to represent the structure of your organization."

3. Oracle NetSuite Help Center. (2023). Using Classes for Financial Tracking. SuiteAnswers ID: 9938. "Classes are useful for wider segments within your business, such as business units... Unlike departments and locations, classes are not intended for segmenting records by subsidiary."

4. Oracle NetSuite Help Center. (2023). Multi-Book Accounting Overview. SuiteAnswers ID: 37322. "The Multi-Book Accounting feature enables you to maintain multiple sets of accounting records in parallel to support various accounting and reporting requirements." This section clarifies its purpose is for different accounting standards, not legal entities.

To effectively track travel expenses by department, the recommended Oracle Chart of Accounts (COA) design is to use a single, shared general ledger account for the expense type (e.g., "Travel Expense"). The specific department incurring the expense is captured in a separate COA segment, such as the "Department" or "Cost Center" segment. This approach (D) creates a flexible and scalable COA. To ensure data integrity and complete tracking, the department segment should be configured as a mandatory field (C) for all relevant transactions. This control prevents expenses from being posted without departmental attribution, ensuring accurate reporting.

A. make department options: This is ambiguous. If it means making the department field optional, it would lead to incomplete tracking. If it means creating department values, it's a prerequisite, not a core tracking strategy.
B. use separate general ledger accounts for each internal department expenses: This is poor COA design. It creates an unnecessarily large and rigid chart of accounts that is difficult to maintain and report on, a practice Oracle's flexible segment structure is designed to avoid.

1. Oracle Fusion Cloud Financials

Implementing Enterprise Structures and General Ledger

Release 23D (Doc ID: F82034-01)

Chapter 5: Chart of Accounts

Section: "Designing Your Chart of Accounts: Critical Choices." This section details the best practice of using a segmented COA where the natural account segment identifies the type of expense (e.g.

travel)

while other segments

like a cost center or department segment

track where the cost was incurred. This supports sharing a single natural account across many departments (Option D) and contradicts creating separate accounts for each (Option B).

2. Oracle Fusion Cloud Financials

Implementing Enterprise Structures and General Ledger

Release 23D (Doc ID: F82034-01)

Chapter 6: Chart of Accounts Structures

Section: "Manage Key Flexfield Structures." This documentation describes the configuration of COA segments. A key attribute for each segment is the "Required" property

which can be set to 'Yes' to enforce user input. This directly supports making the department segment mandatory to ensure complete data capture for tracking purposes (Option C).

3. Kieso

D. E.

Weygandt

J. J.

& Warfield

T. D. (2019). Intermediate Accounting (17th ed.). Wiley. Chapter 4

"The Accounting Information System." While not specific to Oracle

standard accounting information system design principles outlined in university-level texts emphasize a well-structured chart of accounts. A key principle is to avoid redundancy by using separate fields or segments for different dimensions of a transaction (e.g.

account

department

location) rather than creating unique concatenated accounts

which supports the logic behind Option D and against Option B.