Use case
Tax returns, pay stubs and statements to spread-ready rows
Income and balance-sheet lines mapped to your spreading schema — with an income check on top.
The problem
Spreading means retyping: tax forms, pay stubs and statements each hide the same income in different boxes.
- 01Form variety. Tax returns, W-2/1099 equivalents, pay stubs and statements — every source formats income differently.
- 02Box hunting. Analysts hunt Box 1 vs Box 5 equivalents and gross-vs-net across pages of dense forms.
- 03Stale pay stubs. A three-month-old stub passes unless someone checks the pay date against policy.
- 04Inconsistent totals. YTD figures that don't foot with pay-period amounts slip into the spread unnoticed.
The solution
Fieldry maps every income source to spread rows with validation and an income reasonableness check.
- 01Form-aware mapping. Tax forms, stubs and statements each parsed to gross, net, employer and period fields.
- 02YTD footing. Pay-period amounts checked against year-to-date totals; breaks flagged with evidence.
- 03Recency rules. Pay dates parsed and checked against your freshness window automatically.
- 04Spread-ready rows. Clean rows feed scorecards and spreading templates directly — no retyping.
Spreading checks
Search the spreading checks.
See what each check returns.
Every check Fieldry runs across income documents.
Form-aware mapping
Tax forms, stubs and statements each parsed to gross, net, employer and period fields.
YTD footing
Pay-period amounts checked against year-to-date totals; breaks flagged with evidence.
Recency rules
Pay dates parsed and checked against your freshness window automatically.
Command preview
Spread rows
Every income source mapped to the same row shape regardless of form layout.
Anatomy of a spread file
An applicant submits a tax return, two pay stubs and a bank statement — three layouts, one income story to verify.
Fieldry maps all three to spread rows, feet YTD against periods, and flags the stub that outruns the return.
- InputReturn + stubs + statement
- OutputSpread rows + income check
- ReviewExceptions only
From document pile to spread rows
Analyst spreads from cited rows; exceptions carry their evidence.
AnalystYTD footed, recency checked, sources compared — breaks flagged with proof.
FieldryGross, net, employer and period mapped to one row shape with evidence.
FieldryIncome documents arrive in three layouts with different period conventions.
Document
4 milestones, newest first.
Key benefits
Spreads built from cited rows instead of retyped boxes.
No retyping
Form boxes become rows automatically — analysts review instead of transcribe.
Footed totals
YTD and period math checked before it reaches the scorecard.
Freshness enforced
Stale stubs flagged by rule with parsed dates as proof.
Multi-source truth
Return vs stub vs statement disagreements surface side by side.
Spread your toughest applicant
Run return + stubs on free credits and check the rows against the forms.
Get startedRelated products
Related use cases
Related industries
Financial Spreading questions, answered
The questions teams ask most about financial spreading.
Talk to usTax returns, pay stubs, bank statements and employer letters. Each maps to gross, net, employer and period fields in one row shape.
Pay-period amounts are footed to year-to-date totals; breaks flag with both sides cited for analyst review.
Stub vs return vs statement figures compare automatically; disagreements show side by side and your policy decides.
Yes — clean rows export as JSON/CSV or flow via API into spreading templates and credit models.
Parse your first document today
One API for extraction, evidence and automation.