This post is part of a series on creating a simple audit for Microsoft Dynamics GP.
I created a simple audit a while ago when a client had a requiremnet to audit the change of EFT details onvendors, but did not have sufficient budget for a full audit product like the Assure Suite from Fastpath. This is not to say that the Assure Suite is expenseive, but the client in question was a very small client with only two users of Microsoft Dynamics GP.
The requirement for the original user was very simple; an audit on changes to vendor EFT in the single company they had in Dynamics GP.
Many of the audit tools available for Dynamics GP work by creating triggers in the database, and this is the same approach I took. The first step in creating the audit was to create a table to hold the audit table, then to create the triggers on the table to be audited and then to provide a method of reporting for users to use.
Over the course of this series, each of these steps will be covered.