Finance customer and retail partner self-service portal
The financing client or trading partner submits an application with the purchase details. It is clear what is still missing from the examination and what response the funder has provided.
The application channels do not link the data saved and the shortcomings required for a specific product. The customer repeats the actions, and the employee explains which version of the application is being examined.
How the solution works
- A direct customer or partner submits a purchase-linked funding application.
- The funder verifies the application data and submits a request for addition or a financing decision.
- The client provides the requested information or confirms the contract, and the funder returns the current state of the application and the contract.
Key challenges
- The customer re-submits the data already in their possession
- Affiliate channels integrated only partially
Solution capabilities
Purchase and application
The customer or partner provides the funded object, amount and data needed for the product. A later change keeps the connection to the previous submission.
Supplement to documents
Only the documents required for a particular application are requested, indicating the defect and the way it is presented.
Partner Submission Channels
The partner portal and backend apply the same rules of submission and rights. Repeated sending does not create a second application.
Submission of the decision
The client is shown the conclusion passed by the funder and another action is required. The preliminary proposal is separated from the final commitment.
Transfer of contract
Confirmed data is transferred to the contract process, and the signing and payout states return from the systems responsible for them.
Business context
- The customer re-submits the data already in their possession
- The application channels do not link the data saved and the shortcomings required for a specific product. The customer repeats the actions, and the employee explains which version of the application is being examined.
- Affiliate channels integrated only partially
- The partner passes the application on a file or a separate portal, but the results and weaknesses of the checks do not return to its daily workflow. Data is transferred by employees by hand. The partner and funder repeat the adjustments, and the customer waits for a response at the time of purchase. As the scope of application administration work grows, along with the flow.
- Financing application is easier to complete at the time of purchase
- The buyer can apply through the seller of a car, equipment or other property. When the partner sees the necessary data and the answer of the funder, fewer questions have to be passed through several channels. The customer can proceed more smoothly with the purchase, and the seller knows which solution is still needed for the transaction.
Core features
- Purchase and application
- Supplement to documents
- Partner Submission Channels
- Submission of the decision
- Transfer of contract
Key integrations
- Application and Risk Framework
- The application version, the status obtained and the specific disadvantages.
- Identity and Document Tools
- A specific action requires authentication and secure document transfer.
- Partner sales system
- Purchase and Object Data, Queries, and Cancellation Identifiers.
- Funding and contract process
- Authorised application, offer, contract and payout status.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Number of re-asked application data
12–42%Decreasing
This illustrative scenario assumes that 30-60% of errors can be addressed through the data and rule checks described. That share is assumed to fall by 40-70%. Company data is needed to verify both the addressable share and the resulting change.
Count due to a form or transmission gap in repeatedly requested fields per application.
Partner Application Data Transfer Time
12–36%Decreasing
This illustrative scenario assumes that 30-60% of manual data entry and handover work can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.
Measure employee minutes per partner's application for transfer and verification.
Share of funding applications prepared for consideration
2–8%Increasing
Sample starting part - 60%. Assumption: 15-30% of the remaining cases involve incomplete submission of funding documents; a solution would help resolve 20-40% of these cases.
The prepared applications are divided by all the funding applications started by the same group. Approved applications that have turned into sales are evaluated separately.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- Customers do not know what documents or data are missing for their funding application.
- The data provided by the trading partners are re-assembled by the employees into a funding system.
Project scope and implementation
Portal actions are combined with the funder's application system and integrations already provided to partners. If an existing channel allows reliable submission of data and tracking of the application, its capabilities are used. Additional functions are created for specific client or partner actions that are missing.