I like the premise of what you are trying to do by writing under an alias. I loved the Coverlet Meshing articles that were done for awhile, I miss those.
But Coverlet wrote about bigger picture stuff we could relate to. The couple of articles you have written so far are so locally oriented we don't have context (as readers) to know what is going on. Is Finance really that bad there or is your IT stuck in "Glass House" mode?
For example, did they ask for report on CoA because:
1) There is no report to list that out already written.
2) You have nice ad hoc query tool but they don't know which file is CoA master?
3) They are just too lazy to run the report.
On the check printer, was printer in server room to also protect the check stock itself, or some other element of the security to control access to printing A/P checks? Here, any printer which does 8x11 printing can print checks but check stock is locked up and in control of only Accounting. So even though as programmer/analyst I know how to reprint checks, I could never get our check stock to do it. I like being protected like that, don't want anyone accusing me of fraud.
As far as ERP goes, that is a pretty common story. You are right the users should own it but they never do. Systems analysts from IT are invaluable on this to keep things moving. Are you saying your IT people really don't know your business systems enough to assist these people?
Maybe I'm looking at these articles too seriously, that this is all tongue in cheek?