SpendMap

I like that it's a simple process once you do it a few times. I enter individual req's a lot for our vendor purchases, so it follows the same format.

I don't like that I can't edit my req, but have to have it rejected and make a brand new one. It makes it hard to keep the req #'s organized or up to date with the approval process.

The process to complete requestions, purchase orders, the approval system and ease of use.

At this point the pros outweigh the cons.

the approval rules and buyer spend limits helps monitor purchases
Implementation was done by Finance, seemed to go ok but issues when there are credits, SM is not easy for doing credits excluding RMA's with using Sage as your finance software.

Most feel it is simple to do a PO, but modifying or searching for information is difficult and time consuming. Using the 'help' menu takes too long as it is very extensive and complex and everyone is short on time. Help menu explains what the feature is for, but not how to use it
The thing we liked the least was no set of work instructions in the beginning and now there is, everyone has used it for so long, they don't want to go back and re-learn how to

SpendMap is easy to use for all users (Field, Approval, and generating a purchase order). Their customer support staff is easy to get a hold of, extremely knowledgeable of their system and the systems capabilities and are very pleasant to work with.

The way our company decided to create our database has made locating certain items within our database harder or setting up budgets slightly more difficult than the average company. However, SpendMap's team was able to assist us in fixing what we needed done in our system to make the budgets work the way we required them to.

Configurability - while complex to initially understand, very easy once you get the lay of the land.

would love to have more data visible on a screen - item numbers and names, req numbers w/ associated PO numbers - in one place, as an example