Summary of Changes Upgrading eBanking to v8.6 - Sandler*Kahne ...

Summary of Changes 

Upgrading eBanking to v8.6 

(eBanking v8.x is available for MS Dynamics SL 7.0x, 6.5, 6.0) 

With the release of Sandler*Kahne Software’s eBanking v8.6 there are a number of significant 

new (and exciting) changes to the suite of modules. This document outlines these changes and 

how they might affect an installation/upgrade of the eBanking Suite. This document includes all 

changes/enhancements since eBanking v6.2.2. 

ATTENTION: All of these changes should be reviewed in detail before upgrading an existing 

eBanking site to v8.6. 

There are four parts to this document: 

Changes to existing functionality 

- Each voucher/pre-payment is now coded with a “Pay By” method 

- Vendors/Customers have a default “Pay By” and restricted Transaction Types 

- “One Pass” Payment Selection Filter 

- Create and Send (AP and AR) – organized around eBanking files (not batches) 

- Originating DFI Identification added (AP-EFT and AR-EFT) 

New Module 

- Wire Transfer Plus 

New Features 

- Optional Manual Check workflow 

- eBanking Security (Account and Amount Approval) 

- Custom Message/Attachment 

- Advanced Processing Options (2 step processing) 

- Visibility to pending AP/AR documents 

- Effective date displayed 

- Effective date offset 

- Email notations 

- Batch File Format ID, path/filename displayed (and possible error conditions) 

- Option to not check for orphaned eBanking vendors/customers 

- Tax Payments – custom formats 

- AR-EFT – option to filter invoices by due date, discount date, document types 

- AR-EFT – multiple EFTs against a batch and documents 

- Lockbox – support for Credit Memos and discounts 

- Lockbox – multi-line file support 

- Lockbox – split check support 

- Lockbox – enhanced duplicate payment number checking 

- Lockbox – allow entry of deposit date 

Last updated: 4/25/2009, eBanking v8.6 Page 1

- F1 Help 

*Important - Notes to Implementers 


Changes to Existing Functionality 

Each voucher is now coded with a “Pay By” or Payment Method. (AP-EFT & 

Wire Transfer only). 

Previously all vouchers for a vendor designated as an eBanking vendor were assumed to 

be paid via EFT. Now each eBanking vendor has a default “Pay By” method, along with 

other possible payment methods (including a MS Dynamics SL check). However, each 

eBanking vendor can optionally be set to restrict their “Pay By” method to only one 

value. In Voucher and Adjustment entry (03.010.00) and Quick Voucher and Pre- 

Payment Entry (03.020.00), the payment method for each voucher can be selected (the 

field used is APDoc.eStatus). See the screenshot below. 

With this new feature, it is no longer necessary to move an eBanking vendor’s vouchers 

into an SL check batch (if they need to be paid via check) 

Please see Installation/Upgrade Notes – Notes to Implementers section 

The customized Voucher and Adjustment Entry screen (03.010.00): 


The customized Quick Voucher and Pre-Payment Entry screen (03.020.00): 

The customized Document Maintenance screen (03.250.00): 


The customized Recurring Voucher Maintenance screen (03.260.00): 


Vendors/Customers now have a default “Pay By” and can have their 

possible “Pay By” types configured. (AP/AR-EFT & Wire Transfer only). 

In Vendor Banking Entry (DD.250.00), the default “Pay By” method (Entry Class) is 

selected, and there is a new option to indicate that this cannot be changed in Voucher 

Entry (Red). 

Also, there now is an option to restrict the “Pay By” methods that can be used by this 

Vendor (Green). By default, all “Pay By” methods for the format are available. When a 

vendor sometimes needs to be paid by a MS Dynamics SL Check, it can also be added to 

their Transaction Types. (Pay By method, Entry Class and Transaction Type are all 

synonymous terms). 


Transaction Types screen (sub-form) used to configure transactions types for each 

Vendor: 


The eBanking Payment Selection Filter (DD.520.00) now creates all 

eBanking and/or MS Dynamics SL check batches in one pass. (AP-EFT & 

Wire Transfer only). 

Previously, the Payment Selection filter would take one AP Selection batch and remove 

all the EFT Vendor/Vouchers or all the SL Checks. Now the Payment Selection Filter 

