Skip to main content
All CollectionsGetting Started
FAQ about Loanapp Capability
FAQ about Loanapp Capability

Learn more about Loanapp's capability from these FAQs.

Kate Gubbins avatar
Written by Kate Gubbins
Updated over 4 years ago

1. Loanapp Capability 

1.1 Can Loanapp process backchannel messages? 

Yes. We will process your Backchannel messages and:

In the case of a broker submitting from a third party, the Backchannel messages go back into that third party system.

In the case of a Loanapp Direct Broker (i.e. using Loanapp by logging into it directly, the backchannel messages are displayed in Loanapp.

To implement backchannel messages, we will need XSD for expected Backchannel format; XML samples of all types of messages you send.

We have Backchannel APIs that we can provide. We support both REST and SOAP methodologies. We can send through all requirements and documentation so that you can simulate on your end/configure and test. You will need to configure your system with our endpoints etc.

1.2 Do brokers need a user ID & password to access Loanapp?

If using Loanapp directly, a user needs to be set up with user credentials to be able to login. Logins are always username = email address; password = password set by user upon invite.

We have a number of permission levels that can be set for each LENDER user which gives them various rights to use different Loanapp functionalities.

With the correct permissions, Lender users will be able to add, edit and delete brokers/users. Click here for an article on how you can setup broker access and here for an article on how to set up brokerages. 

1.3 How do we manage brokers in Loanapp? 

There is no need for you to manage brokers if they are submitting via an aggregator, this is because their credentials come directly from the aggregators’ database.

If brokers are submitting via Loanapp Direct, you (or Simpology) will need to set up all the brokers with credentials. Brokers receive an invite as per this article.

1.4 How do we reset passwords in Loanapp?

With the right permissions, you are able to re-set passwords for your users, like so:

1.5 Who has responsibility for broker management & maintenance in Loanapp? 

Simpology is happy to manage the bulk upload of your brokers when you launch, and to help with user accessibility on an ongoing basis. However Loanapp has been designed for Lenders to be able to manage user access themselves. 

NOTE: A related question is who's responsible for Lender Users in Loanapp?

The answer is only Simpology is able to create new Lender users and set their permissions. This is because we do this at the “Global” level and only we have access to this. 

1.6 Does Loanapp have different levels of user access?

Yes, we do. Click here to learn about the different user roles and their permissions/functionalities.

1.7 What reporting capability is available in Loanapp? 

Currently, there is no in-built reporting capability in Loanapp; and reporting is a bespoke function.

1.8 What reporting capability do we need in Loanapp? 

Let us know!

                                        ______________________

2. Backchannel Messages 

2.1 How will backchannel messages be communicated to the broker? 

As per 1.2 above, if submission is via an Aggregator CRM, backchannel messages are sent back to the Aggregator CRM (inserted into the relevant customer file).

If submission is via Loanapp Direct, backchannel messages are sent back to, and displayed in, Loanapp.

2.2 How do we provide Backchannel messages in Loanapp? 

Backchannel messages are generally generated by the Lender Loan Origination System (e.g Lendfast); and sent to our Backchannel endpoint for processing by our gateway. Generally they will be REST or SOAP messages.

2.3 How and when do we trigger Backchannel messages?

Rules for when backchannel messages are created and the creation of those messages are generally set within your LOS. These rules will largely be related to your internal loan processing workflow. 

2.4 Who is responsible for triggering Backchannel messages? 

You, the lender.

                                        ______________________

3. Application Submission 

3.1 In what format will Loanapp supply application data? 

Part of our configuration process is the creation of an XSLT which is the mapping of our Loanapp generated data format (CAL 2.x) to the data format of the Lender internal system. For example, our XSLT would transform Loanapp data to Lendfast data. In this way we always deliver data that is able to be consumed by your LOS. 

If you choose not deliver data electronically to your LOS, the alternative is that your loan processors have the ability to download the Application data and supporting documentation directly from Loanapp. Click here to learn how.

3.2 How will applications be received by the lender?

There are various ways for you to receive applications from Loanapp. For example, we can submit directly into your back-end or you could set a central email address for everything to be forwarded there. 

3.3 How will applications be processed by the lender?

You tell us! We would love to understand the process to ensure we are enhancing and not hindering the workflow. 

3.4 How will application data be entered into the lender's system(s)?

Generally, by mapping into your back-end and insert electronically.
                                        ______________________

4. Supporting Documents

4.1 How will supporting documents be uploaded into the lender's system?

You will need to specify an electronic methodology for delivery of supporting documents, otherwise we will send an email notification to a specified email address for each application when a broker has completed the supporting documents upload and the documents are ready to retrieve.

The email will have a specific subject which identifies the submission the supporting documents belong to, something like "Submission/Supporting Docs are now available for download for Loanapp application - XXXX", where XXXX is the Broker Application Reference Number. 

The loan processor will then be able to download the supporting documents. 

4.2 Who will receive and process these documents? 

Generally, it is the credit assessor assessing the loan application. 

4.3 How will lender-specific documents (letter of offer/contracts etc.) be provided to the broker/customer?

Simpology does not handle loan documents. This is a function of the bank, outside of Loanapp functionality. 

4.4 Can this be integrated into Loanapp?

Not currently, but we would be able to create the functionality pretty easily.

4.5 Will Simpology provide user documentation for Loanapp?

Yes, we have a full knowledge-base of articles and tutorials for self-help, check it out here. We also have a training series that we put new brokers through from the day of signup. 

4.6 Will Simpology provide system administration documentation for Loanapp?

Yes, this is largely what is provided during procurement/security analysis. Also we have documentation on all of our APIs, processes, etc.

                                        ______________________

5. Simpology 

5.1 Contracts with Simpology

Simpology has two contracts to be reviewed:

  1. A guidebook configuration contract (for the setup of the Lender Guidebook, integrations, Loanapp etc)

  2. A guidebook subscription contract (for the ongoing Loanapp and Guidebook services, covers all change management and submissions)

5.2 Data security/legal obligations

We have a full suite of documentation to provide that will most likely cover all the security questions you can dream of. We just need your requirements sent to us and we can send them through.

5.3 What requirements are there for customer data security? 

The main requirement we have across all banks is that customer data is not to go outside of Australia. We host with AWS and have active-active redundancy across two data centers, within Australia.

All data is encrypted at REST and we backup and store encryption keys separately. 

We have a whole lot of information we can give you about customer data security.

                                        ______________________

6.1 Training

6.1.1 What are the training requirements for brokers?

Brokers are generally trained by the Lender and the Aggregator. 

Simpology generally trains the trainer… i.e the lender or aggregator. However we want to be involved in training the initial roll out to brokers - as mentioned in 4.5 above.

6.1.2 Who will create training materials for brokers?

On the Lender's products/process etc… the Lender. We think broker understanding of what to expect in terms of communications from the Lender post-submission, throughout the assessment process, will be really important. 

Simpology has a training series which can be branded for the Lenders' purposes.

6.1.3 Who will deliver the training? 

Simpology will conduct training of the Lender staff and BDMs. And also be involved in training the pilot group. 

6.1.4 How will training to brokers be delivered? 

Simpology has an email-based training series and an online knowledge-base. We also offer LIVE CHAT for brokers to get help from us at any time. 

6.2 Training for internal resources

6.2.1 What are our training requirements for Loaapp? 

Credit and processing staff; and BDMs are the key parties who should be trained on using Loanapp. Perhaps marketing and communications.

6.2.2 Can we use the same training material as the brokers?

It's largely the same resources that we use, with some extra materials that are specifically for Lenders. 

6.2.3 Can the same people deliver the training? 

Yes, it will be the same people.

6.2.4 How will internal training be delivered? 

By Simpology, or by trained Lender staff. 

6.2.5 Is there additional training for internal resources available? 

Let us know what you need, and we will do our best to accommodate. 

6.2.6 Are there additional training requirements for internal resources? 

Certainly some additional functionality that brokers do not have.

6.2.7 Who will be responsible for creating these training materials both for the Lender and the brokers?

Simpology has already created extensive resources. 

Did this answer your question?