# Accounting automation software: custom checklists | Meridian

Most accounting automation handles one task. Meridian custom checklists run regular recurring work: start it, walk away and review the finished work.

Canonical URL: https://meridian.pilot.com/accounting-automation-software

## On this page

- How Meridian automates recurring work
- Accounting automation beyond the month-end close
- Hold every client to your firm’s standard, with their exceptions built in
- Stop emailing Excel files between teams
- Recurring work runs on checklists. One-off work goes to Meridian AI
- How this fits into Meridian

## Frequently asked questions

### What is Meridian's checklist system for recurring work?

It is an executable definition of an accounting workflow: the required inputs, ordered steps, controls, expected outputs, dependencies, and review points. Meridian does not simply mark those tasks complete; it uses accounting tools and client context to perform the work. The monthly close is the leading example, but the same model can support other recurring processes.

### How does Meridian support firm-wide templates?

Firm-wide templates encode the default inputs, sequence, controls, outputs, and review expectations for a recurring workflow. Teams can apply the template across a portfolio and override only what is genuinely client-specific. This lowers process drift and makes improvements reusable: when the firm decides a check should occur every close, it can become part of the standard process rather than a tribal reminder. Governance over template changes should be assigned during implementation.

### How does Meridian customize a standard workflow for an individual client?

The standard template supplies the firm’s default process and controls. The client layer overrides the ledger, institutions, chart, accounting basis, materiality, schedules, deadlines, dimensions, and special policies. Meridian executes the resulting workflow with the client’s own history and evidence. This preserves consistency without treating every book identically.

### What kinds of work should a firm run through a recurring checklist, and what belongs in Meridian AI?

Use a checklist when the work has a recurring trigger and a repeatable definition: month-end close, AP processing, year-end tasks, reporting packages, or deadline-driven compliance steps. Use Meridian AI when the outcome is one-off or exploratory: onboarding cleanup, a restatement, a client request, diligence questions, or a chart-of-accounts redesign. A task can move from AI to the checklist once the firm decides it should recur.

### How can Meridian run recurring tax workflows and deadline-driven checklists?

A firm can define required documents, due dates, ordered preparation steps, validations, reviewer roles, and outputs as a checklist. Meridian can gather inputs and execute connected data work, while routing technical judgments to tax professionals. The checklist model can support different entity types; firms should confirm which tax workflows are already packaged and which require configuration.

### Do we have to build every checklist from scratch?

No. The close checklist runs out of the box, and your firm's defaults and client preferences layer on top. For other workflows, start from the SOPs or checklists you already use.

### What is accounting automation software, and how is Meridian different?

Most accounting automation software handles one task, like bank feeds, categorization rules or AP capture, and leaves your team to stitch the rest together. Meridian runs the whole recurring workflow your firm defines, using the client's books, schedules and files, then hands your team finished work to review. Nothing reaches the client without your sign-off.
