In the last post, we laid out the business requirements and provided a simple explanation of how we might implement those requirements. In this post, we’ll outline each of our custom field definitions and how we’ll use them in our solution. We will be adding new transaction body and column fields as well as fields on the employee and expense category records. In a later post, we’ll see how each specific field is used to satisfy a business requirement.
We’re just getting started on a project to migrate from our existing travel and expense solution to NetSuite’s expense report feature. Since this is a new blog, I thought that this might make a series of posts to walk through the design, configuration, customization and deployment of the entire solution. It’s not a complex project, but it will touch on a few areas of customization that some smaller companies might not be comfortable implementing on their own. Our company follows a pretty rigid development process for internal applications and I’ll shield you from most of that, but I’ll certainly touch on each step of that process along the way.