SpreadSpace vs Aloan

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 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.

Form 4562 is read in every part, and the preparer's per asset registers, the hundreds of pages behind the totals, are read row by row, with the printed asset fields retained and every printed register total checked against its rows. The register is its own tab on the return viewer with a source jump per asset row.

Net operating loss carryforward schedules come in as typed rows of loss sustained, previously applied, remaining and available this year, with Form 8990 interest limitation carryforwards, Form 8582 passive losses, Form 6198 at risk limits and Form 7203 basis limits read into their own objects.

A workbook is triaged sheet by sheet across twelve sheet kinds, a comparative statement is fanned out per year, and periods scattered across tabs or across files are stitched into one standard statement with the rows aligned by label and nothing double billed.

Every transaction from 234 registered bank layouts with its date, description, signed amount, check number, kind and page box, a balance for every day, and overdraft, insufficient funds, chargeback, returned item and service fee signals. Each transaction rolls up under a named counterparty in one of 58 classes across 13 sections, and every financing relationship, merchant cash advances included, is found from payment cadence and the transaction text.

A derived figure carries a derivation arrow that folds open to the printed lines that sum to it, from book gain on dispositions to book depreciation, capex and every line of the cash flow statement. A composed figure boxes every line it sums on the source page.

Every return is recorded on both a tax basis and a book basis, and the analyst can use either one or both, with a book P&L bridge for every return year.

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, and the add-backs picker lists every printed line and statement item with its values by year and a checkbox per year. Add-backs follow the basis the analyst chose.

Coverage is configured per entity and per year from the documents' own lines, with debt service assembled from the Schedule L liability balances, the business debt schedule and the implied debt schedule from the bank statements, pro forma with proposed debt and historical, and saved as a named recipe on the loan that renders as its own card.

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.

Every business and person on the loan is reconciled from the documents' printed names, with spelling drift folded and the EIN last four splitting or uniting names, and appears in the entity selector, so cards from several filers sit on one canvas with no fixed cap on how many. A K-1, a personal return and a personal financial statement gather on the same person without hand linking.

Transactions roll up by counterparty with money in, money out, net, business type, class and relationship, the speculative ones held in an under review section, and an analyst override of a class or relationship stands above every heuristic, survives every reprocess and is never re-inferred. Confirming one row pools its byte exact siblings so nothing is moved twice.

Accounts the transactions reference with no statement uploaded are listed by bank and last four with the transactions that revealed them, and an implied debt schedule states every financing relationship with advances, repayments, net, cost of capital and the payment cadence the remittances imply.

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.

Four catalogs, Tax, Bank, Company reported and Custom, with 59 curated tax cards, 40 company reported cards, 13 personal return and personal financial statement cards, 14 personal KPI cards and 20 bank tiles with 7 bank KPI cards, plus per partner, per owner and per K-1 issuer card sets minted from the documents themselves.

Any extracted line becomes a graph, a ratio with real operators and per term multipliers, an aggregate or a KPI card, picked from a searchable list of the return's lines under thirteen groups, the company statements, the personal return and the personal financial statement, and the built visual keeps the source jump on every line it reads.

A finished board saves as a global template that carries its visuals and arrangement to every loan of that type, re-aimed at that loan's filers, while comments, placed pictures, source links and loan bound cards stay behind on the loan that wrote them.

Up to twenty five analysts work one board with live cursors, selections and drags, comment threads pinned to a visual or a bare point on the canvas, prose linked to a source line, and every save kept as a restorable revision.

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 a Word template can stay a Word document with the exhibits anchored into its flow.

Spread visuals import into the memo as vector graphics that stay sharp at any size, the figures are re-derived on the server at print time, and a figure in the memo keeps its source link so a click opens the same boxed line from the memo.

An analyst edits a figure or caption in place, the override applies before every derivation above it, each edit records the label, the column and the previous and new state on the spreading log, and a revert restores the extracted figure with its own log row. Restating a figure is its own permission and its own opt-in API grant.

Every action 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.

Finalizing freezes the board into an immutable snapshot of 124 attributes and 21 ratios, with a machine twin built from the documents alone beside it so a reviewer sees exactly what the analyst changed, and the finalized event carries identifiers, never figures.