> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tesouro.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Disclosures

> How Embedded Banking presents bank disclosures, captures acceptance from the right people at the right moments, and keeps the records your bank partner's auditors will ask for.

Every deposit account in Embedded Banking is governed by a set of disclosure documents owned by the sponsoring bank. The catalog varies by bank, but typically includes the deposit account agreement, fee schedule, funds availability policy, E-SIGN consent, and platform access terms.

Tesouro stores the documents the bank configures, presents them in the embedded widgets (or returns them through the API) at the right moments, captures acceptance from the right people, and records the evidence.

If you're a developer at Northfield Software, you don't implement any of this logic yourself. The widgets present disclosures and capture acceptance automatically. These pages explain the behavior so you know what your business customers see and why.

## Three ideas behind the system

* **Disclosures bind different parties.** Some bind the business entity, some bind an Authorized Signer in their signing capacity, and some bind an individual user personally. The platform models this as the disclosure's [scope](https://docs.tesouro.com/embedded-banking/guides/disclosures/scopes.md).
* **Authorized Signers and ordinary users have different obligations.** What a person is asked to accept depends on whether they're an Authorized Signer. Entity-level obligations follow whoever currently holds that designation, not a named individual, so people joining or leaving a business never break the compliance chain.
* **Everything is versioned and recorded.** Each acceptance stores which document version was shown, to whom, when, and in what capacity. This is the evidence chain banks need for examinations.

## Core concepts

> [accordion] Disclosure
>
> A versioned document owned by the bank, such as Deposit Agreement v4. At any time one version is active, and all forward-looking flows present the active version.

> [accordion] Acceptance requirement
>
> A rule attached to a disclosure that says who must respond and how: a scope (`entity`, `signer`, or `person`) and an enforcement (notice-only or acceptance-required). One document can carry more than one requirement.

> [accordion] Acceptance record
>
> The immutable record written when someone accepts or acknowledges: who, which document version, scope, timestamp, and IP address. Notice deliveries are recorded the same way.

> [accordion] Authorized Signer
>
> The person legally authorized to act on the account and bind the business. It's a verified designation, distinct from the Company Admin permission role. Every active account must have at least one active Authorized Signer.

> [!NOTE]
>
> Authorized Signer is a legal designation; Company Admin is a permission set. A business can have admins who aren't signers and signers who rarely log in. Signer changes go through an identity-verified process with the bank, while admin changes are ordinary user management. See [Authorized users](https://docs.tesouro.com/embedded-banking/guides/users/authorized-users.md) for how users are managed.

## In this section

> [card] [Scopes](https://docs.tesouro.com/embedded-banking/guides/disclosures/scopes.md)
>
> Who responds to a disclosure and what their response binds.

> [card] [When disclosures are presented](https://docs.tesouro.com/embedded-banking/guides/disclosures/when-presented.md)
>
> What each person accepts at application, invitation, and signer designation.

> [card] [Disclosure updates](https://docs.tesouro.com/embedded-banking/guides/disclosures/updates.md)
>
> Notice-only and acceptance-required changes, grace periods, and restrictions.

> [card] [Presentment text and links](https://docs.tesouro.com/embedded-banking/guides/disclosures/presentment.md)
>
> The wording around disclosure links and how it's versioned.

> [card] [Acceptance records and audit](https://docs.tesouro.com/embedded-banking/guides/disclosures/acceptance-records.md)
>
> The records banks and examiners rely on.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.