Platform Feature · LOS Integration

Built to connect to your loan origination system.

PPE1 includes a documented LOS integration API. Your LOS sends a loan; PPE1 checks it is ready to price, runs it through the same engine your users already trust, and keeps a synchronized copy that your loan officers open in place from the LOS, signed in as themselves.

Documented integration API Configured, not coded Runs in your environment LOS-neutral

From your LOS to a priced loan

The same engines price a loan that arrives from your LOS as price a loan entered by hand, so there is one answer for every loan.

  1. Your LOS sends the loan to your PPE1 through the integration API.
  2. PPE1 checks that it is ready to price. If something is missing or cannot be read, the reply says what, in plain language your team can act on.
  3. The engines price it and PPE1 keeps a synchronized copy of the loan.
  1. A loan officer opens it in place from the LOS through a launch handshake, signed in as themselves, with the same roles and scope they have everywhere else in PPE1.
  2. A change to a locked loan sent by the LOS goes to the lock desk as a change request, priced as of the lock.
Your PPE1, your connection, your data

Because you license PPE1 and run it in your own environment, the connection is yours too: your LOS talks to your PPE1 through your own API access, and your loan data never leaves your control. The integration is LOS-neutral. It is designed for any LOS that lets your organization read and update loans through its API.

What your IT team configures

The connection is set up through configuration. There is no custom code inside PPE1, so your mapping survives every upgrade.

Field mapping
Each LOS field your loans carry is mapped to the PPE1 loan field it feeds, once, for your LOS.
Value mapping
Coded values are translated, so a property type or occupancy code in your LOS means the same thing in PPE1.
Validation messages
Every send is checked against what pricing needs, and every problem comes back named in words your team understands.
Open in place
A launch handshake opens the loan in PPE1 from inside the LOS, signed in as the user who clicked.

A locked loan stays under the lock desk's control

The LOS can keep sending changes. It cannot quietly move a locked price.

Changes become requests

When the LOS sends a change to a locked loan, PPE1 raises the same lock change request a loan officer would, on the same Lock Ledger. A change that does not affect the locked price is applied at once by the system. One that does waits for the desk.

Priced as of the lock

The request is priced against the guidelines and the rate sheet in force on the day the loan locked, so the desk sees what the change really costs under the commitment it made.

The Ledger, inside the loan

Opened from the LOS, a locked loan shows a read-only Lock Ledger tab with the full history of the lock and its pricing. The desk's own figures appear only for users entitled to them, and the server enforces that.

Read how the desk works the request on the Lock Desk & Lock Ledger page.

Questions an IT team asks first

Does loan data leave our environment?
No. You run PPE1 in your own environment, and your LOS talks to it through your own API access.
Do we write code inside PPE1?
No. Field and value mapping are configuration, so nothing in PPE1 has to be changed or rebuilt for your LOS.
Which LOS?
The integration is designed for any LOS that lets your organization read and update loans through its API.
What does a loan officer see?
The loan opens in PPE1 from the LOS, signed in as themselves, with their own roles and scope.
What if a send is incomplete?
PPE1 says what is missing or unreadable, in plain language, so the loan can be corrected and sent again.

Talk to us about your LOS.

We will walk your IT team through the integration API and the mapping, on the live platform.

Request Private Access

← Back to all products