AP - Wells Fargo Payment Manager Service

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

blong

Advanced Member

Posts: 21

8/26/2010 3:46 PM

I am looking into utilizing the Wells Fargo Payment Manager service pay our AP vendors in Lawson. The service accepts a single file with several different payment types such as check, ACH, P-Card via Mastercard gateway, etc. Wells Fargo processes the data file and pays each vendor according to the payment type specified.

I support our Lawson system from a technical aspect. I'm trying to determine how to best pull the data from Lawson so that it can be manipulated into the Wells Fargo format.

We currently produce system manual checks (AP155) and ACH (AP160)transactions. Of course both of these generate data files separately and in different formats.

AP155 produces the check file which has the actual payment and remittance information in it. The AP160 produces the ACH file in prodline\work\AP160ACHTAPE but the remittance information is placed in the users print directory.

Has anyone used the Wells Fargo Payment Manager service? If so, what source in Lawson do you use to pull the information from?

Thanks!

jjcyeshua

Veteran Member

Posts: 49

9/5/2010 8:15 PM

I am not familiar with Wells Fargo Payment Manager Service, but it looks to me that ultimately what you want is to pull data for both ap155 and ap160 data files... What i would do is trace the data files back to there tables in lawson. Ccreate a query to pull all the data that you need from the tables, then format it to the way Wells Fargo Service data file...

Hope this helps

blong

Advanced Member

Posts: 21

9/7/2010 12:12 PM

Thanks for the reply! I had decided to take that approach so it is encouraging to know I am headed in the same direction as you suggest. I have identified the following tables to pull from: CBCHECK, APVENMAST, APVENADDR, APPAYMENT and APINVOICE. I think I can find all the data I need regarding payment and remittance information. Once I finalize the criteria for the query and pull the appropriate data, it will be just a matter of formatting that data to the Wells Fargo specs. Thanks again!

Eddie Smith

Advanced Member

Posts: 39

10/14/2010 9:05 PM

We are considering the Wells Fargo Payment Manager service as well and was wondering how far along you are in the process? Our company does a lot of wire payments, currently outside of Lawson, (both domestically and internationally) and we are testing using the AP161 SWIFT format to generate the wires and then send to Wells Fargo for payment. In addtion, we currently use the AP160 to generate ACH payments that are uploaded to Well Fargo via Data Transmission. Will keep you posted on what we find out with the AP161. Appreciate if you would do the same.

blong

Advanced Member

Posts: 21

10/15/2010 11:44 AM

Hi Eddie,

We also utilize the AP160 in our production Lawson system to generate ACH payments and upload them to WF.

Regarding the WF Payment Manager service, we setup a new bank_inst_code = CCR in our Lawson test system and performed a check run using the AP161. We envision executing a check run for CCR daily at most. I utilized a SQL script to pull the data to a flat file as a single source.

I reformatted the data utilizing a PERL script according to WF specifications. I have submitted a file to WF as a test and received feedback on a few corrections to make.

That is where we stand for now. More testing to follow.

blong

Advanced Member

Posts: 21

12/7/2010 4:14 PM

Update on our progress:

We have been live on the Wells Fargo Payment Manager service for a couple of weeks now.

The AP161 (Electronic Payment File Creation) is being utilized to generate the payments. The data is extracted via SQL script with a condition on the serial_number in the CBCHECK table. The serial number can be identified from the AP161 print file.

Reconciling:
The AP161 creates one total transaction to be reconciled similar to the AP160 for ACH payments. Wells Fargo provides us with information on individual payments that clear the bank as a result of being picked up by the vendor. Thus, our Payment Manager payments are processed by the bank more like a manual check instead of an electronic payment. Wish we had known this before hand. Live and learn.

Change in process:
We will start utilizing the AP155 which creates separate transactions to be reconciled. We can still pull the data from the CBCHECK table by a range of check numbers (trans_nbr).

Sam Simpson

Veteran Member

Posts: 239

12/7/2010 6:58 PM

Utilizing Treasury Management from different 3rd party providers we always use both CBCHECK and CBTRANS to interface positive pay data.

jbertoli

Basic Member

Posts: 18

12/22/2010 10:33 PM

We are almost ready to implement our ACH process with a different bank.

First, we are on a very old version of Lawson. We are using the AP161 process and marking Payment Code as EDI. This format provides the most data needed by our 3rd party company handling the process. The 3rd party has minimal requirements so they will take our full file and just utilize the fields I've designated.

Karen Ploof

Veteran Member

Posts: 118

12/23/2010 7:26 PM

What 3rd party company are you using. The one I talked to required a modification to AP161 to get the data in their format. I'd rather deal with someone who can take the AP161 file without modification.

Mark F. Hardy

Veteran Member

Posts: 44

6/15/2011 7:05 PM

Hi Blong:

We too are going to use Wells Fargo Payment Manager. But just the prior month we had another request for Invoice Payments from a 3rd party. So, we decided to use the Positive Pay CB170 for all payment types. The subsystem will accumulate, offload, and create/send an output file for the 3rd party. The CB170WK is used as the driver, and we step back to CBCHECK, DBAPPAYMENT, and DBAPINVOICE.

We coded so a parms of &THIRD_PARTY_CODE can be sent in. That way we will be able to do mininimal setup with a core translation program for each 3rd party.

My question is, did your final custom translate program/sql access the CBCHECK, APVENMAST, APVENADDR, APPAYMENT and APINVOICE files like you initially posted? Or was all the info in the AP160 or AP161 Outfiles? We initially tried sending these Outfiles to Wells Fargo, and they said it did not interface. So I am guessing you had to do the CBCHECK, etc. route. Thanks in advance!

blong

Advanced Member

Posts: 21

6/15/2011 8:02 PM

Hi Mark,

We currently submit CCR, DAC and CHK payment types through Wells Fargo's Payment Manager service. We access the CBCHECK, APVENMAST, APPAYMENT, APINVOICE for each of these types. We also reference the APELECTID table for the CCR transactions because we store our CEO Company ID in the AP01.3 screen which is placed in the PY25 field of the Payment Manager file. We also pull from the L_HAPI table for the CHK payments. This table contains comments that would normally print on the manual check remittance. We place those comments in the IN04 field of the Payment Manager file.

Mark F. Hardy

Veteran Member

Posts: 44

6/16/2011 12:41 PM

Blong, Looks like we are on the right track. Your exta info definately helps. Thanks, again.

Michelle

New Member

Posts: 4

9/26/2012 10:01 PM

We are in the testing phase of implementation of the Wells Fargo payment services. We are having difficulty finding a good place within Lawson to house the delivery code that maps into the using the CK record. Has anyone found a good solution for this?

blong

Advanced Member

Posts: 21

9/27/2012 11:48 AM

We only utilize two codes but maybe our example will give you some ideas. We use code 100 for standard US mail which is the majority of the checks. We use code 410 to have the check sent back to us next day UPS for hand delivery or pickup. If we need an invoice to be paid with the 410 code, our AP clerks select Y on the Enclosure field when entering the invoice. This is on the Payment tab of the AP20.2 screen. Once the invoice is paid, the appayment.enclosure field contains Y. When pulling the data for submitting to Wells Fargo, my SQL script pulls the delivery code as follows:
decode(appayment.ENCLOSURE,'Y','410','100')
. Hope this helps.