Home › Functional documentation › Banking file, consent & review
Document menu← Home
Functional documentation
  1. 01Invoicing & OHADA accounting
  2. 02Invoice pipeline
  3. 03Financing request
  4. 04File analysis
  5. 05Offers & structured conditions
  6. 06Competitive position & market ranges
  7. 07Contracts, facility, and financing servicing
  8. 08Institution KYB
  9. 09Institution subscriptions
  10. 10Collateral & borrowing base
  11. 11Third-party custody
  12. 12Alerts & business observability
  13. 13Partner institutions and availability
  14. 14Legal review
  15. 15Embedded AI
  16. 16Company workspace, tenders & monitoring
  17. 17CRM, bids & contract management
  18. 18Human resources & delivery capacity
  19. 19Contract guarantees & execution loans
  20. 20Banking file, consent & review
  21. 21Bank decision, issuance & documentary evidence
  22. 22Documentary Collateral & verification limits
  23. 23Access rights, Founders program & notifications
  24. 24Data & integrations: universal exports
  25. 25Connected apps, public API, webhooks & MCP
  26. 26ERP connectors & synchronization
  27. 27Banking API & Collateral
Other documents
Functional documentation

Banking file, consent & review

Why

To have a guarantee or loan request reviewed, the company must gather the required information and choose what it authorizes an institution to access. Banking Connect organizes file preparation, consent, transmission, and exchanges during review. The company can then identify missing documents, the recipient, and the status of its request.

How, in the application

Prepare. The company enters the product, purpose, amount, currency, and requested information, then selects an available institution. A draft can be prepared before that choice; it cannot be transmitted without a recipient. The document list and readiness status explain missing documents and unmet criteria.

Consent. The form presents the recipient bank, consent text, and relevant data categories: identity, documents, financial summary, and Collateral file. Consent is dated and tied to this request. Changing the recipient during preparation requires a new check of what is shared. Transmission remains a separate action.

Transmit. The application checks the institution's and product's availability, documents, criteria, and consent again. “Submitted” status and the timeline identify the recorded transmission. They do not represent a favorable decision. The bank can then access the file in its authorized portal, according to the shared categories.

Answer information requests. The bank can take the file under review, request information, or examine a document. The company responds in the request's thread and supplies the requested items. Exchanges remain tied to that recipient. Before a decision is recorded, revoking consent removes the bank's access to the file in the portal; it does not retroactively erase a document already viewed or downloaded.

Safeguards

  • The right to prepare a request does not grant the right to share it: consent and transmission are reserved for authorized company profiles.
  • The readiness check is not a credit decision. Declared data and the presence of a document do not by themselves establish authenticity.
  • Transmission makes the file accessible in the Tauraco bank portal. It does not send it to the bank's external information system.
  • A declined, withdrawn, or expired request retains its history. When a requirement remains linked to that request, resuming it must be organized explicitly; clicking again does not automatically create another attempt.