COREDO – EU Legal & Compliance Services Expert legal consulting, financial licensing (EMI, PSP, CASP under MiCA), and AML/CFT compliance across the European Union. Headquartered in Prague, we provide seamless regulatory solutions in Germany, Poland, Lithuania, and all 27 EU member states.
Pavel Kos
17.03.2026 | 6 min read
Updated: 17.03.2026
I often tell entrepreneurs: opening a corporate account today is not just an application form and a set of incorporation documents. banking compliance relies on a clear, verifiable and logical answer to one question: what is the purpose of the account (purpose of account). The more precisely and transparently you explain the account’s purpose to the bank, the faster you’ll pass onboarding, the lower the risk of additional requests and escalation to EDD, and the more stable your banking relationships will be.
Over years of COREDO‘s work in the EU, the UK, Singapore, Dubai, the Czech Republic, Slovakia, Estonia and Cyprus, the team has implemented hundreds of projects for company registration, licensing of financial services and AML consulting. In every case the account’s purpose became a central topic: it affects client risk assessment, document architecture, integration into the bank’s transaction monitoring systems and, ultimately, the speed of business launch. In this article I have systematized COREDO’s practices and collected real examples of purpose of account formulations for different models so that executives and CFOs can use the material as a practical guide.
Account purpose – source of funds/wealth
A correct understanding of the terms saves weeks of correspondence with the bank. Purpose of account: this is the explanation of why exactly the company opens the account: what types of operations are expected, with which counterparties and in which currencies, how incoming and outgoing payments will look, and how the account purpose correlates with the business model. It is not a one-paragraph declaration, but a concise yet rich narrative, supported by documents and figures.
Difference between the purpose of the account, the source of funds, and the source of wealth
- Purpose of account: the operational use of the account and the expected payment flows. It’s about transactions: who you pay, who pays you, for what and how often.
- Source of funds: the origin of specific funds that come into the account. It’s about incoming money: invoices, contracts, loan agreements, investment agreements.
- source of wealth: the origin of beneficiaries’ capital (UBO). It’s about wealth: sale of a business, dividends, investment income, inheritance.
Our experience at COREDO has shown: when these three concepts are combined into a consistent package, the likelihood of additional questions from the compliance department is greatly reduced. It is easier for the bank to reconcile the logic of incoming funds (source of funds) with the account purpose and ensure that the UBO’s capital history (source of wealth) supports the scale of operations.
What the bank expects in the account description
The bank views the purpose of account through the lens of KYC/CDD. At the onboarding stage the client fills out an onboarding questionnaire with fields about the business model, geographies, categories of counterparties, average and maximum amounts, frequency, currencies, payment channels and the involvement of third parties. If the model is high-risk, EDD is triggered: an enhanced analysis of documents, verification of counterparties and confirmation by independent sources.
COREDO’s practice confirms: a clear structure of the purpose of account and an attached documentary chain reduce the need for EDD even for complex models: trading, PSP, payment aggregation and cross-border services. The bank’s compliance team sees the predictability of flows and can set monitoring rules in advance.
Account purpose: how risk is assessed
A bank’s compliance policy is built on its risk appetite: a set of criteria by which the bank selects clients and the scenarios it is prepared to support. Account purpose is one of the main variables in this matrix. It shows how predictable a client’s behaviour is in the context of sanctions, PEP risks, geographies and industry.
Causes of SARs, risk appetite and red flags
Banks use a list of red flag indicators: payment structuring, round‑tripping/circular payments, layering between related companies, mismatch between the description of activity and the payment purpose in SWIFT messages. If the account purpose is vague, the likelihood of a suspicious activity report (SAR) increases, as do manual reviews.
The solution developed at COREDO is to give the bank a verifiable map of operations: who pays, under which contract, in what currency, how amounts change seasonally, and how discounts and fees are structured. This format closes red flags at intake and reduces the frequency of escalations to the FIU.
How banks verify the purpose of an account
Verification proceeds in two layers: onboarding and ongoing monitoring. At the start, compliance creates client profiling and segments the client by risk. Then the bank’s TMS monitors the conformity of actual transactions with the declared account purpose, compares payment purposes, geographies and counterpart behaviour. A periodic review (periodic review cycles) updates the profile and documents.
The COREDO team often joins precisely at the intersection of onboarding and monitoring. We prepare not only a statement about the account purpose, but also a payment flow mapping that the bank can import into its TMS for rule tuning. This reduces false positives and lowers the load on manual review.
Sanctions and PEP screening
The bank checks sanctions against OFAC, the EU and the UN, conducts PEP screening of beneficiaries and directors, and uses name screening for counterparties. Consideration of CRS reporting and cross‑border tax residency is important: if you operate in multiple jurisdictions, explain where the company’s and the UBO’s tax residency is, and why the account purpose is consistent with that structure. A transparent narrative eliminates ambiguity and removes unnecessary questions.
How to prepare an account explanation
I recommend thinking of the purpose of account as a file that is easily read by three parties: the bank manager, the compliance analyst and the TMS. It should be concise, structured, and supported by evidence.
Onboarding forms: how to fill in the fields
Typical form fields and best practices:
- Activity: an acceptable business description of 2–3 sentences, without jargon or generalizations. Specify the product/service, target markets, client type (B2B/B2C), and sales channels.
- Geographies: countries of suppliers and clients, with shares in percentages.
- Payment flows: inbound vs outbound, average/maximum transaction amounts, frequency, seasonality.
- Currencies: multi-currency operations, conversion, hedging, and settlement/correspondent banks.
- Third parties: agency/escrow mechanisms and criteria for selecting intermediaries.
- Documents: list of contracts, invoices, purchase orders, shipping docs and L/Cs that you attach.
COREDO uses onboarding templates with example phrases for different industries. This approach removes ambiguity in phrasing and speeds up alignment with the bank’s relationship manager.
contracts/invoices/shipping documents/letter of credit/bill of lading
The bank prefers a continuous documentary chain:
- Contract + specification + invoice/PO;
- Delivery: bill of lading (B/L), airway bill (AWB), CMR, packing list;
- Payment: SWIFT/SEPA confirmations, agreed terms (Incoterms, timing);
- Trade finance: letters of credit (L/C), insurance, certificates of origin.
Sampling checks and the quality of evidence are more important than formal volume. If one case is fully transparent, the likelihood of additional requests decreases for the entire portfolio of operations.
Payment flow mapping: flow diagram
I recommend attaching a flow diagram: sources of incoming payments, routes of outgoing payments, fees, conversions, correspondent banks. Mark counterparties with elevated risk, indicate escalation rules and limits. The bank will see that you control third-party payments and will be able to adjust the TMS without unnecessary false positives.
Confirmation of source of funds
For source of funds, use:
- Invoices and certificates of completed work;
- Loan/investment agreements, board resolutions, investor statements;
- Proof of funds for M&A transactions.
For source of wealth:
- Evidence of prior business sales, dividends, brokerage reports;
- Tax returns and residency confirmations.
The COREDO team assembles these packages so they directly reference the account purpose and leave no gaps for the analyst.
Which words are considered “red flags”?
Red flags in wording:
- «General trading activity», «investments in various directions» – too vague.
- «Transfers to third parties by agreement» – no control trigger.
- «Crypto operations/cash-out» without a license and policy – an immediate stop.
Replace them with specifics:
- «B2B wholesale supply of electronics from the EU to the GCC, under contracts with X and Y, Incoterms FCA, average transaction 80–120k, 6–8 payments/month.»
- «Agency commissions under agreement No…, rate 1.2–1.6%, reporting monthly».
Sample account purposes by industry
Below are working examples that the COREDO team adapted for different models. Use them as guidelines, adding your specific data.
Trading company (import-export)
«Purpose of account: settlements for wholesale supplies of medical equipment from manufacturers in the Czech Republic and Slovakia to buyers in the UAE and Saudi Arabia. Incoming payments, prepayment/postpayment on invoices (EUR, USD), outgoing – payments to suppliers and logistics providers, insurance, customs duties. Average incoming payment amount: 90–130k, 10–15 transactions/month. Documents: master agreements, specifications, B/L, insurance policies, certificates of conformity. Currency risk hedged with forwards.»
E-commerce
«Purpose of account: acceptance of payments for the sale of consumer goods in the EU and the UK through marketplaces and PSPs. Incoming: payouts from payment aggregators (EUR, GBP), outgoing: refunds, payment for fulfilment, marketing and 3PL. Average payouts: 25–40k, frequency weekly. Supporting documents – contracts with marketplaces, PSP reports, invoices from warehousing operators.»
Payment agency (PSP) and fintech
«Purpose of account: a settlement account for PSP agent commissions, PI license in the EU undergoing passporting. Incoming: merchant acquiring fees (EUR), outgoing – payouts to merchants and correspondent PSPs, scheme fees. Average balance: 500–700k, share of high‑risk MCCs up to 5% with separate limits. AML policies/KYC/SDD‑EDD attached, TMS configured for rule‑based and behavioral analytics, reporting to the regulator and FIU as required by local law.»
Dividend flows
«Purpose of account: recording receipts from subsidiaries in the EU and Singapore and distributing dividends to shareholders. Incoming – dividend payments and intra-group loans (EUR, USD, SGD), outgoing: dividends, interest on loans, intra-group advisory services. Transactions are infrequent, large, with documentary support (board minutes, intercompany agreements, transfer pricing policy). The account is not intended for operational trading.»
Freelance and outsourcing settlements
«Purpose of account: receiving payments for B2B IT outsourcing services from clients in the EU and the UK, payment of contractors in Estonia and Poland. Incoming: invoices for sprints/fixed milestones (EUR, GBP), outgoing – contractor payments under contracts, taxes and salaries. Average invoice: 8–15k, 20–30 payments/month. Documentary chain: master agreement, SoW, timesheets, acceptance acts.»
Crypto businesses
«Purpose of account: account of an operating company providing SaaS for crypto compliance monitoring (without custody or exchange of digital assets). Incoming: B2B subscriptions (EUR, USD), outgoing – salaries, services, marketing. No separate crypto risk. For a licensed subsidiary with a VASP license, a separate account with AML/CFT policies, on‑chain analytics and restrictions on high‑risk jurisdictions.»
International transfers, third parties, escrow
Some models require special precision in descriptions. Here, not only the wording of the account purpose matters, but also how you document exceptions.
Risks of cross-border operations
Specify through which correspondent accounts and banks the transfers pass, how you reduce the risk of sanctions-related blocks, and how you handle name screening false positives. Describe why the currency structure is sensible, and how you match SWIFT payment descriptions with invoices so the bank’s TMS correctly maps the transactions.
How to describe escrow and agency schemes
Для escrow/agency settlements, describe in detail the role of each participant, the conditions for release of funds, control events and reporting. Attach the escrow agreement, agency agreements, and reconciliation statements. The bank expects to see a transparent audit trail and mechanisms to prevent commingling of funds.
Controlled payments and nominee risks
Если деньги поступают от третьих лиц, поясните, по какой причине и по какому договору. Укажите критерии допуска третьих лиц, KYC‑процедуры и как вы исключаете nominee directors/shareholders и shell‑company признаки у контрагентов. Это ключ к прохождению EDD без задержек.
Avoiding EDD for regular inflows
For regular large inflows, describe:
- The pricing formula and payment schedule;
- Fluctuations in amounts and seasonality;
- Escalation triggers and limits.
Our cases show: when these parameters are specified in advance, the bank maintains standard CDD and does not escalate the client to EDD.
How to reduce the bank’s manual queries
A good story about the account purpose is also good operations. Banks value clients whose processes can be algorithmized.
TMS and reducing false positives
Describe how you integrate the purpose of account into your TMS/ERP: you add tags for counterparties, payment purpose, currencies and limits. Propose to the bank a rule map for rule tuning: allowed countries, MCC, amount ranges. This approach reduces the false positive rate and shortens the bank’s manual review hours.
Due diligence: checklists and templates
The COREDO team developed Due Diligence checklist for a corporate account: list of documents, wordings, flow diagrams and examples of acceptable payment purposes. We add an escalation path: on which event we escalate to compliance, which data we provide first, and how we maintain record retention according to regulator requirements.
Onboarding KPIs: time, declines
I recommend tracking:
- Time to onboard in days by banks and jurisdictions;
- Decline rate and reasons for declines;
- Verification cost (hours of preparation, document collection);
- SAR rate at the bank for your segment.
These KPIs show the ROI from preparing a high-quality purpose of account and help uncover bottlenecks in the process.
GDPR: record retention and audit trail
Respect GDPR and local data protection laws: store KYC packages with restricted access, log changes to the client profile and maintain an audit trail. Banks value discipline in record retention and transparency of decision-making; this reduces risks for both parties.
Frequently asked questions from executives
- How much does the level of detail of the purpose of account affect the speed of account opening? Detailed explanations with supporting documents speed up the decision. Overloading with unstructured details slows it down. Find a balance: 1–2 pages of narrative + an appendix with figures and documents.
- How do you relate the ROI from opening an account to KYC/EDD costs? Count the time savings and the reduced risk of de-banking. Preparing a well-crafted package is cheaper than operational downtime and the loss of correspondent banking relationships.
- How do you scale explanations as the client base grows? Use template descriptions by segment, payment flow mapping by product lines, and update the narrative with each material change.
- Which industry phrasings are preferable for banks in the EU/Asia? Banks value specificity, industry terms without jargon, a clear reference to regulatory frameworks and links to public registries (beneficial ownership registers, company registries).
- How do you minimize the risk of de-banking in high-risk sectors? Don’t hide the risk — manage it: separate accounts for segments, limits, geographic filters, independent counterparty controls and regular periodic reviews with the bank.
COREDO Case Studies
I believe in the power of examples. Below: a few excerpts from our practice where the account’s purpose became a critical factor for success.
Electronics importer in the EU: trade finance
A client with a hub in Estonia and warehouses in the Czech Republic was expanding into the GCC. We defined the account purpose as wholesale deliveries under Incoterms FCA, attached master contracts, specifications, a sample B/L and insurance policies. We prepared a payment flow mapping: incoming from distributors, outgoing to suppliers and logistics providers, and hedging rates. The bank in the EU approved the account within 8 business days; letters of credit (L/Cs) were enabled within a month.
PSP in the UK and EU: licensing
A fintech company was applying for a PI license in one of the EU jurisdictions and opening a current account in the UK. The COREDO team delivered a package: AML/CFT policies, SDD/EDD, a TMS description with rule tuning, an MCC register, limits, and escalation scenarios. The account purpose was described as agency commissions and settlements with merchants, without holding client funds on the operating account. The account was opened faster than the market average; the regulator approved the license within the standard timeframe.
Holding company in Singapore and Dubai
The holding company consolidated dividends from the EU and Asia. We created a separate multi-currency account with clear stipulations: intra-group flows only, board minutes and transfer pricing policy attached, transactions are large and infrequent. The account purpose excluded operational trading and crypto services. The bank in Singapore accepted the package without EDD and set a predictable schedule for periodic review.
Export of SaaS services from Central Europe
The company sold B2B subscriptions in the EU and the UK. We structured the narrative: pricing plans, average MRR, churn, and geographies. We pulled together contracts, SoW, and reports from the billing system. Account purpose: collection of subscription revenues and payments to contractors. The bank in Estonia appreciated the model’s transparency, opened the account in a short time, and enabled foreign currency correspondent accounts.
Preparing a purpose-of-account statement
I use this plan as a checklist with client and compliance teams.
Client and UBO profiling
Gather beneficiary data (UBO), disclose the ultimate beneficial owner, and conduct PEP and sanctions screening. Set the scope: jurisdictions, tax residency, CRS obligations. Check public beneficial ownership registers in the EU/UK.
Business model and narrative
Describe the business in plain language: product, clients, sales, jurisdictions. Summarize inbound/outbound patterns: amounts, currencies, frequency. Add a section on risk management: high‑risk jurisdictions, filters, escalations, de‑risking approaches.
Documents and evidence
Collect the best evidence: contracts, purchase orders, invoices, shipping invoices, L/C, B/L, PSP reports. Tie each transaction type to a supporting document and to the payment purpose. Prepare sampling and a quality checklist.
Payment flow and monitoring
Create a diagram of flows with counterparties, limits, fees, conversions, and correspondent banks. Explain how your TMS or ERP supports monitoring: name screening, rule tuning, false positives, escalation path.
Communication with the bank manager
Provide the package to the bank relationship manager. Discuss risk areas in advance and agree the format of responses to frequent bank inquiries. Specify a contact person on your side and an SLA for responses. This proactive approach reduces the likelihood of a SAR and speeds up onboarding.
Purpose of the account in cross-border operations
- Remove ambiguity: replace “international transfers by agreement” with “payments to suppliers in the Czech Republic and Slovakia for electronics, delivery FCA, weekly invoices”.
- Disclose correspondent banking: “USD payments will go through bank X, EUR: via SEPA; sanctions lists are checked before issuing an invoice”.
- Explain the currency structure and the frequency of conversions; add a policy on exchange-rate risks.
- Show controls over third parties and escrow, if any.
Multicurrency account for the holding company
- Separate the operational and holding accounts.
- Describe intra-group agreements, transfer pricing and the dividend calendar.
- Indicate that the account will not commingle client funds and operational trading.
- Attach board resolutions and intercompany agreements with market pricing.
Reduce the number of requests when opening an account
- Use onboarding questionnaires and purpose of account templates with pre-filled fields.
- Attach a payment flow diagram and a register of counterparties with risk segmentation.
- Send documents in the structure «transaction – proof, payment purpose».
- Clarify the role of the client relationship manager and agree on a communication channel for quick clarifications.
Phrases that reduce the likelihood of SAR/EDD
- “Account purpose: settlements under B2B contracts for the supply of X to the EU. Incoming, prepayment/postpayment from distributors; outgoing to the manufacturer and logistics providers. Documents are attached for each shipment.”
- “The account is used for PSP agency commissions under a PI license. Client funds are held in segregated accounts, operating account: only commissions and operating expenses.”
- “Regular large inflows, dividends by board resolution; documents confirm the source of funds and tax accounting.”
How banks verify the purpose of an account
The bank matches the narrative to actual SWIFT/SEPA payment details, analyzes frequency, amounts and geographies. If there are discrepancies, it requests explanations and documentation. If your audit trail is tidy and record retention is observed, responses take hours, not weeks. A stable client profile reduces the frequency of periodic reviews and makes it easier to scale operations.
How COREDO helps and why it’s beneficial
I built COREDO as a full‑cycle company: company formation in the EU, United Kingdom, Estonia, Czechia, Slovakia, Cyprus, Singapore and Dubai; obtaining financial licenses (crypto, PI/EMI, forex brokerage), AML consulting and onboarding support with banks and EMIs. We bring lawyers, compliance officers and financial analysts together into a single team focused on the client’s assignment.
The benefits of the approach are felt immediately:
- Reduced time to onboard thanks to a high‑quality purpose‑of‑account statement and documentary chain.
- Reduced risk of de‑risking and account closures thanks to predictable payment flows and integration with the bank’s TMS.
- Deliberate cost‑benefit: less manual review, fewer false positives, higher predictability of operational cash.
COREDO’s practice confirms: a transparent account‑purpose narrative is not bureaucracy, but a strategic asset. It increases account opening conversion, speeds up entry into a new market and makes growth manageable.
Conclusions
The account purpose is not a formality, but the primary language of dialogue with the bank. If you clearly explain the purpose of account, show the documentary chain, map payment flows and support this with internal policies, the bank sees a manageable risk and becomes your ally. This is especially important when registering companies internationally, obtaining financial licenses and dealing with cross-border payments.
The COREDO team has been building such solutions for entrepreneurs in the EU, the United Kingdom, Singapore, Dubai, the Czech Republic, Slovakia, Estonia and Cyprus for many years. I have personally seen that a high-quality purpose-of-account statement, prepared according to the plan described in the article, speeds up onboarding, reduces the likelihood of EDD and strengthens trust with the bank. If you need a reliable partner who understands banking compliance and can turn it into workflows and KPIs, COREDO is ready to help: from strategy to successful account opening and sustainable operational support.