"Fake" payment method

Hello all,
 
I'm looking to create a fake payment method to track internal transactions from other departments in the organization.  For example, someone in our development department wants to purchase a CD to give to a patron.  Rather than put it on a credit card and have to pay transaction fees, I want to be able to use a payment method and enter the GL number that they want to charge into the payment window (pretty much the same functionality as using a credit card, just not with real money).
 
We have also considered creating payment methods for each department tied to specific GLs, but the accounts used vary depending on the purpose of the transaction.
 
Do you have another suggestion?  Thanks in advance for your wisdom and insight!
 
Lesley Chaney
Director of Ticket Services
Saint Louis Symphony Orchestra
718 N. Grand Boulevard
St. Louis, MO  63103
(314) 286-4146
(314) 286-4111 fax
Parents
  • Hi Leslie,

    We have a large amount of internal GL MOPs in the system (and we are always adding to them).  It does take a while to set them up and , as I stated, you will probably be adding new ones periodically, but it makes it very easy to account for internal charges.

    The MOP description is simply the GL number so that it is easy to recognize in the payment window.  We originally tried to name each MOP the same as the GL account description, but found that using the raw GL worked better.

    Ours are set so that only the manager user group has access to the MOPs so that the CSRs can't accidentally charge another department.

    It's worked out very well for us.

    Hope that helps

Reply
  • Hi Leslie,

    We have a large amount of internal GL MOPs in the system (and we are always adding to them).  It does take a while to set them up and , as I stated, you will probably be adding new ones periodically, but it makes it very easy to account for internal charges.

    The MOP description is simply the GL number so that it is easy to recognize in the payment window.  We originally tried to name each MOP the same as the GL account description, but found that using the raw GL worked better.

    Ours are set so that only the manager user group has access to the MOPs so that the CSRs can't accidentally charge another department.

    It's worked out very well for us.

    Hope that helps

Children
No Data