Should an ERP system be customized? That is a question asked by many companies. Although some people say it should never be done, in almost every ERP project one of the first user requests is for customization.
If you accept that customization is a fact of ERP life, then what criteria should the project owner use to select and prioritize customizations? One objective framework for deciding on customization has been provided by consultant and author Geoffrey Moore. In his book ‘Dealing with Darwin’ Moore proposed the concept of ‘core’ and ‘context’ as a way to prioritize growth strategies, but the concept can also be extended to ERP customization.
In the dim distant past of ERP, 10 years ago and more, the way you learnt about the software was by referring to the training manuals relating to various modules – Accounts Payable, Bill of Materials, etc. It was a very product-oriented and narrow view of learning. Times have changed, fortunately, and 
As the CFO of an organization, your responsibility is to ensure efficient and effective financial operations and records, and influence overall strategy. An ERP is the foundation of the operations of a business. For a CFO, it enables you to track and report on all business transactions, analyse information, ensure governance and compliance, and increasingly do this via mobile devices. Therefore, you need to be very sure your ERP project will deliver what the business requires, and also what was promised.