Episys

What do you like best?

The eDocs documentation provided to use that software. Two version exists: Offline and Online, thus referring the Docs make it easy to use the software.

The support from vendor Jack Henry and Associates is awesome.

The data reports are generated quick, and search functionality for searching account numbers, names, external loan account numbers and ssn is great.

There is hardly any lag while searching records, and data is returned quick which is impressive.

What do you dislike?

The debugging of code is difficult. The language this File system database support is Power-on, which is less known also difficult to debug.A recent change from support's policy is somewhat inappropriate, when something not so important functionality breaks and if we reach out to support, they request to sign a billable agreement, saying they will charge even for reviewing the problem.

There is no version control for poweron code. Difficult to keep up with who made what changes.

Recommendations to others considering the product:

My experience with Episys has been good, the support is great. Only problem is the programming language used inside Episys which is poweron, there is not much documentation on internet for errors resolution.Also, there is no easy way for debugging the code, as there is no industry standard code editor for poweron. One more thing which is a flaw is, poweron does not have a version control like gitHub or anything similar.

What problems are you solving with the product? What benefits have you realized?

Keeping bank transaction records and querying them for reports. Storing data for accounts, shares, loans and credit cards data for customers/members.

Process transactions, post amounts, transfer funds, and everything else which is needed to run a financial institution.