KE +254 768 341 410 ZA +27 62 701 6801 AU +61 423 605 291 EU +48 690 567 860 sales@softwaredynamicsgroup.com
Phase 2 · Evaluate Dynamics 365 CE · ISV

BankingFlow 365

Banking CRM on Dynamics 365 Customer Engagement: customer 360, onboarding and KYC, lending workflow, collections, regulatory complaints and core-banking integration for retail and SME banks.

← ISV portfolio
What it does

BankingFlow 365 is a banking solution on Microsoft Dynamics 365 Customer Engagement and Dataverse. It fills the gaps that standard Customer Engagement leaves open for a bank: a customer 360 built for banking, onboarding and KYC, a lending workflow, collections, regulatory complaints with service clocks, a banking service catalogue, and a canonical API layer to the core banking system. It is designed for retail and SME banks in Africa, and especially for multi-country banking groups, for example a South African group with subsidiaries in Kenya and Nigeria. Adapter templates cover Infosys Finacle, Temenos T24 and Transact, and Oracle FLEXCUBE, so that the core stays the system of record while relationship managers, onboarding teams, service teams and collectors work in Dynamics 365. Division packs for commercial, transaction, investment banking, markets and wealth are delivered as separate solutions.

Highlights
Banking 360: one workspace for the relationship manager
Onboarding journeys with KYC screening, risk scoring and four-eyes approval
Lending workflow with a delegated-authority approval matrix
Collections: delinquency buckets, strategies and promise-to-pay
Regulatory complaints with per-regulator service clocks
Banking service catalogue: cards, disputes, standing orders and account changes
Adapter templates for Finacle, Temenos and FLEXCUBE
27 pre-configured security roles, field-level security and audit
Screens
Your branches at a glance
Every pipeline, by stage
Screening and KYC in one view
Complaints and arrears, side by side
The bank on one page
Facilities and covenants
Every loan application
Complaints on the regulator's clock
Open an account in minutes
Every account in one catalogue
Every key fact before applying
Track an application
Feature table
Capability Standard Dynamics 365 With this ISV
Core banking integration No first-party core banking connectors; partner delivered A canonical banking API layer with adapter templates for Temenos T24 and Transact, Infosys Finacle and Oracle FLEXCUBE
Customer 360 A thin banking data model, not wired to a core A banking 360 data model: parties, holdings, alerts and consent, with a relationship manager workspace
Onboarding and KYC A sample onboarding app, with no KYC or AML engine Onboarding journeys, screening adapter, risk matrix, four-eyes approval, periodic review and enhanced due diligence
Lending No maintained first-party loan origination workflow Applications, a delegated-authority approval matrix, credit decisions, conditions precedent and a collateral register
Regulatory complaints Generic case management, with no regulator clocks A complaint taxonomy, per-regulator service profiles and regulatory return records
Banking service requests No banking-specific case types A catalogue of card, dispute, standing order and account change requests, each with a service level
Group exposure No banking hierarchy or exposure roll-up Households, beneficial owners and group exposure in the commercial pack
Collections Not provided Delinquency buckets, collection strategies, promise-to-pay and payment plans
Next best action Earlier banking intelligence offering no longer current A rules-based next-best-action engine and role dashboards
Confidentiality Platform tools exist, with no banking configuration Pre-configured roles, field security, control-room support and identifier masking
Covenants and annual reviews Almost no coverage Covenant and annual-review tracking in the commercial pack
Licensing & release
Licence model Quoted per engagement
Trial Demo on request
Current release Release notes in Client Portal
AppSource Not yet listed

Banking CRM for African banks and banking groups

BankingFlow 365 is built for retail and SME banks in Africa, and especially for multi-country groups, for example a South African group with subsidiaries in Kenya and Nigeria. It adds what standard Dynamics 365 Customer Engagement leaves open for a bank, and it connects to the core systems that banks already run, such as Infosys Finacle, Temenos T24 and Transact, and Oracle FLEXCUBE.

The core system stays the system of record for accounts and balances
Relationship managers, onboarding teams, service teams and collectors work in Dynamics 365
Security, audit and confidentiality are configured for a bank from the start

What you need alongside it

BankingFlow 365 runs on Dataverse as model-driven apps. Complaints and service requests build on Dynamics 365 Customer Service cases. The integration layer needs an Azure subscription, and the customer portal needs its own hosting. Microsoft licences for Dynamics 365, Power Platform and Azure are separate and remain with the customer.

