Skip to main content
GullySystem
Professional services

Workflow and Approvals for CPA and accounting firms

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A return passes from preparer to reviewer to partner, with each sign-off dated. A reviewer’s note sends it back to the preparer. Nothing is filed without the partner’s mark.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
CPA and accounting firms

How the business operates.

A CPA firm sells a deadline. Individual returns, business returns, quarterly estimates, payroll filings, reviews and audits each fall due on a date set by someone else. Every one passes from preparer to reviewer to partner.

Client and engagement register

Hold each client, entity and family link with the engagements the firm performs for them, the fee basis and the responsible partner.

Due dates, extensions and recurring jobs

Create returns, filings and monthly jobs from a service list, each with its due date, extension date and assigned staff.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Client and entity register. Hold each client with its entities, owners, family links, contacts and the engagements the firm performs for them. Partnerships, S corporations, trusts and individuals sit side by side on one register.
  • Engagement letters and proposals. Prepare proposals with service scope and fee, and record acceptance. The signed engagement letter and any representation letter stay on the client file, so scope can be checked when a client asks for extra work.
  • Deadline calendar and extensions. Raise each return, filing and monthly job from your service list with its due date and extension date. See the week’s deadlines by person. Quarterly estimates and payroll filings sit beside annual returns on the same calendar.
  • Document checklist and client portal. Send a checklist to the client. Accept uploads by item. Staff see which items are in, which are late and which were chased, so prior-year carryover figures and statements are never requested twice.

Operational bottlenecks to check

Deadlines are tracked in a client spreadsheet

Each return or filing has a due date and an extension date, and both are entered once a year by hand. A missed update shows only when the date has passed, and the penalty notice arrives after.

Document requests are chased by email

Clients send statements, receipts and tax forms in parts and by different routes. Staff cannot tell what is still missing without opening the whole email thread and reading every attachment name.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Engagement set-up

    A proposal is accepted, the engagement letter is signed, and the engagement is created with its services, fee basis, partner, preparer, reviewer and due dates.

  2. 2. Document collection

    A checklist goes to the client portal. Uploads attach to the job, and reminders go to the client for anything still missing, such as a depreciation schedule or a year-end bank statement.

  3. 3. Preparation

    The assigned accountant prepares the return or statements, records hours, ties out balances to the trial balance, and notes any open question for the client or the manager.

  4. 4. Review and sign-off

    A reviewer adds notes against the workpapers, the preparer clears them, and the partner signs off before the file is filed or released.

  5. 5. Filing and delivery

    The filed copy and the acknowledgement are stored on the engagement. The client receives the final documents through the portal, with the signed e-file authorisation beside them.

  6. 6. Billing and follow-up

    A fixed fee or recorded time feeds each bill, a partner approves any write-down, and balances still owing drop onto the collections list.

Industry reports to connect with

  • Deadlines and extensions by week and person
  • Document requests outstanding by client
  • Files awaiting review or partner sign-off
  • Hours and realisation against budget by engagement

Questions before implementation.

When should cpa and accounting firms consider workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Related functions for cpa and accounting firms.

    Talk to us

    Discuss workflow and approvals for your business.

    Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

    What happens after you share your requirements

    1. We review your brief and the systems you already use.
    2. We clarify the workflow, missing information and the work to consider first.
    3. The proposed scope sets out the deliverables, responsibilities and dependencies.
    4. Review the scope and commercial terms before deciding whether to proceed.

    Start with your requirements

    Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

    Share your requirements