For Jack Henry banks
Keep your core. Keep your LOS. Keep your document vendor.
Bookend is built for banks on Jack Henry cores first. It boards through jXchange, enabled through the Jack Henry Vendor Integration Program, and it falls back to a boarding file where write access is still being enabled. Nothing about your core, your LOS or LaserPro changes. Jack Henry is where we start; the adapter contract is core-agnostic and additional core adapters are in development.
Integration
jXchange, the way Jack Henry intends it
SilverLake, CIF 20/20, Core Director
One adapter, configured per core through settings and a versioned field map — not code. Illustrative field codes ship with the demo; your implementation replaces the map with your own.
Vendor Integration Program
Enablement runs through VIP with your test environment first. The adapter is versioned against SilverLake releases.
REST and SOAP bindings
The REST binding is active; the SOAP envelope builder is present for cores that need it. Either way: ping to test, post once, inquire to confirm.
Boarding
Staged, checked, committed once
Staging maps the executed terms to your core fields and validates the required ones before anything is sent. A boarding checker who did not stage it approves. The commit posts a single transaction; a duplicate is resolved by inquiry and recorded as already boarded. The core’s response — success or refusal — is stored verbatim on the loan and can be retried without re-keying.
Fallback
Boarding files when write access isn’t there yet
Before jXchange write access is enabled, or for cores that take a file, Bookend produces deterministic JSON, XML and CSV boarding files with the same provenance behind every field. Switching to jXchange later is a settings change.
Questions Jack Henry banks ask
Does Bookend replace anything we run today?
No. LaserPro or your counsel still produce the documents; your LOS still originates and approves; your core still books the loan. Bookend validates what was signed against what was approved and stages the boarding and the wire request for your approval.
Our core is hosted by Jack Henry. Does that matter?
The containers run in your network and reach the core over jXchange the same way they would on-site. Loan documents stay in your network either way.
What does enablement involve?
A jXchange enablement request through VIP for your test environment, then production. Founding-partner relationships and the file-export fallback keep the implementation moving while enablement completes.
Can we start with the file export and switch later?
Yes. The field map, the two-phase approval and the evidence packet are identical; only the commit step changes.
Start with a Closing Workflow Review
Forty-five minutes with your head of loan operations: we map approval → documents → execution → boarding → funding, count the touches, and pull three recent boarding exceptions. You get a one-page Closing Error and Capacity Map — whether or not you go further.