# Getting Started With Ledge Close Management & Execution

This guide helps you move from manual spreadsheets to an agentic close: AI does preparation work while you focus on review and sign-off.

### Organizing your close

#### Understanding task types

Tasks are the core units of work. In the product, each task has a **type** shown on the task (for example in task management and the task header). The UI recognizes **three** types:

<table><thead><tr><th width="149.2265625">Task type</th><th>Purpose</th><th>Best for</th><th>Notes</th></tr></thead><tbody><tr><td><strong>Checklist</strong></td><td>General close activities</td><td>Procedures, documentation, ad-hoc items. Agents can attach to checklist tasks when enabled</td><td>Posting period and entity are mandatory</td></tr><tr><td><strong>Reconciliation</strong></td><td>Comparing balances between GL and working paper (including bank rec for relevant accounts)</td><td>Balance sheet recs, bank recs (with <strong>Unmatched transactions</strong> / <strong>Matched transactions</strong> where applicable)</td><td>Account and posting period; reconciliation tasks generally require a <strong>working paper</strong> attachment before the preparer can <strong>Sign off</strong></td></tr><tr><td><strong>Flux analysis</strong></td><td>Explaining period-over-period variance for an account</td><td>MoM/QoQ/YoY variance explanations with a <strong>Transactions &#x26; Trends</strong> view on the task</td><td>Account and posting period; preparer must have an <strong>explanation</strong> before <strong>Sign off</strong></td></tr></tbody></table>

#### Lifecycle: statuses and what “preparation” means

Tasks use **concrete statuses** in the app (shown on the task and in filters), not a single label called “Preparation” or “Review.” User-visible status labels include:

* **Open** — work in progress (including when changes were sent back; see **Changes requested** below)
* **Changes requested** — reviewer sent the task back for updates (in close overview metrics, **Preparation** counts **Open** plus **Changes requested** tasks)
* **In review** — with the reviewer; multi-step review can show progress (for example “In review | *n* of *m*” when there are multiple reviewer steps)
* **Done**
* **Canceled**

When an **agent** is involved, you will also see agent-related statuses such as:

* **Running**
* **Awaiting review**
* **Output ready**

There is also a **Pending** state used in the data model; it is not shown as a status tag in the main task status UI.

**Workflow (approvals):** Tasks use an **approval workflow** with **Preparer** and **Reviewer** steps (and optional reassignment, subject to permissions). In the standard preparer/reviewer cards:

* **Preparer:** primary action is **Sign off** (runs the “prepare” step). Before that, the app may block sign-off until required inputs exist—for example a **working paper** on reconciliation tasks, or an **explanation** on flux analysis / flux report tasks.
* **Reviewer:** actions are under **Review**, with **Submit sign off** and **Request changes**.

Comments, attachments, subscribers, and **dependencies** can be added from the task page, or directly from the Checklist using the quick preview drawer.

#### First steps

**1. Configure your checklist**

* **Import checklist:** You can import a checklist from supported spreadsheet formats (the app accepts formats such as **CSV, XLSX, XLS, XLSM, and XLSB**).
* **Folders:** Group tasks in **folders** (for example by team or workstream).
* **Entity:** Use **entity** on tasks and filters to work across legal entities where your templates and folders are set up for multi-entity closes.
* **Preparer and reviewer:** Assign **Preparer** and **Reviewer** (and use bulk assign actions where available) so ownership matches your workflow. Ensure a **default approval workflow** exists where the product requires it.

**2. Connect your general ledger**

* Ledge integrates with **NetSuite** in close flows, to both read (subsidiaries, chart of accounts, vendors, customers, transactions etc.), and write (customer payments, vendor payments, deposits, journal entries, advanced inter-company journal entries, etc.). Connect your ERP integration so balances and transactions can sync for reconciliation, flux, and posting.

**3. Notifications and chat**

* **Slack or Microsoft Teams** can be connected at the organization level (native OAuth flow exists in the app). Use your org’s notification settings for how close and agent events reach you.
* Mention teammates in context where the product supports **@mentions** on tasks.

***

### Automating reconciliations and flux

Ledge goes beyond tracking: reconciliation and flux tasks tie **GL data**, **working papers**, and **agents** together.

#### 1. Bank reconciliations

For **bank** reconciliation tasks, the task includes specific reconciliation views that allows more direct access beyond the agent-generated working paper, including **Unmatched transactions** and **Matched transactions** views, balance context. Those are in-sync with the agent-generated working paper.

#### 2. Working papers

* For **agent** runs, working papers may be produced or updated as **artifacts** you can download, save to storage, or accept into the task.
* If the working paper is create manually, you can attach it to the task directly (a working paper is required for some task types, notably, for **reconciliation** sign-off).

#### 3. Flux analysis and flux report tasks

* **Flux reports** allow users to define custom pivot-table-style reports for period-over-period variance analysis at user-defined resolution. Reports generate flux analysis tasks.
* **Flux analysis** tasks emphasize explanations and **Transactions & Trends**, and allow the user to generate full-fledged agent-based explanations.

***

### AI agents

Agents prepare work for humans to review. Access to a run is available from the task (for example **Agent Studio** and session navigation where enabled).

* **Plans and progress:** Agent plans show step-level progress where the session exposes a plan.
* **Outputs:** Depending on the run, you the agent may produce **a working paper**, **Journal entries**, **Screenshots**, or other artifacts when present.
* **States:** Align with task/agent status—for example **Running**, **Awaiting review**, **Output ready**, then human **In review** / **Done** via the normal approval buttons.

**Activity:** Human and system events appear on the task’s **Activity log** tab.