How to Automate Odessa

A lease is a contract, an asset and a tax position at once

Odessa builds the platform equipment and auto finance companies run on: banks with a leasing arm, captives behind a manufacturer, and independent lenders. One platform carries originations, servicing and remarketing, with portals for customers and dealers, analytics and its own AI layer.

The reason it takes a purpose-built system is that a lease is three things at once. It is a credit exposure to a lessee. It is a physical asset with a serial number, a location, a condition and a residual value somebody forecast years in advance. And it is a tax position, because sales tax, property tax and income tax each treat it differently and each has filing dates.

Get one wrong and the others go with it. A forklift written down against a residual the market will not pay is a loss booked at end of term, years after the person who signed it left.

The credit package is assembled one login at a time

The platform handles what happens once a fact is in the file. Getting the facts in is a person with a browser.

A credit analyst checks the lessee's standing against the secretary of state's register, then searches the same register for UCC filings against the equipment, because a competing lien changes the deal. Somebody emails the lessee's insurance broker for a certificate naming the lender as loss payee, then waits, then emails again. Somebody looks up auction results for the same make and model to test whether the residual on the sheet is near what the market pays.

After funding it does not stop. Certificates expire annually and somebody has to notice. UCC filings have continuation dates. Property tax assessments arrive from jurisdictions that each have their own portal. A lessee's accounts payable portal is where you find out whether an invoice was accepted, weeks before anyone calls it delinquent.

It is checking, one file at a time, and it competes with structuring deals.

Odessa

Certificates checked every renewal Insurance on financed equipment confirmed with the lessee's broker on a schedule, so a lapsed policy surfaces in the week it lapses.

Filings watched, not remembered UCC status confirmed against the state's own register after funding, with each continuation date raised months before the filing would lapse.

Residuals tested against the market Auction results for the same make, model and age read from public results pages and set beside the residual on the book.

Rate cards and scorecards are configuration, not verification

Odessa automates more of asset finance than most lenders configure, and that is the honest starting point.

Originations can be laid out by manufacturer, asset type and fee model, priced from a rules-based rate card, with deduping, sanctions screening and credit bureau pulls as their own frameworks. A rules-based scorecard sits alongside automated and manual decision tools, so straightforward paper moves and difficult files get looked at. Servicing carries billing and invoicing, contract management, funding and syndication, lien filing and a tax layer for sales, property, income and VAT. Remarketing handles terminations, asset collection, inspections and open-end settlements.

Every one runs on what has been entered, or fetched by an integration somebody built. The rate card prices what it is told the asset is. The scorecard grades the bureau file and the fields on the application.

The gap is verification against the outside world. Whether the certificate on file is still live. Whether the UCC search you ran in March is still clean in September. Whether the residual assumption survives an auction catalogue. Those answers sit on other companies' websites, published to anyone who logs in, with no feed behind them.

The asset can be watched for the whole life of the lease

A portfolio checked on a schedule stops being files you open only when something goes wrong.

Insurance certificates confirmed with each lessee's broker at renewal, so a lapsed policy on a financed excavator turns up the week it lapses, not the week it is destroyed. UCC filings checked against the state register after funding and before every continuation date, with the ones nearing expiry on a list and a dissolved entity caught before it becomes a collection problem.

Then the asset side, where the money is. Auction results for the same make, model and hour band read each quarter and set against the residuals on the book, so a drifted assumption shows while there is term left to act. Property tax notices pulled from each jurisdiction's portal before the appeal window shuts. A lessee's accounts payable portal read to see whether the invoice was accepted, so the first collections call is about a rejection, not an accusation.

The line is fixed and it is a regulatory one. Gathering evidence, comparing it against the file and preparing an exception list can run unattended. Approving credit, booking a lease and releasing funds stay with a person who has the authority.

Booking a lease is a decision, and it stays one

So the file arrives complete and current, and the analyst spends their time on the part that needs one. That division is the condition on which any of this is usable.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens the state register, the broker's portal, the auction results or the tax jurisdiction, reads each one, and puts the result against the file.

It runs on your schedule inside your own private environment, restricted to the sites you allow, with a record of every page it opened. No credit is granted, no lease booked and no money moved without a person approving it.

The workflows below are already built, and each one names the systems it opens.