Embedded financial spreading for lending platforms

Give analysts the workspace inside your product.

SpreadSpace™ Embed brings financial spreading and document review into an existing lending application. Your engineering team integrates the experience. Analysts use it to review the evidence, work through the spread and finalize the figures.

Keep the loan workflow in your application while adding a dedicated financial-analysis workspace.

The same workspace, inside your LOS

Bring the native SpreadSpace workspace into your loan origination system (LOS). Analysts get the same interface and financial-analysis features, with navigation that fits the application they are working in.

Embedded in your LOS
Native workspace

Build on the loan workflow you already have

A platform can own the borrower relationship and loan record without also building every part of the analyst experience.

SpreadSpace Embed fits the spreading and review work into that existing application. Instead of sending an analyst elsewhere to assemble the financial analysis, provide the relevant workspace alongside the loan they are already reviewing.

For the analyst, the question is still the credit. For your engineering team, the integration supplies the review interface and a defined path for receiving its approved output.

Choose the experience the analyst needs

The spreading workspace

Use the workspace when analysts need to organize financial information, examine the supporting documents and finalize a spread. The analysis takes place inside the embedded experience rather than in an interface your team must create from scratch.

The document-review panel

Use the review panel when the task centers on inspecting document information and its source. It provides a focused review surface without requiring that every step of your application become a full spreading workflow.

Select the surface around the user's task, rather than exposing the same interface everywhere.

Keep the review connected to the source

A financial summary is more useful when a reviewer can inspect what supports it. In the embedded analyst interface, source-backed figures lead to highlighted document locations. Supported derived figures can be examined through their contributing detail.

For example, a reviewer questioning a reported amount can inspect the evidence in the loan workflow instead of asking a colleague to identify the page and line in a separate message. The interface supports that investigation; the analyst remains responsible for the interpretation.

Receive the version the analyst approved

Finalization is a deliberate handoff, not merely the last time someone saved their work.

When an analyst finalizes a spread, your backend receives an event identifying the approved snapshot and retrieves that record through the API. The event points to the data; it is not the entire dataset.

If the spread is reopened, a separate event lets your system mark its stored figures as under revision. A later finalization produces the new approved version. Your integration can therefore distinguish work in progress from the figures it should use downstream.

  1. Review the evidence
  2. Finalize the spread
  3. Retrieve the approved snapshot

Access begins with your application

Your backend authorizes the embedded session for the relevant loan. Your application can identify the analyst using its own user identifier and retain the connection between that user and a finalized spread.

The integration supports React and plain JavaScript. Implementation documentation covers session setup and the available server SDKs, so your team can evaluate the integration against its own authentication and document-routing requirements.

Test integration behavior separately from document quality

Test mode uses seeded data and sample extraction results. It gives developers a way to exercise the documented integration without treating a sample response as proof of performance on live borrower files.

Evaluate extraction quality separately with representative supported documents. Evaluate the embedded experience by following a review through finalization and checking the result received by your system.

Questions about embedding SpreadSpace

Is the developer the end user?

No. Developers integrate the workspace; analysts and reviewers use it. A successful integration should serve both: a maintainable technical connection and a useful financial-review experience.

Must we embed the workspace to use the API?

No. API-only integrations can retrieve extraction results without embedding the analyst interface. Analyst-approved snapshots are created through finalization in the SpreadSpace workspace or embed.

How does the embedded session identify the analyst?

Your backend authorizes the embedded session for the relevant loan and can name the analyst with its own user identifier. That identifier is returned with a finalized spread, so your system can connect the approved figures to the person who finalized them.

Add the analyst experience, not another disconnected process

Show us where document review and financial spreading belong in your application. We can walk through the user experience, the approved-data handoff and the integration requirements together.