Align
For funders, brokers and lendersTen reads free. No card.Three agents on every file

Every statement, read
like an underwriter would.

Three agents on every file. A reader that shows its work, a verifier that argues with the application, a tamper check that looks at the PDF itself. Then your sheets, your offer, your memo.

Wells Fargo · ···2210 · JuneReading
DateDescriptionAmountCategory
Jun 03SQUARE INC DEPOSIT 240603+4,812.40
Jun 03ONDECK ACH PMT 8821−349.00
Jun 04STRIPE TRANSFER ST-K92+2,105.00
Jun 04ONDECK ACH PMT 8821−349.00
Jun 05OVERDRAFT ITEM FEE−34.00
Jun 06ONLINE TRANSFER FROM SAV+1,500.00
Jun 07KABBAGE LOAN PROCEEDS+12,000.00
Jun 07AMEX EPAYMENT REFUND+212.19
$6,917.40True revenue, these rows
1 · dailyPositions found
Reading…Opening + rows = closing
ReaderRead 3 pages, 84 rows, the running balance agrees.
VerifierDeposits match the application within 4%. No duplicate months.
TamperProducer is the bank's. Fonts consistent. Clean.
Fig. 1 — June, read in front of you. Hover a row to see the page and line it came from; click a category to reclassify it and the month's figures recompute in place.
What it does
8 sto read a statement with a text layer, start to reconciled
3agents on every file: reader, verifier, tamper check
100%of figures pinned to a page and a line you can open
$0.50a read on Scale, every agent and every seat included
  • Text layer or scan
  • Running balance reconciled
  • Positions and cadence
  • True revenue
  • NSF and negative days
  • Daily balance
  • Tamper signals
  • Sheets and offers
  • Deal memo
  • Statements by email
  • Plaid feeds
  • Funder marketplace
The reader

It reads the page, not a guess about the page.

The text layer when there is one, OCR when there is not. Columns found by geometry, rows by their lines, every amount tied back to a box on the page you can open.

Any layoutChase, Wells, BofA, credit unions, statements printed to PDF. The reader learns a bank's layout the first time and keeps it as a template.
Scans, through OCRA photographed or scanned statement goes to the metered reader under the document's name; the desk carries on as if it had a text layer.
Reconciled, or it says soOpening plus every row must equal closing. When it does not, the rows that broke it are marked and their confidence halves.
Categorised by what it isRevenue, transfers, loan proceeds, refunds, lender pulls, NSF and fees. Reclassify a row from the ledger and the month recomputes.
Provenance on every figureClick a number in the report and the statement opens beside it with the line highlighted. Show the page, not the parser.
Positions and cadenceEach lender, its cadence, typical pull, pace a month, share of revenue, and a stopped date when the pulls stopped.
The verifier

Someone has to argue with the application.

The verifier reads the record on the file — stated revenue, positions, time in business — and holds the statements to it. Months are compared to each other; duplicates, gaps and the month that does not fit are named. It writes findings in sentences, not codes.

  • Deposits against stated revenue, with the difference
  • Duplicate and missing months across the file
  • The tamper check: producer, fonts, spacing, arithmetic, a score and a band
  • Judge again after any change, in one click
Fig. 2 — What the agents said about one file, in the order they spoke. Every line is written to the timeline on the record, so the next person reads the same argument.
Sheets and offers

Your guidelines, as rules the desk applies.

Write a sheet the way you would explain it to a new underwriter: months required, balance floors, NSF ceilings, holdback, positions. Every file is judged by every sheet and the figure that decided each rule is right there. The offer is priced from the sheet the file passes, with comparables from your own funded book, and you counter it inline.

  • As many sheets as you have paper grades
  • Thresholds under each figure in the report
  • Approve, counter, ask for more, or decline, on the record
  • The deal memo, one page, from the file
Fig. 3 — One sheet, and the figure that decided each rule. The offer under it is priced from the sheet the file passed, against comparables in your own funded book.
Intake

Statements that file themselves.

Forward a submission to the desk's intake address and its PDFs land on the right deal, are read and verified, and the timeline says who sent them and when. A merchant who connects their bank through Plaid gives you months of clean rows with no PDF at all.

  • Email intake, matched to the deal by application
  • Plaid pulls with the same categories as a PDF read
  • Broker to funder: submit a file to another desk and see the decision
  • Remittance on funding, pulled on the schedule the offer set
01A submission arrivesThe subject names the deal, the PDFs are statements, the file exists or is opened.
02The desk reads itEach statement is read and verified; a failed read says why on the timeline.
03You open a finished fileFigures, positions, findings and sheets are waiting. Judge and send.
Against the usual ways

Three ways a desk reads a statement.

A scrubbing team, a parsing API, or agents that do the underwriter's own checks and show their work.

On every file
A scrubbing team
A parsing API
This desk
Time to a finished read
Hours, in a queue
Minutes
Seconds; scans in under a minute
Who checks the arithmetic
A second person, sometimes
Nobody; you get rows
Opening + rows = closing, or the bad rows are named
Where a number came from
Ask the scrubber
A page number, at best
The page and the line, opened beside the figure
Positions and their cadence
Typed into a sheet
Tagged rows; you count them
Each lender, cadence, pull, pace, share, stopped date
Argues with the application
If someone remembers
Not its job
Stated against observed, duplicates and gaps, in sentences
Your sheets and your offer
Spreadsheets
Your problem
Judged by every sheet; the offer priced from your own book
Cost per statement
Salaries
Per page, per bank, per seat
One read, from $0.50; every seat, every agent
Rates

One read, one statement.

Every plan has every agent, every seat, every feature. Plans meter reads; packs top them up and never expire.

Starter

$0to start

Ten statements on us. No card.

  • 10 statement reads
  • Every agent: reader, verifier, fraud check
  • Sheets, offers and the deal memo
  • Statements by email
Start free
Most desks

Growth

$199/ month

For a desk that reads every day.

  • 250 statement reads a month
  • Unused reads roll over while you subscribe
  • Plaid pulls and OCR of scans included
  • Team seats, no per-seat charge
  • Email support, same day
Start Growth

Scale

$499/ month

For a shop that funds at volume.

  • 1,000 statement reads a month
  • Everything in Growth
  • Funder marketplace and submissions
  • API access and webhooks
  • Priority support
Start Scale
50 reads$1.58 a read · never expires
$79
250 reads$1.20 a read · never expires
$299
1,000 reads$1.00 a read · never expires
$999
Questions
How long does a read take?
A statement with a text layer reads in seconds. A scan takes as long as the OCR pass, usually under a minute for a few pages. The timeline shows each step as it happens.
What if the reader gets a row wrong?
Change its category from the ledger; the month's figures, positions and the sheets recompute. Rows the arithmetic disagreed with are already marked for you.
Can I bring my own guidelines?
Yes. Sheets are yours to write and edit in the desk: months, balances, NSFs, holdback, positions and more, with a threshold under each figure of the report.
Do you keep the statements?
They live in your workspace's own bucket so the page can be opened beside any figure. Delete a statement and its rows, bytes and timeline go with it.
Is there an API?
The desk runs on the same API the workspace uses. Scale includes API access and webhooks; write to us for the reference.

Open the desk.
Drop a statement in.

Ten reads on us, no card. Your first file is read before you finish the coffee.