reviews a Payment Selection and can split that batch into any number of appropriate SL 

check and eBanking batches. 

Below is an example where Batch 000118 has 15 SL Vouchers (to be printed on SL 

checks) and 1 eBanking voucher to be paid via EFT. Upon entering the batch number the 

screen shows a preview of what will occur if Begin Processing is clicked. After 

processing, batch 000118 would be left with the 15 SL Vouchers and batch 000119 

would be created with the one EFT (US-ACH). When the “split” takes place an event log 

is written, recording the details. 

In this way, the filtering process is streamlined and potentially many manual steps may 

not have to be done, including advanced selection options used in the AP Payment 

Selection process. 


Create and Send (AP and AR) – organized around eBanking files (not 

batches) (APAR-EFT, Wire Transfer and Positive Pay). 

This will likely be one of the most visible changes you will see in this new version. In 

previous versions, the user would select check batches for payment (AP-EFT), invoice 

batches to receive payments (AR-EFT), or check batches for transmission (Pos Pay) and 

then select Begin Processing. 

With eBanking v8, the user first creates an eBanking file “record” and then attaches one 

or more SL batches to that eBanking file. There are a number of benefits of this new 

approach: 

Clarity of organization when multiple batches are in one eBanking file. 

eBanking file name can be changed and is stored for future reference 

eBanking file number can be added to the filename 

Easily process actions against the file (print/reprint audit, Keep, Send Emails) 

eBanking file totals are more readily visible 

New feature – Details – allows drill-down to all documents in the transmitted 

eBanking file. 

The new Positive Pay tab in AP-Create and Send Files (DD.500.00). Note the eBanking 

file records in the top grid, and then the associated batches below. 


The new Electronic Funds Transfer/Wire Plus tab in AP-Create and Send Files 

(DD.500.00). Note the eBanking file records in the top grid, and then the associated 

batches below. 


The new Electronic Funds Transfer tab in AR-Create and Send/Receive Files 

(DD.540.00). Note the eBanking file records in the top grid, and then the associated 

batches below. 


Note that the eBanking filename is shown with the eBanking file – and if allowed (setup 

option), it can be renamed as the process starts. Also, as shown here, when used with a 

new setup option, the date and eBanking file number can be automatically appended to 

the filename. (AP-EFT is shown, same for Pos Pay and AR-EFT) 

What was previously called deposit options (AP/AR-EFT only) is now defined with the 

eBanking file record – note that Test File is a new option. 


Batches are selected to be included in an eBanking file in a similar way as in previous 

versions. This sub-form is accessed via the Select/View Batches button for an eBanking 

file (AP-EFT shown, this works the same for Pos Pay and AR-EFT). Note the eBanking 

file number/info on top – along with the path and filename. Also note that each batch 

now shows the eBanking file number it was a part of. 


Another very nice new feature is the “drill-down” inquiry – called Details. It displays all 

the documents included in the eBanking file (AP-EFT/Wire, AR-EFT and Pos Pay). 

The example below (from Pos Pay) shows the Details sub-form – accessed after pressing 

the Details button for an eBanking file. Note that in this case both AP and PR batches 

were in the Pos Pay file. All documents can be shown, or they can be filtered by batch. 

Originating DFI Identification added (APAR-EFT). 

In rare cases this part of the NACHA file (5, 6 & 8 records) differs from the first 8 

characters of the paying account’s transit routing number. This field has been added to 

address this requirement. The field is added in both eBanking Setup (DD.950.00, AP/AR 

EFT/Wire Defaults tab, Company Paying/Cash Defaults tab) and in Company Paying 

Accounts (DD.260.00, AP/AR EFT/Wire tab, Company/Batch tab). 

It is important when upgrading that this field is reviewed and verified with your bank that 

you are using the correct value. 


New Module 

Wire Transfer Plus 

This powerful new module now supports both Domestic and Foreign wires. Additionally 

(depending on the bank), other “Plus” features including Bank Drafts, Corporate Checks 

and even CTX transactions are supported. 

All the additional data elements have been added to the system to support this module. 

Fields include Beneficiary Name/Address, Beneficiary Bank, Intermediary and Credit 

Banks and Ordering Party information. This information is also included on the Vendor 

Banking Information report. 


Processing with Wire Transfer Plus works virtually identically to that for AP EFT 

