Skip to main content

Agent tasks

Agent tasks are AI-assisted tasks that go beyond answering questions. They do work for you, with a person reviewing and signing off before anything is finalized.

note

Agent tasks are a beta capability and may not be enabled for your account. Contact your account manager if you'd like to try them.

What agent tasks can do​

Agent tasks use CloseCore's read access to your ERP transaction data and close files to help automate close work, including:

  • Drafting journal entries: preparing a JE from your data as a reviewable draft, ready to be posted to your ERP once approved.
  • Extracting data from PDFs and images: pulling figures out of supporting documents like bank statements, invoices, scanned pages, and screenshots into your workpapers. OCR is automatic; no extra step is needed for scanned or handwritten pages.
  • Reading and preparing workpapers: browsing your cloud close folders, reading existing xlsx files and Google Sheets, and building new workpapers with formulas, tie-outs, and roll-forwards, the same files a colleague would produce.
  • Transaction matching: matching transaction detail to propose tie-outs.
  • Collecting close support by email: drafting and sending requests to configured recipients, waiting for replies, and continuing the task after reading the response and its attachments.

Skills​

A skill is one thing the agent knows how to do, such as reading a PDF, pulling an ERP balance, or building a workpaper. Agent Skills in the AI menu lists all of them, grouped by where they apply: storage and documents, workbooks, reconciliation and tie-outs, ERP, journal entries, working with you, close data, and the web.

Use the list two ways:

  1. To see what is possible before you write a task, so your steps ask for work the agent can actually do.
  2. To point a step at a specific skill. In a step's guidance, type @ and pick the skill from the list. The agent reads that skill's full instructions before it works the step.

Referencing a skill is optional. The agent can read a PDF whether or not you name the skill, but naming one is useful when a step should follow a particular procedure, for example Prepare JE table for a journal entry or Run a reconciliation for a saved agent reconciliation.

Some skills need a feature that is not on every account (journal entries and agent email, for example), and they appear in the list only when your account has it. Look up reference data works only on tasks where web access is turned on.

Review and sign-off​

Agent tasks fit into the same sign-off model as the rest of your close. An agent produces a draft; preparers and reviewers check it and sign off; only then is a journal entry posted to the ERP. Nothing is written back to your accounting system without a person approving it.

Who can create agent tasks, sign off on them, and post journal entries to the ERP is controlled by roles & permissions.

Email from an agent task​

An agent task can email a contact to request close support and continue working when the contact replies.

  1. Open the task and add each contact under Approved email recipients. The agent can only email contacts listed here.
  2. Under Sending approval, choose Require approval to review each draft, or Send automatically to send drafts to approved recipients without review.
  3. When approval is required, select Approve & Send to send the draft or add instructions and select Request changes for a revision.
  4. Select Wait for reply when the agent should pause the run until the contact replies. The agent can read the reply and its attachments, then continue the task.

Email-triggered tasks​

An agent task can start on its own when an email arrives, for example a bank statement that a bank emails every month.

  1. Open the task and, under Start Mode, choose Automatic when an email arrives. For a recurring task, apply the change to This period and going forward.

  2. Enter a Task mailbox address name. The full address (task-<name>@<your agent email domain>) appears under the field with a copy button as soon as the name is valid. Give that address to the sender. The address can be in To or Cc, and other recipients on the same email are ignored.

  3. Add Allowed senders: the exact email addresses that may start the task. Email from anyone else is recorded and rejected.

  4. Choose how the email's period is recognized:

    • Attachment file name or Subject line with a pattern such as {{MMMM}}_{{YYYY}}, which recognizes July 2026 in Report_July_2026.pdf. Tokens: {{MMMM}} (July), {{MMM}} (Jul), {{MM}} (07), {{M}} (7), {{YYYY}} (2026), {{YY}} (26), plus {{PP}}, {{P}}, {{Q}}, {{FFFF}} and {{FF}} for period-numbered or fiscal-year naming, the same tokens as your period folders. The pattern only needs to match part of the file name or subject. Paste a sample file name to check it.
    • Date received, the month the email arrived in.

    If the month named in the email is not the task's period (for example the July statement arrives named August_2026), set Task period to One month before. The offset can be up to two months either way.

When an accepted email arrives, CloseCore saves its attachments (including the files inside a zip) to the task folder under Agent Email Attachments, starts the task for that period, and tells the agent which email started it. Only the first accepted email for a period starts a run; later emails are recorded.

An email that is not accepted (a sender that is not on the allowed list, no usable attachment, no recognizable period, no task for that period, or a period whose task already started) is recorded under Inbox activity in the task editor, and CloseCore posts a review note on the task so the assignees can follow up.

note

Email-triggered tasks require the agent email feature and a verified agent email domain, which an administrator sets up under Organization settings → Agent email domain.