NETSUITE-FINANCIAL-USER Practice Questions

In NetSuite, the value chosen in the Account Type field classifies the account as asset, liability, equity, income, expense, etc. That classification automatically places the account in the corresponding default section of standard financial statements (Balance Sheet or Income Statement sub-sections). NetSuite’s general-ledger engine uses this value to know where the account appears on reports and how its debit/credit balance is treated. Account Type does not influence subsidiary assignment, exchange-rate selection, or user security; those are controlled by separate fields and role/permission settings.

A. Subsidiary assignment is governed by the Subsidiary field (OneWorld), not by Account Type.

B. Exchange rates derive from transaction currency and date; Account Type is not referenced.

D. User access is governed by roles/permissions and the “Restrict” flags, independent of Account Type.

1. Oracle NetSuite Help Center – “Chart of Accounts Overview”

section “About Account Types”

para. 2-3: explains that Account Type “determines the section of standard financial statements where the account automatically appears.”

2. Oracle NetSuite Help Center – “Creating Accounts”

step 3 note: “Account Type does not affect subsidiary assignment; use the Subsidiary field for OneWorld accounts.”

3. Oracle NetSuite Help Center – “Exchange Rates and Currencies”

first paragraph: describes rate selection based on currency/date

no mention of Account Type.

4. Oracle NetSuite Help Center – “Roles and Permissions”

section “Permission Structure”: clarifies that access is controlled by roles

not by account classification.

Assigning a billing schedule on the item record makes that schedule the item’s default. When the item is added to a sales order, the Billing Schedule field on that line is automatically populated with the item’s default schedule, though users may still override it. The assignment has no effect on other lines or on other items in the same transaction.

A. Only the line containing that item inherits a default schedule; other lines are unaffected.

B. Other items on the order can be entered with or without billing schedules.

C. A single sales order can contain items that use different billing schedules.

1. Oracle NetSuite Help Center

topic “Billing Schedules: Linking Schedules to Items

” para. 2: “When you set a default billing schedule on an item

that schedule is automatically entered on the transaction line for that item.”

2. Oracle NetSuite Help Center

topic “Item Record > Accounting Subtab

” field description for Billing Schedule: “Select a billing schedule to be used as the default for this item on sales transactions. The default can be changed on the transaction.”

(Access to NetSuite Help Center requires valid credentials.)

In NetSuite, when creating a vendor bill payment transaction, the system requires the user to select the source account from which the funds are being disbursed. The "Account" field on the Bill Payment page is specifically filtered to display only accounts of certain types. Official NetSuite documentation confirms that only Bank accounts (for payments via check, EFT, or other cash disbursements) and Credit Card accounts (for payments made using a company credit card) are available for selection to pay vendor bills. These account types represent the sources of funds used to settle the liability recorded by the vendor bill.

B. Asset: General asset accounts (e.g., Fixed Assets, Other Current Assets) are not transactional accounts used for making direct payments to vendors.

C. Expense: Expense accounts are used to record the nature of the cost incurred on the vendor bill itself, not as a source of funds for payment.

E. Non-Posting: Non-posting accounts are used for statistical or budgeting purposes and do not impact the general ledger, so they cannot be used for financial transactions.

1. NetSuite Help Center. (2024). Paying a Single Vendor Bill. SuiteAnswers

Doc ID: N1501211. In the description of the Bill Payment transaction page

the "Account" field is defined as: "Select the bank account or credit card account to use for this payment."

2. NetSuite Help Center. (2024). Paying Bills. SuiteAnswers

Doc ID: 10092. This guide on the bulk payment process states in Step 4: "In the Account field

select the bank or credit card account from which you are paying the bills."

NetSuite’s Intercompany Expense Allocation schedule is defined for one “source subsidiary”; that single subsidiary’s expenses are re-distributed. On the Lines sub-tab you may enter several “destination subsidiaries,” each with its percentage or weight, so the target can be multiple subsidiaries. Therefore option B (multiple targets) and option C (one source) are true; the opposite statements (A, D) are false.

