Skip to main content
GullySystem
Financial services

Collections and Payment Follow-Up for Banks

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.

Accounts past due are listed by branch with days overdue, last contact and promise to pay. Collection officers log each call and visit. Broken promises move the account up the list.

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.
Banks

How the business operates.

A bank serves people and businesses through branches, relationship managers, call centres and digital channels. Each channel keeps its own notes, yet the customer expects one institution. Records built around the account number rarely show who the customer is, which sanction is pending or what was asked last month.

Customer records

Hold each person or business once, with linked accounts, guarantors, contacts, relationship manager and branch, so every team in every department starts from the same customer file.

Applications and approvals

Take account opening and loan applications, route them by amount and role, and keep each decision with the approver’s name, date, covenants and note.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Customer records. Hold each person or business once. Linked accounts, nominee details, contacts, relationship manager and home branch sit on one page that every team opens.
  • Enquiries and product applications. Record every enquiry with its channel and product, carry it forward to an application, and spot the enquiries that have stopped moving after a rate quotation went out.
  • Documents and identity checks. Store identity, address, income and specimen signature papers against the customer. Note who verified each one, and flag documents close to their expiry date.
  • Credit applications and approvals. Route each application by amount and role, and collect the reviewer’s notes on collateral and covenant terms. The final sanction stays with the approver’s name, tenor and date.

Operational bottlenecks to check

Customer details sit in several tools

The branch, the loan desk and the complaints team each keep their own notes. A new mobile number given at one teller counter never reaches the other two desks, and statements and calls go to the old one.

Approvals leave a thin trail

A sanction given by email or in a committee meeting is hard to find later. The file shows the outcome but not the reviewer, the limit applied, the collateral taken or the reason. Audits need all four.

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. Enquiry

    A person asks about a savings account, a card or a term loan at a branch, on the phone or online. The enquiry is logged against the customer and the product asked for.

  2. 2. Application and documents

    The application is entered once. Identity, address and income papers are attached, a collateral valuation is added for secured lending, and each paper is marked as checked with the verifier’s name.

  3. 3. Review and approval

    The request routes to the officer or committee its amount requires. Each sanction is recorded with the approver, the tenor, the covenant terms, the date and the reason for the decision.

  4. 4. Servicing

    Service requests become tickets. A cheque book, a card replacement, a passbook reissue or an address change each gets an owner and a promised date.

  5. 5. Follow-up

    Complaints are answered by their reply date. Accounts past due are listed by age, and every call, promise and moratorium request is noted against the account for the next officer to read.

  6. 6. Reporting

    Branch managers and head office read the same counts of applications, sanctions, complaints and arrears, taken straight from the records, so nobody rebuilds them from sheets at month end.

Industry reports to connect with

  • Applications by product, branch and stage
  • Sanctions by level, approver and turnaround
  • Complaints open, closed and past ombudsman date
  • Collateral valuations due for renewal

Questions before implementation.

When should banks 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