OpenAdaptLoan applications typed into the origination system, and checked
OpenAdapt can type a loan application into an origination system as a program, after a demonstration, and check the stored application another way. On Frappe Lending, an open-source loan system, 6 of 6 synthetic applications were checked, including 3 after a screen change, and 5 of 5 injected faults stopped before saving.
Updated 2026-10-18
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
Frappe Lending 16.2.0 is open source, on a local test copy, with synthetic applicants. Each run created exactly one loan application. A separate API read, a database read and an audit of which tables changed all had to agree before a run counted as Done and checked.
- 6 of 6applications Done and checked
- 3 of 3still checked after a cosmetic screen change
- 5 of 5injected faults stopped before saving
The table-change audit matters: a check that confirms only the fields you typed can miss an extra record. Our research on checkers is about exactly that.
Technical details
Run on OpenAdapt Flow 1.23.0, the engine version used for this test (the current release is 2.2.0). All 6 runs returned VERIFIED: 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. We kept no video of those 5 stops.
In practice
Frappe Lending has a full API; we used it only to check the screen entries. On a system with a full API, you'd use the API.
Where this stands
Tested on Frappe Lending (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 one task your team types every day. We'll tell you whether it fits, and what a test on your own system would cover.