Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.finpace.tech/llms.txt

Use this file to discover all available pages before exploring further.

​
Accounts, arrangements, and mandates

​
Arrangement model

An arrangement is the contractual banking object held by the customer. Examples:
  • demand deposit account
  • savings account
  • overdraft-linked current account
  • loan facility
  • term loan
  • revolving credit line
An account is the operational representation used for:
  • balances
  • postings
  • statements
  • servicing actions
  • payment routing

​
Lifecycle states

Typical arrangement states:
  • draft
  • pending_review
  • approved
  • active
  • restricted
  • dormant
  • closed
State transitions are controlled by:
  • product rules
  • compliance status
  • approval policies
  • funding conditions
  • document completion

​
Signatories and mandates

For business banking, the arrangement model must support:
  • single signatory
  • joint signatory
  • amount-tier authority
  • channel-specific authority
  • transaction-type restrictions
  • validity periods
  • revocation history

​
Standing orders and direct debit mandates

These are separate controlled objects with:
  • creation source
  • customer authorization evidence
  • schedule or mandate attributes
  • status history
  • cancellation reason
  • amendment audit

​
Why this matters to documentation

Tier-1 institutions do not want a generic “account” page. They need to see:
  • the difference between party, customer, arrangement, account, and mandate
  • the lifecycle states
  • who can change what
  • which changes require approval