Dynamics 365 for banking: what standard CE leaves open

Dynamics 365 Customer Engagement gives a bank a strong platform for sales, service and marketing, but not the banking layer on top. Out of the box there is no core banking connector, no KYC or AML onboarding engine, no maintained loan origination workflow, no collections module and no regulator clock on complaints. BankingFlow 365 adds that layer as Dataverse solutions, so the bank keeps Microsoft's platform and gains a CRM built for banking.

Banking CRM for retail and SME banks
CRM for multi-country banking groups in South Africa, Kenya and Nigeria
Customer 360 with holdings, alerts, consent and households
Onboarding, KYC and screening with four-eyes approval
Regulatory complaints with CBK, CBN and FSCA service profiles

Delivery and support

BankingFlow 365 is implemented by Software Dynamics. We start with a fit-gap on your processes and core systems, then configure the modules you need, set up the core adapters and test them against your own system, agree the security roles and regulator service profiles, and support the solution through the Client Portal under a support tier.

One solution, built from modules

Twelve modules for banking on Dynamics 365

BankingFlow 365 is delivered as Dataverse solutions on Dynamics 365 Customer Engagement: a core solution, and a separate solution for each division pack. Start with the modules your bank needs and add the others as you grow.

Banking 360 One workspace for the relationship manager, with the whole customer in view.
  • A party model for individuals, SMEs, corporates and SACCOs, with their identifiers
  • Beneficial-owner relationships, group links and households
  • Accounts, cards and loans shown against the customer
  • Customer alerts and consent records
  • Relationship manager workspace with forms and dashboards
Onboarding and KYC Customers and businesses onboarded through journeys that you configure.
  • Configurable onboarding journeys for individuals and businesses
  • Screening records for sanctions, politically exposed persons and adverse media, through a screening adapter
  • A risk-scoring matrix and enhanced due diligence handling
  • Four-eyes approval
  • Periodic KYC review scheduling
Retail service catalogue Banking service requests that arrive as the right kind of case, with the right clock.
  • Card block and replacement
  • Disputes and chargebacks
  • Standing orders with maker-checker
  • Account change requests
  • A service level agreement for each service type
Lending workflow Loan origination for relationship managers, from application to decision.
  • Loan applications
  • A delegated-authority approval matrix
  • Credit decisions and conditions precedent
  • A collateral register
  • It supports the relationship manager's workflow. It does not replace a full loan origination system with financial spreading or credit-memo automation.
Collections and recovery Delinquent accounts worked in order, with promises kept on record.
  • Delinquency buckets
  • Collection strategies
  • Promise-to-pay tracking
  • Payment plans and hardship arrangements
Regulatory complaints Complaints classified, timed and reported the way your regulator expects.
  • A complaint taxonomy with root cause
  • Service-level profiles per regulator, for the CBK, the CBN and the FSCA, which you confirm against the rules in force
  • Regulatory return records
  • Built on Dynamics 365 Customer Service cases
Division packs Specialist packs for each division, each delivered as its own solution.
  • Commercial banking: covenants, annual reviews and group exposure
  • Transaction banking
  • Investment banking, with a control room and information barriers
  • Markets
  • Wealth
Integration Studio A canonical banking API layer between Dynamics 365 and your core systems.
  • Adapter templates for Infosys Finacle, Temenos T24 and Transact, and Oracle FLEXCUBE, with field mapping
  • Connectors for ComplyAdvantage screening, Smile ID identity checks, a credit bureau and M-Pesa Daraja
  • The core adapters are templates. We configure and test them against your own core system during implementation.
Next-best-action Suggestions for the relationship manager, from rules you control.
  • A rules-based next-best-action engine
  • Recommendations shown on the customer record
Customer portal A web portal where customers choose an account, apply and track the application.
  • Product catalogue and product detail
  • An apply wizard, with document upload
  • Application tracking without a sign-in
  • Only the last four digits of an ID number are shown
Dashboards Role dashboards on the same Dataverse data.
  • Three core dashboards
  • Five more for the division packs
  • Eight model-driven apps in all
Security and control Security configured for a bank rather than left as a blank canvas.
  • 27 pre-configured security roles, with a business unit and team model
  • Field-level security on sensitive fields such as ID numbers and VIP or staff data
  • Dataverse auditing, with a seven-year retention policy configured
  • Per-country data-residency policy records, as a configuration aid
  • Masked identifiers, and immutable records for key compliance entities
  • Control-room support for investment banking
