Glossary

Amendment: an approval-controlled proposal to change an Authorized record.

Account: the Branch and Currency-specific record that holds a customer or internal GL balance under a Product.

Account Condition: an effective-dated policy that controls interest, linked COB commissions, posting schedules, and related Account behavior.

Application: a request being captured and worked through decisioning and workflow before it becomes a live Customer, Loan Contract, or Fixed Deposit Contract.

Authorization authority: the L1, L2, or L3 level a user may approve; it is separate from ordinary entity permission.

Business date / working day: the Company date used for financial processing, advanced by successful COB rather than assumed from local clock time.

COB: Close of Business, the controlled end-of-working-day process.

Collateral Allocation: the amount of lendable Collateral value assigned to a Facility. It is calculated from the selected valuation basis and risk adjustments.

Collateral Pledge: the approval-controlled legal or operational link between a Collateral Asset and the Facility it supports.

Commission Application: the audit result of evaluating one Commission Type against a Transaction or Account.

Commission Type: the charging policy that defines its trigger, payer, calculation, income posting, taxes, and eligibility rules.

Contribution Bucket: a balance compartment used to separate contributed, withdrawable, guaranteeable, held, or invoked Group value.

Contribution Type: the business classification of a Group contribution, including its allowed and default Buckets and whether it affects withdrawal or guarantee capacity.

Conditional Access Policy: runtime conditions that can permit or restrict a Transaction-family action in addition to normal permission and scope.

Dashboard: the online administrative, operational, workflow, processing, and oversight interface.

Data-access scope: the System, Organization, Branch, Self, and entity-specific boundary on the records a user may act on.

Delivery Log: the record of one attempt to send a Hook to a Third-Party System, including timing, retry state, protected request or response evidence, and outcome.

Evidence: the identity, application fact, document, statement, or audit record captured to support a KYC check or workflow Requirement.

External ID: the mapping between a remoteEaze record and the identifier used for it by an external system.

Facility: the approved credit limit and security container used when booking and controlling a Loan Contract.

Guarantee: a Customer's promise to cover a loan amount. A Group-member Guarantee can reserve and later invoke eligible contribution funds.

Hook: a configured outbound event that maps remoteEaze data to a request for a Third-Party System and can map selected response values back.

Maker-checker: staged record authorization separating capture from one or more approval decisions.

Policy: a reusable set of business rules selected by configuration or an Application. Examples include KYC, eligibility, pricing, repayment, interest, and conditional access policies.

Posting batch: one independently balanced group of Transaction lines that shares a Transaction Code, optional Cost Centre, and optional narrative.

Posting line: one Debit or Credit entry in a Transaction batch. It records the Account, amount, Currency, conversion values, and posting snapshots.

Product: the reusable accounting classification under which Accounts are opened. It defines the Product Type, customer-facing behavior, restrictions, and normal balance.

Record status: maker-checker state such as Captured, Pending Auth, or Authorized; distinct from business and processing status.

Review: a decision recorded for the current workflow stage. A Review does not move the Application by itself; the matching Transition does.

Source of Funds: a lending-capital pool and its pricing method, such as customer deposits, donor funds, equity, external borrowing, or internal funds.

Stage: one point in an operational Workflow. It owns the current assignments, Requirements, Reviews, Actions, and available paths.

Tenant / Company: an institution's isolated operating boundary. The UI usually says Company; technical identifiers may say tenant.

Transaction Code: configuration that classifies and controls the posting represented by a Transaction batch.

Transaction: a balanced financial instruction containing one or more posting batches. Its approval status and processing status are separate.

Transition: an Authorized path from one Workflow stage to another. Its Review Outcome and Business Outcome determine when it is available and what the move means.

Workbench: the offline-capable field interface for prepared capture, local Drafts, cached summaries, and queued synchronization.

Workflow: the Product/policy-defined stages, Requirements, assignments, Reviews, Actions, and Transitions used to process an Application.