Alternative to Transcend?

Does anyone know of any reliable CC processing programs that we can switch from Transcend? We're having issues reconciling because they split their batches, and it posts to our bank in separate sums with delays of up to a month. Which is especially difficult to track because we can't print detailed transactions that are contained within these sums to reconcile with either.

According to the customer service reps, this should not be happening, but it is and there doesn't seem to be anything they know how or care to fix. Does anybody else experience the same issues?



[edited by: Sarah Parker at 4:37 PM (GMT -6) on 24 May 2012]
Parents
  • Thank you everyone for your suggestions! Went with Boann's suggestion of checking our merchant account (Harbor Touch), and pulling the detail there, from their online website. Turns out this is a new functionality that didn't exist before it was United Bank.

    We then ran a script to pull all the transactions from Tessitura for the same range we pulled the bank statements for:

    select
    T_PAYMENT.customer_no,
    T_ACCOUNT_DATA.act_name,
    T_PAYMENT.pmt_dt,
    sum(T_PAYMENT.pmt_amt) as total,
    TR_PAYMENT_METHOD.description,
    T_ACCOUNT_DATA.act_no_four

    from T_ACCOUNT_DATA
    JOIN T_PAYMENT ON T_ACCOUNT_DATA.id = T_PAYMENT.act_id
    JOIN TR_PAYMENT_METHOD ON T_PAYMENT.pmt_method = TR_PAYMENT_METHOD.id

    where
    T_PAYMENT.pmt_dt >= '2011-11-01 00:00:00.000'
    AND T_PAYMENT.pmt_dt <= '2012-01-31 00:00:00.000'
    AND T_PAYMENT.pmt_method in (--insert all ID's from TR_PAYMENT_METHOD that is a credit card transaction)

    group by
    T_PAYMENT.customer_no,
    T_ACCOUNT_DATA.act_no_four,
    T_ACCOUNT_DATA.act_name,
    T_PAYMENT.pmt_dt,
    TR_PAYMENT_METHOD.description

    /*
    select * from T_ACCOUNT_DATA
    select * from T_PAYMENT
    select * from TR_PAYMENT_METHOD
    */

    Lastly, we are now in the process of cross-checking the two sheets against each other. We're doing this by creating two separate tables in SQL which I passed onto someone else from the DB to script. This will ultimately dupe transactions to see what's missing/duplicated. I'll post the script on here once we've got the method worked out.

Reply
  • Thank you everyone for your suggestions! Went with Boann's suggestion of checking our merchant account (Harbor Touch), and pulling the detail there, from their online website. Turns out this is a new functionality that didn't exist before it was United Bank.

    We then ran a script to pull all the transactions from Tessitura for the same range we pulled the bank statements for:

    select
    T_PAYMENT.customer_no,
    T_ACCOUNT_DATA.act_name,
    T_PAYMENT.pmt_dt,
    sum(T_PAYMENT.pmt_amt) as total,
    TR_PAYMENT_METHOD.description,
    T_ACCOUNT_DATA.act_no_four

    from T_ACCOUNT_DATA
    JOIN T_PAYMENT ON T_ACCOUNT_DATA.id = T_PAYMENT.act_id
    JOIN TR_PAYMENT_METHOD ON T_PAYMENT.pmt_method = TR_PAYMENT_METHOD.id

    where
    T_PAYMENT.pmt_dt >= '2011-11-01 00:00:00.000'
    AND T_PAYMENT.pmt_dt <= '2012-01-31 00:00:00.000'
    AND T_PAYMENT.pmt_method in (--insert all ID's from TR_PAYMENT_METHOD that is a credit card transaction)

    group by
    T_PAYMENT.customer_no,
    T_ACCOUNT_DATA.act_no_four,
    T_ACCOUNT_DATA.act_name,
    T_PAYMENT.pmt_dt,
    TR_PAYMENT_METHOD.description

    /*
    select * from T_ACCOUNT_DATA
    select * from T_PAYMENT
    select * from TR_PAYMENT_METHOD
    */

    Lastly, we are now in the process of cross-checking the two sheets against each other. We're doing this by creating two separate tables in SQL which I passed onto someone else from the DB to script. This will ultimately dupe transactions to see what's missing/duplicated. I'll post the script on here once we've got the method worked out.

Children
No Data