Process flows by division

How work moves through each banking division

Each flow shows who does what, what Dynamics 365 does by itself, and where the controls sit: approvals, four-eyes, regulator clocks and information barriers.

How a new customer becomes an open account

A new customer applies in a branch or on the portal, passes ID, screening and risk checks with two approvals, and the account is opened in your core system.

Start Onboarding application in Draft, from the branch or the customer portal
  1. Branch officer or customer Capture the application The journey for the country and product sets the steps; the customer gives their details, ID and consents.
  2. Dynamics 365 Verify the ID At ID Verification, each ID number of the applicant and related parties is sent to your core or ID service for checking.
  3. Branch officer Collect documents Required documents are tracked as Requested, Received, Under Review, Accepted or Rejected.
  4. Dynamics 365 Sanctions and PEP screening The applicant and related parties are screened; a potential match blocks progress until every hit is closed with a recorded rationale. Control point
  5. Compliance officer Assess the risk The risk matrix scores country, industry, product, PEP status and channel into a Low, Medium or High rating, which sets the next KYC review date. Control point
  6. Two approvers Four-eyes approval Two different people must approve; the system records who approved and when, and refuses a second approval by the same person. Control point
  7. Dynamics 365 Open the account The customer and account are created in your core system, the new holding is linked, and the application becomes Completed.
  8. Contact centre agent First service request A card block or replacement is sent to your core; a new standing order goes only after a different person approves it. Control point
Result Application Completed, customer and account opened in your core, and the first service request handled

How a loan application reaches a decision

A loan application is assessed and decided by the delegated credit authority that the system selects, with conditions and collateral recorded against the loan.

Start Loan application created at the Application stage
  1. Branch officer or relationship manager Capture the application Product, amount, term, purpose and applicant are captured, then the documents.
  2. Credit analyst Assess the credit Affordability (Pass, Refer or Fail), a risk grade from A to E and a recommendation are recorded.
  3. Dynamics 365 Find the authority The approval matrix picks the lowest authority that covers the legal entity, product, amount and risk grade. Control point
  4. Credit approver Decide Approve, Decline, Refer Up or Approve with Conditions, within the approver's limit; decisions cannot be edited or deleted. Control point
  5. Credit officer Conditions and collateral Conditions precedent, conditions subsequent and covenants are recorded, with collateral such as property, vehicles, cash cover and guarantees.
  6. Branch officer and customer Offer and acceptance The offer is made and accepted; a daily job withdraws offers that have expired.
Result Loan approved, with conditions tracked and collateral recorded, ready for disbursement

How an account in arrears is worked back to current

When an account falls into arrears, a collections case opens with the matching strategy, follows the arrears bucket and closes itself when the customer catches up.

Start Days past due on an account increase, from arrears data synced from your core
  1. Dynamics 365 Open the case When an account goes into arrears, a case opens with the strategy that matches it.
  2. Dynamics 365 Track the bucket The case follows days past due: Current, 1-30, 31-60, 61-90, 90+ and Non-performing.
  3. Collections agent Contact the customer Each contact attempt is logged by channel: call, SMS, e-mail, WhatsApp, letter, field visit or legal.
  4. Collections agent Promise to pay The customer's promise is recorded, then marked Kept, Partially Kept or Broken.
  5. Collections agent and team leader Payment plan A plan moves from Proposed to Approved, Active and then Completed, Defaulted or Cancelled.
  6. Dynamics 365 Cure the case When arrears are cleared, the case is marked Cured automatically.
Result Case Cured when arrears are cleared, or escalated to legal, written off or closed

How a complaint runs on the regulator's clock

A complaint is a Customer Service case with a regulator clock: deadlines come from the bank's conduct regulator and the complaint category, and complaints roll up into the regulator return.

Start Complaint logged on a case, with a category such as charges, fraud, cards, digital channels or mis-selling
  1. Contact centre agent Log the complaint The complaint is added to the case with its category, and the case is flagged as a complaint.
  2. Dynamics 365 Start the clock The rule set for the conduct regulator (CBK, CBN or FSCA) gives the acknowledgement, final-response and update deadlines, in working days. Control point
  3. Complaints handler Acknowledge and investigate The acknowledgement is recorded against its deadline.
  4. Dynamics 365 Flag breaches A daily job marks a complaint as breached when the final-response deadline passes without a response. Control point
  5. Complaints handler Resolve and redress The outcome, root cause and redress (refund, fee reversal or compensation) are recorded, and an ombudsman outcome can be added.
  6. Dynamics 365 and compliance Regulator return The period's complaints are totalled by category into the return, which compliance reviews and marks as submitted. Control point
