PROPOSAL FOR NETSUITE SUBSIDIARY HIERARCHY CHANGE & PDF CUSTOMIZATION

OPPORTUNITY SUMMARY 

This scope will include the Implementation of new NetSuite subsidiaries, Subsidiary hierarchy change and advance PDF customization of some transactions. 

PROPOSAL SUMMARY 

The document covers the scope of Implementation of new NetSuite subsidiaries and Subsidiary hierarchy change and as well as customization of advance PDF template. 

This project aims to seamlessly integrate additional subsidiaries into the existing NetSuite environment while optimizing the subsidiary hierarchy for better management and control. The implementation of new NetSuite subsidiaries and a change in the subsidiary hierarchy to enhance the organization’s operational efficiency, financial reporting accuracy, and decision-making capabilities.  

REQUIREMENTS 

The client wants to design and implement a comprehensive strategy for the creation of new subsidiaries and the modification of the subsidiary hierarchy within their current corporate structure. This strategy should be ensure a seamless transition, improved operational efficiency, and enhanced flexibility for future growth. 

The attached images illustrate the existing and new subsidiary hierarchy. 

Customization advanced PDF template of following transaction’s  

Payment Voucher, Bank Receipt Voucher, Check, Check VP, Proforma Invoice, Commercial Invoice, Vendor Prepayment 

DELIVERABLES 

  1. We will create the following new subsidiaries in the system 
  • SHRINASAL RUSSIA 
    SHRINASAL RUSSIA will be a new subsidiary that will be configured in the system. This subsidiary will be a Copy of SHIRIASAL MIDDLE EAST GENERAL TRADING LLC.  
    subsidiary details: Subsidiary Name: SHRINASAL RUSSIA 
    Currency: RUB (Russian Ruble) 
    Parent Subsidiary: REPORT 
  • IMPORTEX FZE 
    IMPORTEX FZE will be a new subsidiary that will be configured in the system. This subsidiary will be a Copy of Copy of AFRIEXPO FZE. 
    subsidiary details: Subsidiary Name: IMPORTEX FZE  
    Currency: AED (Dirhams) 
    Parent Subsidiary: REPORT 
  • ARIA NEIGHBORHOOD SUPERMARKET LLC 
    ARIA NEIGHBORHOOD SUPERMARKET LLC will be a new subsidiary that will be configured in the system. 
    subsidiary details: Subsidiary Name: ARIA NEIGHBORHOOD SUPERMARKET LLC  
    Currency: AED (Dirhams) 
    Parent Subsidiary: REPORT 
  • MUTTEEENA 
    MUTTEEENA will be a new subsidiary that will be configured in the system. 
    subsidiary details: Subsidiary Name: MUTTEEENA    
    Currency: AED (Dirhams) 
    Parent Subsidiary: ARIA NEIGHBORHOOD SUPERMARKET LLC 
  1. Currently Aria subsidiary is a single subsidiary represented for the location: Muraqqabat. So that for the MURAQQABAT Subsidiary, we will rename the existing ARIA and modify the Parent Subsidiary. 
    subsidiary details: Subsidiary Name: MURAQQABAT 
    Currency: AED (Dirhams) 
    Parent Subsidiary: ARIA NEIGHBORHOOD SUPERMARKET LLC 
  1. We will customize the PDFs of the following records 
    Payment Voucher, Bank Receipt Voucher, Check, Check VP, Proforma Invoice, Commercial Invoice, Vendor Prepayment 
  1. We will customize the report/saved search to incorporating / modifying the 2-3 columns. We are considering the simple changes only. 
  1. We’ll establish 6 custom roles for recently established subsidiaries (SHRINASAL RUSSIA, IMPORTEX FZE, MUTTEEENA).  
  1. We will provide post implementation ad-hoc support for 2weeks. 

ASSUMPTION 

  • The existing items will not be shared with the new subsidiary. If the client wishes to integrate the subsidiaries into the item records, this falls beyond the defined scope. 
  • Excluded the sharing of  COAs, Customers and Vendors with new subsidiaries. 
  • Clients will share all the subsidiary details to create the same.   
  • The major customizations of report and saved searches are out of the scope. We will not consider the customization of reports to adding and changing the more than 3 columns values. 
  • Taxes will not be set up for the SHRINASAL RUSSIA subsidiary.
  • Requests for roles over 6 falls outside the established scope. 
  • The client will share the permission level for each record corresponding to each role. 
  • Customization of PDFs beyond what’s mentioned above will not be taken into consideration. 

Leave a comment

Your email address will not be published. Required fields are marked *