Loan boarding, answered plainly.

Loan boarding is the step after closing when a bank enters an executed loan into its core banking system so it can be serviced: principal, rate, index and margin, dates, payment schedule, borrower and guarantors, collateral, fees, GL and product codes. Boarding is the point where the signed documents become the system of record. Any disagreement between what was signed, what was approved and what was keyed turns into a servicing, accounting or compliance problem from that point on.

The variable terms are spread across seven or eight documents plus the credit approval, and a person compares and re-keys them by hand on every loan. Most of the package is boilerplate. The few percent that varies (rates, dates, amounts, parties) is where cross-document disagreements, transposition errors and stale approval terms hide. Execution gaps, such as missing signatures, initials or notary blocks, are a second family of errors that usually surface only after funding.

Bookend reads the executed closing package, classifies each document, extracts every variable term with its page and position, reconciles the terms against each other and against the credit approval using deterministic rules, verifies execution marks, and stages the core boarding record and the wire request for a second person to approve. Every step is recorded in a hash-chained evidence packet for the loan. It runs inside the bank’s network and is delivered with an implementation engagement.

No. Bookend ships as containers that run inside your network, with extraction and OCR in the image, and no external AI service ever sees a loan document. Documents, extracted terms, findings and the evidence chain live in your database and your document volume. The only outbound call to Bookend is a metering heartbeat carrying an install id, version, period, closed-loan count, page count, coarse health and the license key. The heartbeat is shown verbatim on screen, and air-gapped installs replace it with a signed quarterly report.

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.

No. The software does the comparing and the keying. Your people keep the judgment and the approvals. Every loan passes through a review workstation where a closing specialist accepts, overrides or escalates each finding with a reason code. Boarding and funding are two-phase: the person who stages a record can never approve it. Nothing is committed to the core and no wire request is released without that second approval.

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.

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.

Only for reading scanned pages, and never externally. No frontier model and no external AI service processes your loans, and nothing leaves your network for AI processing. Classification, extraction and execution checks are deterministic rules, and whether two terms agree is decided by versioned rules with documented tolerances, so a result is reproducible on the same input and can be explained to an auditor. The only machine learning is the open-source Tesseract OCR engine, which reads scanned pages on CPU inside the container with its published, pre-trained weights; native PDFs never pass through it. An optional helper can use a large language model to draft a starting template during setup, but it is off by default and stays off unless the bank explicitly turns it on with a model it already has; forms are otherwise taught by hand. Every release ships with a validation pack (golden reference packages with expected results, a page for every rule, and the accuracy report) for the bank’s SR 11-7 model inventory, sized for a community bank.

A per-loan evidence packet as PDF and JSON: document hashes, every extracted value with its source page and position, findings and how each was resolved with reason codes, approvals with who and when, boarding and funding events, and the result of verifying the hash chain. Change one byte in the database and verification fails at that link.

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.

Community and regional banks, typically several hundred million to ten billion in assets, that board loans from executed packages (commercial, consumer, mortgage, SBA or agricultural) or open accounts from a package of signed documents, and especially banks on Jack Henry cores. The people who care most are the head of loan operations, the closing manager, the deposit operations manager, the chief credit officer, the COO and internal audit.

The method is the same for any loan boarded from an executed package: find every variable term with its source, check it against the other documents and the approval, verify execution, and stage the core record for a second person to approve. Commercial packages are where the shipped document set and rule catalog go deepest today. Consumer installment and indirect loans, residential mortgages, HELOCs and SBA loans bring their own documents, such as the Truth in Lending disclosure, the Closing Disclosure, a retail installment contract or the SBA Authorization. A Closing Workflow Review tells you how much of your document set the current release covers and what the engagement would add. Anything the release cannot yet express becomes a product improvement in a signed release, never a custom build.

Yes, with the same engine. Opening a business deposit or treasury management account produces a package much like a loan closing: the application, signature card, corporate resolution or certificate of authority, beneficial ownership certification, formation documents and a W-9. The same kinds of checks apply. The legal name and tax ID should agree on every document, every signer on the signature card should be authorized by the resolution, each document should carry its signatures and dates, and the account record should be staged for a second person to approve before the account is opened. Account packages are scoped with you in the Closing Workflow Review, like any document family the shipped catalog does not yet cover.

No. Bookend checks that the documents in a loan or account package agree with each other and with what was approved, and that they are properly executed. Identity verification, sanctions screening, customer due diligence risk ratings and the decision to open an account stay with your BSA/AML program and the vendors you already use. What Bookend adds is a record, in the evidence packet, of which documents were checked, what disagreed, and who approved it.

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.

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.

Reference sizing is 16 vCPU, 64 GB RAM and 500 GB of storage on your VMware or Hyper-V estate, with no GPU. PostgreSQL by default, or your SQL Server. Signed releases are pulled by your team on your own change-control schedule. The platform never updates itself.

Both are operated by Bookend (Trivium Labs LLC). loanboarding.com explains loan boarding across loan types, and account onboarding alongside it (the process, the errors, the checklist, and how automation with human approval fixes it), and offers the Bookend platform with its services engagement. usebookend.com is the platform’s own site, with product screenshots, security detail and pricing.