Glossary

Use the documentation search to find a term from any page. Each definition below links to the procedure or configuration page that explains the term in context.

Some shared configuration screens and technical interfaces use Quote for an application and Contract for a loan. The customer-facing documentation uses application and loan unless the shared label is visible in Finsaku.

Affiliation

An affiliation is the organisation context represented by a signed-in user. For an intermediary user, it identifies the partner on whose behalf the user is working. Finsaku uses the current affiliation when it sets Seller and Submitter on a new application and when it applies the partner restriction to applicable application queries.

An affiliation does not grant operations by itself. Active permission groups determine what the user can do. See Intermediaries and affiliations and Distribute lending through intermediaries.

Allocation

An allocation is the calculated treatment of part of a payment. It shows whether money was applied to an instalment or invoice line, is waiting to be applied, is held as a deposit, or exceeds what the current calculation can apply.

An allocation order is the priority used during calculation; the allocation is the result. One payment can produce several allocations. See Payment allocation and schedules.

Application

A loan application contains the borrower's request before an agreement exists. It holds the selected product, requested terms, calculation, supporting information, processing status, and lending decision.

Approve records approval. Lend changes the application to Issued and creates the loan. The application and loan then keep their own numbers, statuses, histories, and available actions. See Application overview and Application review and processing.

Borrower

The borrower is the person or legal organisation requesting or receiving the lending. Finsaku stores the party separately so the same person or organisation can be selected in an application and referenced by later loans, payments, documents, messages, notes, and enrichments.

See Find and create people and Person records.

Decision

In Administration, a decision is a configured application rule. A schedule or selected application operation triggers it. If its condition matches, the decision runs the configured application operation and applies any configured field changes.

A decision controls application processing. An event action performs follow-up work after an event; it does not choose the lending outcome. See Decisions.

Enrichment

An enrichment is a dated result returned by a configured external service and stored for a person or application. A credit report is one example. The result supplies information for review; requesting or receiving it does not approve or reject the application.

See Credit reports and enrichments.

Event action

An event action is configured follow-up work that starts after a supported platform event. When its condition matches, it calls a webhook, generates a document, sends email, or sends SMS. Its execution has a separate status such as Completed or Failed.

An event action reacts to an event. A decision evaluates an application rule and can run an application operation. See Event actions and event-action execution history.

Instalment

An instalment is an expected amount with a due date in a loan's payment schedule. It can contain principal, interest, or other lines and has its own status, such as Issued, Overdue, or Paid.

An instalment is not a payment. The instalment states what is expected; a payment states what was received; allocations explain how received money affected the schedule. See Payment allocation and schedules.

Intermediary

An intermediary is a legal organisation that participates in the lending process as a partner. Its Finsaku entry holds organisation details and can be associated with users and permission groups.

Creating an intermediary does not create a user, affiliation, partner query, or external API. Those parts are configured separately. See Intermediaries and affiliations and Distribute lending through intermediaries.

Lend

Lend is the application operation that creates the loan. It is separate from Approve. After it succeeds, the application is Issued and the new loan begins in Active status.

See Process a first application.

Loan

A loan is the agreement created when an authorised user lends an application. It contains the agreed and current terms, balance, payment schedule, received payments, loan actions, and history used during servicing.

Changing or closing a loan uses loan actions and payment processing. The issued application remains available with its own status and history; servicing work takes place on the loan. See Loan overview and Loan changes and closure.

Object Library

The Object Library contains tenant-created structures that can be reused in product versions or referenced by another custom object. A library object defines its stable key, fields, layout, conditions, and summary.

It is separate from System Objects, which describe built-in platform concepts. See Objects and fields and Configure collected data.

Payment

A payment records money received for a loan, including its payer, amount, date, type, action, and allocation order. The payment total alone does not show how the money affected the loan; review its allocations and the recalculated schedule.

See Record payments.

Permission group

A permission group grants a set of Finsaku operations to its active members. Access is cumulative across the active groups assigned directly to a user or through an intermediary.

A group controls what a user can do. An affiliation supplies the partner context in which applicable work is scoped. See Permission groups and Access model and troubleshooting.

Product and product version

A lending product identifies the lending offering. Its active product version contains the data definition and other versioned configuration used when an application is created. Product settings can also select calculation, invoice, template, and workflow dependencies.

See Product settings and Versions and data collection.

Status

A status is the current lifecycle position of one application, loan, instalment, or event-action execution. Status belongs to that specific item: an Approved application can have no loan yet, and an Active loan can contain an Overdue instalment.

Use the status with the available actions and history. See Record lifecycle and statuses.

System object

A system object is a built-in definition for a platform concept such as a person, application, loan, user, or intermediary. Its object type and stable identity are predefined, although administrators can configure permitted fields and presentation settings.

Use a custom Object Library item for a reusable product-specific structure. See Objects and fields.