zograph.
Request a walkthrough

SolutionsFinance

Move finance work forward. Keep authority where it belongs.

Build AI agents that investigate operational cases, prepare recommendations, and carry work through approvals and system checks - while keeping decisions with the right people and systems.

Request a walkthroughExplore the workflow

Featured workflow: Held-payment case handling

Illustration of a held-payment case: the customer Acme Supply Co., the payee Global Parts Ltd., the operating account at Meridian Bank, a payment release memo PR-1042 for $48,250.00 due Sep 15, 2026 with its supporting records complete, and a release request that exceeds the auto-approval threshold and awaits supervisor approval, joined by fine gold lines.

Context brought together

Relevant records gathered for the task.

Work prepared for review

Case memos, recommendations, and next steps.

Authority preserved

Actions governed by your permissions and approvals.

02Workflows to explore

Put agents to work across finance operations.

Bring together records, investigate operational questions, and prepare controlled next steps. Configure agents around the work your finance team handles and the authority each action requires.

  • Featured workflow

    Held-payment case handling

    Investigate the case, prepare the release memo, and coordinate the required human approval and system clearance.

    Output: a reviewed case carried through its authorized next steps.

    See worked example

  • Invoice and payment queries

    Gather invoice, purchase-order, and payment context, identify missing information, and prepare a response.

    Output: query-resolution brief and drafted communication.

  • Reconciliation investigations

    Investigate discrepancies already identified in transaction or accounting records and assemble the available explanations.

    Output: exception pack with supporting records and proposed follow-ups.

  • Period-end evidence preparation

    Gather requested supporting records, organize outstanding explanations, and prepare material for finance review.

    Output: review pack with unresolved items clearly identified.

Your workflow may be different. Agents are configured around your connected systems, working procedures, and action boundaries.

03One workflow, in detail

Illustrative workflow

Featured workflowHeld-payment case handling

Follow a held payment through the decisions that govern it.

Here is how those capabilities come together in a bank payments-operations workflow. An agent investigates the case, prepares the release memo, coordinates communication, waits for the required approval, obtains system clearance, and records the outcome.

A static illustration. Each picture shows one fictional record at a stage of the workflow; nothing here sends a message, releases a payment, or reads a live system, and a submitted transfer is not a settled one.

  1. Investigate and prepare

    Review the customer, account activity, and payee history, and draft a release memo.

    Payment release memo PR-1042 of Sep 10, 2026: to Finance Operations from AP Operations, subject Release held payment, $48,250.00 due Sep 15, 2026, with a summary, a recommendation and three supporting records complete: customer verification, invoice match, policy check.

  2. Communicate within operator authority

    Request permission to send a secure customer message, using your operator authority.

    Secure customer message to Acme Supply Co. through the secure portal, subject Payment under review, from the held-payment verification template, requested by AP Operations on Sep 10, 2026, 10:24 AM, with a preview asking the customer to contact the team securely through their portal; status authorized.

  3. Obtain supervisor approval

    Request approval to release the held payment, including the memo and investigation outcome.

    Release held payment request for P-458271, $48,250.00 to Global Parts Ltd., requested by AP Operations on Sep 10, 2026, 1:14 PM, with the reason for release, three supporting documents PR-1042, CV-2217, IM-3348, and the status Supervisor approval required.

  4. Obtain system clearance before submission

    Once approved, obtain screening-service clearance and then submit the payment to the core system.

    Transfer submitted for P-458271, $48,250.00 to Global Parts Ltd., value date Sep 15, 2026, reference AP-2024-5581, with a processing timeline: release approved at 2:03 PM by C. Wilson, screening cleared at 2:05 PM with no matches found, transfer submitted at 2:06 PM to the core system; status completed.

04Permissions and approvals

Different workflows. Explicit boundaries.

For each agent, define the information it can access, the actions it may take, and when a person or connected system must approve. Here is one example from the featured bank-operations workflow.

Illustration of the arrangement around a payment release memo: a payments agent that investigates, prepares and requests actions; an operator who reviews and authorizes requested actions but approves none; a supervisor who approves high-risk actions; and a screening service that performs compliance and risk checks, each with what it may access, take and approve, joined by gold arrows.

Example policies for the featured workflow

ActionExample policy
Read customer, account, and payee informationAllowed
Change the customer transfer limitDenied
Send a secure customer messageOperator authorization
Release the held paymentSupervisor approval required
Submit the transferScreening-service clearance required, after release

These are example policies for one workflow. Other finance agents can have different boundaries.

Requesting an action is not approving it.

The operator can ask the agent to release the payment, but only the supervisor can approve that action. Submission also requires screening-service clearance.

05The record and the follow-up

See what happened. See what authorized it.

Inspect the agent’s work alongside the permission decisions that governed it. Review what was prepared, what was approved, and what happened next.

Decision record

A complete timeline of actions, permissions, and outcomes.

  1. 10:02 AMSep 10, 2026Customer and account information readAuthorized by: Data access policy
  2. 10:03 AMSep 10, 2026Transfer-limit change refusedRefused by: Administrator rule
  3. 10:26 AMSep 10, 2026Secure customer message authorizedAuthorized by: Operator approval
  4. 2:03 PMSep 10, 2026Held payment releasedAuthorized by: Supervisor approval
  5. 2:05 PMSep 10, 2026Transfer submission clearedAuthorized by: Screening service
  6. 2:06 PMSep 10, 2026Transfer submittedRecorded by: Payment tool
  7. 2:06 PMSep 10, 2026Post-release review queuedTriggered by: Workflow rule

Continue the follow-up without another chat.

A background agent continues the review using the same context, permissions, and policies - so nothing is lost and the right people stay in control.

Post-release review

Event triggered

A background agent is continuing the review using the same context and controls.

  • Review release decision
  • Check submission status
  • Record next action

Starts automatically after transfer submission.

06Connected systems and procedures

Keep your systems part of the decision.

Connect the tools that provide case information and perform permitted actions. Bring your screening logic into the workflow and control selected tool results before they reach the model.

Connected information and actions

Bring together the systems that hold case information and perform permitted actions, such as core banking, payments, and customer data.

Your screening logic

Apply your screening and compliance rules in the workflow, including release and submission checks from your screening service.

Controlled tool results

Choose which tool responses are shared, and transform or mask sensitive details before they reach the model.

Available records and actions depend on the integrations and permissions you configure.

07Get started

Start with one finance workflow.

Bring a process that crosses records, teams, or approval boundaries. We’ll explore what an agent should investigate, what it should prepare, and which decisions remain with your people and systems.

Clearer finance operations.
Better control.