Often the line between an Organisation’s back office finance system and their system of recording prospective customers and opportunity can be quite blurred – in some occasionals aspects of the financial processes end up placed in the front-office systems to distribute responsibility across the business rather than centralized with the Finance team.
This can be due to a system-driven requirement such as a older less user-friendly finance system that requires training, limited licenses or lack of field access or more ideally business process lead in connecting sales and account management to the back-office. To give a recent example, say where a client may be using CRM to run a conference centre and needs to ‘build’ an invoice for a particular customer based on multiple points of sale (accommodation, bar bills, equipment hire, costs of speakers etc) and needs to collect the information from the business before approving and sending the invoice – this could be controlled through Finance or potentially the different points of sale could contribute via a shared solution and then simply leave Finance with the final approval before sending the invoice.
In these cases, aspects of traditional Finance functionality can reside in CRM to support the wider business, this should always be done carefully to avoid trying to ‘reinvent the wheel’ but can occasionally be a good option for a CRM solution to benefit the business.
This essentially (outside of Read-Only integration with the back-office Finance or ERP system involved) is the purpose of the Invoice entity in CRM and using CRM to track the invoicing of agreed Sales Orders. However the default functionality for tracking invoices in CRM has no concept of managing tax rates and different tax codes which can be key to controlling how an invoice might be raised – particularly when working with customers based in different localities where different rates of sales tax may apply.
The following two posts aim to give a break-down of how to add a concept of Tax Code functionally to MSCRM and at the same time give an overview of using the Child Pipeline for developing Plugins.