Turn a stack of paystubs into one income figure
Every document tested before a single number is counted.
Lend on take-home pay, not the gross on the stub.
Tax, benefits and garnishments come out before the payment is set.
Every stub grouped by employer, then totalled over the period it actually covers.
Garnishments and benefit deductions read off the stub as their own lines.
Overtime, tips, and commission split from base wages. Non-income excluded.
The account shows whether payroll is still arriving, in about 50 seconds.
How the monthly figure is calculated.
Total the counted stubs, then divide by the calendar they cover — never by the pay frequency.
Group the stubs by employer
Each counted stub joins the stream of the employer that issued it. Two jobs stay two income streams, and each is totalled on its own.
Measure the span they cover
From the earliest pay period to the latest. A period nobody uploaded is still inside that window, so it stays in the arithmetic as a gap.
Divide the total by the span
Not one paycheck times a pay frequency. A missing stub lowers the monthly figure instead of disappearing from it, so it is never higher than the documents support.
Defend the figure line by line.
Checked against themselves, and against your applicant.
One bad stub is not averaged away.
A file is only as good as its weakest document, so nothing clears on the strength of the stubs that happen to look right.
Catch the file that is too thin or too old
A stack short of what you require, or a newest pay date months behind, is caught alongside the forensic and identity reads.
A clean stub cannot cancel out a flagged one
Four good reads do not pull a warning back, so a file never clears because the problem was outnumbered.
Set your own document minimum and pay-date window
How many documents a file needs, and how old the most recent pay date may be, are settings you own. The status moves when your policy does, not when ours does.
Where the income figure arrives.
One finished result, three ways out: into your LOS the second the run completes, onto a dashboard when a file needs a closer look, and onto a page for the deal file.
The webhook fires the moment the run finishes and one call returns the file, so the income figure and its status reach your LOS before anyone reads a stub.
Every earnings line with the type Kora put on it, so an analyst can check what counted toward the monthly figure and what was left out of it.
A dated document carrying the verified figures and the employers behind them, for the file and for whoever opens it later.
Collect once for the whole application.
One secure request, reused as conditions are added, with every result on the same applicant record.
Watch one income figure come off a stack of paystubs.
Book a demo, tell us what you require before funding, and we’ll walk one stack end to end: every document tested, then one income figure, delivered through the dashboard, a PDF, or the API, with a webhook the moment analysis completes.