Getting started
LoanHub has separate entry paths for borrowers, institutions and existing users. Start with the account type that matches the work you need to do.
Borrower
Create a personal account and complete your borrower assessment.
Institution
Register the company/institution and its initial administrator.
Existing user
Sign in and LoanHub directs you to the workspace allowed by your role.
- 1
Use your own account
Do not share passwords or use another staff member's login. Audit and approval evidence depends on knowing who performed each action.
- 2
Confirm the active institution and branch
Company staff should confirm their active company, branch and role before changing records.
- 3
Complete the information relevant to your role
Borrowers complete personal and affordability information; institution teams complete company, branch, staff and lending setup.
- 4
Use business references when asking for help
Where LoanHub displays a friendly request, loan, client or incident reference, use it when communicating with support rather than copying internal database identifiers.
Borrower guide
The borrower workspace is designed to let a person build a reusable profile, request funding and manage resulting loans without becoming the permanent property of one lending company.
- 1
Register and verify your account
Complete borrower registration with the identity and contact information requested by LoanHub.
- 2
Build the borrower profile
Add employment status, employer/job information, income, living expenses, existing debt and residential details.
- 3
Add banking and assessment details
Maintain the banking information and affordability inputs used by authorised lending workflows.
- 4
Upload supporting evidence
Add identity, payslip, bank statement, residence or employment evidence where the assessment requires it.
- 5
Review consent choices
Profile sharing, document sharing and credit checks are controlled by explicit borrower consent fields. Read what you are authorising before continuing.
- 6
Create a loan request
State the funding need and submit the request into the marketplace when you are ready for eligible lenders to respond.
- 7
Compare lender offers
Review the terms returned through LoanHub before accepting an offer. Do not accept based only on the instalment; understand the full repayable amount and schedule.
- 8
Manage an active loan
Use your loan workspace to follow due dates, payment status, balance, reminders, documents and conversations.
- 9
Keep your profile current
Update relevant employment, financial, banking and supporting information when it changes so future evaluations are based on current facts.
Institution setup
Institution owners and administrators create the structure within which branches, staff, lending products and operating teams work.
- 1
Register the institution
Provide the institution identity, registration/contact information and initial administrator details required by the onboarding flow.
- 2
Complete governance and settings
Review institution settings, governance information, billing/subscription state and any platform approval requirements.
- 3
Create branches
Add headquarters and operating branches with their district, town, contacts and active status.
- 4
Add staff memberships
Create or invite the people who work for the institution and give them only the roles required for their responsibilities.
- 5
Configure lending products
Define product terms, calculation methods, repayment behaviour, fees and other controls before officers create or approve facilities.
- 6
Configure finance and integrations
Where applicable, complete payment, treasury, credit-bureau, gateway or webhook configuration through the authorised settings screens.
- 7
Train each team in its own queue
Loan officers, finance, collections, compliance, HR and other functions should use their role-specific workflows rather than sharing an owner/admin account.
Roles and access
LoanHub uses platform roles, company memberships, branch context and specialist business roles to decide what a user may see or change.
| Role group | Primary responsibility |
|---|---|
| Platform owner / SuperAdmin | Service-wide institutions, plans, platform finance, reports, audit, incidents and technical operations. |
| Company owner | Highest institution authority for settings, branches, staff, products, lending, billing, HR, accounting and reports. |
| Company administrator | Day-to-day institution administration and cross-department coordination. |
| Branch manager | Branch staff, lending work, collections, performance and branch reporting. |
| Loan officer | Marketplace requests, authorised detail unlocks, assessment and lender offers. |
| Finance / treasury | Disbursements, repayments, reconciliation, accounting, cash and financial evidence. |
| Collections officer | Due and overdue accounts, recovery cases and collection follow-up. |
| Compliance / risk / audit | Access review, evidence, regulatory controls, credit risk and independent oversight. |
| HR / performance | Employee records, reporting lines, attendance, payroll, goals and reviews. |
| Customer / IT support | Authorised user assistance, notifications, communication, incidents and safe escalation. |
| Borrower | Personal profile, funding requests, offers, loans, payments, files and conversations. |
Lending lifecycle
LoanHub supports both marketplace-led and direct professional lending workflows, then manages the resulting facility through servicing and completion.
- 1
Receive or create the application
A lender can work with marketplace requests, direct applications or authorised existing-client workflows.
- 2
Evaluate affordability and evidence
Review the borrower profile, income, expenses, debt, bank information, supporting files, consent and any permitted credit/compliance evidence.
- 3
Apply product and decision controls
Use the institution's configured product, calculation method, fees and credit decision rules rather than inventing terms outside the system.
- 4
Create or approve the offer/facility
Record the approved principal, rate, repayment period, instalment and total repayable through the controlled workflow.
- 5
Disburse with evidence
Finance should only mark a disbursement in line with the institution's approved payment method and evidence.
- 6
Service the schedule
LoanHub tracks repayment schedules, allocations, balances, due dates, overdue state and maturity.
- 7
Handle change formally
Use supported top-up, restructure, renewal or early-settlement workflows so the audit trail remains understandable.
- 8
Complete or recover
A fully settled facility can complete; missed obligations move into the collections/recovery workflows rather than being silently edited away.
Payments, treasury and collections
Money movement requires stronger evidence than ordinary record editing. LoanHub separates posting, evidence, branch cash, reconciliation and recovery responsibilities.
Repayments
Post or verify repayments against the correct loan and preserve the payment channel/evidence required by the workflow.
Disbursements
Finance teams control outgoing loan funds and the user responsible for the disbursement is recorded.
Treasury
Branch opening values, money-in/money-out entries, funding transfers and daily submissions support branch cash accountability.
Collections
Due and overdue facilities can generate collection cases and follow-up activity while maturity recovery runs as a controlled background workflow.
Accounting, reconciliation and reporting
LoanHub links lending operations to financial evidence through a double-entry accounting foundation, reconciliation routines and generated reports.
- 1
Use the chart of accounts
Maintain the accounts needed for the institution's accounting policy rather than posting everything to generic buckets.
- 2
Post balanced journals
Journal entries should balance before posting. Corrections should be traceable rather than rewriting history without evidence.
- 3
Review trial balance and statements
Use trial balance, profit/loss and balance-sheet views to review the accounting position generated by posted activity.
- 4
Reconcile external evidence
Use bank statement/reconciliation workflows and approved exceptions to explain differences between operational records and external evidence.
- 5
Generate and schedule reports
Run manual reports when needed and configure scheduled PDF/CSV outputs for recurring management information.
- 6
Review automated reconciliation
LoanHub includes midnight operational reconciliation routines; investigate exceptions instead of treating automation as a substitute for review.
HR, performance and company operations
LoanHub can operate beyond the loan desk, giving the institution a connected workspace for workforce and internal operations.
Chat, calls, notifications and files
Communication is part of the operating record. LoanHub keeps collaboration close to the business workflow while preserving access controls.
Realtime communication
Direct/group conversations, presence, typing state, read state, voice notes and managed attachments.
Managed files
Permissioned upload/download, checksums, encrypted storage, visibility controls and report/document storage.
Controlled calling
Employee call records, company calling policy, recording retention, supervision and quality review where approved infrastructure is provisioned.
Security, privacy and evidence
Every user should understand the difference between being able to see a record and being authorised to disclose or change it.
LoanHub isolates institution tenants and uses active company/branch context when enforcing business access.
Managed files and chat text support authenticated AES-GCM encryption at rest. The authorised LoanHub server can decrypt content to deliver permitted workflows; this is not client-to-client end-to-end encryption.
Production web and realtime traffic are designed to run through HTTPS/WSS.
Ordinary users receive safe error messages and a request reference; technical diagnostics are restricted to authorised platform operations.
Audit and transparency controls are designed to make important CRUD/business activity attributable and reviewable.
Sensitive HR, compliance and finance evidence should use confidential visibility and the narrowest practical role access.
Troubleshooting and safe support
Most support problems can be narrowed down without exposing private information or giving a user excessive access.
- 1
Check the active role
If a menu/action is missing, confirm that the user is operating under the correct professional role.
- 2
Check company and branch context
Company users should confirm the active institution and branch before assuming a record is missing.
- 3
Refresh the session safely
If authentication has expired, sign in again instead of repeatedly retrying a protected action with stale credentials.
- 4
Use the displayed reference
For safe errors, record the request/incident reference and the action being attempted. Do not send passwords, tokens or private keys to support.
- 5
Check external dependency status
Payment, credit-bureau or calling issues may depend on third-party onboarding, credentials, callbacks or infrastructure outside LoanHub.
- 6
Escalate with minimum necessary data
Share only the business reference and context needed for support to investigate. Avoid sending borrower documents or personal financial details in uncontrolled channels.
Quick operating rules
- • Confirm active company and branch before changing company records.
- • Use friendly business references rather than raw database identifiers in support communication.
- • Do not mark money successful without verified provider status or approved manual evidence.
- • Keep HR, compliance and finance evidence confidential unless the workflow explicitly requires broader access.
- • Do not share passwords, API tokens, JWT keys or deployment secrets.