Question about Tessitura Merchant Services (TMS) and Controlled Batches

I have a question about using TMS and Controlled Batches.  We don't use a lot of them, but we certainly use them for:

  • Event Cancellation
  • Pledge Billing

Does this documentation mean that until such a time as Tessitura removes controlled batches, and presumably updates the utilities that rely on them, TMS users cannot use the listed utilities?

Controlled batches cannot be used with EMV or Secure Deviceless Entry payments. If your fundraising department was using controlled batches they will need to transition to uncontrolled batches.

Note: Controlled batch functionality will be removed in a future version of Tessitura. The Network recommends using uncontrolled batch types, except when a controlled batch is required for the following utilities: Contribution Import Utility, Event Cancellation Utility, On Account Funds Disbursement Utility, Direct Debit Order Billing, Direct Debit Pledge Bills, SEPA Direct Debit Order Billing, and SEPA Direct Debit Pledge Billing.

https://www.tessituranetwork.com/Help_System/Content/TN-Application/Payment-Methods/TMS-Getting-Started.htm

X-Posted to Finance

Parents
  • All the utilities that use controlled batches can be used with Tessitura Merchant Services. And that's because they are either using on-file credit card tokens or are refunding by reference number. In other words, no credit card data is being stored in the controlled batch.

    Controlled batches just can't be used for order or contribution processing.

  • Kevin, this differs from what we were told when we cut over in May. We were told we could no longer use controlled batches for any credit card processing, and based on that advice we insisted that all of our sublicensees use uncontrolled batches moving forward for auto-billing.  I am concerned that there seems to be a difference between what's being advised by the implementation teams vs the documentation team.  I'm sorry to post this on the forum. However, many of my users follow these discussions and I want to make sure that they trust what we convey to them.

Reply
  • Kevin, this differs from what we were told when we cut over in May. We were told we could no longer use controlled batches for any credit card processing, and based on that advice we insisted that all of our sublicensees use uncontrolled batches moving forward for auto-billing.  I am concerned that there seems to be a difference between what's being advised by the implementation teams vs the documentation team.  I'm sorry to post this on the forum. However, many of my users follow these discussions and I want to make sure that they trust what we convey to them.

Children
  • I am concerned that there seems to be a difference between what's being advised by the implementation teams vs the documentation team. 

    Hear, hear. We went live on TMS in October, and the above was a repeated concern for us as well.

  • We went live in Oct as well and told to not used Controlled batches as well.

  • Hi Nancy,

    There are several utilities for which controlled batches are required, and you can use those utilities when you are on Tessitura Merchant Services. These are the utilities noted in the documentation Gawain quoted. Looking closer at the list, I realize now that none of the utilities on the list charge credit cards. A few of them make refunds to credit cards, but again, those use the Refund Prior Payments functionality and are completely compatible with Tessitura Merchant Services.

    The standard billing utilities (Pledge, Order, and Invoice) do not require controlled batches and in fact do not allow you to use controlled batches (they are filtered out of the batch type parameter dropdown). This is how they have worked for a long time.  

    It is true, however, that an on-file card could be used in a controlled batch. Here is what we say in the batch documentation about this:

    When Tessitura is installed in P2PE mode (which includes all users of Tessitura Merchant Services), only credit card payments using on-file credit card tokens can be processed in a controlled batch. 
    https://www.tessituranetwork.com/Help_System/Tessitura.htm#Batch%20Administration/Batch%20Introduction%20and%20Planning.htm

    But because it's not likely you would be processing contributions or orders using only on-file credit cards, the use of a controlled batch for contributions or orders becomes impractical. And with controlled batches being scheduled for deprecation in the future, the switch to TMS is a good time to just stop using controlled batches, except for with that list of utilities (which are all either doing refunds or doing direct debit billing in the UK).

    I apologize for any confusion my original posts caused. I'll talk to the implementation team about reviewing what they are saying to see if there is any additional clarification needed there.

    To sum up:

    • If a utility requires the use of a controlled batch, you can continue the use of that utility with Tessitura Merchant Services
    • You shouldn't use controlled batches for anything other than those utilities that require them