Integrations
Finastra integration for financial spreading
How a finished SpreadSpace spread reaches Finastra’s LaserPro and CreditQuest: an export map in its codes, file and API handoffs, and an embedded workspace.
Finastra’s commercial lending products run from origination to closing documents: the LaserPro Lending Platform with Evaluate for origination and Analyze for spreading, CreditQuest with its Financial Analyzer, and LaserPro itself, which prepares the loan documents thousands of institutions close on. A lender that reviews borrowers in SpreadSpace needs the finished spread back in Analyze or CreditQuest and the approved terms through to LaserPro.
This guide covers that handoff as it works today. SpreadSpace names every account in Finastra’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 Finastra receives it through the developer platform and product APIs it documents. There is no Finastra-built connector, and none of the routes needs one.
Where a spread lands in Finastra
Finastra’s spreading lives in two places. CreditQuest’s Financial Analyzer analyzes financial statements and tax returns for credit decisions, and the LaserPro Lending Platform’s Analyze module does the same inside the newer cloud platform. Finastra’s partner integration with FlashSpread imports tax return data into Financial Analyzer for spread calculation, which is the documented shape of an outside spread entering the product. Closing data moves on to LaserPro, whose LaserPro Connect API Finastra offers to third-party loan origination systems.
A spread finished in SpreadSpace lands in those spreading periods, and the approved figures the credit decision rests on travel with the loan to LaserPro. The export map below gives every SpreadSpace account its Finastra name and code first.
Finastra LaserPro Lending Platform
Finastra LaserPro Analyze factsheet
What SpreadSpace hands to Finastra
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. Finastra receives whichever form its import takes.
Exports in the API documentation
Name every account in Finastra’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 Finastra 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 Finastra as the system, and give each account the code and the name Finastra uses for it. The map is saved once per workspace and applies to every loan, and the system is recorded as finastra on everything it codes.
| SpreadSpace account | Account id | Code and name in Finastra |
|---|---|---|
| Revenue | pl.revenue.sales | 4000 Revenue |
| Cost of goods sold | pl.cogs.purchases | 5000 Cost of goods sold |
| Rent | pl.opex.rent | 6200 Occupancy |
| Interest expense | pl.interest | 7200 Interest |
| Accounts receivable | bs.current_assets.accounts_receivable | 1100 Receivables |
| Accounts payable | bs.current_liabilities.accounts_payable | 2000 Payables |
| Current portion of long-term debt | bs.current_liabilities.current_portion_ltd | 2300 CPLTD |
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 Finastra
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 Finastra’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 Finastra’s codes already on every account, and posts them into Finastra through the path Finastra 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 Finastra 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 Finastra by either route above.
Webhooks in the API documentation
Finastra’s side of the handoff
Finastra exposes its products to outside software through FusionFabric.cloud, its developer platform, and through product APIs such as LaserPro Connect. Which of those opens Analyze or Financial Analyzer to an outside spread depends on the lender’s Finastra products and versions, so the import is settled with Finastra: an integration on its developer platform, the statement import the product provides, or a partner listing of the kind FlashSpread holds.
On the API route your service receives the finalize event, reads the snapshot and the mapped statements with Finastra’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 its Finastra code. In both cases the memo PDF and the source documents stay in reach in the embedded workspace beside the Finastra record.
Finastra origination solutions
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 Finastra. 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 Finastra, and no step above depends on one. The file, the API payload and the embedded frame are SpreadSpace’s side of the handoff. Finastra’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