(voucher/batch selection, communications, e-mail notification), so it is very easy to learn. 

Before purchasing/using Wire Transfer Plus, be sure to check with Sandler*Kahne 

Software to see if your bank’s Wire Transfer Plus format has been developed and 

implemented. 


New Features 

Optional Manual Check workflow (AP-EFT, WTP only) 

This is one of the most exciting new features to eBanking. Previously, the workflow to 

create an AP-EFT and/or WTP file required processing a Computer Check Batch. When 

running the batch through the check printing process, the “checks” would be printed to 

plain paper or to a file – as they were going to be paid electronically. 

We have now added a Manual Check workflow option. With this option, the AP-EFT or 

WTP selected vouchers can create a Manual Check batch. Once created, the user can 

immediately go to AP – Create and Send Files (DD.500.00) to create the file and send to 

the bank. With this new feature the reference number of the manual checks can be 

customized to include up to two leading characters to identify these electronic payments 

from checks. Below are some screens that illustrate this new workflow option. 

The Manual Check workflow option is setup in Transaction Types (DD.301.00) 


In Company Paying/Cash Accounts (DD.260.00) the “check” numbering of the manual 

check batch can be custom configured. This is optional. 


With the Manual Check workflow option set (above), the eBanking Payment Selection 

filter will create the Manual Check batch. The next step is to go directly to AP – Create 

and Send Files (DD.500.00) to create the file – no need to go through the checking 

“printing” process. 


A Manual Check batch created by the eBanking Payment Selection filter – note the 

reference number leading character. 


eBanking Security (All modules, Account Number Approval, Amount Approval – AP- 

EFT, WTP only) 

The basic eBanking Security feature was added with eBanking v6.2. It provides for userbased 

security in the “Create and Send …” screens of eBanking, when more than one 

module of eBanking has been implemented (e.g. when AP-EFT and Positive Pay are both 

being used) 

An important use of this is where both AP EFT and Positive Pay are implemented. For 

example, allowing a user to upload Positive Pay files but restricting them from 

transmitting an AP-EFT file. The eBanking Security screen (DD.302.00) gives the 

eBanking Administrator control over these rights. 

Note that when using AR-EFT, the Create and Send and Select Invoices options are 

enabled here- since they now are both available in the one AR-Create and Send/Receive 

Files application (DD.540.00). 

Account Number Approval- Another eBanking Security feature added is Account 

Number Approval – used with AP-EFT and Wire Transfer Plus. When turned on, this 

feature requires two different SL users to confirm a change for a bank account number. 

This prevents fraudulent change of an account number. 

With eBanking Security turned on in eBanking Setup, the Account Number Approval 

option can be turned on in the eBanking Security application. Users are designated with 

rights to Approve Account changes (green) 


With Account Number Approval turned on, the system requires two different users to 

approve an account number change: 


Amount Approval- This new feature allows control over outgoing payments (AP- 

EFT/Wire Transfer Plus). In eBanking Setup, two approval levels are set, with up to 5 

approvers at each level. A user is then designated as the user to determine which users 

can be approvers. 


Now in eBanking Security (DD.302.00), the designated user determines the approvers 

and later those approvers will enter their passwords. The user that can designate 

approvers cannot be an approver themselves. 

Now that the setup is complete, in AP-Create and Send Files (DD.500.00), Amount 

Approval does its job. An eBanking file that contains any documents requiring approval, 

cannot be selected unless the approvers have entered their passwords. In the “Details” 

sub-form – for an eBanking file, any document that exceeds an approval level is noted 

(circled column). 


The Amount Approval tab on the “Details” sub-form is where the approvers and their 

passwords are entered. These can be entered at any time and are stored so different 

approvers can mark the file at different times. Once all the approvers required have 

entered their passwords, the file can be transmitted to the bank. 


Custom Message/Attachment (AP-EFT, AR-EFT, Wire Transfer Plus) 

The email notification feature of eBanking has always allowed for the top and bottom 

portions of the mail to be customized (along with the Subject line). In addition, with 

some customization manager settings parts of the email main body could be customized 

as well. Even transaction details and user fields could be added to the main message. 

With this new feature the main body of the email is now completely customizable. In 

fact, any data from the SL database (or any database) can be included in the email 

