SpreadSpace vs Ocrolus

One REST API with a dated version pinned per request, three hand-typed SDKs in TypeScript, Python and C#, fourteen signed webhook event types with automatic retries, and a skill file that lets a coding agent build the embed and the webhook receiver.

A webhook forwards every file that lands in a loan's inbox to an intake endpoint that resolves the borrower and the loan from your own reference, and a repeat upload of content already extracted is answered as a duplicate rather than processed twice.

Every transaction is extracted with its posting date, the description as printed, the signed amount, the check number, its kind and its position on the statement, and each one gets a page box so a click opens the statement with the row boxed. Wire and ACH descriptions split into who sent it, who received it and what it was for.

A balance for every day of the period with opening, deposits, withdrawals and closing, plus the statement's average, minimum and maximum daily balance and the number of days negative, so the liquidity cushion bands the lowest, average and highest balances with their dates. The liquidity view sits on the same canvas as the rest of the loan.

Five transaction signals, overdraft, insufficient funds, chargeback, returned item and service fee, are detected from the descriptions in severity order, tallied on every counterparty row, counted per month or per year, and plotted over the daily balance.

234 registered bank layouts plus a generic fallback, detection in three tiers, and every parse reconciled to the printed totals and balances before it ships, with an incomplete slice or a fee summary with no transactions refused with a stated reason rather than extracted.

Accounts the transactions reference with no statement uploaded are derived as undisclosed business accounts, named by bank and last four with the transactions that revealed each one, and the flag clears itself as statements arrive.

Transfers between the borrower's own accounts are decided by parsing the account tails out of the description and joining them against the roster of uploaded accounts, failing toward counting the cash rather than wrongly excluding it, so matched transfers are excluded from the operating numbers.

Every transaction resolves to a named counterparty from the structured rail fields first and the cleaned description otherwise, two sub-merchants settled by one processor never collapse into one, and each counterparty row carries money in, money out, net, transaction count, business type, class, relationship and a signal tally.

Operating income, operating outflows with 24 subclasses such as payroll, payroll tax, employee benefits, contract labor, rent, utilities, insurance, professional services, marketing, advertising, software, travel, vehicle, repairs, supplies, shipping, bank fees and cost of goods sold, other income, financing, owner draws and contributions, personal, investing, taxes, internal transfers, intercompany and affiliate transfers, neutralized checks, neutralized reversals and under review. Every class carries a direction and an opposite analog, so an advance and its remittance are a pair.

A fixed daily or weekly run of equal debits reads as a merchant cash advance remittance stream and a monthly varying run across three or more months reads as a term loan schedule, and the implied debt schedule states every relationship with advances, repayments, net, cost of capital, dormancy and the payment cadence, asserted only when at least three payment days exist.

An affiliate, an owner, an officer or a lender named on a tax return, a personal financial statement, a balance sheet or a debt schedule re-tags its matching counterparty at read time through a six rung bind ladder, so a return uploaded days after the statements moves the rows on the next read, and the document link on the counterparty row opens the naming line boxed.

Every row is classified optimistically and a review queue surfaces five candidate buckets, affiliate candidate, nondescript check, nondescript wire, internal transfer candidate and outlier, each with a one click reclassification and a materiality floor per class, while rows placed without confidence sit in the under review section.

Owner personal, discretionary and commingled spend is recognized from the memo phrases on the transactions and offered as add-back candidates for the analyst rather than reclassified silently.

An override of a counterparty's class or relationship is one row per loan and counterparty, survives every reprocess, is never re-inferred and stands above the registry and every heuristic. Overrides apply per counterparty or per transaction, in bulk up to 500 at a time, and come off one by one or all at once.

After an analyst accepts a link or confirms an entity, sibling rows already wearing that registry entity pool into the same relationship group without inference, and the same entity fold pulls only byte exact matches, so nothing is moved twice and nothing unreviewed is auto confirmed.

Every correction sits in one table with its source, and each row carries an undo that reverts what that action wrote while skipping keys an analyst hand edited since. In session undo and redo cover reclassify, merge, split, rename and section moves with a batch sweep undone as one step, and a reset returns the whole analysis to its system generated state.

Source-backed transactions open the statement page with the row boxed, from the spread and source-linked memo figures. Calculated daily balances and counterparty totals reveal their contributing rows and available source links.

Every line of Form 1065, Form 1120-S, Form 1120 and Form 1040 with their schedules, every Schedule K-1 in the packet, the supporting statement behind every overflow line and the per asset depreciation registers, so a large return yields several hundred lines with a box on every figure. Every parent return checks its own arithmetic, and a failing check ships as an underwriting signal beside the data.

Each K-1 is bound to its own supporting statements by a cascade of printed name, partner number, page order and capital account, and its recipient is matched to a person on the loan by identifier, name and address, so a K-1 that lands days later still reaches the right guarantor. No fuzzy person matching exists anywhere, so an unmatched name stays unmatched rather than guessed.

One statement of cash flows per return year is derived from the return, in operating, investing and financing blocks that tie to the change in cash on Schedule L. It renders as a bridge and as the formal three block table.

EBITDA starts from the company statements, from the return on a book basis or from ordinary business income on a tax basis, with add-backs that follow the basis, and DSCR is configured per entity and per year with debt service drawn from the Schedule L balances, the business debt schedule or the implied debt schedule from the bank statements, pro forma with proposed debt and historical.

Every property on Form 8825, across continuation sheets, and each property on Schedule E Part I becomes a row with income, itemized operating expenses and printed depreciation, with years side by side. Each property keeps its source lines, while Form 4562 and the depreciation registers provide the supporting depreciation detail in the return viewer.

Every affiliated and intercompany entity named anywhere on the business and personal returns lands on one schedule, ownership link or not, K-1 or not, from the ownership tables on Form 1120 and Form 1120-S, the issuer behind every K-1, affiliates named in return statements, the personal return's pass through and qualified business income rosters, and related party receivable and payable lines. The schedule feeds the entity roster and re-tags matching bank counterparties to intercompany with the naming line boxed.

The spread is a canvas rather than a form. Every chart, table, KPI card, text box, line and comment pin lands where the pointer releases, drags anywhere, resizes from any edge and magnifies on its own axis, and the canvas grows sideways and downward as the work needs it.

The bank tab offers 20 fixed tiles, the five main cash flow buckets, the liquidity cushion, customer and vendor concentration, the undisclosed accounts roster, the implied debt schedule, the counterparty graph and nine other buckets, plus 7 KPI cards and one investigate graph per financing relationship on the loan. Each tile has a graph face and a ledger table by month unfolding to weeks, with a period selector over the data's real month range.

Up to twenty five analysts work one board with live cursors and comment threads pinned to a visual or the canvas, every save is a restorable revision, and a finished board saves as a global template that carries its visuals and arrangement to every loan of that type.

Upload your existing memo as a PDF or a Word file and it is rebuilt from the builder's own blocks over the page, made once and shared across the team, and the bank charts drop in as vector graphics that keep their source link, so source-backed figures open their printed rows from the memo.

Every action, the counterparty corrections included, lands in an append only log that records who, what, when and the before and after values, kept immutably for up to seven years, and a mistake from last week comes out with one undo from the log even after later actions, with the undo itself logged.