Skip to content
CompanyBook a call

Eliminate FHA interest curtailments.

Proxara finds every extension your FHA loans are entitled to and applies it while the loan is still in default, so the dates on the 27011 are the extended ones and the evidence is already in the claim file.

See it on your own casesHow it works

Works with

HUDFHAGinnie MaeExcelOutlookTeamsSharePointAcrobatAzureMicrosoft 365

The file gets built once, not at every handoff.

Keep the interest the rules allow.

Every extension identified, its conditions proved and its evidence attached, so the days still stand when the claim is reviewed.

See it on your own cases

Live in days, not quarters.

One installer in your own Azure tenant, running on the MSP files you already receive. Extended dates land in MSP’s own fields and your claims system, so nobody opens anything new.

How it works

From the nightly file to the claim file.

Inside your perimeter

It reads the MSP files, bankruptcy feed and attorney mail you already receive, with the court record alongside them, inside your own Azure tenant. The model that reads them has no route to the internet.

Grounded reading on your own infrastructure.

Schema-bound reading

Each document is read once, into a fixed set of facts: the event, its status, its dates and their roles, its conditions. The same document is never read again, and a person is asked only when a fact is missing or two sources contradict.

See it on a sample case

Prove accuracy before you commit.

Two runs on your own live loans before anything is priced.

1. Your live cases

Your live FHA foreclosures in one county, reconstructed from the court record.

Every stay and moratorium counted against HUD’s timeframes, with the page each date came from. Nothing from you, and no login.

See it on your own casesSee it on your own cases

3. Your whole caseload

Deployed in your tenant, with every live default read once.

The first run completes every position and writes it into your own systems. It is production from the first day, not a pilot.

See it on your own casesSee it on your own cases

It runs in your tenant. Proxara has no standing access.

Your own Azure tenant

One installer your administrator runs builds it in a resource group you name. No public ingress, no outside identities, and the reader has no route to the internet.

Only named hosts

It reaches only the hosts in a manifest your compliance team reads. Its one egress client refuses any other host and logs every call.

Immutable lineage

Corrections and specialist decisions are kept as history and never overwrite what came before. A reviewer can reproduce the exact position that supported a submitted claim.

Questions we get.

Why doesn’t my servicing platform do this?
It holds the dates someone typed into it. It does not read the records those dates came from, and it does not work out which extension the loan was entitled to.
Is this a chatbot on our files?
No. One pinned document-reading model runs inside your tenant and ties every date to the words on the page it came from. The deadlines are computed by code from Handbook 4000.1. Nothing is sent to an outside service.
What changes with Update 18?
From 10 November, a servicer can no longer file EVARS for an automatic extension and let HUD’s answer stand in for its own file. The claim file has to carry the evidence, which is what this produces.
Does it replace my specialists?
It replaces the digging. They answer the questions the record cannot settle and certify the claim, on finished work.
What happens at claim?
Block 19 and the comments are written into your claims tool from the record, and the evidence is filed in the claim file. Your specialist reviews and certifies.

Machine speed with human authority.

Go further.

How it worksOne case walked from the docket to the claim file.Security & ITWhere it runs, what it reaches, and what your administrator installs.SampleThe Docket Run report, and what lands in your own systems once it runs.