Fintegral
The scenario desk The income desk The document desk The ULPI desk
Book a call
The document desk Intake Splitting Integrity Completeness In your LOS
The document desk

One upload in. An indexed file out.

A combined submission is split into named documents, checked for integrity and completeness, and written back into LendingPad or Encompass in your own stacking order.

Splitting Integrity Completeness LOS write-back
Book a call
F Document intake Splitting
broker-submission-final.pdf · 412 pages 1 upload
p.1–9
1003 · Loan application Signed · dated
p.10–81
Bank statements · business ••4471 Split into 24 statements
p.82–96
1120S · 2024, with K-1 Indexed
p.97
Photo ID · borrower Expires in 22 days
p.98–124
Entity docs · operating agreement Ownership 100%
Reordered to investor stacking order · 0 unclassified pages · 2 superseded copies marked
Indexed and stacked 412 pages → 18 documents Your naming convention · your stacking order
Written back · 34 fields
Sample submission. Figures illustrative.
A couple in their kitchen at home
01 Intake

The file arrives as one 412-page scan.

Non-QM submissions are thick and they arrive unsorted. Somebody opens the PDF, finds where each document starts and ends, names it, and checks whether anything is missing, stale or altered — before the file can be worked at all.

Indexing is the first bottleneck Nothing downstream starts until someone has read the file end to end just to name its parts.
Missing and stale surface late An expired binder or an absent CPA letter is usually found in underwriting, when the broker has moved on.
Altered pages read as ordinary A retyped amount or a reused statement header looks clean to anyone reading at speed.

Everything downstream waits on the index.

02 Splitting and indexing

Split, named, and in the right order.

Page ranges come from the documents themselves, not from bookmarks or separator sheets. Each document is named the way your team names it, and the file comes back in your investor’s stacking order.

Input
One combined PDF or many uploads — portal exports, phone photos, fax-quality scans, pages that arrive sideways
Recognition
Document type read from content, including handwritten and stamped pages, with the boundary page called out
Naming
Your own naming convention, per investor or per program — nothing renamed to suit us
Statements
Twenty-four months separated into twenty-four statements, each carrying its own period and account
Duplicates
Superseded versions collapsed to the current one, earlier copies kept and marked rather than deleted
Order
Investor stacking order applied, with anything unclassified listed at the top instead of buried
Output
Named documents with page ranges, an index manifest, and the extracted fields for the loan record
03 Document integrity

The page that reads as ordinary.

Every page is checked for how it was produced and whether it is internally consistent. Signals come back with the page, the reason and the evidence — flagged for review, not a determination.

Statement 09 · page 3 under review
01 02 03
Signal 01 · p.3 Review
Type mismatch inside an amount The closing balance is set in a different face and baseline from the rest of the column. Every other figure on the page matches the bank’s template.
Signal 02 · p.1 Review
Template reuse The header block is pixel-identical to a statement from an unrelated file, down to the account holder’s address line.
Signal 03 · document Review
A re-render, not an original No text layer and no bank producer metadata. The page is a 96 dpi raster, consistent with a screenshot rather than a download.
3 signals on 1 document · 17 documents clean · Sample file. Signals are flagged for review, not a determination.

Caught at intake, it’s a phone call. Caught after purchase, it’s a repurchase.

04 Completeness

What’s missing, and what’s expired.

The set is checked against the program’s conditions as it arrives. Missing items and dated documents come back while the file is still the broker’s to fix.

Condition set · 24-month bank statement program 18 of 21 cleared
1003, signed and dated p.1–9 Received
24 months business statements 24 of 24 Received
1120S 2024 with Schedule K-1 p.82–96 Received
Entity operating agreement p.98–124 Received
CPA expense ratio letter not in the file Missing
Homeowner’s insurance binder dated 41 days out Expired
Photo ID expires in 22 days Dated
Open conditions 3, listed for the broker
Sent at intake Sample file, figures illustrative
05 In your LOS

Where the index lands.

Write-back where the API allows it, an export where it doesn’t. Your LOS stays the system of record either way, and your indexing tool keeps working the way your team already uses it.

LendingPad
Write-back LendingPad Documents land in the loan file already split and named, with page ranges and extracted fields attached.
Encompass
Write-back Encompass Indexed into the eFolder against your own document names, stacking order preserved.
PDF CSV JSON
Export Anything else A stacked PDF plus an index manifest and the field record, where no write-back is available.

No new system to log into. The file shows up indexed in the one your team already has open.

06 How it works

Three steps at intake.

01 The submission arrives However the broker sent it — one combined PDF, a folder of uploads, or a portal export.
02 Split, checked, stacked Named documents, integrity signals, and the conditions still open — in one pass.
03 It lands in your LOS Written back or exported, with the manifest and the open conditions attached to the file.

The first person to open the file opens an indexed one.

A mother on the sofa with her two children at home
07 Book a call

Send us five files exactly as they arrived.

We’ll return them split, named and stacked to your order, with the integrity signals and the conditions we’d have raised at intake.

No integration, no commitment, about a week.

Scheduler not loading? Open it in a new tab