Result Complaint resolved with an outcome and redress, and included in the regulator return

How a corporate credit facility is approved and monitored

Credit facilities are analysed, approved by an authority that reflects the whole group's exposure, then monitored through covenants and annual reviews.

Start Credit facility proposed at the Origination stage
  1. Relationship manager Originate the facility The facility type (overdraft, term loan, trade line, guarantee) and the requested limit are set for the company.
  2. Credit analyst Financial ratios Leverage, interest cover, debt service cover, gearing and current ratio are calculated from the statements.
  3. Dynamics 365 Group exposure and authority Approved limits roll up to the company and its group, and the credit authority is chosen from the group exposure and the credit grade. Control point
  4. Credit approver Credit decision A holder of credit authority decides within their limit; decisions cannot be changed. Control point
  5. Credit officer Conditions precedent Each condition is Outstanding, Satisfied or Waived; collateral lending value is market value less a haircut.
  6. Relationship manager Activate the facility The facility moves through disbursement hand-off to Active.
  7. Dynamics 365 Test covenants Each test works out Pass or Breach and freezes the figures; a breach alerts the relationship manager, and only credit can waive it, with a reason. Control point
  8. Relationship manager Annual review The review moves from Scheduled to In Progress, Submitted and Approved.
Result Facility active and monitored, with group exposure kept up to date

How a cash management client goes live

A cash-management or trade client is implemented through tracked tasks; progress and RAG status are calculated, and signing mandates need four-eyes.

Start Mandate received for a product such as online banking, host-to-host payments, SWIFT connectivity or bulk payments
  1. Implementation manager Documentation Agreements and documentation tasks are opened.
  2. Operations Signing mandate The signing rules (any one, any two, A plus B) are captured; activating a mandate needs a second person, and an active mandate cannot be edited. Control point
  3. Implementation manager Set-up Tasks for signatories, entitlements, certificates and billing are tracked as Not Started, In Progress, Blocked or Done.
  4. Dynamics 365 Progress and RAG Every task change recalculates the percentage complete and Green, Amber or Red; Red alerts the relationship manager.
  5. Implementation manager Connectivity and testing Host-to-host, SWIFT and user acceptance testing tasks are worked through.
  6. Implementation manager Training and go-live Training, then Live, then the post go-live review.
Result Client live, followed by a post go-live review

How a deal moves behind the information barrier

Every deal is codenamed and conflict-checked when it is created; only the deal team can see it, and the insider list keeps itself up to date.

Start Deal created at Origination, codenamed, with a deal type and a sensitivity level
  1. Dynamics 365 Conflict check The new deal is checked against every live deal with the same client or target, showing codenames only; restricted deals go on the watch list. Control point
  2. Deal lead Pitch and mandate The deal moves from Pitch to Mandated.
  3. Deal lead or control room Build the deal team Only the deal owner or the control room can add members. Control point
  4. Control room Approve the wall crossing On a confidential deal a new member has no access until the control room approves the crossing; the insider list cannot be edited or deleted. Control point
  5. Deal team Due diligence and bids Buyers and investors move from Identified and NDA Signed through indicative and binding bids to Allocated or Won.
  6. Deal lead Signing The deal reaches Signing.
  7. Dynamics 365 Close and cleanse Closing the deal cleanses every open wall crossing, and removing a member revokes their access. Control point
Result Deal closed won or lost, with every wall crossing cleansed

How a client inquiry is quoted, recorded and kept

Every client request for a quote is time-stamped and frozen once closed, research reads are checked against entitlements, and client revenue sets the service tier.

Start Client inquiry received by phone, chat, e-mail, an electronic platform or in person
  1. Dynamics 365 Stamp receipt A new inquiry gets its received time, with asset class, instrument and direction.
  2. Sales trader Quote The quote time is stamped by the server. Control point
  3. Sales trader Record the outcome Done, not done on price, withdrawn by the client, or expired; business not done is kept for best execution.
  4. Dynamics 365 Freeze the record A closed inquiry cannot be changed, and inquiries can never be deleted. Control point
  5. Markets sales Log interactions Calls, chats, meetings and research calls are logged with a seven-year retention date and cannot be edited. Control point
  6. Dynamics 365 Check research reads Each research read is checked against the client's entitlement, and a read without an active entitlement is flagged. Control point
  7. Dynamics 365 Revenue and tier Monthly revenue loaded from the trading system updates the client's year-to-date revenue and tier.
