The clean work flow for check input would be to have a twain scan scan the check and display it, attach the image to a new transaction and allow you to enter the check data for the attached image.
Reducing the images to low dpi and grey-scale in a compressed form like png, tiff might be a nice way to keep check image storage size down, especially if they are in the xml as base 64 or the like.
DGPickett
The clean work flow for check input would be to have a twain scan scan the check and display it, attach the image to a new transaction and allow you to enter the check data for the attached image.
Reducing the images to low dpi and grey-scale in a compressed form like png, tiff might be a nice way to keep check image storage size down, especially if they are in the xml as base 64 or the like.