message. Also, the contents of the email can be placed in a file and added as an email 

attachment (i.e an .xls with the vouchers/invoices being paid, or a tab delimited or fixed 

field formatted file). 

The customized message is created in a SQL stored procedure. The “standard” email 

message is provided in this procedure. To make a customized message, this procedure is 

“cloned” and then modified to meet the design requirements. 

Below is a screenshot of the new Attachment/Custom Message Details sub-form (part of 

Vendor/Customer Banking Entry – DD.250.00) with the optional settings. Note that all 

of the options are configurable at the system level as defaults, but can be further 

individualized by vendor and/or customer. 


Advanced Processing Options – 2 step processing (AP-EFT, Wire Transfer 

plus) 

This new feature allows the user to break the AP-Create and Send Files processing into 

two separate steps. With Advanced Processing turned off (the way eBanking has 

historically worked), the EFT/Wire file is created, the communications option (browser) 

is launched, then the process/file is “Kept”. In some environments, different personnel 

need to perform these tasks, and at different times. 

With Advanced Processing (APO) turned on, the above process can be broken into 2 

steps – executed at different times. The EFT/Wire file can be created and then another 

person at a later time can upload the file to the bank. And the final Completion 

(Keep/Delete) process can be done after the file has been successfully processed by the 

bank. Below are the controls for Advanced Processing in eBanking Setup (DD.950.00). 

When using Advanced Processing the eBanking EFT/Wire files need to be named 

uniquely, so that with various timings of creating the files and uploading them, they will 

not be overwritten. 


Visibility to pending AP/AR Documents (AP/AR EFT, Wire Transfer Plus) 

In Vendor Banking Entry (DD.250.00) a new frame gives visibility to pending documents 

for this vendor or customer. This is useful when changing values (format, entry class, 

etc.) in this screen. It can be refreshed upon demand. 


Effective Date Displayed (AP/AR EFT, Wire Transfer Plus) 

When using the “Create and Send Files” applications, the effective date used when a file 

was kept is now displayed in the grid. 


Effective Date Offset (AP/AR EFT, Wire Transfer Plus) 

When using the “Create and Send Files” applications, the effective date had defaulted to 

the current Solomon Business date. Now, with this new setting it can be set to a fixed 

number of days after the current Solomon Business Date. This value is set for each File 

Format (default = 0). To modify a value in File Formats (DD.300.00), MS Dynamics SL 

must be set to Initialize Mode. 


Email Notations (AP/AR EFT, Wire Transfer Plus) 

With the addition of the Wire Transfer Plus module, it is now possible to send one 

Vendor a combination of a Wire and an EFT payment in the same SL check batch (this 

will depend on the bank’s Wire Transfer Plus format). When this is done, “Email 

Notations” can be used to indicate on the email remittance advice how each invoice was 

paid. These notations are entered in the Transaction Types screen (DD.301.00) – by 

Format. If left blank, then there is no special notation next to the invoice in the email 

remittance. 


Format ID and Path/Filename Displayed (AP/AR EFT, Wire Transfer Plus, Positive 

Pay) 

When using the “Create and Send Files” applications, as a batch (or batches) is selected, 

the status line now displays the batch’s format ID and the path/filename where the output 

file will be written. This feature is now included for AP-EFT, Wire Transfer Plus, 

Positive Pay and AR-EFT. A setup option allows the path and filename to be changed as 

the file is being created. 

Also, if there is a problem with the path/filename and/or access rights for the current user 

to write to that path/filename, a message is displayed as the eBanking file is selected (the 

message is also displayed on the status line – See Bad Path notation.) 

This message is because the path does not exist: 


This message is because the SOL4PP.TXT file is marked as read-only rights: 


Option to not check for orphaned eBanking records, during “Create and 

Send” Keep process (AP/AR EFT, Wire Transfer Plus) 

Prior to v8 of eBanking, during the “Keep” process (for both AP-EFT and AR-EFT), all 

MS Dynamics SL Vendors were reviewed to check and see if any had been deleted. If 

that was the case, then their corresponding “orphaned” eBanking vendor records would 

be deleted. However, when installations have very large numbers of Vendors, this 

process takes a very long time. 

