BytePro Enterprise

Centralized administration

Keep control of processes with centralized administration via the SQL Server database.

Changes in user permissions, tables (such as the loan programs table), and custom documents are quickly propagated throughout the company; there is no need to manually copy configuration files. In addition, users in distant branches can be disabled immediately.

Validation rules

Validation rules are enforced when the status of the loan is changed, ensuring that the loan is complete and accurate before it enters the next stage in the origination process.

Validation rules are incredibly flexible and can be customized to meet the unique needs of your business. Mistakes can be prevented early by requiring loan parameters to meet the requirements of the loan program.

Audit log

The audit log ensures accountability by tracking every time a field changes. The log records

• Who changed the field
• The time the field was changed
• The new value of the field  

Print log

The print log is updated every time a document is printed or e-mailed.

The log records

• The date and time the document was printed
• Who printed it
• The document description
• Whether the document was printed or e-mailed.

You can use the print log in conjunction with validation rules to prevent a user from handing off a file until all required disclosures have been printed.

Prevent modification of individual fields

You can limit modifications to loan data based on the type of user and the status of the loan file, ensuring that users do not change information inappropriately. An entire file, or just individual fields, can be made read-only.  

Access control to screens, documents and services

Even though a particular set of users may need access to a loan file, you may want to restrict them to certain screens and features. For example, you may not want your loan officers to view the profitability screen or the loan's closing documents.  You can remove those documents from view permanently, or just at some file statuses.

Loan lock-down

Loan files are stored securely in the SQL database, so users can be prevented from copying them to their laptop or USB drive.

Users can only view loan files that are assigned to them -- they won't even know about loan files that aren't.

An administrator can prevent users from deleting loan files, and an administrator can even undelete loan files if an authorized user accidentally or maliciously deleted them.

Lightning Fast Reporting

Easily create comprehensive management reports that let you quickly assess the state of your business in real time.

Because all loan data is stored in a SQL server database, reporting on a large number of loans is lightning fast. In competing LOS software, report generation can be quite slow if loan files are stored individually on the hard disk.

In addition, because data can be centralized in a single database, there is no need to run separate reports for data stored in multiple branches.

Internet access without a VPN

BytePro Enterprise's "Web Services" feature enables remote users to securely connect to the BytePro Enterprise database using a standard Internet connection; no VPN is required. With the BytePro Enterprise application installed, remote users can edit files, order services and print documents just as if they were in the office. Users can be configured so that no data is stored locally, eliminating the possibility of data loss through theft of computer equipment.

Software Development Kit (SDK)

The BytePro SDK lets you develop add-ins that integrate directly into the BytePro user interface. 

The SDK can also allow a stand-alone application to interact with BytePro loan data.

For more information download the SDK Guide.  

Offline file creation

The administrator can allow selected loan officers to start loan files on their laptop computers without being connected to the SQL Server database. When the loan officers return to the office their loan files are uploaded into the main database. All loan data stored locally is encrypted for security.

Users can belong to multiple organizations

Users can belong to more than one organization in the organizational hierarchy, and they can have different roles and permissions at each organization. The administrator has the flexibility to grant a single user extensive permissions for one organization and restricted permissions for another.