Financial services

Financial services · vertical overview and map of the eight screens

The Financial services vertical adapts SellioCRM for banks, credit unions, insurers, asset managers, brokerages and fintechs. It replaces the flat contact with a graph of parties, puts an onboarding case with a checklist in front of any product, runs identity and sanctions checks through market providers, and seals every regulated decision into an immutable trail. It is optional: until an administrator enables it, nothing changes in your CRM.

The Financial services vertical exists because a regulated institution does not sell to a contact: it has a relationship with a party, and that party can only be given a product once it is known, verified and approved. An ordinary CRM inverts that order, lets the offer happen first and pushes the paperwork to the end. Here the order is the regulator's: the party exists, the onboarding case is opened, the requirements are met, screening runs, an officer decides, and only then is the product offered.

💡 To enable it: Settings, then Verticals, and turn on Financial services. Only whoever administers the organization can do that. The menu items in the Financial services group appear once it is on.

What this vertical is, and what it is not

It is the relationship and compliance system, not the banking system. It does not move money, it is not a ledger, and it is never the authoritative source of a balance. When you bring an account over from a source system, it comes in as a mirrored account, keeps the date of the data and shows on screen whether that number is current or stale. That way nobody confuses the snapshot with the original.

Models parties, people and organizations, and the ownership graph between them.
Calculates ultimate beneficial owners by walking that graph and keeps the path as evidence.
Runs onboarding cases with a requirement checklist per party type.
Runs checks for identity, document, biometrics, sanctions, PEP, adverse media, company registry and credit bureau.
Records every regulated decision in a trail that cannot be edited.
Does not execute transactions, does not issue an official statement and does not replace the core banking system.

The map of the eight screens

With the vertical on, the menu gains the Financial services group with eight screens. They were designed in the sequence of the real work, and you can walk from the first to the last without leaving the module.

Overview: the compliance snapshot of the organization. It shows the total number of parties, how many have KYC approved, how many legal holds are active and how many households exist, plus the distributions of parties, onboarding cases, decisions, screening results, offers and applications.
Parties: the central register. Create people and organizations, link relationships with an ownership percentage, calculate the beneficial owners, keep the party profile and mirror the accounts and products they hold in other systems.
Onboarding: one case per party, with the requirement checklist, the risk rating, a read on how many mandatory requirements have been met, and the Approve and Reject buttons.
Screening: the list of verification providers and the trigger for each check. It shows which providers are ready and which are waiting on a credential, and stores every result as evidence.
Offers: offer a product to a party. Only parties with KYC approved are eligible, and accepting or rejecting seals a suitability decision.
Applications: the internal pipeline that starts from an accepted offer. It runs through Submitted, In review, Approved or Declined, and Active.
Households: groups parties into a family or economic group and shows the consolidated balance, split by currency.
Governance: the jurisdictions you edit, the trail of regulated decisions with an integrity check, and the legal holds that prevent deleting a subject under investigation.

The full path, from record to active account

In Governance, review the jurisdictions. Brazil, the European Union and the United States are created the first time you open the screen, and you can add, rename or remove whichever you like.
In Parties, use New party, choose the Type between Organization and Person, enter the Name and click Add party.
Still in Parties, select the party you created and fill in the Profile block. For a person, Occupation, Income range and the Politically exposed person flag. For an organization, Industry, Annual revenue range and Publicly traded. The system returns a Risk suggestion, which is a suggestion and not a decision.
If the party is an organization, build the graph under Relationships: pick the Type, the Related to party and the percentage. The beneficial owners appear calculated just below, with the path that produced them.
In Onboarding, pick the party under Open case for and click Open case. The checklist comes pre-seeded according to the party type.
In Screening, choose the Party, choose the Check and run it. Bring the result back into the case by marking the matching requirement as Met.
Back in Onboarding, once the mandatory requirement count is complete, click Approve. To Reject, enter the reasons separated by commas.
In Offers, pick the party, confirm that it shows as Eligible and click Create offer. Once the offer is accepted, use Apply to open the application and walk it through Submit for review, Approve and Activate.

Example: Vega Capital opens a relationship with Sertão Metalworks. In Parties, the organization is registered and the graph takes on two owners: Ana with 60% and Bruno with 25% of a holding company that owns 40% of the metalworks. The screen shows Ana with 60% effective ownership and Bruno with 10%, each with the path that produced the number. The onboarding case for an organization is created with six requirements, four of them mandatory. The sanctions screening comes back as Clear and the adverse media screening comes back as Review, so the analyst opens an investigation before touching the case. With KYC approved, an offer for a US$ 250,000.00 working capital line is created, accepted by the client and becomes an application that ends as Active.

The doors the system locks

Approving an onboarding case requires every mandatory requirement to be met. There is no approving over the top.
Rejecting a case, rejecting an offer or declining an application requires structured reasons. A refusal with no reason is not saved.
Creating an offer for a party without KYC approved is blocked, and the screen says where to fix it: approve their KYC in Onboarding first.
A subject under legal hold cannot be deleted, and that applies to households as well.
Every regulated decision is written immutably and chained, and the Governance screen has a Verify integrity button to prove nobody tampered with it.

Who can use it and what has to be turned on

Enabling the vertical is up to whoever administers the organization. Once it is on, access to the screens follows the normal permissions of your user role, and data stays isolated by organization just as it is everywhere else in the system. Identity and sanctions checks depend on provider credentials, which are configured by the service operator: with no credential, the provider shows as Waiting on credential and the check returns Not configured, never an invented result.

Frequently asked questions

I turned the vertical off, did I lose the data? No. Turning it off hides the screens from the menu; what you recorded stays stored and reappears when you turn it on again.
Can I delete a party? You can, as long as it is not under legal hold. If it is, the system refuses the deletion in order to preserve the evidence.
Can I erase a wrong decision from the trail? No, and that is deliberate. The trail accepts no edits and no deletions. The right move is to record the new decision, which then becomes the most recent one.
Why does the menu not show Financial services? Either the vertical was never enabled, or your role has no access. Check under Settings, Verticals.

Open this article inside the system →