Institution KYB

Why

Within its commercial network, Tauraco must speak only to genuine financial institutions authorized to lend. This process organizes the building of the file that proves it, before the institution can receive a single request.

How, in the application

A partner institution has its own workspace, an identity in the shared counterparty registry, a declared qualification, and network enrollment. The authorization number entered at registration is a declaration: no function queries an external bank registry to verify it, and the qualification created is always born non_validee (not validated).

The institution submits its KYB file (regulator's authorization, articles of association, RCCM registration, director's identity document) in its workspace, which is accessible for this purpose before its financial-institution qualification is validated. The file follows a simple cycle: a submission moves it to SUBMITTED; only status APPROVED permanently closes the possibility of a new submission — a rejected file can always be resubmitted.

A queue dedicated to the compliance team lists submitted or under-review files. Approving a file does two things in a single act: it moves the file to APPROVED and promotes the counterparty's financial-institution qualification to validee (validated) — it is this promotion, and this alone, that opens the entire set of bank cockpits to the institution (received files, offers, competitive position, market ranges).

Safeguards

• The administration that creates, suspends, or invites an institution's users never opens access to its private commercial files — even a platform administration role never enters institutional-context resolution.
• Validating a qualification is a human, tracked act, never automatic: nothing in the system can promote an unverified declaration by itself.
• Approving an already-complete file requires the mandatory documents to actually be uploaded — approval checks completeness before promoting anything.