Your local timezone
LoanIQ guide library
Getting startedFoundation16 min

Loan IQ tutorial for beginners

Learn the core Loan IQ operating model, terminology and safe workflow habits before processing live servicing activity.

Purpose

Give new users a practical, system-neutral foundation: how deals, facilities and outstandings relate; how events move through controlled workflows; and how to verify results without memorizing confidential screen sequences.

Before you begin

Prerequisites

  • Basic commercial lending lifecycle knowledge
  • Familiarity with borrower, facility, commitment and outstanding terminology
  • Access only through an employer-authorized environment
  • Your institution’s current procedures and authority matrix

Operational sequence

Workflow and validations

01

Orient to the hierarchy

Identify the borrower relationship, deal or agreement, facility and individual outstanding before reviewing activity.

Control check: Legal entity, currency, product, dates and commitment agree to approved source records.
02

Read before changing

Review current status, scheduled events, pending transactions, balances and exceptions.

Control check: No duplicate, future-dated or incomplete event already addresses the request.
03

Translate the instruction

Map the borrower or agent instruction to the correct servicing event and effective date.

Control check: Amount, currency, dates, pricing and settlement details are independently supported.
04

Prepare under maker-checker control

Record the intended event with clear evidence and route it to the required independent reviewer.

Control check: The maker does not release their own critical transaction where policy requires separation.
05

Verify the completed result

Confirm status, cash, principal, accruals, availability, notices and accounting reflect the authorized outcome.

Control check: System positions and downstream evidence reconcile to the instruction.

Troubleshooting

Common breaks and response

The expected transaction option is unavailable

Likely cause

The record status, effective date, user authority, prerequisite event or product configuration does not permit it.

Controlled response

Do not force an alternate route. Check status and prerequisites, then escalate through the approved support path.

Balances look correct but cash or accruals do not

Likely cause

A date, rate, settlement instruction or downstream interface differs from the booked event.

Controlled response

Contain further processing and reconcile the transaction across position, cash, accrual and accounting evidence.

Two similar records appear for the same borrower

Likely cause

The borrower has multiple deals, facilities, currencies or active outstandings.

Controlled response

Use authoritative identifiers and contractual attributes; never select a record from name similarity alone.

Connected impact

Downstream effects

  • Cash and settlement queues
  • Principal, commitment and availability positions
  • Interest and fee accruals
  • Accounting and regulatory feeds
  • Borrower, agent and lender notices

Control record

Audit evidence

  • Authenticated instruction
  • Approved contractual or reference terms
  • Maker-checker record
  • Independent calculation where applicable
  • Post-event position and cash reconciliation

Practical context

Scenario: a beginner receives a drawdown request

Before preparing anything, the operator identifies the correct legal borrower, agreement and facility; confirms availability and value-date rules; checks for pending activity; records the event under the required approval path; and verifies cash, principal and availability after release.

Knowledge check

Check your understanding

What is the safest first action when beginning any Loan IQ servicing task?Show answer
Identify the correct hierarchy record and understand its current status before changing anything. A technically valid action on the wrong deal, facility or outstanding can create material cash, accrual and reporting errors.

Next guide

Deal, facility and outstanding hierarchy

Continue