Skip to content
Stafflo.ai
Buy an audit
Stafflo.ai
Lending

Multi-Lender Submission Desk

Sends one application to every lender you're empanelled with, in each lender's format, paced so portals don't lock you out, and tracks every reply in one place.

The pre-check

Each lender's published criteria, checked before anything is sent

The file for Arun Bandaru, APP-DEMO-0150, a personal loan of 2,75,000 rupees over 36 months, on its Lenders tab. Godavari Demo Finance Limited is selected and marked Criteria met; its published criteria are open, each with what the file says, such as Minimum income 25,000 rupees a month: met (26,000 rupees a month) and Bureau score 700 or above: met (790). Below, Deccan Demo Bank Limited can't be selected, marked 1 criterion not met, with the note that the pre-check decides nothing about credit and Not met: Minimum income 30,000 rupees a month (this file: 26,000 rupees a month). On the right, a card titled Send this file to 5 lenders lists the five lenders with each one's format and number of fields, the signed-in person waiting to send, and the button Send to selected lenders.The real screen, on synthetic data
A criterion not met is named with the file's own value; the pre-check decides nothing about credit

Demo built on synthetic data.

1 of 5: The pre-check

The problem

The same application goes into five portals in five formats. Portals throttle at peak hours, uploads half-finish, and the status of each file lives in someone's WhatsApp.

What it does

Pre-checkBefore anything is sentKiran Varma, personal loanDEMOV5813KGodavari Demo FinanceIncome, age, city and scoreMetDeccan Demo BankEvery published criterionMetKrishna Demo SFBEvery published criterionMetTungabhadra Demo HousingLends for homes and property onlyNot metHampi Demo BankBureau score 742, needs 750Not metSend to selected lendersThree selected

It checks the application against each lender's published criteria before anything is sent.

One applicationKiran VarmaDeccan Demo BankSent onceMusi Demo FincorpABCDESent onceGodavari Demo FinanceSent once

It submits to each lender once, in that lender's format, paced to its portal's limits.

Deccan Demo BankKiran VarmaConditionsBank statement forthe last 6 monthsFile timelineKiran VarmaSent14 Oct, 10:02Acknowledged14 Oct, 10:41ConditionsTaskBank statement,last 6 monthsFrom the letter, p1

It reads lender replies and conditions into one timeline per file.

ToKiran Varma, by SMSAboutYour file with Deccan Demo BankApprove and sendDrafted by the toolNeeds a personNever draftedRejectionHampi Demo BankAsks whyKiran Varma

It drafts routine status updates to the applicant. Anything about a rejection goes to a person.

Try to break it

On the call we'll trigger these, live:

  • A lender's portal throttles at 9:30 a.m. Submissions slow down and finish; none are dropped.
  • A lender changes a form field. The submission stops with a clear message instead of sending half a file.
  • Two executives upload the same applicant. The second upload is caught.
Our copy of the formKrishna Demo SFBFull namePANLoan amountMonthly incomeThe lender's form, todayKrishna Demo SFB portalFull namePANLoan amountNet monthly incomeNet monthly incomeLender form changed: field net_monthly_incomeStopped before sendingNothing reached the portal: no half-filled file

Where it runs

An office computer or a cloud account in your name.

Who else does something like this

UiPath sells software that automates lending work around a lender's existing loan origination system, from application intake to LOS updates.

The Submission Desk keeps a record of every file sent to every lender and can't send the same file twice.

The rules it respects

Lenders stay responsible for their service providers under RBI's Digital Lending Directions, so every submission is logged for their audit.

What our tests measured

How we test

These figures come from test runs on Google's Gemini (gemini-3.5-flash-lite), a hosted model, on synthetic data. We'll add runs on a local model.

Scenarios where every file went to each lender once and every submission was accounted for100%
Files that reached a lender twice, or applicants stored twice0
Half-sent files a lender received0
Facts read correctly from lenders' replies98.75%
Fields a reply doesn't state, left empty100%
Replies about a decline sent to a person100%
Updates put in Draft ready that needed review or a person0
Median time to read one reply2920 ms
  • Run on 15 October 2026
  • Model: gemini:gemini-3.5-flash-lite
  • 407 examples
For your engineers
Engines
Reconciler, Extractor, Gatekeeper
Sealed mode
Test passed: with sealed mode on, it refuses every outbound connection except to the model you've approved.

Data flow

The DSA's loan files (synthetic)Executive uploadsa loan fileDuplicate checkPAN-format ID, productPre-check by ruleeach lender's criteriaExecutive sendsto chosen lendersForm checkthe lender's fields todayReconciler engineonce each, pacedTimeline per filesends, replies, tasksLender portalsten, simulatedLender repliesemails and lettersExtractor enginepage and line, in codeGatekeeper enginedeclines to a personExecutive approvesroutine updates onlySMS gatewaysimulatedaudit_log
Ask about the Submission DeskStart with a pilot