KUBRA overviewKUBRA Consoles
Migration to KUBRA
Presented by Sue Klich and Sherry Stork
• All companies currently using CDS Global will migrate to KUBRA
• Both companies are currently owned by Hearst Corporation• KUBRA manages solutions for more than 500 clients – which equates to
approximately 50 million customer relationships• KUBRA serves three of the five largest U.S. utility companies, and two of the
top ten insurance companies• KUBRA will operate as an independent unit of Hearst Magazine; but will work
closely with CDS Global as migrations are completed.
• KUBRA Payment Processors Supported:• Chase Payment Tech (CPT) is KUBRA’s payment processor of choice
• Pricing based on quantity and all companies migrating will be on the same “rate plan”
• Don’t worry! You don’t have to change processors! Other Certified Payment Processors Include:• First Data• TSYS• Vantiv• Worldpay
• Terminology ‐ CDS Global to KUBRA:• CDS Global eBill (end users) = KUBRA Self Service Portal• CDS Global eBill customer portal (CSR) = KUBRA User Console• KUBRA Administrator = i‐dox Admin (this will be a separate site from User
Console)• CDS Global ezPost payments = KUBRA iConnect• CDS Global Magtek Card reader = KUBRA Ingenico iSwipe
• Card Reader = iSwipe• Must have Chase Payment Tech as the processor• Must utilize Ingenico iPP300 EMV card reader
• PCI compliant device• Keypad for card not present – information encrypted before
leaving the device• Supports chip technology• Purchase through KUBRA
• Utilized for both AM Point‐of‐Sale and CM Payments
• MACC Requirements:
• Open port 1433 to MACC• Support new real‐time balances from CM into KUBRA• Support new real‐time payments from KUBRA into CM• Real‐time means the balances will update between CM and KUBRA
and you will see a pending payment row in CM.
** port may already be open if you are currently subscribed to MACC’s web self‐care, web reporting or TMS
• MACC Requirements (cont’d):• Must be on CM 17.2 or above
• New payment method of ePay replaces credit card• Tokens and auto‐pay credit cards are eliminated in Customer Master (CM) –
(recurring payments moved to KUBRA)• All recurring credit card payment will be processed through KUBRA
these payments will be included in the nightly file from KUBRA • Nightly Batch Processing Unchanged
• eBill (i‐dox) enrollments• eBill ( i‐dox) auto‐pay• Payments
• one‐time, recurring, IVR, SMS, ezPost• Real‐time payments that already exist in Customer Master will be ignored
preventing duplicate payments
Admin Console
KUBRA allows an administrator to customize notifications that will be emailed to the customer in both English and Spanish. KUBRA provides a template or default script.
Admin Console
Admin Console
Setting up groups allows you to create messages or marketing campaigns for different groups.
Admin Console
KUBRA will allow you to create different user roles.
During migration, the Administrator will want to review roles and make any necessary changes.
Admin Console
Admin Console
User Console
User Console
User Console
The Document Manager will show bills associated with a customer and you will be able to print, download, or email the documents.
User Console
Cash Only Accounts means your customer will not be able to make a payment through KUBRA –however, they would still be able to log in to view their bill and balance.
User Console
No longer have to be an administrator to view reports. Access to reports will depend on roles assigned.
User Console
The Notification Manager allows you to view user and system‐generated notifications sent via e‐mail and SMS to subscribers. The information found within the Notification Manager is very useful when troubleshooting anaccount experiencing issues receiving notifications regarding eBills. The activity on the account cantell you if they are or are not logging in correctly and whether they are actually viewing documents.
User Console
The Transaction Manager application allows for reporting on suspected fraudulent activity and tools to mitigate initial and ongoing fraudulent payment activities. Through the use of “rules” iDoxs can block suspicious payments based on particular account numbers, bank account, card numbers etc.
User Console
The Help feature in KUBRA offers lots of information on how each console within KUBRA works. Including Video Tutorials and printable PDFs
Self – service Portal
Self – service Portal
Self – service Portal
Self – service Portal
User Console
An awesome new feature in KUBRA is called “Impersonate”. As the CSR in the User console, find the customer and click ‘Impersonate’.
User Console
Impersonate allows the CSR to see the customer’s account. The CSR cannot change any information, however the CSR will be able to see what your customer is seeing and walk them through the screens as needed to see the
information on their account. This feature can help you ‘train’ your customers!
Migration To
KUBRA
• eBill (i‐dox Admin / User Console)• Validate KUBRA Setup Matches CDS Setup
• Company colors• Company logo• Active CSR’s and associated Security• Access to customer accounts
• Set up Notifications• Default notifications available, or customize the notifications to meet the
needs of your company
• eBill (i‐dox Admin / User Console)• Validate KUBRA DataMatches CDS Data
• Login information• Account number• Profile information (name, email address of records)• Account current and statement balance • Payment data (credit card, bank routing)• Payment history• Payment auto‐pay on or off
• eBill (i‐dox Admin / User Console)• Validate KUBRA Transaction Processing
• Register a new account• Change password and e‐mail address of record• Make one‐time payments and reversals• Payments reflected in Portal and CM• Add new payment account (credit card and bank routing) • Activate and deactivate accounts (i‐dox and payments) • E‐mail notifications distributed properly
• Validate CM Processing• Register new account (prior and after 1st billing)• Make one‐time payments and reversals• Payments reflected in Portal and CM• Import nightly batch files
• Verify reports (balance report from KUBRA will be different)• Verify one‐time payments are not duplicated
• Go Live Decision• Validation above is completed• Verify Paperwork with KUBRA Approved• Pick a migration date
• Night of Migration Activities:• CDS:
• Will send remaining data files to KUBRA, including tokens and recurring Auto Pay.• Deactivates processing• Provides data of activity since latest update to:
• Payment Processor• MACC• KUBRA
• Night of Migration Activities:• KUBRA:
• Uploads data provided from CDS• Moves company from pre‐production to production• Activates processing
• Night of Migration Activities:• MACC:
• Verifies company is on Customer Master version 17.2 or above• Switches processing from CDS to KUBRA within Customer Master• Switches processing to send nightly data to KUBRA (not CDS)• Verifies port is open and database connectivity for real‐time payments/balance• Sends file of recurring Customer Master credit card records/tokens to CDS Global. They
will add the recurring customer information from the CDS Global system and send the file to KUBRA
• Night of Migration Activities:• Company:
• All credit card payments must be processed prior to migration• Modifies web link from CDS to KUBRA • Deactivates Magtek card readers and installs Ingenico card readers• Verifies access to KUBRA Portal and customer data
• Following Business Day Activities to validate:• KUBRA Portal• CM• AM Point‐of Sale
• Where are we now?• MACC is currently working with a beta company • MACC will initiate approximately 12 company migrations to evaluate the
migration process, including the paperwork process, approval process, setup requirements, and process from start to finish
• Note and modify migration process to prepare for all live migrations
Questions ???????????