A no-code account opening form builder, with four-eyes publishing.
Rules, products and documents change faster than software releases. In BAOS, your team builds and changes the account-opening form itself, from fields and rules to document checklists and Swahili text, checks it before publishing, and publishes it under four eyes. Applications in progress stay on the version they started on.
- 24field types: 22 inputs, plus headings and info blocks
- 12rule operators, nested in all and any groups
- 33option sets your team can extend
- 10starter templates, plus BAOS Classic
What the builder does.
A three-pane editor in the BAOS admin console: palette, canvas and properties.
Fields without code
Pick fields from the palette, place them on the canvas and set their properties: text, numbers, currency, percentages, dates, product, branch and segment pickers, file and photo uploads, declarations and more.
Conditional rules
Show a field, or make it required, based on other answers, with operators such as equals, in, is empty and greater than, nested in all and any groups.
Repeating sections
Directors, signatories, members or holders as repeating blocks with a minimum and maximum, shown as a list or a table, with sub-sections inside sections.
Document rules
Document requirements for the application, each signatory, stakeholder, member or account holder, each required or optional, and conditional on answers.
Checks before publishing
Pre-flight checks block a form with empty sections, choice fields without options, missing option sets, duplicate field keys or rules that point at deleted fields, and warn about fields that save nowhere.
Four eyes and version pinning
Whoever last edited a draft cannot publish it. Published versions are immutable and can be restored, and each application reopens on the version it was filled on.
From draft to live, step by step.
How a form change moves through BAOS.
- 1Start from a template
Ten starters (Kenya corporate, Kenya personal, Kenya chama, Tanzania personal, Tanzania enterprise, joint, trustee, Islamic banking, a FATCA/CRS annex and additional signatories), BAOS Classic (9 steps, 110 fields), or a blank form, with 39 prebuilt sections in nine areas.
- 2Build
Fields, rules, repeating sections and option sets, with format checks for KRA PINs, Kenyan IDs, Tanzanian TINs, passports and phone numbers.
- 3Translate
Add Swahili text to each field, beside the English.
- 4Preview
Walk through the form as different personas, to see each conditional branch.
- 5Check
Pre-flight checks block what would break a submission.
- 6Publish
A second person publishes, and the version is frozen.
- 7Measure
A drop-off funnel shows where applicants stop, step by step.
Three 2026 changes in Kenya, and the form edit each one needs.
Each of these changed what a Kenyan bank or SACCO may ask for in 2026. The starter templates do not include these edits yet; in BAOS, each is a change to the published form, not a software release.
| The change | The form edit in BAOS | Still outside the form |
|---|---|---|
| Written trusts must be registered or incorporated with the Registrar of Trusts at BRS from 25 September 2026. Existing trusts have 24 months to comply.Trust Administration Act 2026, ss.5, 77 and 99 | In the trustee form, make the certificate of registration required for new trusts, and add a choice for an older certificate during the transition. | Checking the Registrar of Trusts register. |
| Non-residents no longer need a KRA PIN to open an account.Tax Procedures Act s.12(5B) | In the personal form, make the tax PIN and the PIN certificate required only when the residency status is Resident. | PIN checks at KRA. |
| The High Court declared the Community Groups Registration Act unconstitutional on 10 September 2026, suspended until midnight on 10 February 2027.[2026] KEHC 13419 (KLR) | In the group form, make the registration certificate optional for groups that say they are unregistered, if your policy accepts them. | Your policy decision. |
Examples of form edits, based on Creodata's Kenya fact sheet of 8 October 2026. Not legal advice.
- Annex forms, such as the FATCA/CRS self-certification and additional signatories, cannot yet be attached to an application.
- Restoring an earlier version does not go through the four-eyes check.
- Form text can be English and Swahili; other languages are not supported yet.
- Fields map to BAOS's own application records, not to your core banking system.
Frequently asked questions.
What is a no-code form builder for account opening?
A tool that lets operations or compliance staff change the application form, its fields, rules, documents and wording, without developers or a software release. In BAOS, each change is published as a new form version, under four eyes.
Who can edit and publish forms?
Staff with the form-builder permissions. Whoever last edited a draft cannot publish it, so every change is seen by a second person before applicants get it.
What happens to applications already in progress when we publish?
Nothing changes for them. Each application is pinned to the form version it was started on and always reopens on it; new applications get the new version.
Can we move forms between test and production?
Yes. Forms export to JSON and import from it.
Can the form be in Swahili?
Yes, field by field: each field can carry English and Swahili text. Other languages are not supported yet, and the starter templates ship in English.
Does the form connect to our core banking fields?
No. Form fields map to BAOS's own application records. Staff open the account in your core system and record the account number in BAOS.
See it with your own forms.
Bring your account types and your document checklists to a live demo, and see an application go from the applicant to your reviewers.