Digital account opening software
for banks, SACCOs and MFIs.
Digital onboarding for business, personal, group and joint accounts: a guided application, KYC and compliance captured at source, and a back-office review workflow that takes each applicant from first form to a live account — in your own colours, on Azure or in your own data centre, without the paper.
Paper account opening loses applicants and hides risk.
A form that emails a PDF to a branch is not a digital account-opening process. The applicant cannot see progress, the bank cannot see the applicant, and compliance happens on a photocopy after the fact.
Three years later, when the auditor asks what the applicant actually saw and declared, the answer has to be reconstructed.
- Half-finished applications nobody follows up
Applicants stop at a hard question or a missing document with no draft to come back to — and no one knows they left.
- Compliance captured after the fact
PEP and FATCA declarations and beneficial owners are collected on paper and typed in later, so screening starts after the account exists.
- Every circular is a release cycle
A new regulation, product or segment changes the form, and changing the form means an engineering ticket.
- The record does not match what the applicant saw
Forms change, but old applications are stored against whatever the current form happens to be.
What changes when the whole journey is one record.
Autosave, resume-anywhere drafts and a private progress link — for business, personal, group and joint applications alike.
PEP and FATCA declarations and the beneficial-owner register are part of the application, and every person involved is listed for screening on the same record.
A visual form builder with maker-checker publishing and version pinning — no code, no redeploy.
Each workflow action is recorded with who did it and when, reviewer decisions keep their comments, and applications re-open on the exact form version they were filled on.
Digital onboarding and KYC, captured once and reviewed on a clock.
Digital onboarding is more than an online form. BAOS covers the journey banks are asked to digitise — the application, the KYC and due-diligence capture, the document checklist, the list of people to screen and the staff review — for business, personal, group and joint applicants alike.
Identification details, employment or business particulars, addresses, next of kin and contact data are captured on your published form, with the fields your KYC policy requires marked mandatory.
Declarations are part of the application itself, made by the applicant before an account exists rather than typed in later from paper.
Business applications record significant stakeholders; group and joint applications repeat a full section for every member or holder. Each person becomes a screening subject.
IDs, photos, registration certificates and resolutions are collected against the checklist for that kind of account, with per-holder slots so “complete” means complete for everyone.
Every person involved — directors, beneficial owners, group members, joint holders, signatories — becomes a screening subject, once per person even when they hold two roles, listed on the application for your compliance team. The screening itself runs in your screening tool.
Staff claim the application, verify its documents and approve or reject it, with SLA timers on the workflow steps. Once your core banking system opens the account, they record the account number in BAOS — and every workflow action is logged.
Evaluating digital onboarding solutions? Read build, buy or configure, the KYC onboarding process step by step, and the full account-opening guide library.
Business, personal, group, or joint — one platform.
The applicant's first step is choosing the kind of account. Your bank enables only the kinds it offers — each ships as a starter form you publish from the form builder — and every one of them runs through the same review workflow.
The full corporate journey, from entity profile to facilities.
Individual accounts, captured completely the first time.
Chamas and savings groups, with every member on the record.
Every holder captured as a person in their own right.
One review workflow for all of them. The applicant chooses the account kind, BAOS serves the right form, and every person involved — members, holders, signatories and stakeholders — is listed for screening.
Everything opening a bank account needs — in one flow.
Not a form that emails a PDF to a branch. A complete pipeline: the applicant applies, compliance data is captured in line, and your team reviews and decides against SLA timers.
The applicant picks the kind of account — business, personal, group, or joint — and gets the step-by-step form your bank published for it, with autosave and resume-anywhere drafts.
Applicants register and sign in — using your own customer identity service if you have one — keep a list of drafts they can resume or discard, and track progress by a private reference link that cannot be guessed.
Uploads are driven by your checklist, with their own slot for each signatory, beneficial owner, or group member. Staff verify them one at a time or a whole application at once.
PEP and FATCA declarations and the beneficial-owner register are captured inside the application. The applicant and every person involved — directors, beneficial owners, group members, joint holders, signatories — are listed for screening on the same record.
Board resolutions for companies, group meeting resolutions for chamas, operating mandates and survivorship for joint accounts — with authorized signatories and signing mandates captured and validated in the same flow.
Reviewers claim applications from an unassigned queue into their own, verify documents, and approve, reject or email the applicant for more information — with branch-scoped roles seeing only their own branch.
Every workflow step starts an SLA timer and a dashboard shows the average time each step takes; every workflow action is recorded with who did it and when.
Every question, section, and helper text can carry English and Swahili, edited in the form builder's translation editor — and applicants get a switcher wherever a translation exists.
Run it in your own Azure subscription from Azure Marketplace, or on-premises in your own data centre, installed and supported by Creodata.
Two sides, one application.
The customer picks the kind of account — business, personal, group, or joint — and fills in the guided form your bank published for it. The nine steps below are the Kenya corporate standard template, and every one of them is yours to change. Behind the glass, every kind of application runs through the same review pipeline: claimed by a reviewer, documents verified, approved or rejected, and the account number recorded once your core banking system opens the account.
Change the form without changing the software.
Account-opening forms move — a new regulation, a new product, a new segment. In BAOS that is an afternoon in an admin console, not a release cycle. Build the form visually, publish it under four eyes, and the next application picks it up.
Drag fields from the palette onto the canvas and set their properties on the right. Twenty-two field types, from declarations to repeating people lists — no code, no redeploy, no engineering ticket.
Every published version is immutable, and each application pins the version it was filled on — so an old submission always renders exactly as it was.
A form cannot be published by whoever last edited it. Separation of duties is enforced by the platform, not by policy.
Show or require a field based on earlier answers. The same rules are evaluated identically in the browser and on the server.
Per-field English and Swahili translations, edited in a dedicated translation editor, with a language switcher that appears only where translations have been provided.
Define a pick list once — industries, business types, currencies — and reuse it across every form and step.
Serve a different form by account kind and by channel — self-service or staff-assisted — with a tenant default sitting behind it.
Publishing is blocked on duplicate questions, empty steps, dropdowns with no options, and rules pointing at a field you removed — so a broken form never reaches an applicant.
Walk your draft form through the same screen the applicant will see, before anyone else does.
Configured questions map onto the proper fields of the underlying record — entity name, signatory, shareholding — so reporting and downstream systems keep working, however you rearrange the form.
Export a finished form and import it into another tenant or environment. A form proven at one institution becomes the starting point for the next.
Open drafts by step, measured against submissions — so you can find the question that is costing you applications.
Ten starter forms across all four account kinds ship with the platform, drawn from real account-opening forms in use across the region — including the Kenya corporate standard, the nine-step journey shown above.
Nearly forty prebuilt sections — beneficial owners, member registers, next of kin, signatories, FATCA, board resolutions, and the rest — to drop into any form, grouped across nine areas.
One application, every service it touches.
No re-keying between systems. The customer portal feeds a single application record that flows through compliance capture, documents, SLA timing and audit — and reaches approval complete and validated, ready for your team to open the account in your core banking system.
Self-service sign-up, draft autosave, and reference-token tracking — the only surface the applicant sees — so an applicant can stop, come back and finish without calling the branch.
The single source of truth: the entity or the person, members, holders, signatories, facilities, and mandate — all on one record, so nothing is re-keyed and nothing is lost between teams.
PEP and FATCA declarations and the beneficial-owner register, with the applicant and every person involved derived as a screening subject and a compliance summary on the application — so reviewers can see who still needs screening.
Checklist-driven upload, download, and verification — one document at a time or a whole application at once, including signatory photographs — so the reviewer works a complete file, not a trickle of attachments.
Per-step timers start automatically, and a dashboard shows the average time each step takes — so you can see where applications slow down before applicants give up.
Each workflow action is recorded with who did it, when and from which address, and applicants get an email at each key step — so everyone knows where the application stands, and the record shows it later.
Your brand, your products, your rules.
One codebase serves every institution as an isolated tenant. Configure it from an admin console — no engineering — and the customer portal and application screens wear your colours.
For applicants who would rather just talk.
An assistant that walks an applicant through the same application in conversation, and gives your reviewers an early read on the documents. It ships with the Enterprise plan, and it is deliberately built so that it can never make the decision.
Applicants who would rather talk than fill in a form are walked through it in chat, with interactive cards for choosing a product, completing a section, making the PEP and FATCA declarations, uploading documents, and confirming a final summary.
Those cards are generated from your own published form for the kind of account being opened — with prompts tuned per kind, so a personal applicant is never asked about board resolutions — and stay in step whenever you change the form.
Recognises seven common Kenyan document types, reads the key details, and deterministically cross-checks them against what the applicant typed. The reviewer sees an advisory flag — never an automatic decision.
There is deliberately no tool for submitting, verifying, or approving — those actions do not exist for the assistant. It is rate-limited, capped in how far it can go on its own, and treats document text as untrusted. A person still decides.
Built to survive an audit.
Onboarding is where a regulator starts asking questions. The platform is built so the answers are already recorded rather than reconstructed.
from staff data entry, reviewer and document verifier to compliance officer, branch manager and audit viewer — with fine-grained permissions checked on every request
who did what, in which role, when, and from which address and device — with reviewer decisions and their comments alongside
encrypted sessions, protection against cross-site request forgery, and every service checking who is calling — not just the front door
each institution's data lives in its own database schema, and branch-scoped staff only see their own branch's applications
automated tests that drive the full applicant and staff journeys in a real browser, plus checks that keep the screens and the services in step
the whole environment is defined as code and packaged for Azure Marketplace, so a rebuild is a rerun rather than a rediscovery
Two ways to deploy. One platform.
Run it in your own Azure subscription from Azure Marketplace, or on-premises in your own data centre, installed, configured and supported by Creodata. Where your regulator or your own policy keeps data in the country, choose on-premises.
Plans start at $1,500 per month — see the plans below. The plan price covers BAOS management and support; the Azure infrastructure it runs on is billed separately, on your own subscription.
Talk to us early: on-premises deployments are planned around your infrastructure, your network and the data-residency requirements set by your regulator.
The plan fee covers BAOS management and support; Azure infrastructure is billed separately on your subscription.
Prices as listed on Azure Marketplace. Azure infrastructure is billed separately — typically $40–80 per month for entry deployments, and $500–900 per month for a high-availability Enterprise configuration, plus model usage for the AI assistant.
| Capability | Microsoft Azure | On-premises design |
|---|---|---|
| Relational data | PostgreSQL Flexible Server | PostgreSQL |
| Messaging / events | Azure Service Bus | RabbitMQ |
| Document storage | Azure Blob Storage | MinIO |
| Identity | Microsoft Entra ID (staff) · Azure AD B2C (customers) | Keycloak |
The customer portal runs on App Service, as a static site, or in containers. The Standard and Professional plans install the App Service option; the Enterprise plan runs on Container Apps with autoscaling — the mode that hosts the AI assistant.
A page for each kind of account.
What BAOS records for each account type, its starter form and document pack, and the rules each one answers to.
Fifteen entity types, directors and beneficial owners, signatories, mandates and the board resolution.
Officials who sign, the member register and the meeting resolution, for chamas and other groups.
Two to four holders, each captured in full, with the operating mandate and a survivorship instruction.
Individual, group and corporate members, mapped to SASRA's member rules.
The no-code builder behind every form: rules, document checklists and four-eyes publishing.
Account opening in your market's own terms.
Country pages map each regulator's onboarding rules to what BAOS captures, and list the guides for that market.
CBK's 2025 due-diligence guidance, SASRA's member rules, company and chama documents, and where IPRS and KRA PIN checks fit.
The AML Regulations 2022 with the national ID card as the primary document, BRELA company documents, NIDA checks and two Tanzania templates.
The AML Regulations and Bank of Uganda's due-diligence guidelines, the NIN requirement, URSB documents and where NIRA checks fit.
Law 001/2025, the FIC's account-opening requirements, BNR's 2025 directive on digital account opening and the NIDA check.
The FIC Act and its 2022 Regulations, the TPIN rule for account opening, PACRA beneficial owners at 5% and NRC checks.
Frequently asked questions.
Yes. BAOS is digital onboarding software for account opening. Applicants complete your bank's published form online; KYC and due-diligence data, PEP and FATCA/CRS declarations and significant stakeholders are captured at source; documents are collected against a checklist; every person involved is listed for screening; and staff review and decide on the application against SLA timers, with each workflow action recorded. It covers business, personal, group and joint accounts, serves several brands from one deployment, and runs in your own Azure subscription. BAOS does not check identity documents against national registers itself — it works alongside the identity-verification service you use.
Whatever your published form asks for. The starter templates capture identification details, contact and address data, employment or business particulars, next of kin, the directors, shareholders and beneficial owners behind a business, the members of a group and every holder of a joint account, plus PEP and FATCA/CRS declarations — with document slots for IDs, photos, registration certificates and resolutions. Your team adds or removes fields in the no-code form builder without a software release.
Four: business and corporate, personal (individual), group — including chamas and savings groups — and joint accounts. Choosing the account kind is the applicant's first step, and each kind gets the application form your bank published for it. You enable only the kinds you offer — the business form is published by default and the other three ship as drafts you review and publish — and all four run through the same review workflow.
Yes. The visual form builder lets product and compliance teams design steps, sections, questions, show-and-hide rules, and document requirements with no code, starting from ten bank starter templates and a library of nearly forty prebuilt sections. Forms carry English and Swahili translations, publishing is maker-checker — the last editor can never approve — and every published version is pinned, so older applications always render exactly as they were submitted.
PEP and FATCA declarations and significant stakeholders are captured inside the application itself. BAOS then derives a screening subject for every person involved — directors, beneficial owners, group members, joint holders and signatories — once per person, and lists them on the application for your compliance team. BAOS does not search sanctions or PEP lists itself: screening runs in your screening tool, such as Creodata's AML platform.
The assistant ships with the Enterprise plan, which deploys the Azure Container Apps hosting it needs. It walks applicants through your bank's own published form in conversation, tuned to the kind of account being opened, and pre-checks common Kenyan documents against what the applicant entered so reviewers get an early advisory flag. It has no ability to submit, verify, or approve anything — those decisions stay with your staff — and it runs on Claude through Azure AI Foundry or on Azure OpenAI, inside your own subscription.
Yes. BAOS runs either from Azure Marketplace in your own Azure subscription or on-premises in your own data centre. On-premises, PostgreSQL, RabbitMQ, MinIO and Keycloak take the place of the Azure services, and Creodata sizes, installs and supports the deployment with your infrastructure team. The Enterprise AI features run on Azure AI services, so which of them you use on-premises is agreed with your team.
Three plans are listed publicly on Azure Marketplace: Standard at $1,500 per month for a single brand; Professional at $3,500 per month for up to three brands, with Microsoft Entra ID staff sign-on, Azure AD B2C customer identity, and 24x5 priority support; and Enterprise at $6,000 per month with unlimited brands, the AI assistant, and 24/7 priority-1 support. The plan fee covers BAOS management and support; Azure infrastructure is billed separately on your subscription — typically $40–80 per month for entry deployments. On-premises deployments are priced per engagement.
No. BAOS captures identity details and documents on your form and records the staff review, but it does not look people or companies up in national registers such as Kenya's IPRS or the Business Registration Service, and it does not run liveness or face-match checks. Use it alongside the identity-verification provider or registry checks your bank already uses; staff then verify the documents in BAOS.
Not on its own. eKYC usually means automated identity checks — database lookups, liveness, face match. BAOS is the account-opening workflow around them: the application, the KYC and due-diligence capture, the document checklist, the list of people to screen and the staff review. It sits between your identity-verification provider and your core banking system.
Kenyan and Tanzanian ones: the Kenya corporate standard, Kenya personal and Kenya group / chama templates, and the Tanzania personal and Tanzania enterprise templates — plus joint, trustee, Islamic-banking, FATCA / CRS and additional-signatory templates that work anywhere. Forms for other countries are built in the form builder from the same sections, and the validators cover the Kenyan ID, KRA PIN and Tanzanian TIN formats.
Where you choose: in your own Azure subscription, in the Azure region you pick when you deploy, or on-premises in your own data centre. Azure has no region in East Africa — the nearest are South Africa North and South Africa West — so where your data must stay in the country, choose the on-premises deployment. On the Enterprise plan, the AI assistant's Claude models on Azure AI Foundry run in East US 2 or Sweden Central.
BAOS does not book accounts in your core banking system. Once an application is approved, staff open the account in the core system and record the account number in BAOS, which closes the application. A direct integration with a particular core is a separate project.
See any account opened end to end.
We'll walk you through the applicant journey, the form builder, and the review pipeline — across business, personal, group, and joint accounts, in your institution's colours. Or deploy it yourself from Azure Marketplace.
More on account opening
Corporate Account Opening Requirements in Rwanda: RDB Documents, Beneficial Owners and Signatories
Opening a company, partnership, NGO or cooperative account in Rwanda: RDB, RGB and RCA certificates, the 25% beneficial-owner test, signatories and the TIN.
Corporate Account Opening Requirements in Tanzania: BRELA Documents, Beneficial Owners and Signatories
Corporate account opening in Tanzania: GN 397 entity information, BRELA documents and the 2026 form numbers, beneficial owners, signatories and the TIN rule.
Corporate Account Opening Requirements in Uganda: URSB Documents, Beneficial Owners and Signatories
Company account opening in Uganda: AML reg 21 documents, URSB searches, the beneficial owner register (Form 1, Form 3), BoU's 5% marker, signatories and TINs.