Number three on the enhancement voting list is ‘Import Cash Receipts from Excel or CSV’.

Our initial thought was to provide an expected generic Excel or CSV file format that imports just as the current statement import formats.  As we put more thought into it we began to look more to the future and see this as an opportunity to create a standard XML import into Payment Management.  The idea of still providing the generic file format, but also providing an interface (which the generic import would use) and documentation for those who have development talent and would like to directly feed the system without a user manipulating data into the generic format and manually importing.  Such a system would set us up for utilizing XML statement downloads from the van lines (currently supported by United, Mayflower and Atlas) as well as prepare us as others follow suit.

While existing imports would continue to work as they do now, we would need to provide new functionality that allows users to see payment management batches that were created through the new interface.  These batches would then need to be imported…this becomes similar to the process in Revenue Entry where revenue downloads are queued up and then the user imports them when they are ready.

Click here to see a mock up of the Payment Management screen with this functionality.

Once a download exist in the import pane the user can select one and click on Import.  This would bring up a dialog that allows the user to import as either a cash receipt batch (positive payments only) or a van line statement.  This dialog would allow the user to choose the branch, batch name and journal/wire date as well as make order and payment type associations.

Click here to see a mock up of the Cash Receipt option.

Click here to see a mock up of the Statement option. 

So what do you think of this approach?  It will take more time investment on our part up front, but the long term benefits seem to merit the investment.

Looking forward to your comments…