Most people who are using the free version of SpendMap want to track and report on their spending based on one or more account codes or account code “segments”, such as a cost center, general ledger account, department, business unit, project, fund, etc.
We’ve had a few support tickets from people who seemed a bit mislead by our default terminology for the account code fields. Most commonly, people are using the Project or Job Fields, when they could get more benefit using the Cost Center field instead.
So in this blog post, we’ll discuss a few options for setting up the account code fields in SpendMap. For more details, check out this section of the Online Help…
– System-Wide Features and Information > Master Files > Account Coding (Overview & Guidelines)
SpendMap includes 5 user-definable fields that can be used for coding Purchase Orders and other transactions. By default they are labeled as;
- Cost Center
- G/L Account
- Project
- Job
- Request-By
But you can change the names of these fields, so please don’t feel obligated to use the default field titles.
And you do not need to use all of these fields if you don’t want to. Most small businesses that are using the free version of SpendMap will use only Cost Center and maybe G/L Account, while Project, Job and Request-By are typically only used by larger organizations with more complex account coding needs, such as larger public, government or non-profit organizations. (more…)
But unlike SQL Server and Oracle databases used in our paid version, there’s nothing running on the server to do any behind-the-scenes database maintenance.
Craig had the Free Version of SpendMap installed on his laptop (including the database), and the voltage regulator went out, so he couldn’t power up his machine.
What role do expense reimbursements play in your Purchasing process?

