Is your manual expense management process in crisis?
It's easy enough to manually process a few expense forms here and there. But suddenly there comes a time when the volume
just gets too much. You're spending days a month just trying to catch up, never mind do anything useful.
BIS can help.
DIY
Someone decided it should be easy enough to build a system in house. It worked OK for a while, but there are now problems
on a regular basis. The original developer has left. Where is the original source code? HELP!
Snapshot
Management has asked for a snapshot of all cardholders who have not yet put their expense form in. All you know is, it's the ones
not in that pile of paper over there. You think.
|
|
SAP / Oracle / etc
It can sound logical - why shouldn't expense management be in your financial system? Well, financial systems like SAP cover a lot of ground -
their focus on expense management in an Australian context is not huge. So you'll have to spend money on consultants to make the system
useful and user-friendly. This means specifications, test plans, development, testing, documentation and ongoing support.
All to reinvent the wheel.
Aren't there more strategic things for these resources to be working on? For BIS, expense management is all we do.
Oh, and we have 30+ organisations using iCMS and SAP.
Non-Australian systems
It seemed OK at the time, but now you're finding that tax is not being managed well and you
are spending time every month fixing things up. And the call centre is ...well, somewhere out there but definitely not in Australia.
Expense management in an Australian context is all we do. We should get out more...
Bank provided systems
This can sound appealing, and is often subsidised in mysterious ways. But who will set it up properly for you? Can it process other types of data?
If you change banks what happens? How responsive is the support? Who is ultimately responsible for the system - the bank, or someone else?
If you use BIS it's clear-cut. We take responsiblity no matter what.
|
