April, 2013
ePay Advantage
User’s Guide
Copyright
Copyright © 2013 Nodus Technologies, Inc. All rights reserved.
Your right to copy this documentation is limited by copyright law and the terms of the software license agreement. As the software licensee, you may make a reasonable number of copies or printouts for your own use. Making unauthorized copies, adaptations, compilations, or derivative works for commercial distribution is prohibited and constitutes a punishable violation of the law.
Trademarks Nodus eStore Solution Stack, Scheduled Payments, ePay Advantage, Credit Card Advantage, eStore Advantage, eSOP™ Advantage and Retail Advantage are either registered trademarks or trademarks of Nodus Technologies, Inc. in the United States.
The names of actual companies and products mentioned herein may be trademarks or registered marks - in the United States and/or other countries - of their respective owners.
The names of companies, products, people, and/or data used in window illustrations and sample output are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted.
Warranty disclaimer Nodus Technologies, Inc. disclaims any warranty regarding the sample code contained in this documentation, including the warranties of merchantability and fitness for a particular purpose.
Limitation of liability The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Nodus Technologies, Inc. Nodus Technologies, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual. Neither Nodus Technologies, Inc. nor anyone else who has been involved in the creation, production or delivery of this documentation shall be liable for any indirect, incidental, special, exemplary or consequential damages, including but not limited to any loss of anticipated profit or benefits, resulting from the use of this documentation or sample code.
License agreement Use of this product is covered by a license agreement provided with the software product. If you have any questions, please call the Nodus Technologies Support at 909-482-4701
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
3
Revision History:
Author Date Version Changes Approved Date
Table of Contents
1. Introduction ... 10
1.1. PA-DSS Compliance ...11
1.2. Tokenization (Optional)...11
1.3. New Features in ePay Advantage SP2...13
1.4. Terms and Conventions ...14
1.5. Additional Resources ...18
2. ePay Advantage Installation ... 19
SSL Certificate Setup ...19
Username & Password Restriction Setup ...19
3. Product Configuration Settings ... 21
3.1. Administration Settings...21
3.1.1. Default Admin Log-in ... 21
3.1.2. Browse to Admin Site ... 21
3.1.3. Documentation... 22
3.1.4. Site Settings... 22
3.1.4.1. Company Information Tab ... 22
3.1.4.2. Transaction Processing Options ... 23
3.1.4.3. Content Management tab... 27
3.1.4.4. E-mail Setup ... 28
3.1.4.5. Payment Scheduler Options tab ... 29
3.1.4.6. Landing Page Options tab ... 30
3.1.5. Back Office Settings ... 31
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
5
3.1.5.3. Payment Options ... 33
3.1.5.4. Card Name Mapping ... 35
3.1.6. Feature Settings... 36
3.1.6.1. Payment tab ... 36
3.1.6.2. Customer Wallet tab ... 38
3.1.6.3. Past Due Invoices Reminder Options tab ... 40
3.1.6.4. CAPTCHA tab ... 41
3.1.6.5. Grid Column Options ... 42
3.1.7. Recurring Billing Settings ... 43
3.1.7.1. Recurring Invoice tab ... 43
3.1.7.2. AutoPay tab ... 47
3.1.8. Installment Payment Settings ... 49
3.1.9. Sales Order Entry Settings ... 50
3.1.9.1. Sales Order Entry Settings tab ... 50
3.1.9.2. Order tab ... 52
3.1.9.3. Invoice tab ... 53
3.1.10. Manage Contract Class ID... 54
3.1.10.1. Delete or Edit a Manage Contract Class ID ... 55
3.1.11. Tax Settings ... 56
3.1.11.1. Troubleshooting: Avatax ... 58
Disabled Event Viewer ... 58
Permission for Event Log ... 58
3.1.12. Manage Users ... 59
3.1.12.1. Creating New Users ... 59
3.1.12.2. Registering CSRs and Customers ... 61
3.1.12.2.1. Registering Customers ... 61
3.1.12.2.2. Registering CSRs ... 63
3.1.12.3. Manage Users... 64
3.1.12.3.1. Delete Admin ... 64
3.1.12.3.2. Unregistering or inactivating a CSR or Customer User Account ... 64
3.1.12.3.4. Change Email... 65
3.1.12.3.5. Enabling ’See All Customers’ Functionality for CSR... 65
3.1.12.4. User Group Permission ... 67
3.1.12.5. User Group Setting... 69
3.1.13. Queues ... 70 3.1.13.1. Document Queue ... 70 3.1.13.2. Payment Queue ... 74 3.1.14. Reports ... 75 3.1.14.1. Payments ... 75 3.1.14.2. Installment Contracts ... 77
3.1.14.3. Recurring Billing Contracts ... 78
3.1.14.4. AutoPay Contracts ... 80
3.1.14.5. AutoPay Payments ... 81
3.1.14.6. Preview Recurring Billing Invoices ... 82
3.1.14.7. Audit Payments... 83
3.1.14.8. Credit Card Expiration Report ... 84
3.1.14.9. Outstanding Invoices Report ... 85
3.1.14.10. System Information ... 87
3.1.14.11. Error Logs Report ... 90
3.1.15. Email Templates ... 91
3.1.15.1. Payment Confirmation Template... 91
3.1.15.2. Payment Declined Template... 92
3.1.15.3. New User Welcome Template ... 94
3.1.15.4. New Invoice Import Template ... 95
3.1.15.5. New Customer Import Template ... 96
3.1.15.6. Confirm Reset Password Template ... 98
3.1.15.7. Recurring Billing Invoice Payment Declined Template ... 100
3.1.15.8. Past Due Invoices Reminder Template ... 101
3.1.15.9. Failed Document Submission to GP Template ... 103
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
7
3.1.15.12. CCA Transaction Notification Template ... 106
3.1.15.13. Express Pay Notification Template ... 107
3.1.16. Documentation ... 110
4. Product Overview... 110
4.1. ePay Functionalities ...110
4.1.1. Single Sign-On... 112 4.1.2. Customer Activation ... 113 4.1.3. Site Log-in... 1164.1.3.1. Log-in Using Customer ID ... 116
4.1.3.2. Log-in Using E-Mail Address ... 117
4.1.3.3. Log-in Using a Customer Chosen User Name ... 118
4.1.4. Additional Log-in Management ... 119
4.1.4.1. Edit an Account ... 120
4.1.4.2. Create a New Account... 120
4.1.5. Accessing ePay using Customer or CSR User Accounts ... 121
4.1.5.1. Look up Customers – Parent/Child Accounts... 121
4.1.5.2. Update CSR Profile ... 122
4.1.5.3. Update Customer Profile ... 124
4.1.5.4. Update Customer E-Mail Address ... 125
4.1.5.5. Update CSR E-Mail Address ... 126
4.1.5.6. Reset Password ... 126
4.1.8.1 Create New Wallet Item ... 128
4.1.8.1 Edit Wallet Items ... 128
4.1.5.9. Account Summary ... 131
4.1.5.10. View/Filter Posted Account Receivable Invoices (Paid Transactionss)... 131
4.1.5.11. View Outstanding Invoices ... 133
4.1.5.13. View and Track Payments (Payment History) ... 135
4.1.5.14. Payment Deposits ... 138
4.1.5.15. Apply Existing Credit ... 139
4.1.7. Integrating with PayPal Hosted Payment Page ... 143
4.1.8. Payment via Paylink... 144
4.1.8.1 Paylink as Express Pay ... 144
4.1.8.2 Paylink with Credit Card Advantage (CCA) ... 146
4.2. Make Payment against a Posted AR Document...151
4.2.1. Making a Credit Card Payment ... 151
4.2.2. Making an eCheck Payment ... 156
4.3. Scheduled Payments ...158
4.3.1. View Scheduled Payments ... 158
4.3.2. New Installment Payment Plan ... 160
4.3.3. View/Search for an Installment Payment Contract ... 164
4.3.3.1. View Payment Receipt ... 164
4.3.3.2. View Amortization Schedule... 166
4.3.4. Edit Installment Payment Contract ... 167
4.4. Recurring Invoicing ...169
4.4.1. Create a Recurring Invoice Billing Contract ... 169
4.4.1.1. Assign Different Start/End Bill Dates to Multiple Items ... 176
4.4.2. Edit the Recurring Invoice Billing Contract ... 178
4.4.3. View the Recurring Billing Invoice Contract ... 181
4.4.4. Place an Existing Recurring Billing Contract on Hold ... 182
4.4.5. Cancel an Existing Recurring Billing Invoice Contract ... 183
4.4.6. Skipping an Invoice Contract Billing Cycle ... 185
4.5. Recurring Payment AutoPay Contracts ...187
4.5.1. Setting Up a New Payment Contract ... 187
4.5.2. View/Edit an AutoPay Contract ... 190
4.5.3. Cancel an Existing Payment Contract... 192
4.6.
eSOP™
Advantage (Web Sales Order Entry) Overview...193
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
9
4.6.3. eSOP End of Day Report ... 197
4.6.4. eSOP Order History ... 198
4.6.4. CSR Administrative Page Access ... 200
4.7. Mobile ePay...200
4.7.1. How to Access ePay Mobile Site ... 201
4.7.2. How to Use ePay Mobile Site ... 202
4.7.2.1. Account Summary Page ... 203
4.7.2.2. Making Payment Against Outstanding Invoice(s) ... 204
4.7.2.3. Invoice History ... 208
4.7.2.4. Wallet ... 209
4.7.2.5. Navigation ... 210
4.8. Frequently Asked Questions ...211
Appendix A – GP Invoice Import Mapping ... 213
Appendix B – GP Customer Import Mapping ... 217
Appendix C – Tax Detail Mapping ... 218
Appendix D – Sales Person Mapping ... 219
Appendix E – Supported Document Types ... 220
1. Introduction
or many companies, handling invoices is still an old-fashioned paper process, despite the fact that the customer experience is becoming more web-based every day. By using Nodus ePay
Advantage, ERP users can avoid this disjointed method of invoicing, and send the invoices
electronically to their customers. The result is a streamlined and automated business process that reduces the billing cycle and collection cost; in addition to improving efficiency, cash flow and
communication.
ePay Advantage supports both Business to Business (B2B) and Business to Consumer (B2C). This means that the company sends invoices directly to the customer and the customer can log-in to the online bill pay web site, browse their invoices, view invoice details, process credit card and electronic check payments, and receive confirmation receipts.
The payment transaction will then be automatically applied against the outstanding invoices in the back office accounting system.
This introduction covers the following: PA-DSS Compliance
New Features in ePay Advantage Terms and Conventions
Additional Resources
F
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
11
1.1. PA-DSS Compliance
ePay Advantage meets all the security requirements for Payment Application - Data Security Standard (PA-DSS) to help user achieve PCI Compliance for credit card processing. This user’s guide describes the features and functionality of ePay Advantage. However, all security features that help make this
software compliant with credit card industry standards are described in the PA-DSS Implementation Guide for ePay Advantage.
In order to become and remain PCI Compliant, it is strongly recommended that the PA-DSS Implementation Guide is carefully read and all the recommended best practices are followed.
1.2. Tokenization (Optional)
ePay Advantage support Tokenization to Allow Off-Premises Secure Storage of Sensitive Credit Card information to simplify PCI Compliance self-assessment process.
ePay Tokenization is an alternative for merchants who require credit card security measures but are reluctant to invest in the higher levels of cost and maintenance required for internal infrastructure needs.
In contrast to the regular ePay, the tokenization version does not encrypt or store credit cards on the local database(s) and therefore, does not require additional hardware and software maintenance. The tokenization process starts when a credit card is processed and the information sent to a payment gateway. When this payment request is sent, the following happens:
1. The payment request is sent directly to the gateway
2. The gateway validates the card information , verifying that the account is active
3. If the card is approved, the gateway assigns a token – a random series of alphanumeric characters. As opposed to the standard credit card encryption process, this token is assigned to the credit card, which is not encryptable or decryptable.
4. The token is sent back to ePay software, where it is stored and used for any future payment processing whenever the credit card is needed.
Tokenization Support is controlled by a registration key for ePay Advantage. If ePay’s registration key include support of Tokenization, then from the Setup ID selects on ePay Admin Portal (Site Settings > Transaction Processing Options > ePay will only list the Setup ID(s) where ‘UseToken’ flag is set to TRUE on Nodus Connection Manager.
Figure 1-1 Tokenization Settings
If the registration key for ePay Advantage includes ‘Tokenization’ option, under System Information on Admin Portal (Reports > System Information), Token keyword will also be listed under Modules within Version Information section.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
13
1.3. New Features in ePay Advantage SP2
Change Item # Change Details
Change-#1 New Feature to Provide PayPal Hosted Page Support
Bundled with Tokenization version, ePay helps merchants achieve PCI Compliance much easier by collecting sensitive credit card information on a web form hosted by PayPal and pass them along with transaction data securely to PayPal server.
With Hosted Page, the point of entry for credit cards no longer belongs to the ePay site; therefore, it will reduce the complexity of PCI Compliance self-assessment process for merchants.
Change-#2 New Feature to Provide Credit Card Expiration Report and Email Notification Admin and Customer Support Rep (CSR) users will be able to access the expired card report for a list of expired and to-be-expired credit cards by a specified date range. The expired card email notification can also be manually or automatically sent out to customer(s) to avoid last minute transaction decline.
Change-#3 A New Theme with Enhanced User Experience
- Update Search Option to allow search transactions by Date Range or by Document Number
- Enhance Wallet Entry Selection with List View
- Added Optional Prepayment Capability into Outstanding Invoices list - Ability to Display or Hide page columns
- Reword Menus and Text Labels
- Update All Email Templates with Sample Messages - Removal of Account Summary Graphical Charts Change-#4 Admin Portal Configuration Checklist Wizard
Add a Configuration Checklist into Admin Portal to assist with setting up and configuring the ePay web portal.
Change-#5 New Feature to Support GP Term Discount
Synchronized Customer’s assigned Payment Term ID from GP Customer
Maintenance so term discount is accounted for when payment is paid by a specified discount date. Feature can be enabled or disabled if needed.
Change-#6 New Feature to Email Paylink as Express Pay Option
ePay is able to email a payment link that customers may click and make a one-time payment without having to login to ePay.
- Improved Forgot Password & Password Retrieval Process - Added additional level of security for Account Activation
- Ability to enforce security restriction for ePay’s Username and Password Change-#8 New Feature to Support eCheck Account Type
Ability to define the account type for eCheck entry, whether ‘Checking’ or ‘Savings’ Change-#9 Ability to Hide On-Hold Customers from Customer Lookup List
CSR user may choose to hide GP’s on-hold customer accounts from ePay’s Customer Lookup List.
Change-#10 Enhancement of User Management via Admin Portal - Ability to update admin user’s email address
- Ability to unlock a user login after maximum login attempts have been reached
Change-#11 Enhance Processed Payment Report
- Add Scheduled tab to list any payment that is still scheduled to be processed - Add Failed Attempt Count to list the number of attempts for reprocessing
and the reason why it failed to process. Change-#12 Add Additional Variables into Email Templates
[[[ShipToAddress]]]: Ship To Address [[[BillToContact]]]: Bill To Contact [[[PO#]]]: PO#
Change-#13 New Feature to Email Paylink Notification
Allow CCA (Credit Card Advantage) user to send a payment link to end-customer so payment information can be entered via ePay’s web page. Since credit card
information doesn’t have to be entered within Dynamics GP window, this will help simplify PCI requirements. (Available only on Tokenization version of ePay) Change-#14 Add Total Balance Due on Account Summary
Add ‘Total Balance Due Amount’ into Account Summary page so user can check the total outstanding amount for his/her account.
1.4. Terms and Conventions
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
15
TERMS DESCRIPTION
Customer/User People who browse the ePay website to make payments against their outstanding invoice(s).
Administrator/Admin User
ePay Administrator and/or other people who work on behalf of the merchant who operates and maintains the ePay website.
ERP users Enterprise Resource Planning system users, i.e., Dynamics GP customers Users
Wallet A section of the application where credit card and eCheck information is stored
SOP Sales Order Processing
RM Receivables Management
IVC Invoice Entry
CONVENTION DESCRIPTION
http://www.nodus.com Used to specify file paths and URLs ePay Nodus ePay Advantage
GP Microsoft Dynamics – Dynamics GP (formerly Great Plains)
RB Recurring Billing
RBP Recurring Billing Payment
SP Scheduled Payment
ESOP Electronic Sales Order Processing
AR Account Receivable
B2B Business to Business
CONVENTION DESCRIPTION
Disconnected mode This feature ensures that when ePay is disconnected to Dynamics GP accounting system, that customer transactions will continue in real-time without interruption.
Nodus Synchronizer A tool/utility that allows data, documents and records to synchronize between two systems -. specifically Dynamics GP and ePay Advantage 4.0
VAR (Value-added Reseller) A company that takes an existing product and adds ‘value,’ usually in the form of a specific application designed to work with the existing product. The value-added application is resold as a new product, or ‘package.’
Network Topology The arrangement or mapping of network elements such as links and nodes.
DMZ server Based on military usage of the term, but more appropriately known as a demarcation zone or perimeter network, DMZ server is a physical or logical subnetwork that contains and exposes an organization's external services to a larger, untrusted network, usually the Internet. The purpose of a DMZ server is to add an additional layer of security to an organization's Local Area Network (LAN); an external attacker only has access to equipment in the DMZ, rather than the whole of the network.
MSDTC The Microsoft "Distributed Transaction Coordinator" manages transactions that are distributed across multiple servers
COM Component Object Model is a Microsoft centric interface standard for software componentry introduced by Microsoft in 1993. It is used to enable interprocess communication and dynamic object creation in any programming language that supports the technology. The term COM is often used in the software development industry as an umbrella term that encompasses the OLE, OLE Automation, ActiveX, COM+ and DCOM technologies.
SOAP Simple Object Access Protocol and lately Service Oriented Architecture Protocol a protocol for exchanging XML-based messages over computer networks, normally using HTTP/HTTPS. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework so that more abstract layers can build on it.
Customer Master The customer’s master table that stores and maintains all customer records in an Enterprise Resource Planning system like Dynamics GP
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
17
CONVENTION DESCRIPTION
Failed status Occurs when an electronic document or some other form of data fails to be electronically communicated between systems
Sent(submitted) status An electronic document or some other form of data that has been successfully transferred to another system
Child Account A secondary account set up by the main account holder. For example, a company might have several websites under different names, selling different products. Each of these websites could be set up as a child account associated with the main account.
Token/Tokenization A random series of numbers and alpha characters assigned by a
payment gateway to a credit card for the purpose of securely processing credit card transactions.
1.5. Additional Resources
Contact your VAR or Nodus Technologies to ask additional support questions.
METHODS ADDRESS/PHONE
E-mail [email protected]
Web Site http://www.nodus.com
Telephone (909) 482-4701 and Dial 2 for Support
Fax (909) 482-4705
Mail 2099 S. State College Blvd. Suite 250
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
19
2. ePay Advantage Installation
Instructions regarding how to install ePay Advantage and its required components are located in the ePay Installation Guide. Please contact Nodus Support for a copy of this manual.
SSL Certificate Setup
It is highly recommended to configure ePay web sites to use Secure Sockets Layer (SSL) connections to ensure that both incoming requests and outbound responses are encrypted prior to transmission. After purchase and install a SSL certificate in IIS, do the following to automatically redirect visitors using HTTP to HTTPS:
1. Log on to IIS server that ePay web site is installed 2. Go to installed ePay web site folder
3. Open CustomizationUrl.config in notepad or any text editor 4. Add the following lines right above “</rewrites>”
<add name="ssl" virtualUrl="http\://(.*)" rewriteUrlParameter="ExcludeFromClientQueryString" destinationUrl="https://$1" redirectMode="Permanent" ignoreCase="true" redirect = "Domain" />
5. Save this file.
Username & Password Restriction Setup
Username and password length and strength can be enforced for users on ePay to lower overall risk of a security breach and provide better protection against customer’s financial data.
Follow the instruction below to setup a preferred length and strength for both username and password: 1. Go to the web server where ePay application is installed.
2. Go to the ePay Site folder (Example: C\Program Files\Nodus\ePay\ePay\SiteFiles) 3. From SiteFiles folder, go to Controls folder
Modify Username Expression: <td class="FieldValue">
<asp:TextBox SkinID="InputField200" ID="txtUsername" runat="server" MaxLength="50" meta:resourcekey="txtUsernameResource1"></asp:TextBox>
<asp:RequiredFieldValidator Display="Dynamic" ID="valUsername" runat="server" ErrorMessage="User Name is required." Text="*" ControlToValidate="txtUsername"
ValidationGroup="reg" meta:resourcekey= "valUsernameResource1"></asp:RequiredFieldValidator>
<asp:regularexpressionvalidator ValidationGroup="reg" id="val3Username" runat="server" ErrorMessage="Username must be between 6 and 20 characters starting with a letter and containing only letters and numbers"
Display="Dynamic" ControlToValidate="txtUsername" ValidationExpression="^[a-zA-Z]([\w\d\-\.\@]{5,19})$">*</asp:regularexpressionvalidator>
</td>
Modify Password Expression: <td class="FieldValue">
<asp:TextBox SkinID="InputField200" ID="txtPassword" runat="server" TextMode="Password" MaxLength="20"
meta:resourcekey="txtPasswordResource1"></asp:TextBox>
<asp:RequiredFieldValidator Display="Dynamic" ID="valPassword" runat="server" ErrorMessage="Password is required." Text="*" ControlToValidate="txtPassword"
ValidationGroup="reg" meta:resourcekey="valPasswordResource1"></asp:RequiredFieldValidator> <asp:regularexpressionvalidator ValidationGroup="reg" id="Regularexpressionvalidator1" runat="server" ErrorMessage="Password must be between 6 and 20 characters starting with a letter and containing only letters and numbers" Display="Dynamic" ControlToValidate="txtPassword" ValidationExpression="^[a-zA-Z]([\w\d\-\.]{5,19})$">*</asp:regularexpressionvalidator> </td>
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
21
3. Product Configuration Settings
3.1. Administration Settings
3.1.1. Default Admin Log-in
The default log-in credential for Administrator users: User Name: admin
Password: password
NOTE: For security purpose, please update your admin’s default password at initial login from Manage Users > Manage Users > Select ‘Administrator’ under Display users in role of > Click Reset Password.
Figure 3-0 Admin Mandatory Password Reset
3.1.2. Browse to Admin Site
Admin users are automatically redirected to the Admin Site upon login.
3.1.3. Documentation
ePay Advantage documentation can be accessed by choosing the Documentation menu selection from the main menu bar. Documentation available includes the ePay Advantage:
User’s Guide Release Notes Installation Guide
3.1.4. Site Settings
Path: Settings > Site Settings
All changes in this section are taken into effects by scrolling to the bottom of the Administration home page and clicking the Save button.
NOTE: Changes made to the Admin settings might also require the restart of Nodus Scheduler service on the ePay web server. User will get a prompt message from ePay if that action is required. (To restart the Nodus Scheduler, right-clicked on ‘Nodus Scheduler’ > Choose option ‘Restart’)
Figure 3-2 Restart Nodus Scheduler
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
23
Set up company information by filling out the form and clicking the Save button at the bottom of the page.
The Upload option allows user to browse to the location of a graphic file and upload the company logo.
The Remove option allows user to clear out the existing logo image from Admin Site.
Figure 3-3 Company Information
3.1.4.2. Transaction Processing Options
Figure 3-4 Transaction Processing Options (without Tokenization)
Figure 3-5-1 Transaction Processing Options (with Tokenization)
1. Mark any applicable option checkboxes (see table below for a detailed description) 2. From the Credit Card Setup ID drop list, select a setup ID used for credit card processing 3. Check the Accept credit cards box to allow customers to pay with credit card(s)
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
25
site; therefore, it will reduce the complexity of PCI Compliance self-assessment process for merchants.
4.1. By default, the option ‘Use PayPal Hosted Payment Page’ is unchecked, meaning the feature is disabled. Checkmark the option to enable the PayPal Hosted Payment Page with ePay.
4.2. Upon enabled, all the ePay controls where user enters credit card information will be replaced with PayPal Hosted Page as an embedded iFrame.
4.3. Populate the Currency Code supported for PayPal Payflow Pro gateway account. 4.4. Checkmark PayPal Live Mode Enabled box for Production usage.
5. From the eCheck Setup ID drop list, enter a setup ID used for eCheck processing. This optional setting is established at installation. If the Set up ID is not available, refer to the steps below to create a new Setup ID from Nodus Connection Manager.
6. Check the Accept eCheck box to allow customers to pay with electronic checks
NOTE: To add a new entry to both the credit card and eCheck setup ID droplists, use the following steps: Create Setup ID from Nodus Connection Manager
1. Navigate to Start > All Programs > Nodus Technologies > Nodus Connection Manager 2. Type the new setup ID in the Setup ID textbox
3. Click Save on the top menu
4. Close the Nodus Connection Manager 5. Navigate to Start > Run
6. Type the following: ‘iisreset’ 7. Click OK
8. Verify that the new setup ID appears in the appropriate droplist
ALTERNATE METHOD:
1. Navigate to Start > All Programs > Nodus Technologies > Nodus Connection Manager 2. Type the new setup ID in the Setup ID textbox
3. Click Save on the top menu
4. Close the Nodus Connection Manager
5. Recycle the App Pool used by the ePay website
FIELD DESCRIPTION
Credit Card Setup ID Allows selection of a payment gateway setup ID for credit card transaction.
Credit Card Transaction Type Permits the user to create Book or Sales
transactions. Once chosen in Site Settings, all sales transactions will use this option until changed here.
NOTE: The ‘Book’ transaction option is only for ePay application that has eSOP sales order processing module enabled.
Accept Credit Cards Activates the option to accept credit card payments.
AVS enabled When activated, ePay verifies the billing address used by a credit card transaction.
CVV2 Required The security code on the back of the credit card is required to be entered and will be validated when this option is chosen.
eCheck Setup ID Allows selection of a payment gateway setup ID for eCheck transaction.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
27
3.1.4.3. Content Management tab
Figure 3-6 Content Management
Click on the Current Theme link to bring up a list of out-of-box ePay theme options.
Figure 3-7-1 Content Management Default Themes
A custom look can also be created by making HTML changes described in the following section.
To implement a custom theme on the ePay Advantage website:
1. Navigate to the Apps_Themes sub-folder located in the: <installed directory>\EPay\Site Files folder on your web server (or wherever you have installed the application on your web server)
2. Open one of the default theme folders and modify the HTML in this location in the .css and/or .skin files
RECOMMENDED METHOD: A new theme can also be installed by taking the following steps: 1. Copy one of the existing theme folders
2. Name the folder to help identify the new custom theme 3. Edit the .css and/or .skin file as needed
4. Save the changes
5. Return to the Content Management section on the ePay Advantage website and click on the link to view the new custom theme
3.1.4.4. E-mail Setup
This section describes how to set up e-mail on your ePay Advantage site. 1. Enter e-mail server address in the SMTP Server Address text box
2. Enter e-mail server log-in credential (optional – if your e-mail server does not require user authentication) in the SMTP Server Login: text box
3. Enter a valid e-mail address in the Test Email Address text box to test the e-mail setup 4. Click the Send Test Email button.
5. Verify that the e-mail was received by the address entered in the Test Email Address text box
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
29
3.1.4.5. Payment Scheduler Options tab
The payment scheduler works in real-time 24 hours a day. The scheduler runs one transaction type (see the list transaction types below) at a time in a measured sequence established by the Scheduler Interval setting.
FIELD DESCRIPTION
Stop Processing Payment after
Enter the number of payment processing attempts. This sets the total number of times the scheduler will try to process a single payment transaction.
Example: If transactions failed to process twice, there would be no further attempts made at reprocessing if the option is set to 2. After the number of preset attempts, the payment document status will be set to Failed.
Re-Process Payment after
When a payment is declined or unable to be processed, the user can set the time gap (in minutes) between attempts before the scheduler reprocesses the failed payment transaction.
Scheduler Interval Allows the user to establish a period of time between processing individual payment transactions.
The following payment types are run concurrently by the scheduler: Scheduled Payments
Recurring Billing Invoices AutoPay contracts Installment Payments
3.1.4.6. Landing Page Options tab
The option gives the user the ability to select the default landing page for both CSR and Customer users on ePay Advantage after the user logs in. To utilize this feature:
For the CSR user, select the drop-down list and choose a preferred landing page For the Customer user, select the drop-down list and choose a preferred landing page
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
31
3.1.5. Back Office Settings
Path: Settings > Back Office Settings
3.1.5.1. Back Office Integration tab
The Back Office Connection settings facilitate communication between the website and Dynamics GP Back Office. Click the Save button to make any changes permanent.
FIELD DESCRIPTION
Back Office Connection This field is filled in by Nodus during the initial installation. Thereafter, if there are any changes to the client’s Transact Service back office URL/Domain, the customer must update the URL and click the Save button at the bottom of the page.
Store ID Click the Reset button to acquire a Nodus Synchronizer-generated Store ID.
Functional Currency Click the Import Functional Currency link to import the existing functional currency into ePay from Dynamics GP.
IMPORTANT: This must be done prior to using ePay Advantage.
Submit Documents to Back Office in real-time
Leave this checkbox marked to allow transactions to be processed in real-time.
If unchecked, the Nodus scheduler will submit the documents to Dynamics GP. If the Nodus scheduler service is stopped, all documents will stay in ‘Pending’ tab until scheduler service is restarted.
Figure 3-11 Back Office Integration
3.1.5.2. Customer Options tab
The Customer Options section enables the user to configure reference information such as the customer number. Click the Save button at the bottom of the Back Office Settings page to make any changes permanent.
FIELD DESCRIPTION
Customer Prefix Allows a unique customer identifier to be associated with a newly created customer. All newly created customer accounts integrates into Dynamics GP will have the predefined customer prefix so user would know these accounts were not generated from Dynamics GP.
NOTE: This function is only used with the eSOP module where CSR user can create new customer account on ePay.
Customer Number Length Allows the length of the customer account to be adjusted as need. Dynamics GP allows maximum length of 15 characters as customer number.
NOTE: This function is only used with the eSOP module where CSR user can create new customer account on ePay.
Allow Customer Registration Marking this checkbox allows customers to register themselves without administrator or CSR assistance. However, the
customer must exist in Dynamics GP before they can self-register/activate their account.
IMPORTANT: If unchecked, the customer will not be able to activate their account.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
33
Figure 3-12 Customer Options
3.1.5.3. Payment Options
Similar to Customer Options, the Payment Options section sets up the payment document reference identification information. Click the Save button at the bottom of the page to save any changes.
FIELD DESCRIPTION
Payment Prefix Allows the user to enter a unique prefix to help identify the
payment number. Type “NEW”, “PYMT” or whatever is appropriate for your company’s use. This will be the prefix for the GP payment receipt number.
Payment Number Length Define a character length for the payment document number, including the prefix. Type ‘16’ in the Payment Number Length box to allow payment document with 16 characters.
NOTE: Dynamics GP allows maximum of 17 characters for Cash Receipt Payment document.
Payment Batch Prefix Allows the user to enter a unique prefix to identify the payment batch. Type ‘EPAY’ in the Payment Batch Prefix box unless a different batch prefix identifier is desired.
NOTE: Payment’s Batch Name in GP will have the following format <Specified Batch Prefix + CurrentDate> (ex: EPAY20090101)
Finance Charge Prefix Allows the user to enter a unique prefix to identify the finance charge document number. In the Finance Charge Prefix box, type ‘FC’ unless a different finance charge prefix identifier is desired.
NOTE: This setting is only used by Installment Payment module.
interest batches. Type ‘UNAPP’ in the Unapplied Interest Batch Prefix box unless a different prefix identifier is desired.
NOTE: The Finance Charge settings are only required if you have Installment Payment module where ePay would create a finance charge document in order to apply the accrued interest payment.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
35
3.1.5.4. Card Name Mapping
This area is where credit card names are mapped for Dynamics GP credit cards. Leaving a credit card field blank will make that card type unavailable to users on the website. These fields will be blank by default after ePay Advantage is installed.
1. Type in the credit card name as shown below for each credit card type to be accepted.
NOTE: Users who choose not to accept a specific credit card type can leave the text box blank for that credit card. The populated card name must exist and match with Dynamics GP credit card names located in GP under Tools > Setup > Company > Credit Cards
2. Click the Save button at the bottom of the page
NOTE: Once the card name has been used on a payment transaction, it will be grayed out and user will no longer be able to update.
3.1.6. Feature Settings
3.1.6.1. Payment tab
This page contains configuration options related to payment features.
NOTE: These configuration options are global options and once they are enabled, the settings will apply to all ePay users (both CSR & Customers).
OPTIONS DESCRIPTION
Allow partial payment Permits a partial payment amount against an outstanding invoice.
Allow deposit payment Enabling this feature allows ePay to accept deposits from customers for payment deposit. Deposit payments are not associated with any outstanding invoices. These payments integrate into Dynamics GP as unapplied payment receipt(s).
Allow Pay Later Enabling this feature lets ePay allows user to schedule the payment for a future date.
Allow Apply AR Documents Enabling this feature will enable users to apply any existing credits/payments/returns (if available on their account) to outstanding invoice(s).
Allow Term Discount Enabling this feature will enable ePay to support Dynamics GP Term Discount (if applicable).
Once enabled, term discount related information such as Discount Available, Discount Date, Discount Taken will be available to users on Outstanding Invoices page.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
37
3.1.6.2. Customer Wallet tab
This page contains options for customer wallet maintenance.
OPTIONS DESCRIPTION
Validate on new Wallet Entry This option is to ensure the credit card information entered by user is valid prior to save the information into ePay database.
If enabled (checked), the credit card validation option causes a transaction of type "Authorization" to be processed for a small amount (typically $0.01) against the customer's account when a new Wallet entry is added by a customer. No money will actually be taken out of the customer's account.
IMPORTANT: Please be aware that there will be Payment Gateway transaction fee associated with this transaction.
Credit Card Expiration Warning Checkmark the option ‘Automatic Credit Card Expiration’ to enable ePay to send out email notification automatically if there are expired card(s). By default, this option is
unchecked.
Once enabled, user can choose the date(s) for the system to send out ‘Credit Card Expiration Notification’ email.
Select the number of months prior to expiration to send out advanced notification to avoid last minute credit card decline for customers.
Checkmark the box ‘Send for Credit Cards on Contracts only’ to ONLY notify users with existing (inactive and active) recurring contracts with expired card.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
39
3.1.6.3. Past Due Invoices Reminder Options tab
This option gives the user the ability to send out automated payment reminders via e-mail (to view the email template, see Past Due Invoices Reminder in the Email Templates menu). The user can specify the day or date when the payment reminders are sent. To utilize this feature:
1. Check/uncheck the Enable Payment Reminders box to enable/disable the feature. 2. Select the Weekly or Monthly option.
3. For Weekly, select the preferred day(s) to send out the payment reminder 4. For Monthly, select the preferred date(s) to send out the payment reminder 5. Click the Save button at the bottom of the page
NOTE: Users can select either ‘Weekly’ OR ‘Monthly’ - not both. Once weekly or monthly is chosen, the user can pick which day of the week or date of the month to send out the reminder e-mail.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
41
3.1.6.4. CAPTCHA tab
This option gives an extra security feature for ePay site. It enables the tool to verify whether an actual human user or computer bot is using the site in order to block internet spam programs. Nodus is using the reCAPTCHA from Google, with the following needed to enable CAPTCHA with ePay:
The User would need to register for reCAPTCHA from the following link to get two keys:
http://www.google.com/recaptcha/whyrecaptcha ReCaptcha Public Key
ReCaptcha Private Key
ReCaptcha Theme: user can apply a theme against the Captcha by select from the drop-down.
OPTIONS DESCRIPTION
Enable CAPTCHA for user login If enabled, the CAPTCHA box will be displayed on the user login page.
Enable CAPTCHA for user registration If enabled, the CAPTCHA box will be displayed on the account activation page.
Enable CAPTCHA for Forgot Password If enabled, CAPTCHA is enabled for the Forgot Password page
Sign up for free Click on the link to be routed to Google reCAPTCHA account registration.
reCAPTCHA Public Key Populate the public key provided from Google reCAPTCHA account
reCAPTCHA Private Key Populate the private key provided from Google reCAPTCHA account
reCAPTCHA Theme The preferred theme or layout for reCAPTCHA from the drop-down list.
Tester After the reCAPTCHA public and private keys are entered, clicking the Refresh button will validate the keys.
Figure 3-16 CAPTCHA Setup Options
Figure 3-17 reCAPTCHA Sample
3.1.6.5. Grid Column Options
This option provides admin user the flexibility to control the display columns against Outstanding Invoices and Paid Transaction pages on ePay.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
43
Checkmark any checkbox(es)under ‘Hide’ will hide that column from the Oustanding Invoices grid and/or the Paid Transactions grid.
OPTIONS DESCRIPTION
Customer PO# GP’s Customer Purchase Order Number populated on the invoice document.
Discount Taken Discount Amount Applied against the Invoice Document if term discount is applicable.
Source GP’s Document Creation Source to identify the sales module the document was created from. (ie: SOP, RM)
Last Payment Date If there are multiple payments processed against an invoice, this represents the date of the last processed payment.
3.1.7. Recurring Billing Settings
Path: Settings > Recurring Billing Settings
This section allows the user to configure settings needed to successfully run the Recurring Billing module of ePay Advantage. Recurring Billing Settings consist of 2 sub-modules: Recurring Invoice and AutoPay (Recurring Payment).
NOTE: Recurring Billing (with both Recurring Invoice & Payment) is an optional add-on module in ePay Advantage.
3.1.7.1. Recurring Invoice tab
If company supports subscription model, Recurring Invoice module enables company to generate Recurring Invoice Contract for their customer(s). Based on the pre-defined frequency of the contract, Sales invoice/order document will be created automatically on a periodic basis. The created
invoice/order document will be seamlessly integrated into Microsoft Dynamics GP without any further user intervention.
The Invoice/Order document can be created with/without payment transaction. (See section 4.4.1 for more details)
FIELD DESCRIPTION
Contract Number prefix Allows the user to enter a unique prefix to help identify the type of contract within ePay.
Contract Number Length Enter the number of digits used in the contract number. The maximum number allowed is 16.
Invoice Number Prefix Allows the user to enter a unique prefix to help identify the ePay’s recurring invoice in the accounting system.
Invoice Number Length Enter the number of digits used in the invoice number. The maximum number allowed is 16.
Invoice Back Office Document Type Specify the type of invoice for newly-generated invoice documents from ePay. IMPORTANT: The invoice type MUST already exist in Dynamics GP
Order Number Prefix Allows the user to enter a unique prefix to help identify the ePay’s recurring order in the accounting system.
Order Number Length Establish the number of digits used in the order number. The maximum number allowed is 16.
Order Back Office Document Type Specify the type of order for newly-generated order documents from ePay. IMPORTANT: The order type MUST already exist in Dynamics GP
Default Site ID The specified site ID will be the default site ID on the RB Contract header for New Invoice Contract form.
Markdown Type Specify the type of markdown on the Recurring Billing Contract, whether by:
Amount: Currency amount off of unit price Percentage: Percentage off of unit price
Reactivate On-hold Contract If checked, user needs to provide the preferred method of handling the missing billing cycle during the on-hold period. There are two options:
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
45
Use Current Item Price If checked, the contract item price will be calculated based on the current item price imported from Dynamics GP.
If unchecked, the contract item price is always the contracted original price.
Generates Invoices if Payment Failed If checked, invoice with failed payment transaction (declined by the gateway) will post to GP with no payment line.
If unchecked, the invoice won’t be generated if failed payment is detected while running the RB Contract. User can view the error message and reprocess from contract view.
Required Contract Class ID for RB Contract If unchecked, the contract class ID is not a required field and does not need to be populated before a user can save the Recurring Invoice contract. If checked, the contract class ID is a required field and needs to be populated before a user can save the Recurring Invoice contract.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
47
3.1.7.2. AutoPay tab
AutoPay (Recurring Payment) module enables company to generate Recurring Payment Contract for their customer(s). Based on the pre-defined frequency of the contract, payment (Cash Receipt) document will be created automatically on a periodic basis. The created payment document will be seamlessly integrated into Microsoft Dynamics GP without any further user intervention.
The AutoPay contract can also be used by customers themselves if they would like to schedule their own automatic payment.
Fill out the fields described in the accompanying table.
FIELD DESCRIPTION
Contract Number Prefix Allows the user to enter a unique prefix to help identify the type of contract within ePay.
Contract Number Length Establish the number of digits used in the contract number. The maximum allowed is 16.
Payment Applying Rule When a payment is received, this setting establishes how payment receipts are applied against customer account in GP.
EXAMPLE: ChooseOldestFirst to apply payments to the oldest outstanding invoice document first. Other choices include:
Unapplied – the generated payment will integrate into Dynamics GP as an unapplied payment (Cash Receipt).
LatestFirst – apply generated payment to latest invoice first.
SmallestAmountFirst – apply generated payment to invoice with smallest amount first.
LargestAmountFirst – apply generated payment to invoice with largest amount first.
Allowed Payment Amount Options Permits several options for accepting payments for AutoPay. This will be the global option available on AutoPay across all users (both CSR and Customer).
NOTE: At least 1 option must be checked. Admin user can check more than 1 options.
Fixed Amount: If a user selects this option, then Nodus AutoPay will process the specified payment amount based on the defined frequency basis of the contract.
Based on Invoice Due Date: If a user selects this option, then Nodus AutoPay determines the payment amount based on the invoice due date. If the due date is less than or equal to the system date, then the invoice’s payment will be processed.
Based on Invoice Document Date: If a user selects this option, then Nodus AutoPay determines the payment amount based on the invoice document date. If the document date is less than or equal to the processed system date, then the invoice’s payment will be processed.
Based on All Outstanding Invoices: If a user selects this option, then Nodus AutoPay determines the payment amount based on all existing posted outstanding invoices (including invoices with future document date)
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
49
3.1.8. Installment Payment Settings
Installment Payment module enables company to generate Installment Contract for their customer(s) to provide financed plans & options. Based on the pre-defined frequency of the contract, payment (Cash Receipt) document will be created automatically on a periodic basis. The created payment document will be seamlessly integrated into Microsoft Dynamics GP without any further user intervention. The Allow CSR to select Setup ID option permits a different Setup ID to be chosen for specific payment gateways such as Verisign, USA ePay, Authorize.Net on installment payment contracts. If the option is unchecked, then CSR user will not be able to pick a Setup ID during installment contract creation and update.
NOTE: This is an optional add-on module in ePay Advantage.
3.1.9. Sales Order Entry Settings
Path: Settings > Sales Order Settings
eSOP (web-based Sales Order Entry) module enables company to generate invoice and order document for their customer(s) from the web. The created invoice/order document will be seamlessly integrated into Microsoft Dynamics GP without any further user intervention.
Enable the settings according to the information on the accompanying table. To make changes permanent, click the Save button at the bottom of the Sales Order Settings page.
NOTE: This is an optional add-on module in ePay Advantage.
3.1.9.1. Sales Order Entry Settings tab
FIELD DESCRIPTION
Default Site ID The default site ID information can be entered here. Once populated, the eSOP form will always have this site ID as a default value when the form loads. If no changes made, this is the warehouse site where inventory item will be allocated from.
Filter Items by Site ID This option allows items in product lookup list to be filtered according to the selected Site ID.
If unchecked, product lookup list will display all items that have been imported from Dynamics GP.
Batch Prefix Allows entry of a prefix identifier for Sales batches for all generated eSOP documents.
Submit Newly Created Customer to Back Office
With this option, newly created customer
information is either sent directly to GP right after creation or the customer data is sent together when the first order document is created and submitted to Dynamics GP.
Default Document Type An initial document type on the eSOP form, such as an invoice or order, is loaded when a user logs into ePay.
Show Cost Displays the cost (determined by the cost type) for a line item on the sales order form.
CONFIDENTIALITY NOTICE - The information contained in this document is confidential and proprietary. This document is to be used with the
understanding that it will be held in strict confidence and not used for reasons unrelated directly to the specific purpose of this document. No part of the document may be circulated or reproduced for distribution outside the Client organization without prior written permission from Nodus Technologies, Inc.
51
Show Cost Type This setting establishes the cost type for an item as available in Dynamics GP. There are two options: Current – current cost value of the item in GP Standard – standard cost value of the item in GP
Default Class ID Sets the GP class ID for new customers created in the sales order entry area.
3.1.9.2. Order tab
FIELD DESCRIPTION
Order Number Prefix Allows the user to enter a unique prefix to help identify the order number in Dynamics GP.
Order Number Length Establish the number of digits used in the order document number. The maximum number allowed is 16.
Order Back Office Document Type Specify the Order Type ID for newly generated orders from ePay.
IMPORTANT: The document type ID MUST already existed in Dynamics GP.
