December: Tips & Tricks

1 - Cross Charge Multiple Subsidiaries for Billings (Purchase Orders), Sales Orders, and Journal Entries

The ability to cross-charge multiple subsidiaries is desirable when a Target Subsidiary field from the Vendor record needs to be defaulted at the PO/Billing line item level, for purposes such as Stipend expenditure (ie, pledges received) to be paid.

The logic to be employed for when this field is populated for PO/Billing purposes, is that upon saving of the PO/Billing record, an Intercompany Journal Entry will be created automatically as such:

Debit: Intercompany Clearing (or Due from Source) x, xxx.xx [Source Subsidiary]
Credit: Accounts Payable (or Unbilled PO Receipt) x, xxx.xx [Source Subsidiary]
Debit: Expense (or Item Account) x, xxx.xx [Target Subsidiary]
Credit:  Intercompany Clearing (or Due to Source) x, xxx.xx [Target Subsidiary]

To do this, you must use the following method:

Vendor Bill Sub A CREDIT A/P Sub A DEBIT Expense Sub A
Company JE DEBIT A/P Sub A CREDIT Company Clearing Sub A DEBIT Company Clearing Sub B CREDIT A/P Sub B
Write Check Sub B DEBIT A/P Sub B CREDIT Bank Sub B

In essence, you are writing off the debt in Subsidiary (Sub) A and transferring it to Sub B, who then pays the Vendor with a cheque. This method entails using (2) different Vendor records because vendors belong to a subsidiary (this cause some reporting obscurity because the Bill and the Payment will never really be linked).

You can use the same methods with Accounts Receivable.

2 - Saved Search Internal ID

Some useful tips to help in the creation of search filters using internal ID:

  • If you want to use numerical value (ie, greaterthan, equalto...) always use 'internalidnumber' rather than 'internalid'
  • If you are using internalid with the anyof operator, ensure that the ID list is not null or undefined. 
    • The error shown when trying to use a null list will tell you that the operator is wrong (confusing!)
3 - How do hierarchical customers behave with customer support and customer center?

Both support and transaction information follow these rules when hierarchical customers access the Customer Center: - Parent customer can see all information from all children customers - Child customers can only see their own information.

When a case is opened through email capture, here are a series of situations to show how NetSuite determines the company to associate to the case:

Email address set on:

Parent Record - Child Contact: uses child record customer
Parent Record - Child Record: uses anonymous customer
Parent Contact - Child Record: uses child record
Parent Contact - Child Contact: uses anonymous customer
Customer Record - Other Customer Record: uses anonymous customer
Customer Record - Other Customer Child Contact: uses other customer child
Customer Record - Other Customer Parent Contact: uses other customer parent contact
Customer contact - Other customer contact: uses anonymous customer
Customer contact - Other Customer child contact: uses anonymous customer

1 comment:

  1. While entering the Bill in NETSUITE, from more POs, is it possible to have the relevant PO number in the Item Line. So that we come to know that similar items are being booked under the correct PO.