Lending Core overview

Every other part of the platform ends up asking the Lending Core the same question: what is true about this loan right now? It is the flagship system of record, and it owns the answers — products and their policy, loans and their schedules, disclosures, payments, autopay, statements, and the double-entry ledger those records post to. Split those answers across two systems and the balance a borrower is quoted stops matching the balance the books close on, with nothing to say which one is the loan. The servicing workspace runs natively on this core; the same servicing workflows can also run on a core you already operate — see bring your own system of record.

Three families, not one with options

A product is the rulebook behind every obligation: it supplies defaults and hard constraints, and the terms a loan resolves at origination are frozen on the loan, not looked up at servicing time. A product edited in year two would otherwise silently restate a contract signed in year one.

Merchant advances are a separate family with their own terms, lifecycle, accounting, and API resource — selecting one never toggles an installment loan into a commercial contract. The example portfolio — Harbor, Juniper, Cedar, and Northstar — carries one consistent set of balances and dates through every family’s guides.

A loan advances only by command

Movement happens through explicit, permissioned lifecycle commands: SUBMITTED proposes terms without moving money, approval authorizes them — and computes and finalizes the APR disclosure in the same step — and the loan becomes ACTIVE only when released funds post as a disbursement through the funding API, value-dated to the posted date rather than the day someone clicked “fund.” A loan that went active on the click would charge interest for days in which the borrower had no money. Delinquency, hardship, restrictions, and servicing plans are overlays on an active obligation, never replacement states, and charge-off, write-off, and contract termination are distinct governed outcomes — never aliases for normal payoff.

Accepted by a processor is not money

A payment is an operational intent first and a ledger transaction later. Posting is value-dated: Harbor’s $517.14 ACH debit settles on September 15 but posts effective September 12, the date the borrower paid, and delinquency follows the value date — so three days of network latency never become three days of arrears. Every terminal payment is checked three ways — provider settlement, payment intent, ledger transaction — and a settled debit with no posting surfaces as a classified reconciliation exception, not a silent gap. Money the lender has already received and not recorded is the kind of error that is cheap to find on the day and expensive to find at close.

Underneath, accounting is strict double entry: every posted transaction balances to the cent, and Harbor’s first installment is readable straight from the journal — $517.14 of cash against $424.39 of principal and $92.75 of interest.

Disclosure is a lifecycle step, not an endpoint

For covered closed-end consumer credit, the APR engine applies the actuarial method of Regulation Z, Appendix J to the loan’s dated cash flows. Every charge definition carries an immutable finance-charge classification with a legal-basis citation, and the calculation fails closed — an unclassified fee can never reach a disclosure, and an unknown fee is never treated as excluded. Failing closed costs an approval; guessing at a fee costs a misstated APR on a signed contract.

There is nothing to remember to call: the disclosure is finalized automatically at approval (an APR-enabled product cannot approve a loan without one), revalidated at disbursement against the actual funding facts, and superseded — with both records retained — if those facts changed. The finalized record stores every input, convention, and tolerance it used, so an auditor can reproduce Harbor’s disclosed 17.29 from a 13.25% nominal rate and a $252.00 prepaid fee without access to live configuration.

Every state change is a governed command

Each one carries its own permission. Human calls carry a LendEasy-Case header naming an open case when case management is enabled, maker-checker can park any flagged command for a different approver, and every execution writes a governance record that is never edited — who acted, in which context, through which route. A year later the contested question is rarely what the balance is; it is who was allowed to change it, and that record is the only thing that answers. The servicing action catalog documents 24 governed actions across schedule, interest, charge, refund, restriction, and terminal families, each with its own page. Undo is specific, never generic: where a dedicated undo command exists it is itself governed, and nothing deletes history.

Autopay is an initiator, not a shortcut

Autopay reads current due facts each cycle and creates one normal, idempotently keyed payment intent per due obligation. It never writes to the ledger itself, so an enrollment that misfires produces a payment that can be traced and returned like any other rather than a balance nobody can source. Enrollment requires the borrower’s preauthorized-transfer authorization evidence, and the Regulation E notice window is wired into configuration itself — a FULL_DUE enrollment is accepted only when the product’s statement lead leaves the ten-day advance notice described in § 1005.10(d), because the due-date statement is the notice artifact. Cancellation is the revocation of record.

Explore the Lending Core

• Products & templates — the rulebook behind every loan, including disclosure and statement policy.
• Example portfolio — Harbor, Juniper, Cedar, and Northstar: the four contracts every guide reuses.
• Loan lifecycle — from application to an evidence-backed terminal state.
• APR & disclosures — the Appendix J solve, worked end to end on Harbor.
• Payments & repayments — intent, settlement, value-dated posting, and returns.
• Accounting — balanced journal entries and the authoritative export surface.
• Autopay — amount and timing policies, notice coupling, and per-rail failure policy.
• Statements — cutoff windows, frozen snapshots, and governed regeneration.
• Servicing actions — the 24-action governed catalog and its maker-checker contract.
• Merchant advances — receivables purchase, remittance, and reconciliation.