I have been remiss on posting to my site/blog. I have been swamped, buried in work.
The credit card import module has been completed and running now for 1 week in a production environment with no bugs yet.
Here are the basic functions of the module..
1. User downloads credit card transaction detail from Chase as a CSV file, then drops file into designated directory. User can name file whatever they want.
2. Module imports csv data, archives file and renames it. All imported data is linked back to that specific file so user can look up individual transactions with ease, all the way back to original csv data. If user imports the same file several times or if there are duplicate transactions the process cleans it up.
3. Module processes imported transactions into employee expense reports, adding transactions to appropriate open expense report or creating a new one if needed. Transactions will be added to either the appropriate report based on transaction date, or in current expense report if the appropriate one has been submitted.
4. Employees open their automagically created expense reports and add project number information as well as account for each detail, adding descriptions if needed.
5. User runs a report which shows any import errors, employee expense entry errors or missed imported transactions.
6. When expense reports have been completed, they are posted using normal Vision procedures.
7. When a payment is made to the credit card company, user locates payment serial number in imported data (all transactions are imported, even chargebacks and payments) and processes that payment using a workflow. The workflow creates journal entry files to allocate the cash effect to all projects based upon which details were paid by that payment, and where the employees assigned them. This shows cash flow on a per project basis when that credit card payment is made.
8. Journal entry file can then be posted through normal Vision procedures.
If you would like more information about this module please contact me.