Immutable approval basis
Closing can execute the decision, but it cannot silently rewrite the terms or policy state that credit approved.
§ Platform - CORE Closing + CORE Servicing
CORE Closing turns an approved borrower file into a controlled funding record. CORE Servicing moves funded tranches into schedules, obligations, ledger activity, sandbox payment operations, reviews, and action packages. Approved terms, policy decisions, evidence, and human actions stay connected instead of being rebuilt after underwriting.
An immutable approval snapshot anchors conditions, funding reconciliation, and certification. The certified funded tranches then become the opening balances, schedules, obligations, and audit links used in servicing.
Approval snapshot -> funding certification -> boarding -> servicing05 · CORE Closing
CORE converts the approved borrower file into a controlled closing case without re-keying the credit decision. The closing team works from a frozen approval snapshot while conditions, participants, checklist work, funding variances, and certification remain attributable.
Create an immutable snapshot of approved terms, parties, collateral, capital stack, policy treatment, and decision history.
Convert the approved project into a closing case with participants, policy-linked conditions, and a configurable checklist.
Resolve applicability, collect evidence, record waivers, and keep every outstanding item visible to the closing team.
Compare approved amounts with proposed and actual funded tranches, verify wires, and surface variances before release.
A named human certifies funding readiness and creates the durable record that servicing can board.
Closing can execute the decision, but it cannot silently rewrite the terms or policy state that credit approved.
Conditions retain their source, applicability, evidence, owner, resolution, and waiver treatment.
Unresolved applicability, required conditions, an unbalanced funding package, and unverified wires produce explicit blockers before certification.
Program-specific readiness can be layered into Closing. SBA E-Tran readiness, locked exports, and manual precheck tracking are available in scoped deployments; CORE does not submit live to SBA.
Same borrower file · same approved terms · same audit trail
06 · CORE Servicing
Each proposed funded tranche moves into a servicing loan with its schedule, opening balance, obligations, program profile, and source-case links intact. Portfolio teams can operate the loan without rediscovering why the structure, covenant, or condition exists.
Create the servicing loans, opening balances, amortization schedules, program profile, and links back to the certified closing case.
Carry covenants, borrower and guarantor duties, recurring reviews, and subject-specific follow-up into an operating calendar.
Track sandbox payment intents, provider events, settlement review, posting, suspense, reversals, and the normative append-only ledger.
Keep current, grace, late, and delinquent posture visible alongside covenant status, annual reviews, and portfolio work queues.
Assemble evidence, authority, approvals, and decision history into program-authorized servicing action packages, with separate human-only default controls.
Financial events are posted, corrected, or reversed through traceable entries instead of overwriting prior state.
Sandbox settlement review, suspense handling, reversals, and a kill switch keep payment operations deliberate.
The conventional baseline stays agency-free; SBA 7(a), SBA 504, and USDA B&I overlays apply only when selected.
Payment posting is currently a sandboxed control workflow, and portfolio scans are run on demand. External payment processors, live money movement, and bank-specific booking mappings remain deployment integrations, not claimed live features.
§ Fit
The controlled workflows are implemented end to end behind restricted access. External rails and bank-specific booking integrations remain explicit deployment seams.
Closing conversion with immutable approved terms, parties, collateral, capital stack, policy basis, and decision history
Policy-linked conditions, manual-applicability resolution, participants, and a configurable closing checklist
Funding-package reconciliation and wire verification, followed by exact approved-tranche matching and human funding certification
Boarding proposed funded tranches into servicing loans with schedules, opening balances, and source-case links
Subject-aware obligations, covenant follow-up, annual reviews, payment posture, on-demand portfolio scans, and work queues
Sandbox payment intents, settlement review, posting, suspense, reversals, and an append-only ledger
A conventional baseline with program overlays applied only when the selected program requires them
Program-authorized servicing action packages with evidence and approval history, plus separate human-only default controls
§ Path
Controlled rollout: closing, boarding, obligations, ledger, sandbox payment posting, annual reviews, and action packages are implemented behind restricted access. Portfolio scans are currently on demand. Live agency submission, external payment processor connections, and bank-specific booking mappings are not live.
Approved terms, policy treatment, conditions, parties, collateral, and sign-off remain tied to the version that entered closing.
Readiness is calculated from lifecycle state, unresolved applicability, required conditions, funding-package balance, and wire verification - not a vague status badge.
Approved amounts, funded tranches, opening balances, payment events, postings, suspense, and reversals preserve a traceable ledger path.
Certifications, overrides, payment reviews, annual reviews, and action-package decisions record who acted, when, why, and against which evidence.
§ Next Step
We will map the exact handoff from your credit decision into closing, boarding, obligations, payments, reviews, and portfolio actions - including what belongs in the first controlled deployment.