Unfortunately I haven't got to de-paper my company yet, however this doesn't mean I've not looked into the matter.
'paper workloads' is pretty general.
it comes down to 'is there an electronic system or systems-in-tandem that will meet the need of whatever department, and whomever interacts with that department'.
When I first started here, we didn't have a IT ticketing system, so I've set that up, which has stopped (the majority of) people writing post-its on my desk and monitor. :P
I'm not a trained business analyst, but in working out the processes here, it comes down to, do you have a concrete process for types of requests in your department?
and by concrete, i mean flowcharts. yes, don't cringe, they are awesome.
until you can say "If I get a request for X type of thing, if I think it's a good idea, who do I go to approval, with what info, or alternatively, what's the formal process for declining X thing".
If you dont have a flow chart for how a system works, how can you expect to build an electronic system around it?
BUT
if you've got that, a package that I've been looking at, that looks VERY interesting is http://phpformgen.sourceforge.net/ it looks flexible enough to handle the information you want, in whatever format.
be it sending in an email, updating a record in a database or writing to file output.
All the other research I've found has lead me to proprietary tools that looked put together by relatively small companies, none looking that great, and most of them working around ASP and looking relatively unsupported.
edit: also, the only thing phpformgen doesn't do is authentication. but once the form is generated, if you know what you're doing with PHP and LDAP, i'm sure it could be implemented.