Skip to main content
TheDocs
Sign in Book a Demo
Industry

Procedures your auditor can trace, and customers can read

Financial services documentation carries two burdens at once: it has to be evidentially sound internally, and genuinely useful to a customer externally. One platform, two audiences.

Start free trial Book a demo
  • Approval trails
  • Read acknowledgement
  • India / EU / US residency

What does a bank or NBFC use a documentation platform for?

Internally, for controlled procedures: operations manuals, KYC and onboarding processes, credit policies and branch procedures - each with a named owner, a defined approval path, a review cycle and a record of who has acknowledged the current version. Externally, for a customer help centre and, often, a partner or distributor portal. TheDocs runs all of these as separate projects inside one workspace.

  • Sequential approval steps with named approvers per category.
  • Read acknowledgement per person, reset on every approved change.
  • Superseded versions retained with their approval record.
  • Full audit log of content and permission changes.
  • Data residency in India, the EU or the US.
  • SSO, SCIM and granular per-category permissions.
Content

What gets documented

Operating procedures

Branch operations, onboarding, KYC, collections, disbursement. Controlled, approved, acknowledged.

Policy documents

Credit, risk, AML and information security policy - owned, reviewed on a cycle, and versioned.

Customer help centre

Public, indexed, answering the questions that otherwise reach a call centre at cost.

Partner and DSA portals

Product and process documentation for distributors, restricted to named partner accounts.

Onboarding material

Role-specific paths for new staff, with the acknowledgements built in rather than chased.

Technology runbooks

Incident procedures and system documentation, restricted to the teams that need them.

In detail

What matters when the regulator asks

Evidence in minutes

Audit findings in documentation are rarely about the content. They are about not being able to show the process around it.

  • Who wrote each version, who approved it, and on what date - on one screen per procedure.
  • The exact text in force on any chosen past date, with its approval record.
  • Acknowledgement reports by person, team or document, exportable as CSV.
  • Access log showing who opened a restricted procedure and when.
  • Change history including restorations, with the actor recorded.

TheDocs handles document control. Risk registers, control testing and issue management belong in a GRC platform - the API links the two.

Data handling your security team will check

In BFSI the security review usually happens before the functional evaluation. These are the answers it needs.

  • Data residency in India, the EU or the US, committable contractually on Enterprise.
  • TLS 1.2+ in transit, AES-256 at rest, per-workspace logical isolation.
  • SAML and OIDC SSO with optional enforcement, plus SCIM provisioning.
  • AI can be disabled per project, so internal procedures stay out of any inference path if policy requires it.
  • Sub-processor list, DPA and a completed standard security questionnaire available on request.

Related

Standard Operating Procedures

Version-controlled SOPs with review cycles and read acknowledgement.

Review Workflows

Draft, review, approve, publish - with owners, due dates and reminders.

Access Control & SSO

Public, private or partner-only, with SAML and OIDC single sign-on.

Security

How TheDocs protects, isolates and backs up your content.

Fintech: A Partner Documentation Portal

Public docs, partner-only docs and internal runbooks in one platform.

Versions & History

Every revision kept, compared side by side and restorable in one click.
Frequently asked

Questions people ask before they start

Yes. Superseded versions are retained with their approval record, so you can produce the exact text that was live on any date along with who approved it and when.

India, the European Union or the United States - chosen when the workspace is created, and committable contractually on Enterprise. Content and backups stay in the chosen region.

Yes, per policy and per person or group. When a new version is approved, acknowledgement resets and everyone affected is notified with a summary of what changed. Reports are exportable.

No. It manages documentation - authoring, approval, distribution, acknowledgement and history. Risk registers, control testing and issue management stay in your GRC tool, and the API links them.

Yes, as separate projects in one workspace. A public help centre for customers, a partner portal for distributors, and internal procedures - shared authors, entirely separate audiences.

Ask us for the security pack before you ask us for a demo.

Start free for 14 days. No credit card, no setup fee, and your content is yours to export at any time.

Start free trial Book a 30-minute demo

Questions first? Email sales@thedocs.in or call +91 8585953085.