Skip to content

Record lifecycle and statuses

A status shows the current lifecycle position of an application, loan, or instalment. User actions and configured automation change statuses. Labels, notes, and assignments add context without changing them.

Keep origination and servicing separate

An application answers what the borrower requested and what processing outcome has been recorded. A loan answers what agreement is being serviced. Lend is the operation between them: it changes the application to Issued and creates the separate Active loan.

Within the loan, the schedule describes expected amounts. Payments describe money received. Allocations explain how each payment affected the schedule or why some money remains pending, on deposit, or as an overpayment.

Keep partner identity separate from access

Concept What it represents What it controls
Intermediary The legal partner organisation. Organisation details and the users and groups associated with that partner.
Affiliation The intermediary context represented by the current user. Seller and Submitter defaults on a new application and partner scoping for applicable application queries.
Permission group A set of allowed operations. What the user can read or change; access is cumulative across active groups.
Partner application query A configured application list with Partner visibility. Which submitted applications appear in that list when the affiliation restriction applies.

An affiliation does not grant permission, and an intermediary does not create a partner channel by itself. Use Intermediaries and affiliations for access maintenance and Distribute lending through intermediaries for the complete channel.

Keep information, rules, and follow-up separate

Concept Question it answers Direct result
Enrichment What did the configured external service return for this person or application? Stores a dated result for review. It does not approve or reject the application.
Decision Do the configured application conditions match when this schedule or application operation triggers the rule? Runs the configured application operation and field changes when the condition matches.
Event action What follow-up should run after this platform event? Calls a webhook, generates a document, sends email, or sends SMS when its condition matches.

These features can appear in one workflow without becoming one operation. A reviewer can use an enrichment result, a decision can change application processing, and a later event action can notify another system. An event-action failure has its own execution status; check it separately from the application status.

Use the Glossary when you need one definition and the links to its detailed guidance.

Use status with its record history

When you investigate a record, check three things together:

  1. the current status, which tells you the recorded outcome so far;
  2. the available actions, which show what the current user can do next;
  3. the history, which shows how and when the record reached that status.

Available actions also depend on the product, permissions, and configured process. A missing button does not by itself mean that the status is wrong.

Record What its lifecycle describes
Application Progress from initial entry through review, approval, lending, rejection, or expiry.
Loan Whether the agreement is active or has reached a closing or transfer outcome.
Instalment Whether a scheduled amount is upcoming, due, overdue, paid, or cancelled.
Payment allocation How recorded money has been applied or held.

Application lifecycle

The exact route depends on your organisation's process. The following statuses are available to loan applications.

Application status reference

Status Meaning for a user
New The application has been created and can still be worked on.
Incomplete Required information or another processing step is missing.
Ready The application is ready for its next configured review step.
Approved The lending decision is approved, but no loan has been created yet.
Quoted A formal offer has been prepared when that step is used.
Accepted The offered terms have been accepted when that step is used.
Issuing Finsaku is processing the creation of the loan.
Issued Lending completed and the loan record was created.
Rejected The application was declined. It may be reinstated if the process allows it.
Expired The application is no longer valid.
Deleted The application was removed from active work.

Typical application transitions

A configured process can omit Ready or add the Quoted, Accepted, and Issuing states.

Loan lifecycle

A loan is created only after an application is lent. Later payment processing and formal loan actions determine whether it remains active or reaches a closing state.

Loan status reference

Status Meaning for a user
Active The loan is in force and is not otherwise closed.
Repaid The loan has been fully repaid.
Terminated The agreement was ended through a termination action.
Cancelled The loan was cancelled.
Renewed A renewal replaced or continued the original agreement.
Expired The agreement reached its configured expiry.
Ceded The loan was transferred through a cession process.
Write-off The remaining amount was written off through the configured process.

Typical loan transitions

Instalments and payment allocation

Loan status, instalment status, and allocation outcome answer different questions. An active loan can contain overdue instalments, and one payment can contain more than one allocation outcome.

Instalment status

An instalment can be New, Issued, Overdue, Paid, or Cancelled.

Allocation outcome

A payment amount can be Allocated, Pending, Overpayment, Deposit, or Penalty Deposit. One payment can contain several allocation outcomes at the same time.

For example, part of a payment can settle overdue interest, another part can reduce principal, and a remaining part can stay on deposit. Review the allocation detail rather than relying only on the payment total.

Typical instalment transitions