AR - Support Both Pre-Authorized Debit & Credit?

Sort:
You are not authorized to post a reply.
Author
Messages
Garth Gerwing
Basic Member
Posts: 27
Basic Member
    Lawson AR has EFT capabilities - that are targeted toward a "Pre-authorized Debit" scenario - I.E. maintains customer bank account data in support of EFT. We will be engaging a credit card 3rd-party vendor in support of processing pre-authorized credit card transactions as well.

    In effect - pre-auth debit/credit amount to the same general requirements - although the resulting file TX's will need to be distributed to 2 seperate financial institutions: pre-auth debit->bank, pre-auth-credit->CC vendor.

    Has anyone attempted to orchestrate both of these concurrently within Lawson AR? Our issue is that, even though we believe that we could configure AR to address - all resulting EFT occurrences (regardless of type) will have the same "Pay Code" assigned - as this is defaulted at the Company level. Ideally, we would like these to have seperate/distinct "Pay Codes"

    NOTES:
    - we aren't using the Lawson Billing module
    - we believe that we could setup each type with a seperate physical file format - and in that way segregate the resulting TX's
    - possible to set one up as EFT - the other as BOE (Bill Of Exchange)?

    Any feedback would be most appreciated.
    You are not authorized to post a reply.