Integrations
Jack Henry integration for financial spreading
How a finished SpreadSpace spread reaches Jack Henry LoanVantage: an export map in its codes, file and API handoffs on finalize, and an embedded workspace.
Jack Henry serves community and regional banks with its banking cores, and its LoanVantage loan origination system handles commercial lending with financial spreading inside it. A lender on a Jack Henry core that reviews borrowers in SpreadSpace needs the finished spread back on the LoanVantage application, in the accounts its spreading templates expect, and the booked loan on the core afterwards.
This guide covers that handoff as it works today. SpreadSpace names every account in LoanVantage’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 Jack Henry receives it through the APIs it publishes on its developer site. There is no Jack Henry-built connector, and none of the routes needs one.
Where a spread lands in LoanVantage
LoanVantage is Jack Henry’s commercial loan origination system, with financial spreading, tax return spreading, document imaging and reporting inside it. Jack Henry publishes a LoanVantage API on its developer site, a REST interface for exchanging application data and documents with third-party systems, and jXchange, the translation layer that moves business information between Jack Henry cores and outside software over REST and SOAP. A developer account on jackhenry.dev opens the documentation for both.
A spread finished in SpreadSpace lands on the LoanVantage application as the spread its templates read, and the loan reaches the core through LoanVantage’s own boarding. The export map below gives every SpreadSpace account its LoanVantage name and code before anything moves.
What SpreadSpace hands to Jack Henry
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. Jack Henry receives whichever form its import takes.
Exports in the API documentation
Name every account in Jack Henry’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 Jack Henry 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 Jack Henry as the system, and give each account the code and the name Jack Henry uses for it. The map is saved once per workspace and applies to every loan, and the system is recorded as jack-henry on everything it codes.
| SpreadSpace account | Account id | Code and name in Jack Henry |
|---|---|---|
| Revenue | pl.revenue.sales | 4000 Gross sales |
| Officer compensation | pl.opex.officer | 6000 Officer salaries |
| Interest expense | pl.interest | 7000 Interest expense |
| Cash | bs.current_assets.cash | 1010 Cash |
| Accounts receivable | bs.current_assets.accounts_receivable | 1200 Trade receivables |
| Lines of credit | bs.current_liabilities.lines_of_credit | 2100 Line of credit |
| Notes payable, long term | bs.longterm_liabilities.notes_loans_payable | 2500 Term debt |
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 Jack Henry
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 Jack Henry’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 Jack Henry’s codes already on every account, and posts them into Jack Henry through the path Jack Henry 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 Jack Henry 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 Jack Henry by either route above.
Webhooks in the API documentation
Jack Henry’s side of the handoff
The LoanVantage API covers applications, applicants and the documents attached to them, so the documented path for an outside spread is the application record and its documents, with the spread’s figures entered into LoanVantage’s spreading templates from them, or an import Jack Henry’s services arrange. jXchange is the path when the lender’s team wants the finalized figures or the borrower’s reviewed debt schedule beside customer and account records on the core itself.
On the API route your service receives the finalize event, reads the snapshot and the mapped statements with LoanVantage’s codes on every account, and writes through the LoanVantage API or the import. On the file route the analyst attaches the statements workbook to the application, each line carrying its LoanVantage code. Jack Henry’s own collateral says implementing the LoanVantage API takes technical expertise, and the lender’s integration team owns that last step 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 Jack Henry. 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 Jack Henry, and no step above depends on one. The file, the API payload and the embedded frame are SpreadSpace’s side of the handoff. Jack Henry’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