Why the path matters
A transaction list shows individual payments. A fund-flow view helps an analyst understand sequence: where money entered, how quickly it moved, whether it split across counterparties, whether recipients appear connected, and whether value returned through another path. That sequence can reveal questions that no single payment answers.
The view is bounded by available data. A fintech can analyse transactions and entities it has received or can lawfully access through configured sources. It should not imply knowledge of activity at an external institution when that activity is not present. Unknown destinations remain unknown, not hidden facts filled in by a model.
Visualisation also does not convert a pattern into a conclusion. Rapid transfers can reflect ordinary treasury operations, supplier settlement, payroll, tax, or time-sensitive inventory purchases. The analyst’s task is to compare observed flows with the customer profile and seek evidence for plausible explanations.
An illustrative SME financing example
Consider Cedar Works Ltd., a fictional small manufacturer. The company states that financing will purchase production equipment and raw materials. An illustrative €180,000 facility is paid into its operating account. All names, amounts, and events in this example are synthetic.
Within 30 hours, €146,000 moves out. Cedar sends €38,500 and €37,800 to two new counterparties, €34,700 across three payments to a third, €20,000 to a company sharing a director with Cedar, and €15,000 to an established logistics provider. Seven days later, €12,000 returns from the director-linked company with the reference “project adjustment.”
Several signals merit review: most financing moved soon after receipt; payments were split; four recipients were new; one recipient had a known entity link; and part of the value returned. The observed use also differs from a simple expectation of direct payments to an equipment vendor. None of this establishes an offence.
Read patterns in context
Rapid onward transfer describes timing. It becomes more relevant when paired with customer context: Was the financing intended for immediate supplier settlement? Had contracts already been signed? Is fast movement common for comparable customers? A percentage alone cannot answer those questions.
Payment splitting describes one obligation or flow divided into smaller transfers. It may be used to avoid a control, but it may also follow invoice schedules, banking limits, staged delivery, or separate legal entities. Analysts should examine amounts, references, beneficiaries, timing, and supporting documents before inferring purpose.
Circular flow means value returns to the originator or a connected party, directly or through intermediaries. It can indicate attempts to create artificial activity, but refunds, cancelled orders, deposits, intercompany treasury, and error corrections can create similar shapes. The explanation needs to match the amount, timing, contracts, and accounting treatment.
Entity links add context. Shared directors, addresses, devices, contact details, or counterparties may reveal relationships that affect risk. A digital or network signal does not establish identity by itself. It tells the analyst what connection to verify.
Evidence to request and compare
For Cedar Works, the analyst might request the financing purpose statement, supplier contracts, invoices, purchase orders, proof of delivery, beneficial-ownership information for relevant counterparties, and an explanation for the returned funds. Internal records may show whether the director-linked company was disclosed and whether related-party payments fit policy.
The evidence should be tested against the flow. Do invoice totals match payments? Do dates align with delivery? Are payment references consistent? Is the refund documented by a credit note and returned to the expected account? Are counterparties active businesses in the stated sector? Inconsistency does not automatically prove wrongdoing, but it guides the next question.
Missing information should remain visible. If beneficial ownership is unavailable for one recipient, record that gap. If only Merid-received transactions are shown, label the boundary. If a connection is based on a shared IP or device indicator, present it as a signal requiring assessment, not verified common control.
- Commercial basis: contracts, invoices, orders, and the stated purpose of funds.
- Delivery evidence: shipment, acceptance, or service records appropriate to the transaction.
- Entity context: ownership, directors, addresses, and disclosed related parties.
- Payment logic: amount, timing, references, refunds, and reconciliation to accounting records.
From graph to documented decision
A useful investigation view combines a graph with a transaction timeline. The graph reveals links and concentration; the timeline preserves sequence and exact values. Filters should make clear which period, accounts, and relationship types are displayed. On mobile, the same information should remain available as an ordered list rather than depending on a dense diagram.
An alert might flag rapid dispersal. A case may group that alert with the customer profile, linked-entity signal, screening results, documents, and analyst notes. The final record should state what was observed, what evidence was reviewed, what remained unresolved, and which policy-defined action followed.
FATF’s risk-based guidance supports focusing controls and resources according to assessed risk. SAMA’s monitoring guidance provides a jurisdiction-specific example of ongoing scrutiny for unusual activity in relation to known customer information. Neither source says that a flow pattern proves laundering, and neither endorses a particular vendor.
Following the money is therefore a disciplined way to organise evidence. It helps analysts ask better questions, compare explanations with actual movement, and document a proportionate decision. The value lies in the connection between pattern, context, evidence, and review—not in the visual drama of a graph.
Primary sources
These sources support the regulatory and standards-related statements in this article. They do not endorse Merid or certify any product.
- Risk-Based Approach Guidance for the Banking SectorFinancial Action Task Force (FATF), October 2014
- Section 6: Record KeepingSaudi Central Bank (SAMA) Rulebook
- Section 7: Monitoring of Transactions and ActivitiesSaudi Central Bank (SAMA) Rulebook