> ## 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.

# Acceptance records and audit

> The immutable records written for every acceptance and notification, and what banks can see and export.

Every acceptance writes an immutable record, and every platform-delivered notification, such as acceptance-required prompts and reminders, writes a delivery record. Records are never edited or deleted. Superseded acceptances remain in history beneath the current status.

For notice-only updates, where the bank delivers notice through its own channels, the bank retains its own delivery evidence.

```json title="Illustrative acceptance record" lines theme={null}
{
  "type": "acceptance",
  "business_id": "biz_8f3a…",
  "accepted_by": "usr_c91d…",
  "scope": "entity",
  "disclosure_id": "deposit_agreement",
  "disclosure_version": 4,
  "presentment_text_version": 2,
  "accepted_at": "2026-10-18T14:32:09Z",
  "ip_address": "203.0.113.42"
}
```

This shape is illustrative. See the API reference for the current schema.

## Questions the records answer

* Is the entity bound to version N, and who bound it?
* Did this signer acknowledge the terms they operate under?
* Did this individual consent to electronic delivery?
* When was notice of the change delivered, and to whom?

## Bank visibility

Bank back-office staff can view acceptance status per business and per user in the partner portal. This includes grace-period countdowns, restricted accounts, and businesses with no active Authorized Signer. They can also export acceptance evidence for examinations.


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