We find the accounting contact to be in important part of managing our invoices, however there are also many limitations. I wanted to know of others' thoughts. Here's some of what I've found.
1) Accounting contact at the Client and Invoice level, but not the project level.
In most cases, a company will have a single accounting contact, and having a client level accounting contact works fine. However, we have many clients with whom we have multiple project contacts, but they all have different invoice contacts. This makes it a challenge to manage the invoices. We could set up "branches" for each, and manage them as separate branches with separate accounting contacts. But that seems like a work around.
We'd like to be able to determine an accounting contact at the project level so the PM can update or manage this information... Putting this information on the "People" card in the project would be very helpful.
2) No API connection to the accounting contact. You can't add/update the accounting contact through the API. So our work around is to create/update the main client contact information. Again, not ideal, because we will either have inconsistent data or we need to manually add accounting contacts for each new client.
I guess that's my list for the accounting contact so far. Any other thoughts or experiences?
Customer support service by UserEcho