Client onboarding in Symba Workflow manages the path from applicant information to an approved or rejected client record in Symba Microbanking. The exact journey depends on the organization's configured fields, terms, fees, savings products, and review policy.
An application begins through an enabled authenticated channel such as Symba USSD. Symba Workflow may collect names, contact details, location information, identifiers, and organization-specific fields. Optional fields can be skipped only when the configured journey allows it.
An application started in Symba USSD begins its Preparation stage while applicant information and any configured consent are collected. Staff use Symba Portal to prepare and review the saved application rather than creating a separate application.
When applicant terms are configured, the applicant accepts them through the applicant channel. Staff cannot accept the terms on the applicant's behalf. When no terms are configured, completed applicant information proceeds directly to pending-client provisioning.
An organization may configure a registration fee. Symba Workflow durably queues collection through Symba Payments and records the result on the application. For registration started through Symba USSD, the application is saved before client and charge creation begins. After the payer is selected, Symba USSD confirms that the request is being prepared. Symba Workflow initiates it asynchronously and records the payment attempt after Symba Payments returns a correlated result. Queue acceptance and payment-request initiation do not prove provider acceptance and payment does not prove that the fee was received. The registration fee readiness item becomes complete only after a confirmed successful outcome.
If the initial payment request fails, the registration fee remains outstanding. Staff collect the outstanding amount against the same client charge through the organization's available Symba Payments or Symba Microbanking collection path. Symba Workflow continues after the authoritative client charge shows the required payment. An uncertain payment remains blocked until it has been investigated.
The readiness checklist covers application details, applicant consent when required, client provisioning, any configured registration fee, and verified client-detail synchronization. After every required item is complete, authorized staff use "Submit for review". The reviewer can approve, reject, or request correction according to the organization's review rules. A correction returns the application to Preparation for permitted changes and resubmission.
Preparation may show Creating client in Symba Microbanking while the inactive client is being created. After that record and its charge are confirmed, the status changes to Awaiting registration payment until the fee is paid.
Approval moves the application to Finalizing while Symba Workflow activates the same pending client and opens configured savings accounts. The application finishes with an Approved outcome only after those records are confirmed.
Rejection moves the application to Finalizing while Symba Workflow rejects the same pending client in Symba Microbanking. It finishes with a Rejected outcome only after confirmation. Registration fee, payment, and client evidence remain available in the application history.
If activation, account provisioning, or rejection cannot be confirmed because of configuration or external record state, the application shows Failed attention at its current finalization step. Authorized staff can retry after correcting the cause.
Symba Workflow can compare an applicant with existing Symba Microbanking clients. The organization's policy determines how staff should handle a possible match, including whether to continue onboarding, link the application, or stop for review.