Accounting vs programmers how to win?

mesline2011-08-04 09:31:44

Electronic accounting

mesline, 2011-08-04 09:31:44

Probably many programmers had to listen to: Well, you are a computer scientist, help me do this and that.
How to explain to the accounting department that a programmer and an administrator are different things?
How to win without wasting much energy and at the same time not be bad for the accounting department, so that you still get paid on time?

Answer the question

In order to leave comments, you need to log in

12 answer(s)

VenomBlood, 2011-08-04
@VenomBlood

- Well, you're a computer scientist - help me to do X.
- Ok, no problem. By the way, you deal with money, can you help me do Y?
Where Y is any difficult task related to money but not related to accounting.

KoXGen, 2011-08-04
@KoXGen

In our organization, this issue was resolved by a joint trip to the general manager, after which it was the administrator who was hired to ensure the operability of the equipment and help in certain matters of accounting, planning, etc. and so on ... And about the secretary, who before that called us every 10 minutes, I generally keep quiet.

interrupt_controller, 2011-08-04
@interrupt_controller

as an option to say: "I can do it, but it's not in my competence and I'm not paid for it." As a result, you can get a bonus for helping

lifelover, 2011-08-04
@lifelover

If the one on whom the salary depends asks, you need to help)

4dmonster, 2011-08-04
@4dmonster

Queue their requests and help them AFTER you complete your immediate tasks. And intelligibly explaining it to them. So that they understand: You are not obliged to do this, but you will help out of the kindness of your soul, but not to the detriment of your duties.

Vladimir Chernyshev, 2011-08-04
@VolCh

Go to the general manager and say something like “I won’t finish this project on time because the administrator at the facilities always disappears, and the accountants are constantly distracted from work.”

papersaltserver, 2011-08-04
@papersaltserver

Here the situation is as follows: if there is a person in whose responsibility this is, then you just need to repeat the memorized phrase “I do not have the rights to perform this task, contact Vasya”, but if there is no responsible person in the organization, then nothing can be done - it will be a feature of the organization, until the management understands the need for change (and this is usually a long process).

fkvf, 2011-08-04
@fkvf

And what will the accounting department do if you "accidentally" crash an important database? (after making a backup)
And then you will say - I'm a programmer, I generally don't understand this well, I made a mistake, well, it doesn't happen to anyone.

Juggler, 2011-08-04
@Juggler

Actually, this is not your question - it should be sorted out by the head of the department. It is necessary to drip more often on his brain.

tibalt, 2011-08-04
@tibalt

the ticket system would help your office

Mikhail Lyalin, 2011-08-05
@mr_jok

divide through orders, etc. areas of responsibility, indicate who and what tasks solves, enter the position of IT

Vadim, 2011-08-05
@vshemarov

But do you still have an admin who should resolve issues that arise in accounting? It is necessary to explain to the chief accountant that you all have a narrow specialization. like theirs - since there are four of them, the chief accountant never deals with the primary, the one that leads the primary, probably does not deal with salaries, etc. So it is with you - everyone has a narrow specialization, they should understand this. And in general, there are planned works approved from above, and the fulfillment of any requests from outside without the knowledge of the authorities - you can catch good guys for this. The most important thing here is not to send the user with his problem, but to sympathize and find reasons why you cannot solve his problem right here and now. Moreover, it is desirable so that he is imbued with sympathy for you.
And after all these explanations, it would be good to point to a specific person (this, of course, the head of the department should do), to whom the accounting department should contact on all issues. Perhaps in your situation it should be an admin who, after listening to their next request or problem, decides whether he fixes it himself, or passes it on to the programmers, or reports to the head of the department.
From my own experience, I can say that often the user does not even expect an immediate solution to the problem, it is much more important for him to see that his problem was accepted, he was listened to with understanding, and they promised to fix it within a reasonable time.