Accounting workpapers

The operator prepares. Your reviewer decides.

An operator ties the trial balance to the ledger and the source documents, flags the exceptions and prepares the workpaper. Your reviewers sign off before anything is saved or sent.

ISO 27001 · GDPR · Every run auditable

CC-25 · Calder Components Ltd · FY2025

Revenue and receivables lead schedule

Illustrative engagement

Preparation log

  1. 1Read TB_FY25.xlsx
  2. 2Mapped 5 accounts to the lead schedule
  3. 3Tied revenue to GL_FY25.csv
  4. 4Tied bank to statement p. 2
  5. 5Flagged 1100: €18,000 apart
  6. 6Flagged 4010: cut-off
  7. 7Missing: Oriel Retail contract
  8. 8Drafted request to L. Grant

Lead schedule

Trial balance · support · source

  • 4000 RevenueTied

    €8,412,300 · €8,412,300 · GL_FY25.csv · account 4000

  • 1100 Trade receivablesException

    €1,286,450 · €1,268,450 · AR_aged_Dec.xlsx · total row€18,000 apart: digits look transposed in the aged listing

  • 1150 Accrued incomeTied

    €96,000 · €96,000 · Contract C-114 · clause 4.2 · p. 3

  • 1010 BankTied

    €612,980 · €612,980 · Bank statement 31 Dec 2025 · p. 2

  • 4010 Credit notesException

    €0 · €42,700 · Credit note CN-26-004 · dated 3 Jan 2026Cut-off: dated after year-end for a December delivery

  • Missing support: Oriel Retail · €210,000 of revenue. No signed contract in the engagement folder

Waiting for E. Moretti, audit manager

Send 1 client request and save the workpaper to the engagement folder

Enterprises running operators on Alomana

  • up to 80%less manual data entry
  • 25–35%faster month-end close and audit completion
  • 45 minto review a mandate, down from 6 hours
  • 2×mandates handled per accountant

What the operator prepares on every file

The preparation, done before the reviewer opens the file.

  • The trial balance

    Maps the trial balance and ledger exports to your lead schedules

  • The tie-outs

    Ties each balance to the ledger, the bank statement or the contract

  • The sources

    Writes the document, page or ledger line next to each figure

  • The exceptions

    Flags transposed digits, cut-off issues and unexplained differences

  • The missing support

    Lists what is missing and drafts the request to the client

  • The review file

    Prepares the workpaper and the review notes for your reviewers

How the operator prepares a workpaper

  1. Connect

    The engagement folder, the exports and your checklist.

  2. Prepare the file

    Tie-outs, exceptions and sources, in Excel.

  3. Review and approve

    Your team signs off. It saves and logs it.

Nothing leaves the file without a yes.

  • Saving to the engagement folder waits for a person's yes
  • Requests to the client wait for a person's yes
  • A declined action is not retried
  • Every run logged: input, output, tools, user

Held for a reviewer · CC-25

Request to L. Grant, controller, Calder Components

Hi Laura, for the FY2025 audit we need the signed contract for Oriel Retail, which covers €210,000 of revenue. Could you upload it to the shared folder? Thank you, the audit team

Run record
Input
TB_FY25.xlsx, GL_FY25.csv, AR_aged_Dec.xlsx
Output
CC-25 Revenue and receivables lead.xlsx
Tools
Execute code, create file
User
E. Moretti, audit manager
Measured on
  • Staff hours per engagement
  • Review notes per file
  • Days from PBC to ready for review
  • Exceptions found before review
Works with
  • Excel, CSV and PDF files
  • SharePoint
  • Google Drive
  • Google Sheets
  • Snowflake
  • PostgreSQL
  • Slack
  • Your ledger or audit software via MCP
Trusted for
  • ISO 27001
  • GDPR
  • Never trains on your data
  • Single-tenant for enterprise

A custom operator typically goes live in up to 4 weeks.

Questions firms ask about AI workpaper preparation

What is an AI workpaper operator?

An autonomous agent that prepares workpapers from the client's records. It reads the trial balance, the ledger and the supporting documents, ties out the balances, flags exceptions and missing support, and prepares the workpaper and review notes for your team to review and sign off.

Does it replace our audit or tax software?

No. It works on the files your engagements already use: trial balance and ledger exports, spreadsheets and PDFs, in SharePoint or Google Drive, and returns Excel workpapers and lists. Ledger, audit or tax software outside the connector library connects through a remote MCP server.

Does it sign off or contact clients on its own?

No. Sign-off stays with your reviewers. Saving to the engagement folder, sending a request to a client and every other write or send wait for a person's yes. A declined action is not retried, and every run is logged: input, output, tools and user.

Which systems does it connect to?

Alomana has 20+ connectors, including SharePoint, Google Drive, Google Sheets, Snowflake, PostgreSQL and Slack, activated per deployment. Excel, CSV and PDF files are read directly. Systems outside the library connect through a remote MCP server.

How long does it take to deploy?

A custom workpaper operator, built around your firm's checklist and templates, typically goes live in up to 4 weeks, including validation and integration.

Is our client data private?

Alomana is ISO 27001 certified and GDPR-compliant, and your client data is never used to train AI models. Enterprise deployments run single-tenant, in a dedicated instance.

Bring one engagement's trial balance.

Talk it over with sales: what the operator needs from your systems, and how it goes live.

Alomana is a secure enterprise AI platform where autonomous agents, called operators, run business processes end to end. Every run is fully auditable.