Integrations
Baker Hill integration for financial spreading
How a finished SpreadSpace spread reaches Baker Hill: an export map in Baker Hill’s account codes, file and API handoffs on finalize, and an embedded workspace.
Baker Hill’s commercial loan origination platform, known for years as Baker Hill NextGen and offered today within its UN/FY lending and risk platform, carries a commercial loan from application through underwriting, approval and portfolio management, with statement spreading, global cash flow and credit memo preparation inside it. A lender that reviews borrowers in SpreadSpace needs the finished spread back in Baker Hill under the account names its spreading templates and memo use.
This guide covers that handoff as it works today. SpreadSpace names every account in Baker Hill’s terms through a per-workspace export map, hands the finished spread over as a file, through the API when the analyst finalizes, or inside an embedded workspace, and Baker Hill receives it through the paths Baker Hill provides. There is no Baker Hill-built connector, and none of the routes needs one.
Where a spread lands in Baker Hill
Baker Hill’s statement spreading takes financial statements and tax returns into spreads, ratios, projections and global cash flow on the borrower’s record, and its credit memo reads those spreads. Baker Hill extends the platform through partners rather than a public developer portal. Its integrations page lists bureau, identity, document capture and e-signature partners, and it has partnered with FlashSpread to spread tax returns into the platform without manual entry.
That partnership is the shape an outside spread takes in Baker Hill. The figures land in the same spreading periods its own tool fills, which is why the export map below names every SpreadSpace account in Baker Hill’s terms before anything moves.
Baker Hill statement spreading
Baker Hill partners and integrations
What SpreadSpace hands to Baker Hill
Four things leave SpreadSpace. The first is the extracted document: every line a tax return, financial statement or bank statement prints, each with the page and the boxed region it was read from. The second is the mapped statement: the profit and loss statement and the balance sheet placed on the workspace’s chart of accounts, with each account’s figure per period and the arithmetic that walks the printed lines to the printed totals. The third is the finalized spread: the attribute snapshot an analyst approved, with its figures, periods and source document references, frozen at a version number. The fourth is the credit memo as a PDF.
Each has a file form and an API form. One document exports as CSV or JSON on its own, and a set of documents on one loan bundles in the background as CSV, JSON or, for bank statements, XLSX. The loan’s spread comes out as two Excel workbooks, one of statements and one of tables, with the rows a figure is derived from indented under it. The finalized figures are read from the loan’s attributes endpoint and the mapped statements from the borrower’s mapping endpoints. Baker Hill receives whichever form its import takes.
Exports in the API documentation
Name every account in Baker Hill’s terms
The chart of accounts is the workspace’s own. Its accounts carry SpreadSpace ids such as pl.opex.rent and bs.current_assets.cash, and Baker Hill holds the same accounts under its own codes and names. The export map is the translation. In Settings, open Chart of accounts and then Export map, choose Baker Hill as the system, and give each account the code and the name Baker Hill uses for it. The map is saved once per workspace and applies to every loan, and the system is recorded as baker-hill on everything it codes.
| SpreadSpace account | Account id | Code and name in Baker Hill |
|---|---|---|
| Revenue | pl.revenue.sales | 400 Net sales |
| Cost of goods sold | pl.cogs.purchases | 500 Cost of sales |
| Rent | pl.opex.rent | 610 Rent |
| Depreciation | pl.opex.depreciation | 690 Depreciation expense |
| Cash | bs.current_assets.cash | 100 Cash |
| Property, plant and equipment | bs.noncurrent_assets.ppe | 150 Fixed assets |
| Retained earnings | bs.equity.retained_earnings | 390 Retained earnings |
From then on every mapped statement carries the codes. Each account in the mapping’s tree answers with its external code and label beside its figure per period, the payload names the system, and the accounts the map codes that the statement does not use are listed, so nothing posts blind. A map can also be saved through the API, up to 1,000 entries and the whole map each time, and a save that crosses another is refused rather than merged. After any save, each mapping reads as stale until it has been prepared again with the new codes, and a webhook announces the fresh one.
Statement mapping and the export map in the API documentation
Three routes into Baker Hill
The first route is a file. An analyst downloads a document’s export or a bundle from the document list, a job requests the two workbooks, and the files are loaded through Baker Hill’s import or attached to the loan. It needs no engineering and suits a team that files a few spreads a day.
The second route is the API. When an analyst finalizes a spread, SpreadSpace sends a spread.finalized event to your endpoint, signed with a shared secret, naming the loan and the snapshot. Your service reads the snapshot from the loan’s attributes endpoint and the mapped statements from the borrower’s mapping endpoints, with Baker Hill’s codes already on every account, and posts them into Baker Hill through the path Baker Hill documents. SDKs for TypeScript, Python and C# wrap the calls, and the event carries the snapshot id, so a handler that records the ids it has posted stays idempotent under a retry.
The third route is the embedded workspace. Your application asks SpreadSpace for a single-use signed URL and seats the spread in an iframe beside the Baker Hill record, so an analyst opens the source documents without leaving the loan, and no token crosses the parent frame. The figures still finalize into the same snapshot and reach Baker Hill by either route above.
Webhooks in the API documentation
Baker Hill’s side of the handoff
Baker Hill does not publish an open API reference, so the import of an outside spread is arranged with Baker Hill: a statement import the platform provides, an integration built with its services team, or a partner listing of the kind FlashSpread holds. The lender’s integration team and Baker Hill’s decide which, and the figures SpreadSpace hands over are the same in every case.
On the API route your service receives the finalize event, reads the snapshot and the mapped statements with Baker Hill’s codes on every account, and passes them to that import. On the file route the analyst loads or attaches the statements workbook or the CSV bundle, each line carrying the Baker Hill code beside it. The embedded workspace keeps the source review beside the Baker Hill record in either case.
Set up the handoff
Create an API key with the scopes the route needs: extractions read and export for the files and the mapped statements, spreads read for the snapshot, chart of accounts write to save the map from code, webhooks write to register the endpoint and embed write for the iframe. Save the export map for Baker Hill. Register the webhook endpoint, send the test event and verify its signature. Then run the whole loop on a test key against the sandbox loan, whose sample spread finalizes on request, before the first live loan.
SpreadSpace ships no connector written by Baker Hill, and no step above depends on one. The file, the API payload and the embedded frame are SpreadSpace’s side of the handoff. Baker Hill’s side is its documented import, its API or its services team, and the section above names the public pages that describe it. A lender that wants the two sides joined for it can ask sales.
API keys and scopes in the documentation
Sample documents and the sandbox loan in the documentation
Integrating financial spreading with a loan origination system