Document Imaging and Purchasing Card Statements

sweta-priyadarshini

Hi,

Am looking to talk to others who have implemented Purchasing Card Statements (PCS) and their related documents using a document imaging system (aka ECM - Enterprise Content Management). We use OnBase from Hyland, so if you have experience with that all the better, but it's not necessary. As you'd surmise we use Lawson Financials (version 9.01), but the solution doesn't have be be tied to it.

We're working on our AP implementation and we're looking to include PCS. A couple areas we'd like to get information / feedback about include:

- The PCS has the credit card number on it, so we have concerns about PCI and how the statements should be handled (e.g., keep original under one doc type and highly secure it; keep the redacted version as a second doc type to support less stringent security).

- We're looking to tie the PCS and supporting documents together with some unique identifier, preferably something other than the credit card number, and wonder what approaches others have taken. Our thinking is to store this unique identifier within Lawson to tie the two systems together.

If you have done this and are willing to share your experiences, I'd really appreciate it. I'm happy to talk off-line, though anything you're willing to share via the forum works too.

Thanks,

Dennis