What do you need?
The user manual, the functional documentation, and a team that answers — for the business filing an invoice as much as for the institution assessing it.
The documentation
The public documentation portal, current with every release.
User manual
The journey screen by screen: login, ERP, financing, security interests, third-party custody, institution workspace.
Open the manual →Functional documentation
What the platform does and does not do: production gates, evidence chains, the exact scope of every module.
Read the documentation →Release notes
What changes, release after release.
See the release notes →Frequently asked questions
From https://app.tauraco.io/login, with your username and password. There are three entry points: standard login, password recovery ("forgot password"), and accepting an invitation received by email if a company or institution has attached you to its workspace. For security, five failed login attempts lock the account for fifteen minutes.
A request is built on what your ERP already knows (invoice, history, inventory): you choose the invoice, the amount, the product, and the institutions in your network to send it to. Tauraco does not lend, never touches the funds, and computes no rate: the terms (rate, advance, fees) are set by the bank or institution assessing the file, and the financing decision belongs to it entirely.
A file reaches the institution already structured — invoice, activity history, checks, supporting documents — rather than as a declarative form. Each institution then assesses it against its own commercial criteria (caps, excluded sectors, maximum durations), which remain its property: visible neither to the company nor to other institutions.
Once an offer is accepted, a contract is generated and an electronic signature envelope opens for three signatories: the company, the financing institution, and Tauraco as witness. The facility only becomes drawable once all three signatures are obtained — a blocking condition, never bypassed silently.
The Collateral register centralises pledged assets (receivables, contracts, inventory, equipment...) and their legal status, assessed rule by rule with reference to the relevant OHADA uniform act. When a facility is backed by inventory, a custodian can be designated by deed: it confirms receipt of the goods and only releases stock upon the beneficiary's express authorisation.
Each institution holds a subscription tier (Standard or Premium), assigned by the platform operator — never self-service. The Premium tier unlocks detailed file analysis, competitive positioning, and the assisted-analysis cockpit; on Standard, those panels stay visible but locked.
A pan-OHADA demonstration network exists for guided tours and trials, strictly isolated from real data: it appears in no counter unless explicitly enabled, and is never served to a real client. Any "demo view" used by a platform operator is capped at fifteen minutes, logged, and refused on a real tenant.
Every company and every institution operate in a strictly isolated space, enforced at the database level (tenant identifier, row-level security policies), with dedicated roles whose privilege contract is versioned and tested. No query can cross tenants.
Still have a question?
Write to us directly, or use the contact form — the same team answers both.
Technical documentation
Runbooks, architecture, and API reference: reserved for internal teams and authorised partners.