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 the extraction model in the image. 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.

A model does one narrow job: it classifies documents and locates fields, inside the container. Whether two terms agree is decided by deterministic, versioned rules with documented tolerances, so a result is reproducible on the same input and can be explained to an auditor. Every signed release ships with a validation pack (test sets, accuracy by field type, known failure modes, change history) 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, 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.

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. loanboarding.com explains commercial loan boarding (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.