This new option (set in eBanking Setup (DD.950.00) allows for this “orphan” checking to 

be turned off. If turned off, it is recommended that it be turned on periodically (say 

quarterly), to “clean up” any orphaned eBanking Vendors/Customers. After one “Keep” 

has been processed (and the checking has been done), it can be turned off again to save 

the processing time. 


Tax Payments – custom formats (AP-EFT only) 

Custom formats (addenda records) can now be used with tax payments. There’s also a 

new option to place the Tax ID on the “6” record. 


AR-EFT – multiple EFTs against a batch and documents 

In previous versions of eBanking an invoice batch could only be accessed once to collect 

payments against it. Now, with v8 of eBanking, invoices within a batch can collected 

against any number of times at any period in time. In addition, a partial collection against 

an invoice can be processed and then later in another eBanking file another partial 

collection can be done (no limit on the number of partial collections or collections against 

a batch). As each invoice batch is processed in an eBanking file a “Group” is used to 

track the various collections. Note the Batch number and Payment Group for this 

collection. 

When on an A/R document, then Application Details sub-form (DD.531.01) give drilldown 

inquiry on all the EFT “Groups” that have been collected against this one 

document. 


AR-EFT – option to filter invoices by due date, discount date, document 

type 

Additional filter options have been added (green), to allow filtering of invoices by their 

due date, discount date and document type. For the dates, a future date can be set, and all 

invoices with a due or discount date prior to that date can be displayed. Now the 

document, discount and due dates are displayed for each invoice (red). 


Lockbox Processing – support for Credit Memos and Discounts (Lockbox 

module) 

Credit Memos can now be applied and discounts taken (if appropriate) as per an entry in 

the import file. The Lockbox Processing mapping needs to include these new fields if 

used – use File Formats (DD.300.00), Lockbox Processing tab. 


Lockbox Processing – multi-line file support (Lockbox module) 

Multi-line files lockbox import files have “check’ records followed by invoice records. 

One standard file type that is used is called BAI. Lockbox now supports this type of file 

– the Wells Fargo BAI2 format comes with eBanking and any other multi-line file can be 

easily added through a custom stored procedure. 


Lockbox Processing – split check support (Lockbox module) 

In some cases checks will be paying invoices that belong to different SL customers. 

Because a SL Payment Application batch requires a payment record by customer, the 

payment amount per customer must be determined. When the Lockbox Workbench 

locates records in the Payments grid where the check number and amount are the same, 

yet the SL customers are different, a new Payment Customer Check (DD.542.00) screen 

is used to divvy up the check amount amongst the SL customers. 


Lockbox – enhanced duplicate payment number checking 

When the A/R Payment Application batch is created, checking is done to insure that 

duplicate payment numbers are not being created for a customer. A message is given if 

some are found and the process is stopped. The Duplicate Ref Nbr column has been 

added that will be marked for those payments that have the same number in an existing 

SL batch for this customer. They can be edited here, and the process can continue. 


Lockbox Processing – Payment Application Batch - Deposit Date can be 

specified (Lockbox module) 

Previously, when creating the A/R Payment Application batch, the deposit date was 

automatically set to the SL Business Date. Now it is displayed and can be modified (it 

defaults to the SL Business Date). 

F1 Help (all modules) 

Now throughout eBanking, the F1 Help key will display the full product documentation 

(the User Guide and Reference manual – this file is found in the 

eBanking\Documentation folder). To view a .PDF, the Adobe Acrobat Reader must be 

installed. This free reader can be downloaded from 

http://www.adobe.com/products/acrobat/readstep2.html. 


*Notes to Implementers 

Installation/Upgrade Notes (These steps are VERY IMPORTANT, and must 

be followed.) 

1) AP-EFT/Wire only - Because of this new functionality, ALL installations of eBanking 

that use the AP-EFT or new Wire Transfer Plus module MUST install BSL 

customizations. Therefore Dynamics SL Customization Manager is now a 

required module (AP-EFT and/or Wire Transfer Plus only). These customizations 

affect AP Voucher and Adjustment Entry (03.010.00), Quick Voucher and Pre-Payment 

Entry (03.020.00), AP Document Maintenance (03.250.00) and AP Recurring Voucher 

Maintenance (03.260.00). See the installation document for details on how to do this 

install. 

However, unlike in previous versions, even though the customizations are in the common 

