---
title: "About the Advanced Transaction Object (ATO) – Controlled Entity & Data Entry Management in Board"
slug: "about-the-advanced-transaction-object-ato"
description: "Understand how ATO offers a guided interface for Planners to create and edit Entity members and Relationships, with data entry enabled in Cubes once selections are made."
tags: ["Data Entry", "Developer", "End user", "Objects"]
updated: 2025-10-07T13:16:59Z
published: 2025-10-07T13:16:59Z
canonical: "help.board.com/about-the-advanced-transaction-object-ato"
---

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

# About the Advanced Transaction Object (ATO)

The Advanced Transaction Object (ATO) management provides the end user with a controlled and guided environment for creating new Entity Members and Relationships.

In ATO management environments, you can also use the Data View Object to allow end users to enter data in Cubes right after the creation of a new Entity Member.

Typically, the structure of an ATO management environment in a Screen or a Container includes:

- one or more Entity editors, which allows the creation or edit of Entity Members.
- (optional) one or more Data View Objects allowing data entry related to newly created Entity Members. To do so, Data Entry must be enabled on one or more Data Blocks of the Layout, and Data Entry actions must be performed at the physical level of the Cubes. See [Data Entry on Cubes](/v1/docs/data-entry-on-cubes-cube-write-back) for more details.

The following picture shows a Screen with ATO management enabled:

![contents/assets/images/ATO.enablement.PNG](https://cdn.document360.io/8d6f1ae8-0cac-4d0d-a208-6245b83df94a/Images/Documentation/about-the-advanced-transaction-object-ato-image-ldke80j8.png)

When an ATO management environment contains at least one Entity editor and at least one Data View, the Layout of all Data Views is executed only after the user selects an Entity member on each of the available Entity editors. This allows the Capsule designer to create a Screen where the end user must explicitly make a selection on an Entity editor before entering or viewing data.

The following picture shows a Screen with ATO management enabled, but the user hasn't selected a member on all the Entity editors:

![contents/assets/images/ATO.second.PNG](https://cdn.document360.io/8d6f1ae8-0cac-4d0d-a208-6245b83df94a/Images/Documentation/about-the-advanced-transaction-object-ato-image-dww6nuhx.png)

As you can see, the Layouts associated with the Data Views are not executed and no data is displayed.

Learn more about:

- [**Enabling ATO management**](/v1/docs/enable-ato-management)
- [**Entity Editor in ATO environments**](/v1/docs/entity-editor-in-ato)

## Related

- [Enable ATO Management](/enable-ato-management.md)
- [Entity Editor in ATO](/entity-editor-in-ato.md)
- [About Data Entry and Advanced Transaction Object (ATO)](/about-data-entry-and-advanced-transaction-object-ato.md)
- [Data Entry on Cubes (Cube write-back)](/data-entry-on-cubes-cube-write-back.md)