A. Source may be multiple subsidiaries – NetSuite allows only a single source subsidiary to be chosen on an allocation schedule, so this is incorrect.

D. Target can only be one subsidiary – Multiple destination subsidiaries can be listed, each with an allocation percentage, so this is incorrect.

1. Oracle NetSuite Help Center

“Creating an Intercompany Expense Allocation Schedule

” Step 3: Subsidiary field – “Select the source subsidiary (only one).” (2024.1 documentation

Internal Article ID 103005).

2. Oracle NetSuite Help Center

same article

“Lines Subtab” – “Enter one or more destination subsidiaries and specify allocation percentages.”

3. Oracle NetSuite SuiteAnswers Article 10102

“Automated Intercompany Management – Expense Allocation

” Answer section

bullet 2: “An expense from a single source subsidiary can be allocated across multiple destination subsidiaries.”

In NetSuite’s standard Order-to-Cash (accounts-receivable) lifecycle, a sales order that requires approval moves through three system-defined statuses:

1. Pending Approval – user approves the Sales Order.

2. Pending Fulfillment – warehouse fulfills (ships) the order, creating an Item Fulfillment record.

3. Pending Billing – finance bills the Sales Order, which generates the customer Invoice (A/R).

Thus the correct sequence is: Approve Sales Order → Fulfill Sales Order → Bill Sales Order, exactly as shown in option A.

B. Bills before goods are shipped; NetSuite does not permit billing while status is Pending Fulfillment.

C. Fulfillment cannot occur until the order is approved; status would still be Pending Approval.

D. Billing first violates status flow; order must be approved and fulfilled before Pending Billing is reached.

1. NetSuite Help Center

“Order to Cash Process Flow – Sales Order Statuses” (2023.2): Pending Approval → Pending Fulfillment → Pending Billing.

2. NetSuite Help Center

“Sales Order Transaction Lifecycles”

paragraph “Approving

Fulfilling and Billing Sales Orders” (2023.2).

3. SuiteAnswers Article 10111 “Sales Order Process Flow” (rev. 2023-05-12)

Steps 3-5.

In NetSuite, clicking Auto Apply on the Apply sub-tab of a Vendor Credit causes NetSuite to allocate the credit beginning with the oldest open vendor bills (by transaction date) and continues chronologically until the credit amount is exhausted. No other prioritization—such as balance size or newest bill—is used.

A. Matching balance is not considered; date order rules.

C. Newest bills are processed last, not first.

D. Balance size is irrelevant; age of bill controls application sequence.

1. NetSuite Help Center

“Vendor Credit > Apply Sub-tab

” 2023.2 documentation

paragraph “Auto Apply”: “Click Auto Apply to automatically apply the credit to the oldest outstanding vendor bills first.”

2. NetSuite SuiteAnswers Article 9963

“How Auto Apply Works for Vendor Credits

” rev. 2022-11-15: “The system allocates the credit starting with the oldest vendor bill(s) and proceeds by date until the credit is fully applied.”

Because the bill amount changes, the memorized transaction must prompt the user each month instead of posting automatically; therefore set Action = Reminder.

Since the payment should recur until the user stops it, set the recurrence to Indefinite rather than a fixed “Number Remaining.”

B. Override Transaction Date – lets NetSuite replace the original date with the execution date; not required to handle variable amounts or open-ended recurrence.

C. Action: Automatic – posts without user review, unsuitable when the amount varies monthly.

E. Number Remaining – forces a fixed count of future postings; contradicts the “continues until canceled” requirement.

1. Oracle NetSuite Help Center

“Creating Memorized Transactions – Field Descriptions

” sub-section “Action.” Notes that “Reminder” is used when amounts or other details vary (Help Center Article ID 10155

para. 4).

2. Oracle NetSuite Help Center

“Memorized Transaction Schedule

” section “Recurrence Options – Indefinite vs. Number Remaining” (Article ID 8642

para. 2-3).

