Document validation and loan boarding for community banks. Jack Henry first.
Prove the loan is right. Then board it.
Bookend reads every executed package (commercial, consumer, mortgage, or a new account), reconciles every variable term against what was approved, verifies execution, and stages boarding and funding for your own maker-checker approval. It all runs inside your network, with an examiner-ready evidence packet for every loan.
On-prem
Containers inside your network. No cloud tenant for loan documents.
No data egress
Documents and extracted terms never leave the institution.
Examiner-ready
A hash-chained evidence packet for every loan, exportable as PDF and JSON.
Human approves
Nothing is boarded and no wire is sent without your maker-checker sign-off.
The problem
The 5% of every package that isn’t boilerplate is where boarding errors live.
Rates, dates, amounts, parties. A closing specialist compares them across every document in the package and the approval, keys them into the core, and prepares the wire by hand, on every loan. Bookend does the comparing and the keying, and leaves the judgment and the approvals with your people.
Stare-and-compare, retired
The note says one rate and the boarding sheet another. A guarantor is on the approval with no guaranty in the package. Disbursements don’t sum to principal. Each disagreement surfaces as a finding with every source attached.
No re-keying
The boarding record is built from the executed documents, mapped to your core fields, and shown with provenance before anyone approves it.
Execution gaps caught before funding
Unsigned pages, missing initials and empty notary blocks are exceptions on the review screen, not discoveries after the wire.
How it works
Validate → verify → board → fund → evidence
- 1
Validate
The package and the approval come in; every term is extracted with its page and position.
- 2
Verify
Rules reconcile the terms and check execution. A specialist accepts, overrides or escalates each exception.
- 3
Board
The staged core record is approved by a checker and committed once, with the provider’s answer recorded.
- 4
Fund
The wire request is staged from the disbursement authorization and approved by a second person. Your wire room sends it.
- 5
Evidence
The loan is sealed. The packet proves what was checked, by whom, against what, and that nothing changed since.
Operating principle
The engine finds. The rules judge. A human approves.
Classification and extraction are deterministic and run inside your network. No frontier model or external AI service ever sees a loan document. Whether terms agree is decided by deterministic, versioned rules that can be explained to an examiner. Every loan passes a review screen where a specialist accepts, overrides or escalates before anything reaches the core.
Capabilities
Six blocks, one pipeline
Intake
Upload, watch folder, LOS integration or API. Native PDFs and scanned executed copies, plus the credit approval record (LAR).
Extraction with provenance
Every document classified, every variable term located with page and position. Each value keeps a link back to the exact spot it came from.
Reconciliation
Deterministic, versioned rules compare the note, loan agreement, guaranties, disclosures, disbursement, boarding sheet and approval against each other. Agreement or exception, per term, explained line by line.
Execution verification
Signatures, initials, dates and notary blocks checked per document against the bank’s execution templates. Missing marks become exceptions with the zone highlighted.
Boarding
A staged boarding record mapped to your core fields, approved by a second person, committed through jXchange or a file export. Never twice.
Evidence
An append-only, hash-chained packet per loan (extractions, comparisons, overrides, approvals), exportable as PDF and JSON for auditors and examiners.
Every package
One engine for every loan type, and for new accounts
Commercial, consumer and mortgage loans are all boarded from executed documents, and they go wrong in the same ways. Opening a business account is the same job with different paperwork. Bookend runs the same checks on each: terms that must agree, documents that must be present, and marks that must be on the page.
Commercial and CRE
Notes, loan agreements, guaranties, security documents and the credit memo. The deepest part of the shipped catalog.
Commercial packagesConsumer and indirect
Installment contracts, the Truth in Lending disclosure, add-on products and liens, checked on every file instead of a sample.
Consumer packagesMortgage and home equity
Note, security instrument and riders against the Closing Disclosure, with escrow and rate terms set from the documents rather than product defaults.
Mortgage packagesSBA and agricultural
Closing documents against the SBA Authorization, guaranteed portions and program codes, and seasonal payment schedules.
SBA and ag packagesRenewals and modifications
Change-in-terms and renewal documents against the approval and the account already on the core.
Changes to existing loansAccount onboarding
Signature cards, resolutions, beneficial ownership and W-9s checked against each other before a business or treasury account opens.
Account onboarding
Commercial packages are where the shipped catalog goes deepest today. Other packages are scoped with you in the Closing Workflow Review, so you know what is configuration and what would come in a later signed release. The guides on loanboarding.com walk through each package in detail.
Delivery
Delivered with implementation, not downloaded
Every Bookend installation is a professional-services engagement: discovery of your closing workflow, install inside your network, your approval record and core fields mapped, a parallel run on twenty to thirty of your own historical closings with an accuracy report, training, and go-live with human approval on every loan. Four weeks is typical, and nothing in it forks the software for your bank.
Proven on your closings first
The parallel run is the acceptance test: your packages, your approval record, your findings, compared with what your specialists found.
The engagement, stage by stageJack Henry first
SilverLake, CIF 20/20 and Core Director through jXchange under the Vendor Integration Program. File export for any core today; more adapters in the works.
For Jack Henry banksSupported after go-live
Signed releases you pull on your own schedule, runbooks that ship with the product, Standard or Premium support with a named engineer.
How it is priced
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.