Services engagement
Delivered, not downloaded.
Bookend is one signed release for every bank. The engagement adapts it to yours: your documents, your approval record, your core, your credit policy, and your controls. We prove it on your own historical closings before the first live loan and hand it over with what your auditors expect. Four weeks is typical. You are live on boarding files in week four, and the jXchange commit is switched on when enablement completes.
Photo: Christina Morillo / PexelsBefore the engagement
Two steps that cost you almost nothing
A 45-minute Closing Workflow Review leaves you with a one-page Closing Error and Capacity Map, whether or not you go further. If it makes sense, a paid pilot runs the platform on your next twenty closings (redacted if you prefer, boarding files only, no core write), with findings reviewed alongside your specialists each week.
Closing Workflow Review
Free · 45 minutes · your head of loan operations
We map the path from approval to documents to execution to boarding to funding, count the touches and hours, and pull three recent boarding exceptions. You keep the one-page map.
Book the reviewPilot on your next 20 closings
Paid · redacted if you prefer · no core write
Your packages and your approval record, with the findings compared against what your specialists found. The pilot report is the basis for the implementation decision.
The engagement
Five stages, one team on each side
- 01 · Week 1
Discovery
Your document sources, approval record format, boarding practice and core fields, wire process, roles and segregation of duties. Network, database, TLS and mail decisions. We answer the vendor-risk questionnaire.
Done when: A signed configuration workbook and the environment request.
- 02 · Week 1
Install and enablement
The release is verified and started on your host, TLS is set at your edge, the onboarding wizard is completed with your relay and database, and roles are created. jXchange enablement is requested through VIP, with boarding files as the interim path.
Done when: Readiness green, SMTP and core tests passed, security sign-off on the install.
- 03 · Week 2
Configuration and mapping
A LAR profile for your approval format. A core field map version with your product and GL codes. Execution templates for your document set, and your own forms taught by pointing at values on one example. Rule tolerances, reason codes and justification policy set to your credit policy.
Done when: Every canonical field maps; a preview boards a real loan cleanly.
- 04 · Week 3
Parallel run
Twenty to thirty historical closings processed alongside your existing process. Accuracy by field type, findings against known outcomes. Where your documents differ from the validated templates, a specialist fixes the source on the page and the platform learns the form.
Done when: An accuracy report you accept, and specialists working the workstation unaided.
- 05 · Week 4
Training and go-live
Role-based training, then go-live with human approval on every loan (that never changes). We walk internal audit and compliance through the evidence packet and file the validation pack in your model-risk inventory.
Done when: First production loans sealed, audit accepts the packet, and support takes over.
Who it is for
Community banks that board commercial loans from executed packages.
Typically several hundred million to ten billion in assets, with a commercial lending operation the closing desk has to keep up with, and, to start, a Jack Henry core. The people who care most are the head of loan operations, the closing manager, the chief credit officer, the COO, and internal audit.
Who is involved
What we need from the bank
Implementation is light on your calendar, but it isn’t zero. These are the people we work with, and roughly when.
Head of loan operations
Sponsor and decision-maker throughout: discovery, the parallel-run reviews, and the go-live decision.
A closing specialist
The subject-matter expert for your documents and your approval record, and the first user of the workstation in the parallel run.
IT and information security
Host, network, database, TLS and mail decisions in discovery, then the install and the vendor-risk review.
Core administrator or Jack Henry liaison
jXchange enablement through VIP, test credentials, product and GL codes for the field map.
Internal audit or compliance
The evidence packet walkthrough and the model-risk inventory entry before go-live.
A boarding checker
The second person in maker-checker for boarding and wires, trained before the first live loan.
What stays the same
Configuration, never a fork
Nothing in the engagement changes the software for your bank. Field maps, approval-record profiles, execution templates, tolerances, and reason codes are versioned data in your own database. You can preview them before they go live, and they carry forward through every release. If your documents or your core need something the release can’t express, that becomes a product improvement for every bank rather than a custom build you would be stuck maintaining.
Questions
Engagement FAQ
What is the services engagement?
Bookend is delivered with services rather than downloaded. A free 45-minute Closing Workflow Review maps your approval-to-boarding path and leaves you with a one-page Closing Error and Capacity Map. A paid pilot runs the platform on your next twenty closings, redacted if you prefer. Implementation covers discovery, install inside your network, approval-record and core-field mapping, a parallel run on twenty to thirty historical closings with an accuracy report, training, and go-live with human approval on every loan. It typically takes four weeks. Hypercare and support follow.
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.
How is it priced?
Per closed loan, with an annual minimum and a one-time implementation engagement that is part of every deal. Counsel-drafted packages on larger loans are a premium tier, and air-gapped installs carry an uplift. There is no public rate card because the right number depends on closing volume, loan mix and core. A short conversation settles it.
Who is this for?
Community and regional banks, typically several hundred million to ten billion in assets, with a commercial lending operation that boards loans from executed packages, and especially banks on Jack Henry cores. The people who care most are the head of loan operations, the closing manager, the chief credit officer, the COO and internal audit.
Start with a Closing Workflow Review
Forty-five minutes with your head of loan operations. We map the path from approval to documents to execution to boarding to funding, count the touches, and pull three recent boarding exceptions. You keep a one-page Closing Error and Capacity Map, whether or not you go further.