The Period Close Checklist is dynamically generated by NetSuite; it shows only the tasks that are relevant to the accounting features and modules that are turned on in that specific account (e.g., Multi-currency, Projects, Inventory). NetSuite Help explicitly states that “the tasks that appear on the Period Close Checklist depend on the features that are enabled in your account.”

A. Year-end is closed by closing each final period; checklist is recommended but not formally “required.”

B. Tasks are locked to a prescribed sequence; later tasks cannot be started until prerequisite ones are complete.

C. The checklist is system-generated; users cannot insert bespoke or customer-specific tasks.

1. NetSuite Help Center

“Close Accounting Periods – Period Close Checklist

” 2023.2 documentation

Section: Overview

¶2 (“…tasks that appear depend on the features that are enabled in your account.”).

2. NetSuite Help Center

“Period Close Checklist Task Order

” 2023.2

¶1 (“The tasks must be completed in the order shown; each task unlocks the next.”).

3. NetSuite Help Center

“Limitations of the Period Close Checklist

” 2023.2

¶3 (“You cannot add custom tasks to the checklist.”).

NetSuite’s Fixed Bid – Milestone project type is designed so the customer is invoiced only when predefined milestones—commonly represented by key project tasks—are reached. Each milestone holds a fixed amount; once the related task is marked complete, the billing engine releases that amount to the sales order for invoicing. This precisely matches the requirement that “a sales order should be billed when certain key project tasks have been completed.”

A. Time and Material – Bills continuously for approved time/expenses/items, not tied to milestone task completion.

B. Charge Based – Uses charge rules to accumulate charges; timing is rule-driven, not strictly milestone-driven.

D. Standard – Standard (item-based) sales orders bill on item fulfillment or cash sale creation, unrelated to project task milestones.

1. Oracle NetSuite Help Center

SuiteProjects > Project Billing Types > “Fixed Bid – Milestone” (2024R1): “You bill the customer when each milestone—typically a project task—is completed; each milestone has a fixed amount.”

2. Oracle NetSuite Help Center

same section

“Time and Materials”: “Invoices are generated from approved time entries

expenses

and items.”

3. Oracle NetSuite Help Center

SuiteProjects > Charge-Based Billing Overview (2024R1): “Charges are created per charge rule; billing is driven by charge dates

not project task completion.”

4. Oracle NetSuite Help Center

Transactions > Sales Orders > “Standard Sales Order”: bills upon item fulfillment/invoice creation

no link to project milestones.

In a NetSuite OneWorld account, a single vendor record can be configured to support operations across multiple business units and currencies. A vendor can be associated with a primary subsidiary and then shared with multiple other subsidiaries, enabling centralized vendor management while allowing for subsidiary-specific transactions. This multi-subsidiary assignment is a core feature of OneWorld. Furthermore, to facilitate international commerce, a vendor record can be set up to accept transactions in multiple currencies. This is managed on the 'Currencies' subtab of the vendor record, where different transaction currencies can be added in addition to the vendor's primary currency.

B. There is one Credit Limit value per Vendor. While factually true that the standard vendor record has a single credit limit field, options A and D describe core capabilities specifically enabled and emphasized by the OneWorld architecture.

C. Vendors can only be assigned to one subsidiary. This is incorrect. A fundamental feature of NetSuite OneWorld is the ability to share entity records, including vendors, across multiple subsidiaries to avoid data duplication.

1. NetSuite Help Center / SuiteAnswers

Answer ID: 10011

"Assigning a Subsidiary to a Vendor." This document states

"In NetSuite OneWorld

you can share vendor records with multiple subsidiaries. When you create a vendor record

you associate the vendor with one primary subsidiary. Then

you can make this vendor available to other subsidiaries." This directly supports option D and refutes option C.

2. NetSuite Help Center / SuiteAnswers

Answer ID: 72881

"Setting Up Multiple Currencies for Transactions with an Entity." This article explains

"You can add currencies to entity records to enter transactions in a foreign currency. The Currencies subtab is available on customer

vendor

and partner records." This confirms that vendors can have multiple currencies

supporting option A.