system database, the eBanking tables DO NOT have to be installed on all application dbs 

associated with the system db. Installation is only required on the app dbs that need to 

use eBanking. 

2) AP/AR-EFT only. A new field: Originating DFI Identification has been added. 

This field is used in the NACHA file and in most cases the left-most 8 digits of the 

company’s transit routing number is used. However, in rare instances it needs to be a 

different value. This new field MUST be reviewed in both eBanking Setup (DD.950.00, 

AP/AR EFT/Wire Defaults tab, Company Paying/Cash Defaults tab) and in Company 

Paying Accounts (DD.260.00, AP/AR EFT/Wire tab, Company/Batch tab). Please 

confirm with your bank as to the correct value, and then update your system (in the two 

places noted above). 

3) AP-EFT/Wire. All A/P Payment Selection batches that are to be paid via EFT 

and/or Wire MUST be processed and paid before v8 of eBanking is implemented. 

Voucher batches that have been entered and/or released prior to Payment Selection will 

be updated (APDoc.eStatus) by the upgrade process described in 3) below. 

4) AP-EFT/AR-EFT/Wire. Review the File Formats (DD.300.00) application for 

EFT/Wire formats that will be used. Check only those formats that are to be used. 

Additionally, go to the Transaction Types application (DD.301.00) for each format 

and be sure ONLY the transaction types that you need are selected. Also, check the 

vendor/customer default types as appropriate. For existing Vendors to be updated 

correctly, you must de-select and then re-select any transaction types that will be 

used. As you leave the screen (as you are saving) Message24164 will appear (answer 

Yes) and then all your existing Vendors will be updated with their set of correct 

transaction types. In addition any vouchers not yet selected for payment will have their 

“Pay By” method updated with the Vendor’s default method. 

5) Wire/Positive Pay – Customized formats – This applies to any Crystal report that 

has been customized to create a format (generally placed in the Usr_Rpts folder). With 

v8 the filter condition on the report no longer uses “ComputerName”. So in Crystal 

Designer, use the menu option - Report, Selection Formula, Record… to edit your filter 

and remove the {XDDFile_Wrk.ComputerName} = RIPARAM("ComputerName") part 


of the filter. With v8, regardless of computername, any user can access the working table 

records. 

6) AP-EFT/Wire - FYI only - With v8 of eBanking a trigger has been added to the 

APDoc table. Its purpose is to correctly set the “Pay By” code for a voucher when it is 

added via a process outside the A/P data entry screens (e.g. Project Controller T&E, 

Purchasing PO Receipt, web apps, etc.) This trigger is applied as part of eBanking’s 

database maintenance process. 

7) All Modules – Bank Communications has been removed. SL7 only. Builtin 

serial communications has been removed from the product (SL7 only). This was 

removed since modems are rarely used for bank communications (having been replaced 

by web protocols - https or ftp). If modem communications is still required, then 

eBanking’s User Communications can call the Windows Hyperterminal application. 

8) AR-EFT only – New with eBanking v8 – the main menu application “Select 

Invoices for EFT” has been removed. It is now part of the AR – Create and 

Send/Receive Files (DD.540.00). So, if using the eBanking Security feature, you must 

now designate which users can Create and Send an AR-EFT file and which can Select 

invoices for payment. 

9) All modules – Periods to retain eBanking Files. This is a new option for each 

module (eBanking Setup – DD.950.00). eBanking uses working tables that store data and 

with this new option, during the “Keep” process, older records are removed from these 

tables. The minimum setting is 2 periods (only records 2 periods and older will be 

removed), but can be set higher if more historical data needs to be saved. The reason to 

keep historical data would simply be to view older eBanking files, print their audit 

reports, etc. Note that the eBanking files that are sent to the bank (ACH, Wire, Pos Pay, 

etc.) are NOT removed during this “clean-up” process. 

10) Lockbox – A part of the old AR – Create and Send Receive Files (DD.540.00) has 

been moved to a new .exe (the Retrieve and Import lockbox files). So be sure to give 

Lockbox users SL Access Rights to this new .exe – Retrieve and Import Lockbox 

Files (DD.541.00).

Summary of Changes Upgrading eBanking to v8.6 - Sandler*Kahne ...

Create successful ePaper yourself

Delete template?

Save as template?