NS-ERP Sample Questions & Answers

The standard NetSuite workflow for vendor prepayments is to first create the Purchase Order. Then, a Vendor Prepayment transaction is created and linked to that PO, which posts a debit to the prepayment asset account and a credit to cash. After receiving the items and entering the full Vendor Bill, the previously created prepayment is then applied to the bill, reducing the open A/P balance.

This is false. While the Administrator role has the necessary permissions by default, a custom role can be configured with the 'Period Closing Management' permission to allow non-administrators to execute the Period Close Checklist tasks. This is a best practice for segregation of duties.

This combination correctly uses NetSuite's hierarchical pricing logic. Price Levels with Quantity Pricing Schedules handle the tier and volume requirements. For key accounts, assigning item-specific pricing directly on the customer record (Customer-Vendor Pricing) is the standard method and will override the general Price Level. Finally, the SuitePromotions feature is designed to apply additional discounts (like the quarterly campaigns) on top of the calculated price, meeting all requirements without custom scripting.

The CSV import process runs using the permissions of the user initiating the import. If the user's role is restricted to a subset of subsidiaries, the system will not be able to find or validate the subsidiary references for those they cannot access, resulting in an 'Invalid reference key' error, even if the names are correct. The user must either use a role with access to all required subsidiaries or have the import performed by someone who does.

Mass Updates are the primary tool in NetSuite for making the same change to a large number of records simultaneously. The user can define criteria to select the legacy customers and then define an action to set the 'Inactive' field to true for all of them in a single operation. This is far more efficient than manual updates or a CSV re-import for a simple field change.

To correct a fundamental aspect like the depreciation method on an asset that has already posted depreciation, the historical GL impact must be removed first. The correct procedure is to delete the depreciation journal entries for the affected periods. This allows the asset record's depreciation method field to become editable again. After changing the method, the depreciation schedule must be regenerated, which will calculate the correct past and future depreciation amounts that can then be posted.

'Edit' level permission allows a user to create and modify a transaction record. The ability to approve a transaction is controlled by a separate mechanism, either the 'Approval Limit' on the employee record (for standard approvals) or the specific states and transitions in a workflow. Granting 'Edit' access does not inherently grant approval rights. 'Full' access would grant the ability to delete, which might not be desired. 'Create' is too restrictive as it prevents editing after the initial save.

The search should be based on the Sales Order transaction. This allows you to compare the Sales Order's creation date with the date of its fulfilling transaction (Item Fulfillment). A formula can then be used in the results or criteria to calculate the difference between {datecreated} and {fulfillingtransaction.datecreated}. Basing the search on Item Fulfillment would make it difficult to include sales orders that have not yet been fulfilled, which are necessary for calculating the percentage against the total.

A Vendor Return Authorization is a non-posting transaction. Its purpose is to track and authorize the return of goods to a vendor. The GL impact does not occur until subsequent transactions are processed, such as shipping the items (Item Fulfillment) which credits inventory, and receiving a Vendor Credit which debits Accounts Payable.