eBanking Suite for Microsoft Dynamics AX 2012 - Sandler*Kahne ...
eBanking Suite for Microsoft Dynamics AX 2012 - Sandler*Kahne ...
eBanking Suite for Microsoft Dynamics AX 2012 - Sandler*Kahne ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
www.sksoft.com<strong>eBanking</strong> <strong>Suite</strong><strong>for</strong><strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong> <strong>2012</strong>Updated: May 25, 2015 Page 1
<strong>eBanking</strong> <strong>Suite</strong> parameters ..................................................................................................................... 18<strong>AX</strong> License In<strong>for</strong>mation ........................................................................................................................... 19E. Un-Install ................................................................................................................................................. 20Introduction ............................................................................................................................................ 20Remove the <strong>eBanking</strong> <strong>Suite</strong> <strong>AX</strong> Objects (SKS <strong>eBanking</strong> Model) ............................................................. 20Uninstall the <strong>eBanking</strong> Help files ............................................................................................................ 20Remove the Client Assembly .................................................................................................................. 20Remove the EFT+ email templates (v5 and later) ................................................................................... 20F. Backup & Restore .................................................................................................................................... 21G. Revision/Enhancement History .............................................................................................................. 21Appendix A – Setting up <strong>eBanking</strong> Security ................................................................................................ 52Security layers ......................................................................................................................................... 52System tools ............................................................................................................................................ 52Setting up <strong>eBanking</strong> security ................................................................................................................... 52Duties ...................................................................................................................................................... 52Duties by module: ............................................................................................................................... 52Roles and duties: ..................................................................................................................................... 53The duties and roles assigned by <strong>eBanking</strong>: ....................................................................................... 53Positive Pay ......................................................................................................................................... 53Electronic Bank Reconciliation ............................................................................................................ 53Lockbox (AR eSettlement w/Lockbox) ................................................................................................ 54APEFT Plus! .......................................................................................................................................... 54AREFT Plus! ......................................................................................................................................... 55Privileges ................................................................................................................................................. 55Appendix B – Organization hierarchies in <strong>eBanking</strong> ................................................................................... 56Overview ................................................................................................................................................. 56<strong>eBanking</strong> support .................................................................................................................................... 56Positive Pay ......................................................................................................................................... 57Electronic Bank Reconciliation ............................................................................................................ 57AR eSettlement w/Lockbox, APEFT Plus!, AREFT Plus! ....................................................................... 57Setting up organizations ......................................................................................................................... 57Security ................................................................................................................................................... 58Updated: May 25, 2015 Page 3
Setup data ............................................................................................................................................... 58Appendix C – Virtual Company Setup ......................................................................................................... 59Positive Pay ......................................................................................................................................... 59Electronic Bank Reconciliation ............................................................................................................ 59AR eSettlement w/Lockbox ................................................................................................................. 60APEFT Plus! & AREFT Plus! .................................................................................................................. 60Notes to existing customers – switching to virtual companies .......................................................... 60Updated: May 25, 2015 Page 4
* If you are using Business Ready Licensing, the required Bank, Accounts Payable, AccountsReceivable and General Ledger modules are included in Business Essentials as part of theFinancials I license.Note on Custom Positive Pay <strong>for</strong>matsThe <strong>for</strong>mats we provide (at no charge) are designed per the bank’s specification. Our goal is to buildup a library that can be shared with the whole <strong>AX</strong> community. When a <strong>for</strong>mat request is site orimplementation specific we can provide a quote to create that customized <strong>for</strong>mat.Note on Custom APEFT Plus! And AREFT Plus! <strong>for</strong>matsUnlike Positive Pay, EFT+ <strong>for</strong>mats are much more complex to develop. If a particular <strong>for</strong>mat isrequired and does not exist in our library we will develop it <strong>for</strong> a fixed amount. This should havebeen identified in the sales process. If not please contact SK sales (sales@sksoft.com) to start theprocess of reviewing the file specification and determining pricing. We generally can deliver a new<strong>for</strong>mat within 30 days of obtaining the file specification.B. Installation/SetupOverviewThe <strong>eBanking</strong> <strong>Suite</strong> installation includes both a client and server install. For the server install,the instructions vary based on whether this is an initial install, adding on to an existing install orupgrading from an <strong>AX</strong> 2009 installation with the <strong>eBanking</strong> <strong>Suite</strong> already installed.Install OverviewCopy files to your systemServer Installo Install the server assemblyo Install pre-upgrade code on source system (if upgrading from an <strong>AX</strong> 2009install of <strong>eBanking</strong>)o Install the SKGS <strong>eBanking</strong> Model (RTM, FP-CU3, FP-CU4, FP-CU5, R2, R2-CU6, R2-CU7, R3 or R3-CU8)o Import File Formats (<strong>for</strong> Positive Pay and APEFT/AREFT Plus!)Client Install (each client installation)o Install the client assemblyHelp InstalloInstall the <strong>AX</strong> <strong>2012</strong> helpSetup Security/PermissionsEnter unlocking keysIf adding a New Positive Pay <strong>for</strong>mat – see the section at the bottom of this documentUpdated: May 25, 2015 Page 6
Copy Files to your System1. Double click the installation file <strong>AX</strong><strong>eBanking</strong>-7-x-x-6x.exe.2. Unzip to folder C:\SKS_<strong>eBanking</strong>Install (or any other folder of your choice)3. Click Unzip – the following files will be copied to your system:FileFolderInstallation DocsClient FilesServer FilesFormatsHelp FilesSample FilesC:\SKS_<strong>eBanking</strong>InstallC:\SKS_<strong>eBanking</strong>Install\ClientC:\SKS_<strong>eBanking</strong>Install\ServerC:\SKS_<strong>eBanking</strong>Install\FormatsEDI820LayoutsEFT Addenda (US federal tax payments)Holidays (banking holidays)EFT+ <strong>for</strong>matsPositive Pay <strong>for</strong>matsLockbox <strong>for</strong>matsC:\SKS_<strong>eBanking</strong>Install\HelpC:\SKS_<strong>eBanking</strong>Install\Sample FileseBankRecLockboxUtilities (ftp scripts, batch files)Server InstallNote: All <strong>eBanking</strong> <strong>Suite</strong> AOT objects are prefixed with SKS_ and then a module prefix followed by anunderscore (ex: SKS_PP_ or SKS_BR_. Some of the original Positive Pay objects were leveraged by other<strong>eBanking</strong> modules and the objects were not renamed. Since objects were not renamed, some objectsthat are used by multiple <strong>eBanking</strong> modules are prefixed with SKS_PP_ (ex: SKS_PP_Setup is used by allmodules).Upgrading from an <strong>AX</strong>2009 installation of <strong>eBanking</strong>Please contact <strong>AX</strong> support (axsupport@sksoft.com) be<strong>for</strong>e proceeding.Install the SKGS <strong>eBanking</strong> Module on a New <strong>AX</strong> <strong>2012</strong> Install (<strong>eBanking</strong> is being installed atthe same time as <strong>AX</strong> <strong>2012</strong> is first being installed)NOTE: The order of these steps is CRITICAL!1. Client files - Copy SKS.Common.dll, SKS.Common.R2.dll or SKS.Common.R3.dll from theClient folder of your SKS_<strong>eBanking</strong> install to this folder on your server: C:\Program Files(x86)\<strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong>\60\Client\Bin directory. SKS.Common.dll is used with <strong>AX</strong><strong>2012</strong> RTM, FP-CUx. SKS.Common.R2.dll is used with <strong>AX</strong> <strong>2012</strong> R2, R2-CUx.SKS.Commond.R3.dll is used with <strong>AX</strong> <strong>2012</strong> R3-CUx.Updated: May 25, 2015 Page 7
9. Re-start the AOS (this allows <strong>AX</strong> to recognize the model update).10. Open <strong>AX</strong> <strong>2012</strong>.11. You will be prompted that the model store has been modified. Choose the Skip option and clickthe OK button.12. Open the SKS_<strong>eBanking</strong>_<strong>Suite</strong> project. Review the objects in the <strong>AX</strong> node and determine ifmerging is necessary on your system due to Cumulative updates or customizations.a) Right-click each object in the <strong>AX</strong> node and choose Compare.b) <strong>eBanking</strong> is installed on the ISV layer. You’ll need to compare the isv layer object to theother layers of your installation. These layers are typically sys, syp or fpk depending onwhat version of <strong>AX</strong> you are running.c) Click the Compare button.d) The lower part of the screen displays differences between the two layers. Click eachnode on the left side and review the code that displays on the right side. Use the leftand right arrows to add or remove changes.e) After changes are made close the compare window.f) Right-click the object and choose Compile.13. Starting with <strong>eBanking</strong> v7.3, the SKS Advanced Bank Reconciliation Server is no longer used (an<strong>AX</strong> batch job is now used to import Bank statement files). The service can be uninstalled fromPrograms and Features (SKS Advanced Bank Reconciliation Service <strong>for</strong> <strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong>)14. If upgrading from an <strong>eBanking</strong> build prior to version 5.3.0.6x:Method changes to table objects were moved to event handlers. If <strong>eBanking</strong> waspreviously installed and a merge was per<strong>for</strong>med on a layer above the ISV layer, somemerged code may need to be removed. <strong>eBanking</strong> specific code was removed from thetable methods and replaced with event handlers. Please review the following tableobjects and remove previously merged code if necessary: BankChequeTable, CustTrans,LedgerJournalTable, LedgerJournalTrans and WMSBillOfLadingOrder.15. If upgrading from a prior version of <strong>eBanking</strong> and upgrading to a different <strong>Microsoft</strong> <strong>Dynamics</strong><strong>AX</strong> version:a) In the AOT go to Data Dictionary > Base Enumsb) Locate HierarchyPurposec) Right click SKS_PPControl and choose propertiesd) If the EnumValue is different than the EnumValue noted prior to installation, you willneed to follow the directions below to modify the code. The code will upgrade any dataassociated with the prior EnumValue to the new EnumValue.e) Right click SKS_BRControl and choose properties.f) If the EnumValue is different than the EnumValue noted prior to installation, you willneed to follow the directions below to modify the code. The code will upgrade any dataassociated with the prior EnumValue to the new EnumValue.Updated: May 25, 2015 Page 13
Once this is updated and the Windows indexing process has completed (Control Panel >Indexing Options), the <strong>eBanking</strong> <strong>Suite</strong> help should be available.Import Positive Pay File Formats (only if using Positive Pay)1. Open <strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong> <strong>2012</strong>.2. Go to <strong>eBanking</strong> <strong>Suite</strong> -> Setup -> <strong>eBanking</strong> <strong>Suite</strong> parameters -> Modules tab.3. In the Positive Pay group, click the Import File Formats button.4. Enter or browse to C:\SKS_<strong>eBanking</strong>Install\Formats\SKS_PP_FileFormats.csv.5. Click OK.6. The data will be imported. An Infolog message will display showing the number of recordsAdded, Updated and Deleted.7. Click Close on the message.Import EFT Plus! Formats (only if using APEFT or AREFT Plus!)1. Open <strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong> <strong>2012</strong>.2. Go to <strong>eBanking</strong> <strong>Suite</strong> -> Setup -> <strong>eBanking</strong> <strong>Suite</strong> parameters -> Modules tab.3. In the EFT+ group, click the Import EFT+ File Formats… button.4. Enter or browse to C:\SKS_<strong>eBanking</strong>Install\Formats\SKS_EFT_FileFormats.csv.5. Click OK.6. The data will be imported. An Infolog message will display showing the number of recordsadded, updated and deleted.7. Click Close on the message.Import EFT Plus! EDI820 Layouts (only if using APEFT Plus! with CTX)1. Open <strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong> <strong>2012</strong>.2. Go to <strong>eBanking</strong> <strong>Suite</strong> -> File <strong>for</strong>mats -> EFT+ file <strong>for</strong>mats -> Setup EDI 820.3. Click the Import layout button.4. Enter or browse to the C:\SKS_<strong>eBanking</strong>Install\Formats\EDI820Layouts folder.5. Select the EDI 820 layout that you need. e.g. EDI820_US_ACH_CTX_STP.csv6. Click OK.7. The data will be imported. An Infolog message will display showing the number of recordsadded.8. Click Close on the message.9. Repeat <strong>for</strong> other EDI layouts that you need.Setup Security/Permissions1. See Appendix A – Setting up <strong>eBanking</strong> SecurityOrganization Hierarchies1. See Appendix B - Organization hierarchies in <strong>eBanking</strong>Updated: May 25, 2015 Page 16
Virtual Companies1. See Appendix C - Virtual CompaniesUpdated: May 25, 2015 Page 17
C. Unlocking KeysYour <strong>AX</strong> reseller will provide you with an unlocking key <strong>for</strong> the <strong>eBanking</strong> <strong>Suite</strong> (or you can call or emailthe registration department as shown on the <strong>eBanking</strong> <strong>Suite</strong> parameters screen). The software is in“demo” mode without an unlocking key. When in demo mode, files are restricted to 3 records (Pos Pay/APEFT+/AREFT+ – 3 records in the output file, eBank Rec /Lockbox – 3 records processed from the inputfile).The unlocking key is based on the <strong>AX</strong> License Serial number (red arrows), total number of <strong>AX</strong> Users(Functional + Enterprise + Server) (green arrows) and the <strong>eBanking</strong> <strong>Suite</strong> Product version (blue arrow) aswell as the combination of <strong>eBanking</strong> modules and EFT+ <strong>for</strong>mats that have been licensed. Below you cansee where the Serial Number and <strong>AX</strong> Authorized Users are displayed in <strong>eBanking</strong> Setup parameters andin the <strong>AX</strong> License In<strong>for</strong>mation screen.Be sure to ONLY check the <strong>eBanking</strong> modules that you are licensing.<strong>eBanking</strong> <strong>Suite</strong> parametersNOTE: If any of the above bolded values change a new unlocking key may be required. The <strong>eBanking</strong><strong>Suite</strong> is licensed based on tiers of the Enterprise + Functional + Server user counts (1-25, 26-75, 76-299and 300+). If the user count changes and moves to another tier a new unlocking key is required – andthis will require a license upgrade.Updated: May 25, 2015 Page 18
NOTE: You can use unlicensed modules in “demo” mode by simply checking the “Active” option on themodules tab.<strong>AX</strong> License In<strong>for</strong>mationThe <strong>AX</strong> Serial number and Users count are also found on the License In<strong>for</strong>mation screen. They are foundunder the <strong>AX</strong> Administration Module | Setup | Licensing | License In<strong>for</strong>mation screen (once the licensefile has been loaded, the Access Licenses tab shows the counts by types of users):Updated: May 25, 2015 Page 19
E. Un-InstallIntroductionThis section discusses how to un-install the <strong>Dynamics</strong> AOT objects that belong to the <strong>eBanking</strong> <strong>Suite</strong>feature.1. Remove the SKS <strong>eBanking</strong> Model.2. Remove the Help files.3. Remove the client assembly.Remove the <strong>eBanking</strong> <strong>Suite</strong> <strong>AX</strong> Objects (SKS <strong>eBanking</strong> Model)1. Warning! Per<strong>for</strong>ming these steps will remove all <strong>eBanking</strong> <strong>Suite</strong> data.2. Open a command prompt as Administrator.3. CD to C:\Program Files\<strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong>\60\ManagementUtilities.4. Run the following command (your path to the model file may be slightly different):Axutil listDelete each SKS model listed using the following command:Axutil delete /model:SKS.xxxxx5. This removes the <strong>eBanking</strong> suite code.6. Re-start the AOS (this allows <strong>AX</strong> to recognize the model removal).7. Start <strong>AX</strong> <strong>2012</strong>.8. You will be prompted that the model store has been modified. Choose Compile andsynchronize.Uninstall the <strong>eBanking</strong> Help files1. Use Control Panel | Add/Remove Programs to uninstall “SKGS <strong>eBanking</strong> – <strong>AX</strong><strong>2012</strong> Help – vx.x.x”Remove the Client Assembly1. Per<strong>for</strong>m the following steps on each Client workstation where the <strong>eBanking</strong> <strong>Suite</strong> was originallyinstalled.2. Go to the path where the client assembly was installed. It should be something similar toC:\Program Files (x86)\<strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong>\60\Client\Bin.3. Locate SKS.Common.dll (used with RTM or FPCUxx) or SKS.Common.R2.dll (used with R2 or R2-CUx) or SKS.Common.R3.dll (used with R3) and delete it.4. Repeat steps 1-3 above on the Server.Remove the EFT+ email templates (v5 and later)1. Go to Basic > Setup > E-mail templates.2. Delete the four templates that have an E-mail ID that starts with SKS_EFT.Updated: May 25, 2015 Page 20
F. Backup & RestoreThe SKS-<strong>eBanking</strong> <strong>Suite</strong> is written as a <strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong>–based application. The <strong>eBanking</strong> <strong>Suite</strong>fields and tables will be treated the same as any other data and will be backed up as part of the core<strong>Microsoft</strong> <strong>Dynamics</strong> <strong>AX</strong> backup process.G. Revision/Enhancement HistoryNote: v6 and greater includes AREFT+, v5 does not* (starred) items are new features or product enhancementsRevision 7.5.1 – 5/25/2015 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a newunlocking key)eBankReco Un-matched Transactions – correct label on Create GL button to “Select a parsing rulegroup id” (#3446)o Import – fix ZBA bug on concentration transactions – were being matched improperly(#3463)o *Import – create GL journal entries in a designated company (#3483)AR eSettlement w/Lockboxo Import – field number (order) is ignored <strong>for</strong> a LB comma delimited file (#3381)o Import – BAI2 file that only contains 1, 2 and 9 records is not properly imported (#3390)o Import – “already marked <strong>for</strong> settlement” transactions are not recognized with settlingwith “oldest outstanding” method (#3425)o Import - System.NullReferenceException <strong>for</strong> a CSV file that is imported that utilizes thedefault customer setting (#3464)o Workbench - incorrect lockbox settlement checkmark color when "sum like referencenumbers within same payment" is turned on (#3393)o Workbench – reassign payment uses wrong customer name (#3422)o Workbench – need to accommodate computers with lower screen resolution (#3468)o Auto-Process - does not add a file history when auto-create payment journal fails due toledger dimension validation (#3477)o A/R Journal creation – description shows "eSettlement/lockbox journal %1" in thejournal line if no description is mapped or added in workbench (#3456o A/R Journal creation - exchange rate is not correctly moved to the payment journal(#3482)o A/R Journal creation - dimensions are blank <strong>for</strong> payments settled against invoices thatappear in the errors grid in workbench (#3245)Updated: May 25, 2015 Page 21
o A/R Journal creation - unable to create payment journal due to suspended financialdimension generates Lockbox file history Action "A/R payment journal post failed" eventhough journal wasn't posted (#3505)o Bank Account - changing lockbox setup options does not update "default from setup"lockbox bank account options (#3490)o File Formats - SKS_LB_FileFormatMaintain privilege has incorrect settings (#3455)o <strong>eBanking</strong> Parameters – auto-credit account parameters grid does not populate correctly(#3481)AP EFT+o A/P Method of Payment – <strong>eBanking</strong>-EFT+ validation is executing <strong>for</strong> non-EFT+methods of payment (#3437)o Inbound processing - Payment status in an AP Payment journal is not set to Rejectedwhen Transaction NACK is processed and Inbound transaction status actions Paymentjournal line status is set to Rejected (#3449)o Inbound processing - AP Payment Journal set to auto-post linked to an inbound file ismarked as posted in EFT+ file history but the payment journal remains open (#3451)o Inbound processing - Receive "Cannot edit a record in ACH sequence(SKS_EFT_ACHSequence). The record has never been selected." in EFT Inbound batchjob when EFT file entry is Transmitted but no payments are in the file (#3466)o Inbound processing - EFT Inbound batch job stuck in EXECUTING status when inboundfile contains a Rejected transaction and Post journal on file complete is on (#3467)o <strong>eBanking</strong> Parameters - Fixed Field Code lookups not being linked to Vendors on CSVImport (#3453)o <strong>eBanking</strong> Parameters- Limit text properties set incorrectly – affected data entry fieldlengths (#3486)Generalo CoreFtpUpload.bat has a comment that refers to PosPay setup. It should not refer toPosPay setup at all as these values come from the Communications <strong>for</strong>m. (#3445)o Build - Restore Missing Method: LedgerJournalTansCustPaym > Data sources >LedgerjournalTrans > Fields > MarkedInvoice > modified > updatePaymnetTerms()(#3452)o Permission properties - Access levels Updated to "Delete" – to allow user access tocertain <strong>for</strong>ms (#3473)Updated: May 25, 2015 Page 22
Revision 7.4.2 – 3/31/2015 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a newunlocking key)Positive PayoCreate/Send – bank accounts with the PosPay <strong>for</strong>mat removed still have checks inthe select/view sub-screen (#3406)eBankRecoooooooUn-matched Transactions – rename the “All” radio button to “All pre-matched andun-matched” (#3378)*File import - add support <strong>for</strong> zero balance accounts (ZBA) so that BR files withsingle line deposits to concentration accounts can be "swept" from theirappropriate ZBA accounts (#3436)File import – when moving a file to the archive folder files without a fileextension are having their name changed. Fixed (#2889)File import - receiving "GL auto-posting failed" <strong>for</strong> companies that have autopostingdisabled. (#3275)GL Mapping rule - receiving "Cannot update cross-company" when changingfrom a mapping to matching rule and using multiple companies and the bankaccount is in a different company(#3395)File import - failure when cross company and 03 record is missing an end balancecode type (#3358)File Import - bank accounts not set up in Cash and Bank and <strong>eBanking</strong> causesfailure of other bank accounts to load. Fixed (#3426)AR eSettlement w/Lockboxo*File Formats – added support to define the 5 (batch header) record and 7 (batchtrailer) record in Field Layout <strong>for</strong> Lockbox file <strong>for</strong>mats (#3306)o File Formats - renamed the "Verify bank account number" label to "Verify lockboxaccount number" (#3307)o Bank Account – option is re-labeled to “Automatic posting” (#3341)o Workbench - move to payments grid does not move the amount to settle anddiscount amount when the invoice accepts a discount (#1419)o Workbench - lockbox takes discount amount even if past the due date <strong>for</strong>discount. Fixed (#1886)o Workbench – added support to modify financial dimensions on the payment.Now Accountant role can view and AR Payments Clerk can open and modify.(#2754)Updated: May 25, 2015 Page 23
o Workbench – discounts do not consider the grace period specified <strong>for</strong> the Methodof payment. Fixed (#3191)o Workbench - discounts are not taken when the check date is not included in the 6records of Lockbox files but the deposit date in the 5 record is within thediscount date (#3202)o Workbench – dimension code re-written to be without service dependency (#3283)o File Import - when selecting a file <strong>for</strong> a bank acct and two paths referenced havethe same “like” characters (e.g. Lockbox and Lockbox1) this message would bepresented "This file is already in eSettlement/lockbox Journal (xxx). You mustdelete the eSettlement/lockbox Journal to re-import this file." Fixed (#3313)o File Formats - file <strong>for</strong>mats should not be allowed to be deleted if they are in usein a lockbox back account (#3339)o Matching Rules – do not allow deletion if in use (#3340)o Workbench – decimal positions in payment amounts in CSV files were beingignored. Fixed (#3380)o Create Payment Journal – “one voucher setting” <strong>for</strong> journal names are not beinghonored. Fixed (#3387)o Workbench - payments should use the customer's default financial dimensionswhen the payment doesn't settle an invoice and the “default dimensions frominvoice” option is selected (#3250)o Workbench – lockbox totals are incorrect when using “split by batch” option.Fixed (#3418)o Workbench - split payments with settlement amount not mapped does not splitproperly. Fixed (#3421)o Workbench – auto-credits not being created when importing externalsettlements. Fixed (#3431)o File Formats - EDI820 and EDI823 <strong>for</strong>mats need decimal separator enabled(#3434)AP EFT+o *File <strong>for</strong>mats – support added <strong>for</strong> EFT+ control files (#3346)o Create/Send – posted payment reversal - only one invoice balance is reinstatedwhen reverse an AP EFT payment that settled more than one invoice. Fixed(#3361)o Create/Send – journal posting - completing an AP EFT file and automaticallyposting the AP payment journal causes other unprocessed AP EFT payments inthe AP journal to be transferred to a new AP Payment Journal which has notbeen sent to EFT (#3296)o <strong>eBanking</strong> <strong>Suite</strong> Parameters - Vendor <strong>eBanking</strong> Details “maintain” privilege alsoUpdated: May 25, 2015 Page 24
AP EFT+o Create and Send - Addenda file not printing vendor name in the file (#3175)o Addenda Configuration - YYYYMMDD <strong>for</strong>mat <strong>for</strong> dates in addenda switches backto YYMMDD on save (#3309)o Create and Send – ACH – block fill not working correctly when over 10 payments(#3322)o Bank Account – AP EFT+ - block fill field disappears from screen if “Use defaults” buttonis checked or unchecked (#3320)AR EFT+o <strong>AX</strong> Payment Journal – Added Change EFT+ state – send file now option (#3318)Generalo Registration/unlocking key code moved to server side (#3292)o Support <strong>for</strong> R3/CU8 (#3324)Revision 7.2.0 – 11/17/2014 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a newunlocking key)eBankReco GL mapping rules – allow matching <strong>for</strong> txn types when the mapping rule fails to find avalue in the lookup screen (#2638)o File Import – when the bank file includes time in a date field, remove the time value andretain the date(#2952)AR eSettlement w/Lockboxo Workbench – Support ability to have unmatched negative settlements break into aseparate negative payment record in good payments grid (#3255)Updated: May 25, 2015 Page 26
AP EFT+o Code Lookup - <strong>for</strong>mat group should be validated against valid <strong>for</strong>mat groups (#2987)o Create and Send – under certain circumstances the Next Action combobox is disabledand set to Select (#3062)o Character Replacement groups added (#3169)o Create and Send – ACH file <strong>for</strong>mat used incorrect service class code when a change wasmade to the vendor bank account. (#3179)o Create and Send - Paying a vender into two different vendor bank accounts, results inthe beneficiary in<strong>for</strong>mation from the first account appearing on subsequent transactionlines (#3231)o Vendor <strong>eBanking</strong> Details/Additional Data - 'A field requires additional data' warningoccurring when trying to close Additional Data (#3241)Revision 7.1.1 – 10/21/2014 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a newunlocking key)eBankReco Imported Statement History - UI cleanup - grid width, grid row shading, multi-select,status bar (#3100)o File Formats – support <strong>for</strong> MT940 (#3107)o Click-n-Match - not showing transactions in the top or bottom grid when the bankaccount id contains a comma (#3160)o Matching - eBankRec not auto matching when bank account id contains a comma(#3187)o Parse rules - added ability to trim leading zero from parsed values (#3208)AR eSettlement w/Lockboxo Process Files – Added a column <strong>for</strong> the physical file name associated with a particularlockbox journal. (#2464)o Workbench - LB Batch total doubles when records <strong>for</strong> check paying +1 INV appear inpayments and payments with errors (non-BAI2) (#2961)o Workbench - Posting date not defaulting correctly in Create Payment Journal dialog(#3014)o Workbench - Receive error when attempting to insert a record across companies intothe errors grid (#3092)o File import - Settlement amount is incorrect in BAI2 files with multiple 4 records settlingthe same invoice within the same check (#3104)o Formats – Symcor added (Canada) (#3131)o Workbench - Import a description from a lockbox file and enable it <strong>for</strong> edit within theworkbench <strong>for</strong>m (#3159)o File Formats - Added credit settlement and negative payment indicators to configurelayouts more precisely (#3162Updated: May 25, 2015 Page 27
oooProcess Files - added option to filter lockbox journals – completed, not completed(#103)Setup – Bank Account – added option to create individual payment lines <strong>for</strong> each invoicebeing settled (#3192)File Import - AutoCredit fails when a credit invoice reference is the same as the invoicenumber (#3212)AP EFT+o Communications - <strong>for</strong>m allows Inbound direction <strong>for</strong> modules that don’t support it(#3093)o Inbound File - Add status action has incorrect label on <strong>for</strong>m (#3095)o Inbound File Groups - Change error message that displays when changing Action (#3098)o <strong>eBanking</strong> Parameters – AP EFT+ Setup – options are cut off (#3099)o Communications – after selecting a Batch Job ID, the communications ID changes(#3120)o Create and Send File - Path and file name fields too short and not scrollable on EFT+create/send <strong>for</strong>m. Can't see all data (#3127)o AP Payment Journal - Able to delete the AP Payment Journal that contains paymentssent to EFT that haven't been processed - <strong>AX</strong> <strong>2012</strong> R3 (#3137)Revision 7.0.0 – 9/16/2014 (NOTE: an EB pre-6.7 to 6.7 or greater upgrade requires a newunlocking key)eBankReco Automation features – auto-create statements, auto-post GL journal, auto-reconcilestatement (#3040)AR eSettlement w/Lockboxo File Formats – correct spelling on EDI column (#3010)AP EFT+o Inbound (return) file support (#3039)o Automation features – auto-create/send, auto-post journal, delayed payment rejectionreversal (#3041)Generalo <strong>eBanking</strong> setup parameters – change default purge months from 2 to 24 (#3037)Revision 6.11.2 – 8/19/2014 (NOTE: an EB pre-6.7 to 6.10 upgrade requires a new unlockingkey)Updated: May 25, 2015 Page 28
Positive Payo Formats - ARP Register field 7 optional description field data no comma allowed (#2846)o Audit report - Positive pay audit report doesn't include the positive pay file number andGrand Total label is on the left side of the page but its ':' is on the right side of the page(#1883)o Create/Send - Checks From option in Select/View Checks does not filter records in thegrid when deselecting a check with a date that is less than 60 days ago (#1244)eBankReco Service – AB.Service shows running but is not processing folders after loss of access to aremote folder (#2822)AR eSettlement w/Lockboxo Import - Lockbox CSV files assign values from files out of order (#3005)o Workbench - Reassigning a payment causes the invoice number to be added to thenewly created payment record in the AR journal (#3004)o Support added to process fees (#2960)o Support <strong>for</strong> EDI820, EDI823 file <strong>for</strong>mats (#2959)o Support <strong>for</strong> multiple lockbox file <strong>for</strong>mats per bank account (#2958)o Support <strong>for</strong> multiple bank accounts within the same lockbox file (#2576)o Workbench – Cannot move invoice to good grid because of incorrect "invoice found <strong>for</strong>wrong customer" error (#2953)AP EFT+o Formats – Wells Fargo PMS – Receiving party bank ID type was not recognized (#2955)o Formats - US-Chase-SUA-28 field 7 vendor bank account pulling from Chase Bankaccount and not vendor (#2832)o Formats - US-CITI-CDFF FT – writing file - payment spec requires field 4 (Value date) andfield settings <strong>for</strong> vendors with SWIFT codes are not correct (#2831)o Create/Send – MAL - Contact name / e-mail is defaulting fax and phone number as wellas email (#2829)o Vendor <strong>eBanking</strong> Details – Right-click on vendor address or MAL email - could notprocess the lookup table value on the Args instance. The table 'LogisticsLocation' doesnot exist as a root FormDataSource <strong>for</strong> the <strong>for</strong>m 'DirPartyTable' (#2828)o Vendor <strong>eBanking</strong> Details – more descriptive messages <strong>for</strong> required fields (#529)o Create/Send – failed emails will now retry 3 times instead of 1. (#2751)Revision 6.10.303 – 7/25/2014 (NOTE: an EB pre-6.7 to 6.10 upgrade requires a new unlockingkey)AP EFT+o Setup – EFT+ - code lookups (#2885)o Vendors – account approval changes (#2886)Updated: May 25, 2015 Page 29
o Bank Accounts – account approval changes (#2886)o Setup – EFT+ Formats - Citibank – Ecuador <strong>for</strong>mat added (#2887)o Setup – EFT+ Formats – <strong>for</strong>mat grouping feature (#2888)Revision 6.10.1 – 5/30/2014 (NOTE: an EB pre-6.7 to 6.10 upgrade requires a new unlockingkey)Positive Payo File Formats - positive pay <strong>for</strong>mat able to be deselected while in use by Bank Accountand defaulted in parameters (#2249)o Bank Accounts – added support <strong>for</strong> archive option and path (#2391)eBankReco Imported file details – cannot filter the grid on description field (#2725)AR eSettlement w/Lockboxo Workbench – error grid invoice lookup taking too long to retrieve invoice list (#2416)o Bank Accounts – added support <strong>for</strong> archive option and path (#2391)o Workbench – creating/updating journals – error when number sequence is longer thanjournal ID length (#2683)o Lockbox File Formats - receive erroneous message "Are you sure you want to delete thispayment line..." message when delete a Lockbox file <strong>for</strong>mat (#2687)o Lockbox File Formats - end positions are <strong>for</strong>ced to be greater than start position in BAI2lockbox <strong>for</strong>mats/ last indicator default error (#2715)o Workbench - payments are automatically settled against the oldest invoice <strong>for</strong> acustomer set to "No settlement (#2734)o Workbench – creating/updating journals – Ledgerjournaltrans.MarkedInvoiceRecID <strong>for</strong>an AR Payment Journal created from Workbench contains CustTrans.Recid instead ofCustTransOpen.Recid (#2772)AP EFT+o <strong>AX</strong> > AP > All Vendors - Error executing code: SKS_EFT_Addenda (object), methodvalidateAddenda called with invalid parameters in AP All vendors > Invoice tab > Settleopen transactions (#2707)o Create and Send - EFT + File Details <strong>for</strong>m should not show data on the MAL tab if it is notan MAL payment (#2708)o EFT+ File Formats - EFT file <strong>for</strong>mat <strong>for</strong>m should check to make sure the MAL class exists<strong>for</strong> the <strong>for</strong>mat when the MAL option is selected (#2711)o Bank Accounts – added support <strong>for</strong> archive option and path (#2391)AR EFT+o Create and Send - Change column order of File details and make <strong>for</strong>m re-sizable. Hide e-mail fields if e-mail is not being used (#2360)o Bank Accounts – added support <strong>for</strong> archive option and path (#2391)GeneralUpdated: May 25, 2015 Page 30
o Support added <strong>for</strong> R3 (#2739)Revision 6.9.1 – 5/2/2014 (NOTE: an EB pre-6.7 to 6.9 upgrade requires a new unlocking key)Positive Payo Create/Send Files - Positive pay file name not created properly when the file name endswith a period (#527)eBankReco Rule Groups - Prevent deletion of an eBankRec Matching, GL mapping, or Parse rule if itis in use (#2330)o Posting GL ledger created by eBankRec - Error when posting GL if cross company ledgeraccount used in GL mapping rules on R2 and newer builds (#2685)o SKS Adv Bank Rec Service - Application log error message ABRFolderNames would likemessage to reflect error in partition name (#2582)AR eSettlement w/Lockboxo Workbench - When using a BAI2 Lockbox <strong>for</strong>mat that maps to the Bai2_CITI <strong>for</strong>matID,moving more than one record from the errors grid to the payment grid will blank outthe payment journal posting date (#2526)o Workbench - Attempting to per<strong>for</strong>m a select all on the errors grid causes an "Invoice notfound" warning to appear <strong>for</strong> each record in the grid (#2527)o Setup/Workbench – Add option to allow duplicate check numbers in Workbench(#2624)o Workbench - Receive "Access denied to method validateLedgerAccount in classFinancialDimensionValidationService." when user attempts to create an AR paymentjournal and the user has the Accounts receivable payments clerk roles assigned (#2668)AP EFT+o Copy Addenda Form - The word “<strong>for</strong>m” should be removed from the caption (#2623)o Bank Holiday Copy Group Form - Caption reads Bank holidays instead of Copy bankholiday group (#2622)o General - Add support <strong>for</strong> EFT Master Account List (MAL). This is used with Virtual Paycard systems (e.g. Chase-SUA) (#2645)o Paymode-X (BoA-CPPX <strong>for</strong>mat) - Populate Disbursing Paymode-X Account ID <strong>for</strong> the CHKpayspec and populate Vendor Number <strong>for</strong> the <strong>for</strong> the PMX and CHK payspecs <strong>for</strong> the US-BOA-CPPX AP EFT file <strong>for</strong>mat (#2636)o WF PMS XML <strong>for</strong>mat – Added additional field <strong>for</strong> a separate wire routing number(#2654)Generalo Upgrade message - Change message box "An upgrade is required, click OK to proceedwith this normal process of upgrading The word “<strong>for</strong>m” should be removed from thecaption (#2623)o <strong>eBanking</strong> Parameters/Registration tab - Add licensing notes to registration <strong>for</strong>m toclarify pricing policy (#2136)Updated: May 25, 2015 Page 31
oDate fields - Date fields in <strong>eBanking</strong> should have a date lookup button. This is commonin <strong>AX</strong> <strong>for</strong> date fields (#2542)Revision 6.8.2 – 4/8/2014 (NOTE: pre-6.7 to 6.8 upgrade requires a new unlocking key)eBankReco Import files - Imported transaction <strong>for</strong> .19 (no leading zero) imports as 0.00 (#2546)o Reconciliation/Click-n-Match - Unreconciled transactions selected total shows USDcurrency Imported transactions selected total shows CAD currency unable to matchtransaction (#2601)AR eSettlement w/ Lockboxo File <strong>for</strong>mats – Field layout cuts off end of word <strong>for</strong> the <strong>for</strong>mat id (#2137)o Import files – support <strong>for</strong> file with one line that doesn't have carriage returns (#1240)o Import files – Get “record already exists’ when creating new customer <strong>eBanking</strong> details– under rare cases (#2497)o <strong>eBanking</strong> <strong>Suite</strong> Parameters - typo in Auto-credit account parameters message whenexiting <strong>eBanking</strong> <strong>Suite</strong> parameters (#2500)AP EFT+o Vendor <strong>eBanking</strong> Details - optional EFT+ Account in<strong>for</strong>mation fields only displayingwhen set to required, not used (#2417)o Vendor <strong>eBanking</strong> Details - E-mail notification check box not automatically checked whenvendor has an e-mail address, the vendor is auto-added in Vendor <strong>eBanking</strong> details, andAP EFT is setup <strong>for</strong> e-mail notifications (#2579)o Communications – add support <strong>for</strong> communication IDs (#2407)o Banking Holidays – add calendar support <strong>for</strong> prenotes & effective dates (#2283)o Addenda Configuration – add support <strong>for</strong> tax and child support ACH addenda (#2046)AP EFT+o Communications – add support <strong>for</strong> communication IDs (#2407)o Banking Holidays – add calendar support <strong>for</strong> prenotes & effective dates (#2283)Revision 6.7.2 – 3/7/2014 – (NOTE: pre-6.7 to 6.7+ upgrade requires a new unlocking key)Positive Payo Communications – automation features added (Upon Journal Posting, Fixed Time(#2406)eBankReco File Formats – added support <strong>for</strong> the Australian NAI <strong>for</strong>mat (#2135)AR eSettlement w/ LockboxUpdated: May 25, 2015 Page 32
ooooImport files – when using any of the optional lookup methods – all those methods willnow be checked be<strong>for</strong>e using the default settlement method – was using defaultsettlement method if there was no invoice number (#2418)Workbench – wrong in<strong>for</strong>mation in message when creating A/R payment journal(#2423)Workbench – error grid select all option did not work with alternate lookup such ascustomer requisition number (#2460)Import files – auto-credits being created, but not matched and placed in the error grid(#2461)Generalo Now include label files <strong>for</strong> all English locales - <strong>AX</strong>SKSen-au, -ca, -gb, -ie, -my, -nz, -sg, -us,-za (#1079)o New unlocking key required <strong>for</strong> v6.7 (#2462)Revision 6.6.2 – 1/24/2014Positive Payo Format – check rejected in a payment journal (now marked as void) was not appearingcorrectly in the original pos pay file (#1245)o Create/Send Files - Select/View Checks displays checks included in a file plus any checkthat can be included in a PP file, fixed so only checks included in the original file areshown (#2394)o Create/Send Files - Positive Pay file when complete a file then later void a check theselected checks number is incorrect (#1247)o Audit Report - The Company Id field in the Positive Pay audit report displays thesks_pp_filedetail.dataareaid instead of the company the check was created in (#1376)o Create/Send Files - The Positive pay file number label is missing in the Positive Pay -Select/View Checks <strong>for</strong>m (#1460)o Create/Send Files - Amount field in Select/View Checks <strong>for</strong> Positive Pay is enabled to beedited, now fixed to remain disabled. (#2058)eBankReco Import files - In BAI2 files eBankRec treats a space in the field as the end of the line.(#2387)o Matching/Mapping - Enhance eBankRec to enable Parsing, Matching and GL Mappingrules to be shared across all companies (#2394)AR EFT+o Create/Send Files - The header and trailer records are showing in the AP/AR Create andsend File Details <strong>for</strong>m as transmitted records (#1673)Revision 6.6.1 – 1/6/2014 eBankRecUpdated: May 25, 2015 Page 33
o Import files - BAI2 file with line feeds and no carriage return does not import (#2351)AR eSettlement w/ Lockboxo Workbench - able to select multiple payments <strong>for</strong> same invoice from error grid and sendthem both to payments grid as settled (#2355)o Workbench – added lookup type/reference fields to support <strong>AX</strong> transactions that don’thave invoice numbers (#2337)o Workbench - records with the same check number that appear in both the payment gridand the payments with errors grid should not be able to be added to a payment journal(#2339)o Processing files - <strong>for</strong>matting/layout consistency issues (#2338)o Processing files/Workbench - bank totals should not show on Journal summary andProcess esettlement/lockbox files <strong>for</strong>ms if BAI2 <strong>for</strong>mats are not in use (#2347)o General - support <strong>for</strong> payment reference processing (in addition to invoice number, BOL,Cust. Req., Sales Order) (#2342)AR EFT Plus!o Create and Send files – the Adv. Email, Adv. e-mail sent and Adv. e-mail failure countsare missing from the File Details <strong>for</strong>m (#1672)Revision 6.5.2 – 12/9/2013eBankReco Import file - Import BAI2 file into bank reconciliation with $ does not bring in theamount of check (#2098)o Import file - detail lines <strong>for</strong> accounts with a leading zero in the "Bank Accounts" screen,will not import. (#2231)o AP Vendor transactions/checks - add clear date field (#2296)o Major enhancement – new architecture <strong>for</strong> matching and mapping. Matching RuleGroups, GL Mapping Rule Groups, Parsing Rules. Click <strong>for</strong> details on theseenhancements. (#2299)o Click-n-Match screen - when selecting a prematched transaction, the unmatching of theexisting prematch would not update the totals and not allow exiting the screen. (#2311)o Reconciliation – Import bank file - correction amount is not set if a match was foundwith an amount tolerance (#2324)AR eSettlement w/ Lockboxo Documentation – User Guide - added Hints/Tips topic covering cross-companysettlementso Documentation – Reference - added document <strong>for</strong> Workbench – Create PaymentJournalo Workbench - over/under payment tolerance is not used <strong>for</strong> credit payments (#862)o Workbench - give users options to handle duplicate settlements more effectively thancurrent "settlement marked by another user" functionality (#1677)Updated: May 25, 2015 Page 34
o Corrected error when opening <strong>eBanking</strong> Parameters after an upgrade. Receivedmessage: “Cannot insert multiple records invoice secondary match sks_lb_invoice matchcustomer requisition mxn080911a” (#998)o Customer bulk load – loading customers - incorrect customer name (#1117)o Import - Auto-credit does not work if the customer/invoice is in a different companythan the processing/payment company (#1144)o Workbench – add "Select All" button (#1190)o Payment Journal post gets error - Cannot edit a record on open customer transactions(CustTransOpen). An update conflict occurred due to another user process deleting therecord or changing one or more fields in the record (#1193)o Workbench - Auto Credit created <strong>for</strong> wrong customer if Account and Account suggestionare both present in errors grid (#1261)o Workbench - "Create free text invoice" button in the error grid should open in theCustomer Company of error grid record (#1268)o Workbench - when moving payments to errors gird, settlement in<strong>for</strong>mation is lost ifsettlement amount was first zeroed out on settlement screen be<strong>for</strong>e move (#1288)o Workbench - Settle amount taken <strong>for</strong> larger than amount that document balance(#1300)o Workbench - LB requires full settlements if rounding parameters are set to zero in <strong>AX</strong>setup (#1312)o Import - Invoices created thru Auto-credit do not have tax, language and address fieldfilled in properly (#1316)o Workbench - Cannot move unsettled payment to good grid without an invoice number ifa bad invoice number was imported from lockbox file (#1369)o Import - Auto-credit and auto-debit GL entries in lockbox to support multiple companieswith multiple chart of accounts (#1429)o Workbench - auto reversing checkbox (payments grid) is not checked when a credit notethat was auto created is applied to a payment record (#1464)o Workbench - LB Invoice field is incorrect in errors grid when record is moved from topgrid to error grid (#1484)o Workbench - customer company field is blank in the errors grid when the Invoiceerror/note is "Found, <strong>for</strong> wrong customer" (#1517)APEFT Plus!o Create and Send - Set vendor to inactive <strong>for</strong> AP EFT+ yet allows txn to pass validation inAP Payment Journal (#893)o <strong>eBanking</strong> Parameters - Message "EFT+ e-mail cannot be enabled until Administration->Setup->E-mail parameters are set up." should refer to System administration, notAdministration (#1042)o Vendor Bulk Load - vendor name is incorrect in grid (#1049)o Create and Send - records in grid should be sorted from highest to lowest EFT+ filenumber instead of lowest to highest (#1066)o Create and Send - Change the behavior that occurs when using bank debits (aka creditmemos) in APEFT+ and using bank credits <strong>for</strong> AREFT+ (#1257)Updated: May 25, 2015 Page 42
eBankReco Click n match - if sorting by check number and picking 3 checks on top of grid and 3 onbottom of grid it only saves the last check as cleared. (#639)AR eSettlement w/ Lockboxo LB - credits not creating credit <strong>for</strong> previous invoices found on this same check and thoseinvoices all pointed to the same company customer, use that customer (#699)o Create credit is not creating a credit but an invoice (#700)o Credit note assigned as a transaction that is already marked. Should allow the creditnote to process successfully. (#707)o Credit notes are not being tagged as credit notes if the lockbox file cannot find aninvoice or customer <strong>for</strong> the record being imported (#762)o LB payments without a check number import each “4” record as individual payments(#805)o Unable to select a credit note in the Errors grid when the credit note's number is thesame as another open credit note <strong>for</strong> the customer (#806)o LB ability to create a credit payment in the workbench and leave it unapplied (#809)o AR Payment Journal created from Lockbox doesn't appear in AR Payment Journal whenjournal name as Private <strong>for</strong> user group set to an <strong>AX</strong> user group (#1022)o Create an Invoice from a Sales Order, the Invoice does not appear in thesks_lb_InvoiceMatch table (#954)o R2: AR payments created <strong>for</strong> LB payments do not have the Offset account specified(#999)o Label in Lockbox setup is incorrect (#1072)o Customer company in Customer <strong>eBanking</strong> Details is not set when a record is created <strong>for</strong>a customer that was processed in Lockbox (#1043)APEFT Plus!o PNC bank spec needs space filled after payment set 641-1057 (#720)o PNC vendor <strong>eBanking</strong> details requires bank account and routing number. They needSWIFT and IBAN (#871)o Vendor bank account fields required when they shouldn't be <strong>for</strong> the EU-SEB-INT, PL-SEB-0511, SE-BGC-0711, and US-PNC-FX-R2 APEFT file <strong>for</strong>mats (#853)o Poland <strong>for</strong> the vendor side is pulling the bank account and routing number. Need to pullthe SWIFT code and bank account number. (#908)o Poland file field 15 the transaction classification need quotes around the field. (#922)o Poland bank spec in the 4 record needs the SWIFT (#869)o Vendor bulk load vendor creates vendor <strong>eBanking</strong> with no vendor bank account yet thatis required field (#949)o Load all vendors and click on bulk load bank accounts and do not get a list of all vendorbank accounts (#965)o Cannot edit a record in Vendor bank accounts (VendBankAccount). The record has neverbeen selected. (#967)Updated: May 25, 2015 Page 44
o When VendTable is virtualized the Vendor Bank Accounts show <strong>for</strong> both companies butonly saved <strong>for</strong> one which makes the vendor bank account drop down list blank inVendor <strong>eBanking</strong> details (#1008)o You are not able to change the path or filename when "Can change filename and path increate and send" is checked (#972)o Vendor Details email template resets to the <strong>eBanking</strong> Setup values on save (#1021)o Email templates not defaulting correctly in Customer <strong>eBanking</strong> details and Vendor<strong>eBanking</strong> Details (#1024)o Can't edit a record in EFT + file (SKS_EFTAP_FILE) the operation can't be completed sincethe records were not selected <strong>for</strong> update (#1046)o Discount amount was incorrect if past discount date (#903)o Segment count in SE record of US-BOA-CHK-EDI820 is incorrect (#920)o The vendor bank account drop down list is empty in the Vendor <strong>eBanking</strong> details <strong>for</strong>mwhen the VendTable and the… (#993)o CLRObject static method innovaction error when trying to create and send AP EFT withemail turned on (#1010)o <strong>eBanking</strong> Vendor detail and Customer detail records get created even if Auto create notset in <strong>eBanking</strong> (#1088)o In the AP create and send screen, the print audit report check box does not default thevalue from setup screen (#1078)AREFT Plus!o ACH file issues - offset and total amounts (#1023)o Processing both AP EFT and AR EFT could incorrectly select the file record from theother module (#1025)o Check AR test file do not receive message box (#1064)o Payment journal has transactions that are selected in EFT+ file: 000001. Message boxdoes not give actual file number (#1067)o Incorrect label when the Can change file name and path in create and send is checkedwith Server Side processing turned on. The AP module is displayed in the label insteadof AR (#1050)o Can't edit a record in EFT + file (SKS_EFTAP_FILE) the operation can't be completed sincethe records were not selected <strong>for</strong> update (#1046)o The Complete message box does not appear <strong>for</strong> AR EFT+ if the Separate usersubmits/uploads the file to the bank (2-step) checkbox is checked in AP EFT+ (#1051)o Block Fill is being ignored if only AR EFT+ is active (#1098)o Numeric File ID Modifier is never used in a US-ACH file (#1096)o Error can't locate email template. Check template name and language in setup (#1044)Generalo Registration screen – when authorized users is 600000 - Arithmetic operation resulted inan overflow. at SKS.Common.EBCommon. RegistrationCheck(STring Checkkey, StringmoduelString, Int32EFTLicFormatsNbr, Boolean isUserInteractiveMode) (#1115)o Auto create customer and vendor are missing from <strong>eBanking</strong> setup in <strong>2012</strong> (#1087)o Issue with unlocking keys – including Task users (#885)Updated: May 25, 2015 Page 45
o Add support <strong>for</strong> <strong>AX</strong> <strong>2012</strong> FP CU3 and <strong>AX</strong> <strong>2012</strong> FP CU4 (#955)Revision 5.4.2 – 2/6/2013eBankReco Click and Match - items in click and match selected, Imported bank file showsreconciled, Account reconciliation checks not cleared. Fixed (#822)o Dimension used when creating the GL journal entry <strong>for</strong> transaction type was notcreating dimension <strong>for</strong> right side of entry (#850)APEFT Plus!o Discount amount was incorrect if past discount date (#903)o Vendor custom fields do not show (#928)o Creating EFT+ file taking too long (over an hour). Fixed (#1039)o Issue showing prenotes on Create and Send fixed.Generalo Issue with unlocking keys – including Task users (#885)Revision 6.0.2 – 1/7/2013eSettlement/Lockboxo LB payments without a check number import each 4 record as individual payments(#805)o Unable to select a credit note in the Errors grid when the credit note's number is thesame as another open credit note <strong>for</strong> the customer (#806)o Ability to create a credit payment in the workbench and leave it unapplied (#809)APEFT Plus!o Poland – modify to use SWIFT code (#908)o <strong>eBanking</strong> Parameters – setup – multiple issues (#910)o Create and Send – initial record not getting created (#912)AREFT Plus!o First releaseGeneralo File paths are now controlled by server side accounts – <strong>for</strong> security (#767)Revision 5.4.0 – 12/17/<strong>2012</strong>APEFT Plus!o Finland EU-SEB-1211 need routing number and IBAN in file (#749)o Change <strong>for</strong> US-PNC-FX-R2 (#697Generalo Add support <strong>for</strong> <strong>AX</strong> <strong>2012</strong> R2 (#828)Revision 5.3.0 – 11/28/<strong>2012</strong>Positive Payo Payee name issues with comma would like quotes in payee name field (#748)eBank RecUpdated: May 25, 2015 Page 46
o Error executing code: Wrong argument types <strong>for</strong> addition received when importing BAI2BR file (#656)o A line 16 record that ends with a "/" followed by spaces includes the "/" in the last fieldinstead of ignoring it since it means the line is continued with the following 88 record(#763)o The ability to take one deposit and apply it to several deposits on the imported bankreconciliation file (CLICK-N-MATCH) (#260)APEFT Plus!o Bulk load design issue: Vendor <strong>eBanking</strong> Details <strong>for</strong>m should have button to directlylaunch bulk load. (#753)o Finland EU-SEB-1211 need routing number and IBAN in file (#749)Generalo Registration change <strong>for</strong> user counts (#756)o Installation support <strong>for</strong> <strong>AX</strong> <strong>2012</strong> Feature Pack (#752)Revision 5.1.7 – 11/1/<strong>2012</strong>Positive Payo Check status option <strong>for</strong> positive pay includes Void status checks but not able to get avoid (bankchequetable.chequestatus = 3) status check (#557)eBank Reco Advanced bank rec service should display a better error message when the ABR svcversion differs from the <strong>eBanking</strong> version (#660)o Electronic Bank Reconciliation File Format has not been setup <strong>for</strong> this bank accountreceived in Event log. (#634)eSettlement/Lockboxo Database upgrade should initialize the lockbox alternate lookup options to only searchon invoice by default. (#636)o The Payment total in the error grid section does not display the proper value when thePayment amount = Sum of check amounts is checked <strong>for</strong> the file <strong>for</strong>mat (#521)o Label on create payment dialog in LB Workbench should be Posting date vs. Transactiondate (#684)o Cannot edit a record in eSettlement/lockbox Journal AR (SKS_LB_JournalAR) errordisplays when importing a settlement file with tolerance (#649)APEFT Plus!o Vendor <strong>eBanking</strong> details is creating vendor but not payment specification when changemethod of payment and spec <strong>for</strong> Vendor in <strong>AX</strong>. (#708)o Cannot edit a record in Vendor bank accounts (VendBankAccount). “The record hasnever been selected." message received when have Auto create vendor record turnedon and edit existing vendor to have AP EFT+ method of payment (#711)o Name PNC should be included in description <strong>for</strong> <strong>for</strong>mat US-PNC-FX-R2 (#653)o PL-SEB-0511 <strong>for</strong>mat is incorrectly zero padding amount (#671)o Setting up to use virtual companies, vendor <strong>eBanking</strong> details screen does not work.Fixed (#648)Updated: May 25, 2015 Page 47
APEFT - The Active checkbox and the Enable method of payment/payment spec in journalcheckbox in the Vendor <strong>eBanking</strong> details screen do not default as checked like they do in <strong>AX</strong>2009. (#471) APEFT - Issues with the AP EFT+ audit report (#558) APEFT - Payment amount on AP EFT+ file details displays as negative amount but the Paymenttotal on Create and send AP EFT+ files shows positive amount (#573) APEFT - The Selected payment journals field count can go negative in the AP EFT+ select/viewpayments screen (#544) APEFT - If the Create and send AP EFT+ files grid is empty and the Select/view payments grid isempty when the user clicks on the Select/view payments button the message "Form cannot becalled directly." Displays (#543) APEFT - When checking the box Company ids are unique by payment specification, the fields <strong>for</strong>PPD, CCD and IAT that were disabled disappear from the screen. (#606) APEFT - When File id modifier is set to Numeric (1-9) and more than 9 files are created in thesame day, the file id modifier is incremented to 10, 11, 12, etc. instead of reset at 1 whichcauses the field placement in the ACH file to be incorrect. (#609) APEFT - The RDFI ID that is displayed in the ACH file <strong>for</strong> an IATB transaction type in record 714,field 41-74 is incorrect. (#614) APEFT - Show payments already selected check box is enabled <strong>for</strong> a Transmitted status EFT line(#560) APEFT - Unable to include an EFT payment previously included in a different EFT file (result ofbug 537) (#554) APEFT - Format request Bank of America - Outsourced check printing (#457) eBankRec - Unable to maximize Imported electronic bank reconciliation file details (#547) Lockbox - Create payment journal you can change the document date would like the transactiondate changed to the document date as well. (#280 Lockbox - External settlement file dialog does not default to the directory set up <strong>for</strong> thatcustomer. (#617) Lockbox - Multiple issues with Invoice lookup <strong>for</strong> lockbox want the column "Invoice reference"renamed to "lookup type" (#594) Lockbox - Lookup options <strong>for</strong> Lockbox allows having 2 lookup types that are the same not surehow it will decide which one to use (#595)Revision 5.1.2 – 8/16/<strong>2012</strong>GA release <strong>for</strong> AP EFT Plus!Lockbox – when importing BAI2 files, split into separate LB journals by batchLockbox – manage “in use” when multiple users are editing LB journalsLockbox – record routing and account numbers to use in matching customersLockbox – add “None” as a settlement method, by customer (settlement is done manually)Lockbox – capability to import settlement data independently of main lockbox file (separate filesprovided by customers) - External Settlement.Lockbox - External settlements can be <strong>for</strong> multiple customersLockbox - Credit note supportLockbox - Secondary invoice match supportLockbox - Payment reassign button added to Workbench screenUpdated: May 25, 2015 Page 49
Lockbox - Ability to specify Journal name by Bank AccountLockbox - Multiple BAI2 <strong>for</strong>mats supportedLockbox - RTN/Acct will only save off now if workbench is pushed to a payment journalLockbox – Provide option to match by multiple criteria (Invoice, Bill of Lading, CustomerPurchase Req number, SO number)eBankRec - Click-n-Match allows flexible matching (1 <strong>AX</strong> txn to Multiple bank txns, Multiple <strong>AX</strong>txns to 1 bank txn, Multiple <strong>AX</strong> txns to Multiple bank txns)Compiled with <strong>AX</strong><strong>2012</strong> RTMRevision 4.4.4 – 3/29/<strong>2012</strong> Compiled with <strong>AX</strong><strong>2012</strong> RTM Lockbox – Added image identifiers Registration – removed Task users from licensing keyRevision 4.3.34 – 3/5/<strong>2012</strong><strong>AX</strong> <strong>2012</strong> RTM build <strong>AX</strong> <strong>2012</strong> samples files need to be updated <strong>for</strong> advanced bank reconciliation (#122) <strong>AX</strong> <strong>2012</strong> sample files need to be updated <strong>for</strong> lockbox (#123)When two companies with the same bank account id and <strong>eBanking</strong> is virtualized multiple errorsare occurring in Positive Pay (#138)The SKS.Common.dll file is pulling the Vendor Name from the Checks Recipient name when itshould be pulling from the Vendor master address name field (#112)Revision 4.3.32 – 1/16/<strong>2012</strong>Installation revised to always install SKS.Common.dll on the serverBug 80 – Issue with using more than 100 companies with virtual companies or organizationalmodel. Fixed.Revision 4.3.3 – 12/22/2011 <strong>eBanking</strong> Setup parameters - enhanced user count licensing based on Task + Functional +Enterprise users. HTML help not yet includedeBankRec Adv– added journal level matching (<strong>AX</strong> journal total matching to bank entry)eBankRec Adv– imported transaction that creates a GL tran doesn’t get a bank tran type – fixedeBankRec Adv– enhanced to support GL journal level matching in addition to AP and AReBankRec Adv–AR payment with a payment fee was not matched – fixedeBankRec Adv–unable to clear an imported txn using Check/Deposit slip number – fixedeBankRec Adv–unable to match an imported txn when Check/Deposit slip number included aspecial character – fixedeBankRecAdv – transactions do not import when followed by txns set to “Do Not Import” - fixedRevision 4.3.0 – 8/17/2011Updated: May 25, 2015 Page 50
eBankRec Adv – enhancement to match payment journal total to a bank statement entry (beta).Revision 4.2.2 – 11/29/2011 <strong>eBanking</strong> Setup parameters - enhanced user count licensing based on Task + Functional +Enterprise users. HTML help not yet includedRevision 4.2.1 – 8/24/2011Beta release of <strong>eBanking</strong> <strong>for</strong> <strong>AX</strong> <strong>2012</strong>. HTML help not yet includedUpdated: May 25, 2015 Page 51
Appendix A – Setting up <strong>eBanking</strong> SecuritySecurity layersThe <strong>eBanking</strong> <strong>Suite</strong> uses the <strong>AX</strong> <strong>2012</strong> security layer model. An understanding of Roles, Duties, Privileges,Entry Points and Permissions is required to implement <strong>eBanking</strong> Security. Please review the <strong>AX</strong>documentation <strong>for</strong> details on these topics.System tools<strong>AX</strong> provides screens that allow Administrators to assign users to role and assign duties to roles and viewprivileges.The Application Object Tree (AOT) can be used to review details related to security. A new Securitygrouping is in the AOT. Roles, Duties and Privileges <strong>for</strong> the <strong>eBanking</strong> <strong>Suite</strong> can be viewed here. All<strong>eBanking</strong> <strong>Suite</strong> security objects are prefixed with SKS_. On any security object you can right-click andchoose Add-Ins -> Security tools. From there the selecting will change based on which security objectyou are on. The choice will either be View related security objects or View related security roles.On each <strong>for</strong>m, you can look at the permissions in the AOT. Read, Update, Create and Delete each havetheir own set of permissions. The majority of the permissions are auto-generated. You can use the areato view or override permissions. The most common scenarios are adding table permissions to a <strong>for</strong>m,excluding specific controls or adding associated <strong>for</strong>ms.Setting up <strong>eBanking</strong> securityThe <strong>eBanking</strong> <strong>Suite</strong> ships with pre-defined Privileges and Duties. The Duties are added to pre-defined <strong>AX</strong>Roles. The Privileges and Duties are separated by module – Positive Pay, eBank Reconciliation and ARSettlement w/Lockbox (Lockbox). They are also separated into security tied to Read permissions andsecurity tied to CRUD (Create, Read, Update Delete) permissions.DutiesFor <strong>eBanking</strong>, the duties are separated between Policies (Setup) and Process. All screens needed toper<strong>for</strong>m Setup are in the duties with the AOT name of Policies. All screens needed to per<strong>for</strong>mprocessing are in the duties with the AOT name of Process.Duties by module:Duty (AOT name)Positive PaySKS_PP_PoliciesEnableSKS_PP_PoliciesInquireSKS_PP_ProcessEnableSKS_PP_SelectionOverrideSKS_PP_ProcessInquireDuty descriptionMaintain <strong>eBanking</strong> Positive Pay policiesInquire into <strong>eBanking</strong> Positive Pay policiesEnable <strong>eBanking</strong> Positive Pay processingEnable <strong>eBanking</strong> Positive Pay check selection overrideInquire into <strong>eBanking</strong> Positive Pay processingElectronic Bank ReconciliationUpdated: May 25, 2015 Page 52
SKS_BR_ProcessEnableSKS_BR_ProcessInquireSKS_BR_PoliciesEnableSKS_BR_PoliciesInquireLockbox (AR eSettlement w/Lockbox)SKS_LB_PoliciesEnableSKS_LB_PoliciesInquireSKS_LB_ProcessEnableSKS_LB_ProcessInquireAPEFT Plus!SKS_EFT_AutoCreateEFT_ProcessEnableSKS_EFT_ProcessEnableSKS_EFT_ProcessInquireSKS_EFT_PoliciesEnableSKS_EFT_PoliciesInquireAREFT Plus!SKS_EFTAR_ProcessEnableSKS_EFTAR_ProcessInquireSKS_EFTAR_PoliciesEnableSKS_EFTAR_PoliciesInquireEnable <strong>eBanking</strong> Reconciliation importInquire into <strong>eBanking</strong> Reconciliation importMaintain <strong>eBanking</strong> Reconciliation policiesInquire into <strong>eBanking</strong> Reconciliation policiesMaintain <strong>eBanking</strong> Lockbox policiesInquire into <strong>eBanking</strong> Lockbox policiesEnable <strong>eBanking</strong> Lockbox processingInquire into <strong>eBanking</strong> Lockbox processingEnable AP EFT+ create now processingEnable <strong>eBanking</strong> AP EFT+ processingInquire into <strong>eBanking</strong> AP EFT+ processingMaintain <strong>eBanking</strong> AP EFT+ policiesInquire into <strong>eBanking</strong> AP EFT+ policiesEnable <strong>eBanking</strong> AR EFT+ processingInquire into <strong>eBanking</strong> AR EFT+ processingMaintain <strong>eBanking</strong> AR EFT+ policiesInquire into <strong>eBanking</strong> AR EFT+ policiesRoles and duties:The <strong>eBanking</strong> suite does not add any pre-defined roles. It uses the existing <strong>AX</strong> roles related to thefunctions that are extended by the <strong>eBanking</strong> <strong>Suite</strong>.The duties and roles assigned by <strong>eBanking</strong>:Duty nameRole namePositive PayMaintain <strong>eBanking</strong> Positive Pay policiesEnable <strong>eBanking</strong> Positive Pay processingEnable <strong>eBanking</strong> Positive Pay check selection overrideInquire into <strong>eBanking</strong> Positive Pay policiesInquire into <strong>eBanking</strong> Positive Pay processingTreasurerTreasurerTreasurerAccounting managerFinancial controllerAccounting managerFinancial controllerElectronic Bank ReconciliationMaintain <strong>eBanking</strong> Reconciliation policiesTreasurerUpdated: May 25, 2015 Page 53
Enable <strong>eBanking</strong> Reconciliation importInquire into <strong>eBanking</strong> Reconciliation policiesInquire into <strong>eBanking</strong> Reconciliation importTreasurerChief financial officerAccountantAccounting managerAccounting supervisorFinancial controllerChief financial officerAccountantAccounting managerAccounting supervisorFinancial controllerLockbox (AR eSettlement w/Lockbox)Maintain <strong>eBanking</strong> Lockbox policiesEnable <strong>eBanking</strong> Lockbox processingInquire into <strong>eBanking</strong> Lockbox policiesInquire into <strong>eBanking</strong> Lockbox processingAccounts receivable payments clerkAccounts receivable payments clerkCollections agentCollections managerChief financial officerAccounts receivable clerkAccounts receivable managerAccountantAccounting managerAccounting supervisorFinancial controllerAccounts receivable centralized payments clerkCollections agentCollections managerChief financial officerAccounts receivable clerkAccounts receivable managerAccountantAccounting managerAccounting supervisorFinancial controllerAccounts receivable centralized payments clerkAPEFT Plus!Maintain <strong>eBanking</strong> AP EFT+ policiesInquire into <strong>eBanking</strong> AP EFT+ policiesAccounts payable payments clerkChief financial officerAccountantAccounting managerAccounting supervisorFinancial controllerAccounts payable centralized payments clerkUpdated: May 25, 2015 Page 54
Enable <strong>eBanking</strong> AP EFT+ processingInquire into <strong>eBanking</strong> AP EFT+ processingAREFT Plus!Maintain <strong>eBanking</strong> AR EFT+ policiesInquire into <strong>eBanking</strong> AR EFT+ policiesEnable <strong>eBanking</strong> AR EFT+ processingInquire into <strong>eBanking</strong> AR EFT+ processingTreasurerAccounts payable clerkAccounts payable managerAccounts payable payments clerkChief financial officerAccountantAccounting managerAccounting supervisorFinancial controllerAccounts payable centralized payments clerkTreasurerAccounts payable clerkAccounts payable managerAccounts receivable payments clerkCollections agentCollections managerChief financial officerAccounts receivable clerkAccounts receivable managerAccountantAccounting managerAccounting supervisorFinancial controllerAccounts receivable centralized payments clerkAccounts receivable payments clerkCollections agentCollections managerChief financial officerAccounts receivable clerkAccounts receivable managerAccountantAccounting managerAccounting supervisorFinancial controllerAccounts receivable centralized payments clerkPrivilegesPrivileges and entry points can be reviewed in the AOT using the methods described in the System toolssection above. The <strong>eBanking</strong> <strong>Suite</strong> uses menu items as the entry points defined in the privileges.Updated: May 25, 2015 Page 55
Appendix B – Organization hierarchies in <strong>eBanking</strong>OverviewIn <strong>AX</strong> <strong>2012</strong>, a new concept was introduced <strong>for</strong> managing organization hierarchies. The changes helpsupport scenarios <strong>for</strong> viewing data across multiple organizations including but not limited to companies(called legal entities in <strong>AX</strong> <strong>2012</strong>). This is the eventual replacement to virtual companies. In <strong>AX</strong> <strong>2012</strong>virtual companies are still supported.Here is a link to an article on Organization hierarchies:http://technet.microsoft.com/en-us/library/hh242144.aspx<strong>eBanking</strong> support<strong>eBanking</strong> needs to support the new organization hierarchy and provide backward compatibility support<strong>for</strong> virtual companies. The organizational hierarchy is used to determine which companies will beincluded in <strong>eBanking</strong>. Positive Pay and Bank Rec have new “Organization hierarchy purposes” definedand Lockbox uses the out of the box “Centralized purpose”. The Organizational hierarchy is added tothe organization hierarchy purpose.Below are two different Organization hierarchies (CEC and CEE). In each example, all of the companies(legal entities) shown in the hierarchy would be available.Updated: May 25, 2015 Page 56
Positive PayChecks from any companies in the organization hierarchy attached to the <strong>eBanking</strong> Positive Pay purposeand that the user has access will be available to include in the Positive Pay file. If no companies are inthe organization hierarchy, virtual company setup will be used. If no virtual companies are found, thecurrent company will be used.Electronic Bank ReconciliationBank accounts from any companies in the organization hierarchy attached to the <strong>eBanking</strong> BankReconciliation purpose and that the user has access will be imported. If no companies are in theorganization hierarchy, virtual company setup will be used. If no virtual companies are found, thecurrent company will be used.AR eSettlement w/Lockbox, APEFT Plus!, AREFT Plus!Lockbox and AP/AR EFT+ use the out of the box organization hierarchy purpose called “Centralizedpayments” to determine which companies should be used when finding Invoices.Setting up organizationsUse the Organization administration menu to setup organizations. Under Setup -> Organizations, thereare multiple screens. Organization hierarchies is used to layout the organization structure. Organizationhierarchy purposes lists the purposes and allows you to attach hierarchies to the purpose.Updated: May 25, 2015 Page 57
SecuritySecurity in the organization hierarchy is controlled by the organizations assigned to the roles in the User<strong>for</strong>m. For each role listed <strong>for</strong> the user, you can click Assign organizations and grant rights to allorganizations or specific organizations. This security restricts the companies that you can see in anorganization hierarchy.Setup dataIn <strong>AX</strong> 2009, setup data like File <strong>for</strong>mats could be shared using virtual companies. In <strong>AX</strong> <strong>2012</strong>, this is donedifferently if you are not using virtual companies. To share data in <strong>AX</strong> <strong>2012</strong>, you need to change thetable property “SaveDataPerCompany” to false. This will allow the data to be saved once in <strong>AX</strong> and usedby all companies.Appendix C (below) lists the tables that should be placed in a table collection to support virtualcompanies. This same list can be used to share data across all of the companies. If using virtualcompanies in <strong>AX</strong> <strong>2012</strong>, the setup in Appendix C (the same as documented in <strong>AX</strong> 2009) should be used.It is not mandatory to share the setup data if using Organization hierarchies. The companies will bedetermined based on the Organization hierarchy purpose. Sharing setup data is a convenience to allowusers to not have to repeat the setup in each company.Updated: May 25, 2015 Page 58
Appendix C – Virtual Company SetupThe <strong>eBanking</strong> <strong>Suite</strong> supports the use of virtual companies to centralize processing. <strong>eBanking</strong> does notrequire the use of virtual companies but can be configured to take advantage of any virtual companysetup you may have.To set up virtualization you need to create or update a table collection. This is done via the AOT(Application Object Tree) -> Data Dictionary -> Table Collections.If you need to create a new table collection it will need to be added to a virtual company:1. Go to Administration -> Setup -> Virtual company accounts2. Choose a Virtual company or create a new one.3. Add Company accounts if necessary4. Add the new Table collection to the selected table collections.Positive PayUsing virtual companies allows selecting checks and processing files <strong>for</strong> multiple bank accounts acrossmultiple companies.The following <strong>eBanking</strong> tables must be placed in the table collection:SKS_PP_FileSKS_PP_FileDetailSKS_PP_FileFormatSKS_PP_HeaderTrailerThe following table is optional as to being placed in the table collection (it would only be done if alsousing eBank Rec Advanced and/or Lockbox Processing):SKS_PP_Setup - this table links to the LedgerJournalName table. If this table is virtualized or ifthe journal name that you are using in all companies is the same, the SKS_PP_Setup table can bevirtualized.Electronic Bank ReconciliationUsing virtual companies allows <strong>for</strong> processing a single file that contains transactions <strong>for</strong> multiple bankaccounts across multiple companies.The following <strong>eBanking</strong> tables must be placed in the table collection:SKS_BR_BankHeaderSKS_BR_ErrorLogSKS_BR_FileFormatSKS_BR_FileFormatDetailUpdated: May 25, 2015 Page 59
The following tables are optional as to being placed in the table collection:SKS_BR_FileFormatTranMapping - this table links to BankTransType, LedgerTable and Dimensiontables. If those tables are already virtualized, the SKS_BR_FileFormatTranMapping table can bevirtualized.SKS_PP_Setup - this table links to the LedgerJournalName table. If this table is virtualized or ifthe journal name that you are using in all companies is the same, the SKS_PP_Setup table can bevirtualized.AR eSettlement w/LockboxLockbox allows processing payments against invoices within any company when <strong>AX</strong> is configured toallow <strong>for</strong> centralized processing. It uses the same rules as the <strong>AX</strong> Payment Journal as to centralizedprocessing.The following tables are optional as to being placed in the table collection:SKS_PP_Setup - this table links to the LedgerJournalName, CustPaymMode andNumberSequence tables. If these table are virtualized or if the journal name that you are usingin all companies is the same, the SKS_PP_Setup table can be virtualized.SKS_LB_FileFormatSKS_LB_FileFormatDetAPEFT Plus! & AREFT Plus!APEFT Plus! allows processing payments against invoices within any company when <strong>AX</strong> is configured toallow <strong>for</strong> centralized processing. It uses the same rules as the <strong>AX</strong> Payment Journal as to centralizedprocessing.The following tables are optional as to being placed in the table collection:SKS_PP_Setup - this table links to the LedgerJournalName, CustPaymMode andNumberSequence tables. If these table are virtualized or if the journal name that you are usingin all companies is the same, the SKS_PP_Setup table can be virtualized.SKS_EFT_FileDetailSKS_EFT_FileFormatSKS_EFT_FileFormatLookupsSKS_EFT_FileFormatNotesSKS_EFT_Setup – this table is linked to other tables that also may need to be virtualizedNotes to existing customers – switching to virtual companiesIf a table is setup <strong>for</strong> individual companies and then later, the table is virtualized, all of the existing datawill no longer display in the screens. It is still in the database, it just won't be displayed.An example: File <strong>for</strong>mat in company CEU and company CEE. Create a virtual company CCC and placethe file <strong>for</strong>mat table in the virtual company. Now if in CEU or CEE, it will only display record <strong>for</strong> CCC.The dataAreaId field in the file <strong>for</strong>mat table contains the company id. If the dataAreaId was changed toUpdated: May 25, 2015 Page 60
CCC on an existing CEU or CEE record, it would start displaying in the virtual company. So a user wouldneed to decide if they wanted to change an existing record or create a new record. If they changeexisting records, they will most likely need to also eliminate a record. So CEU would become CCC andCEE would get eliminated.Here’s a blog post that gives more in<strong>for</strong>mation on this process: http://blog.colesys.com/?p=15Updated: May 25, 2015 Page 61
Change language