Loan applications typed into the origination system, and checked
After a demonstration, OpenAdapt can type a loan application into an origination system as a program, then read the stored application back by a separate route to check it. On Frappe Lending, an open-source loan system, all 6 synthetic applications passed that check, 3 of them after a screen change. Each of 5 injected faults stopped the run before saving.
Updated 2026-11-19
Use the API first
If your origination or servicing system has a usable API for the step, use it. OpenAdapt is for the form the system still makes a person complete.
The Frappe Lending test
We ran the test on a local test copy of Frappe Lending 16.2.0, which is open source, with synthetic applicants. Each run created its loan application and nothing else. Before a run counted as Done and checked, a separate API read, a database read and an audit of which tables changed all had to agree.
- 6 of 6applications Done and checked
- 3 of 3still checked after a cosmetic screen change
- 5 of 5injected faults stopped before saving
We include the table-change audit because a check that confirms only the fields you typed can miss an extra record. Our research on checkers covers that kind of miss.
Technical details
This test ran on OpenAdapt Flow 1.23.0. All 6 runs returned VERIFIED, which means that a read through the system's API, with its own sign-in, agreed with a direct database query and with an audit showing no other table changed. The 5 injected fault cases returned HALTED before the save, and we kept no video of those stops.
In practice
Frappe Lending has a full API, which we used only to check what OpenAdapt typed on screen. On a system like that, you would use the API for the entry itself.
Where this stands
We tested it on Frappe Lending, which is open source, with synthetic applicants.
Sources
- OpenAdapt on Frappe Lending 16.2.0 (open source), 16 Jul 2026, synthetic applicants: 6 of 6 loan applications checked through the API, a database read and a table-change audit (3 normal runs, 3 after a cosmetic screen change); 5 of 5 injected faults stopped before saving.
See it on your process
Bring a task your team types every day. We'll tell you whether it fits and what a test on your own system would cover.