Skip to main content
GullySystem
Professional services

Collections and Payment Follow-Up for CPA and accounting firms

Turn unpaid customer balances into assigned follow-up actions.

Sales and Distribution

Does this function belong in your operation?

Use when customer credit creates balances that require organised follow-up.

An invoice becomes due or a payment promise needs checking.

Clients who file but do not pay appear in an ageing list by partner. Calls and promises are noted. Returns can be held back until fees are settled.

Bring the records the workflow depends on.

  • Outstanding invoices
  • Customer contacts
  • Follow-up ownership and rules

Outputs to check

  • Assigned collection action list
  • Payment-promise and dispute history
  • Overdue balance follow-up report

Follow the collections and payment follow-up workflow.

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

  1. 1. Prepare balances

    Use current invoices, credits and allocated receipts.

  2. 2. Prioritise action

    Assign due accounts and separate disputed amounts.

  3. 3. Contact the customer

    Record the discussion, promise and next date.

  4. 4. Check the outcome

    Confirm whether payment arrived or another decision is needed.

  5. 5. Close or escalate

    Remove settled items and route unresolved exposure to the authorised owner.

Who uses the module, and who approves?

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

Accounts assistant

Works the list from the top and keeps the notes current.

Field collector

Carries the day’s route on a phone and records what was actually brought back.

Sales executive

Knows what the customer owes before asking for the next order.

Owner

Reads promises broken twice, and decides who stops getting goods.

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.

Customer disputes invoice

Separate the dispute owner and action from routine payment reminders.

Promise date missed

Record the failed promise and route the next action under the agreed policy.

Payment received during follow-up

Reconcile it before sending another demand for the same amount.

Can this work independently?

Collections can use a reviewed outstanding-balance import. Invoice and receipt connections keep the amount current, while credit control decides whether further orders are held. Follow-up records do not post payments; settlement must come from the authorised receipt or accounting process.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • We go through your receivables and the way calls are made now. You send a recent outstanding statement. A note comes back on how accounts are grouped.
  • Timing before and after the due date, tone of messages and escalation limits are agreed. You approve the wording for each stage. Open bills are imported from your accounting software. The accounts team checks a sample against the ledger. Mismatches are corrected.
  • Collectors and the accounts assistant use the list beside their old method. Notes go in. Gaps in the list are fixed. Collectors are trained on the phone screens. The diary is set aside. From then on the daily list is the working tool.

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.

  • Follow-ups use current balances.
  • Payment promises retain dates.
  • Settled invoices leave the active collection list.
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 collections and payment follow-up?

Use when customer credit creates balances that require organised follow-up. An invoice becomes due or a payment promise needs checking.

What should we bring to the requirements discussion?

Bring anonymised examples of Outstanding invoices; Customer contacts; Follow-up ownership and 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. Turn unpaid customer balances into assigned follow-up actions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Communication permissions and collection conduct remain your responsibility. The customer’s actual payment is recorded separately from follow-up activity.

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. Follow-ups use current balances. Use this check when reviewing the first working version.

Talk to us

Discuss collections and payment follow-up 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