Result Inquiry closed and frozen, with revenue and client tier updated

How a private client is profiled, invested and reviewed

A scored suitability profile sets the client's risk band, every portfolio is checked against it, and assets under management and goal progress are kept up to date.

Start Suitability profile started in Draft
  1. Private banker and client Suitability questionnaire Risk tolerance, capacity for loss, investment horizon and experience are captured.
  2. Dynamics 365 Score the profile The answers are scored into a band from Conservative to Aggressive, capped when capacity for loss is low or the horizon is short. Control point
  3. Dynamics 365 Freeze and supersede A completed profile is frozen, the previous one is superseded, and the client's portfolios are re-checked. Control point
  4. Private banker Set up the portfolio The mandate type is discretionary, advisory, execution only or custody only.
  5. Dynamics 365 Suitability check and AUM A portfolio riskier than the client's profile is flagged with an alert, and the client's assets under management are recalculated. Control point
  6. Private banker Financial goals Retirement, education or property goals get targets and contributions, with progress shown as On Track, At Risk or Off Track.
  7. Private banker Portfolio review Reviews move from Scheduled to Prepared, Held and Actions Agreed.
Result Client invested within their profile, with goals tracked and portfolio reviews held

Steps that reach your core banking system run through the BankingFlow integration layer, configured and tested against your core during implementation.

Frequently asked questions

What is BankingFlow 365?

A banking solution on Microsoft Dynamics 365 Customer Engagement and Dataverse. It adds customer 360, onboarding and KYC, a lending workflow, collections, regulatory complaints, a banking service catalogue and core banking integration to standard Customer Engagement.

Does it replace our core banking system?

No. The core system remains the system of record for accounts and balances. BankingFlow 365 is the customer and relationship layer on Dynamics 365, connected to the core through adapters.

Which core banking systems does it connect to?

It includes adapter templates for Infosys Finacle, Temenos T24 and Transact, and Oracle FLEXCUBE. The adapters are templates that we configure and test against your own core system during implementation.

Does it include loan origination?

It includes a lending workflow: applications, a delegated-authority approval matrix, credit decisions, conditions precedent and a collateral register. It is not a full loan origination system, so financial spreading and credit-memo automation are not part of it.

How does it handle KYC and screening?

Onboarding journeys hold screening records for sanctions, politically exposed persons and adverse media through a screening adapter, with a risk-scoring matrix, four-eyes approval, periodic review scheduling and enhanced due diligence. The screening provider does the screening, and compliance decisions stay with your bank.

Which regulators does it cover?

Service-level profiles are set up for the CBK in Kenya, the CBN in Nigeria and the FSCA in South Africa. You confirm the values against the rules in force. We do not give legal or regulatory advice.

Is Microsoft Dynamics 365 suitable for banks?

Yes, as the platform. Dynamics 365 Customer Engagement and Dataverse give a bank sales, service, security and audit. The banking layer, such as core banking integration, KYC onboarding, a lending workflow, collections and regulatory complaints, is what BankingFlow 365 adds.

Which countries is BankingFlow 365 designed for?

Banks in Africa, and multi-country banking groups in particular, for example a group headquartered in South Africa with subsidiaries in Kenya and Nigeria. Regulator service profiles are set up for the FSCA, the CBK and the CBN.

Does it cover corporate, investment banking, markets and wealth?

Yes, through division packs delivered as separate solutions: commercial and corporate banking (credit facilities, covenants, annual reviews and group exposure), transaction banking, investment banking with control-room support, markets, and wealth and private banking.

What do we need to license?

Dynamics 365 Customer Service for complaints and service requests, the Dynamics 365 and Power Platform licences your users need, and an Azure subscription for the integration layer. Microsoft licences are separate from BankingFlow 365. We quote BankingFlow 365 per engagement.

How do we start?

With a 45-minute consultation, then a discovery and fit-gap workshop on your own processes. You receive a written fit-gap and a phased plan before a programme is agreed.

Let's talk Solutions.

Plan Your ERP & CRM Roadmap with Our Experts.

Book a consultation Estimate your return
Call Book a consultation
Software Dynamics
Typically replies within business hours (EAT)
Hello. What are you trying to solve? Pick one and we will route you to the right person. I want to see a demo I am an existing client and need support Tell me about electronic invoicing