Flow Diagram · Money Manager
Collect account balances
How Money Manager keeps every customer's balances up to date, checks their health and, when a balance runs low, asks a partner for microcredit offers.
The example of the step-by-step guide. Each actor has a lane and time runs left to right; diamonds are decisions. Take the guided tour for the four layers of the notation.
- Partner goalThe partner wants as many offers as possible, to have a wider impact.A goal can belong to a partner, not only to the customer: here it shapes how the offer request is built.
- Decisions in the flowA diamond is a decision; each branch carries its answer.Keep decisions for the business choices that change the flow. Technical retries do not belong here.
- Event between componentsDashed line: an event. Accounts & Transactions tells the advice side that a balance changed.The checks run on their own service, so a slow check never delays the balance sync.
- Actors: Scheduled data sync per user, Collect accounts and balances, Verify auth credentials, Provide accounts and balances, Sync balances, Run account balance health checks, All fine?, Create issue(s), Low or negative balance?, Anonymise profile and retrieve microcredit options, Process profile and send microcredit offer(s) details, Done
- System Entities: User Bank Connection Refresh, Bank Connection, Account, Account Balance (time series), Currency, Account Health Check Execution, Account Health Check, Account Health Check Issue, Account Health Check Issue Template, Microcredit offer request, Microcredit offer options
- Metrics: Refresh success rate (Scheduled refreshes that end with up-to-date balances.), Offer screening ratio (Offer requests that come back with at least one microcredit option.)
- Technical Components: Accounts & Transactions, Bank Adapter (many), Bank System, Customer Advice & Insights, Users, Partner's system
- Partner goal. The partner wants as many offers as possible, to have a wider impact.. A goal can belong to a partner, not only to the customer: here it shapes how the offer request is built.
- Decisions in the flow. A diamond is a decision; each branch carries its answer.. Keep decisions for the business choices that change the flow. Technical retries do not belong here.
- Event between components. Dashed line: an event. Accounts & Transactions tells the advice side that a balance changed.. The checks run on their own service, so a slow check never delays the balance sync.
