Guide · Jack Henry
Loan boarding for Jack Henry banks
Bookend is built for banks on Jack Henry cores first. It boards through jXchange, enabled through the Jack Henry Vendor Integration Program, and falls back to a boarding file while write access is still being enabled. Nothing about your core, your LOS, or LaserPro changes.
By the Bookend team5 min read
Photo: Kristina Chuprina / PexelsjXchange, the way Jack Henry intends it
jXchange is Jack Henry’s integration layer for its cores. Third-party software reaches it through the Vendor Integration Program, which provides the enablement, the test environment, and the versioning against SilverLake releases. Bookend’s core adapter speaks jXchange with the REST binding active and the SOAP envelope builder available for cores that need it. Either way the pattern is the same: ping to test the connection, post the boarding transaction once, and inquire to confirm.
A versioned field map for each core
Canonical loan terms (principal, rate, index, margin, dates, payment, parties, collateral, fees, and coding) map to each core’s fields through a field map that is data, not code. It carries your product codes, GL accounts, officer and branch codes, and collateral codes. It is versioned, and you can preview it against a real loan before it goes live, so the first production boarding is never the first time the map has been exercised. Illustrative field codes ship with the demo, and implementation replaces them with yours.
Staged, checked, and committed once
Staging maps the reconciled terms to the core fields and validates the required ones before anything is sent. A boarding checker who did not stage the record approves it. The commit posts a single transaction. If it is interrupted, it resumes. If the core reports a duplicate, the adapter inquires rather than posting again and records the loan as already boarded. The core’s response, whether success or refusal, is stored verbatim on the loan and can be retried without rekeying.
Boarding files while enablement completes
VIP enablement takes time. The file-export path keeps implementation moving with deterministic JSON, XML, and CSV boarding files that carry provenance behind every field, produced from the same staged record and the same two-phase approval. Switching to a jXchange commit later is a settings change. The field map, the approvals, and the evidence packet are identical.
What stays exactly as it is
Your core
SilverLake, CIF 20/20, or Core Director books the loan the way it always has. Bookend hands it a validated, approved record.
Your LOS and documents
The LOS still originates and approves. LaserPro or counsel still produce the package. Bookend reads what was signed.
Your wire room
The wire request is staged and approved in Bookend and exported. Your wire room sends it. The platform never transmits a wire.
Not on Jack Henry?
The adapter contract is core-agnostic by design. Additional core adapters are being developed as products, not one-off projects, and the boarding-file path works with any core today. Tell us your core in a Closing Workflow Review and we will tell you plainly where it stands. Product detail on the jXchange integration is on usebookend.com.
Questions
Questions Jack Henry banks ask
Which core banking systems are supported?
Jack Henry first: SilverLake, CIF 20/20 and Core Director, boarding through jXchange under the Vendor Integration Program. For any core, Bookend produces deterministic JSON, XML and CSV boarding files with provenance behind every field, and additional core adapters are in development. The adapter contract is core-agnostic, so switching from file export to a direct commit is a settings change.
Our core is hosted by Jack Henry. Does on-prem still apply?
Yes. The containers run in your network and reach the hosted core over jXchange the same way they would on-site. Loan documents stay in your network either way.
How long does implementation take?
Four weeks from kickoff to go-live is typical for a bank that has the environment provisioned and twenty to thirty historical closings gathered at kickoff. Install is a runbook, mapping and templates are data, and the parallel run processes the closings in an afternoon. The rest of that week is your specialists reviewing findings. jXchange enablement through the Vendor Integration Program runs in parallel and can outlast the engagement, and the file-export path means go-live never waits for it.
Does Bookend replace our LOS, document system or core?
No. LaserPro or counsel still produce the documents, your LOS still originates and approves, your core still books the loan, and your wire room still sends the wire. Bookend sits between the executed package and the core. It validates what was signed against what was approved and stages boarding and funding for your approval.