Skip to main content
GullySystem
Financial services

Bank Reconciliation for Payment service providers

Match bank statement entries with the ledger.

Finance & Accounting

Does this function belong in your operation?

Use when bank activity needs checking against the books.

A statement becomes available for a period.

Settlement files from the acquirer are matched to payout batches and to the bank statement. A difference of one transaction is listed with its amount. Finance clears it before the next payout.

Bring the records the workflow depends on.

  • Bank transactions
  • Ledger entries
  • Matching rules

Outputs to check

  • Matched transaction register
  • Unmatched and disputed entry list
  • Reconciled account statement

Follow the bank reconciliation workflow.

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

  1. 1. Load the statement

    Check the account, period and opening balance.

  2. 2. Load ledger entries

    Use the corresponding books and retain source references.

  3. 3. Propose matches

    Compare amounts, dates and references, including grouped payments.

  4. 4. Resolve exceptions

    Review charges, reversals and unidentified entries before approved adjustment.

  5. 5. Close the reconciliation

    Verify ending balances and retain any unresolved differences explicitly.

Who uses the module, and who approves?

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

Accounts assistant

Runs the match, clears the easy lines, and leaves the questions for somebody who knows the customers.

Your accountant or auditor

Opens the unmatched list at closing and sees the reason written against each entry.

Owner

Sees the real cash position, without counting a cheque from a customer who has stopped answering.

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.

Bank charge missing in books

Prepare an adjustment for accounting approval before completing the match.

One payment covers several entries

Record the allocation and verify that the combined amount agrees.

Reversed bank transaction

Unwind the earlier match with history intact and review the affected ledger entry.

Can this work independently?

Reconciliation can use exported statements and ledger files. Receipt, expense and accounting links reduce re-entry but are not required for a controlled import. Approved adjustments must be posted in the accounting process; matching alone does not change the bank account.

Systems and records it connects with

  • Receipts management: Recorded customer payments and invoice allocations.
  • Expense tracking: Approved cost entries, evidence and payment references.
  • Payment gateway settlements: Provider transaction references, fees and settled amounts.
  • Finance and accounting reporting: Ledger-based period totals and reconciliation outputs.

Configure, test and introduce the workflow.

  • List each account and the format its statement arrives in. A note comes back. It names the accounts to set up and the import route for each.
  • Provide a closed-period bank statement and its ledger. Test ordinary matches, bank charges, combined payments and reversals. The accountant checks matched entries, unresolved differences and the ending reconciliation before approving the rules.
  • The accounts assistant and the accountant sit down with their own data. Questions are logged and answered in writing. The next statement is imported on arrival. The close is reviewed together, and rules are adjusted from what the team found.

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.

  • Opening and closing balances reconcile.
  • Transactions are not matched twice.
  • Unresolved differences remain visible.
Payment service providers

How the business operates.

A payment business keeps two kinds of record. One is the transaction stream from your gateway or acquiring partner. The other is the context around it: who the merchant is, which merchant discount rate applies, what was paid out, what sits in reserve and what is disputed.

Merchant onboarding file

Keep application, KYC papers, sanctions screening result, MCC and approval on a single file per merchant, with a checklist, a named reviewer and the status of each document.

Rate cards and pricing

Record the discount rate, per-transaction fee and scheme pass-through by payment mode and merchant, with effective dates, so each payout uses the rate in force on the day of capture.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Merchant application and KYC file. Open one file per merchant with the application, ownership papers, director identity documents for know-your-customer checks, bank proof and website review. A checklist shows which paper is missing and who is chasing it.
  • Screening and risk review log. Record each sanctions and adverse-media check with its result, reviewer and date. Assign the merchant category code and a risk tier, and keep the reasoning for an approval or a decline.
  • Contracts and rate cards. Store the signed merchant agreement beside its pricing: discount rate, per-transaction fee, scheme pass-through and payout terms by payment mode, each with an effective date.
  • Capture and transaction file import. Load the capture, refund and fee files from your gateway or acquirer in the layouts they send. Totals per merchant and per day are shown before any payout is built.

Operational bottlenecks to check

Onboarding stalls on one paper

One identity-check file is parked for a director’s address proof, but the team cannot count other files waiting for the same document. Merchants sign with a rival gateway.

Rate cards live in a spreadsheet

Someone keys the negotiated rate by hand. The payout then runs at the standard rate. Finance posts a reversal a fortnight later.

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

    A merchant applies through a form or a sales contact. The business type, expected volume, payment modes and website are captured, and an analyst is assigned.

  2. 2. KYC and screening

    Papers are collected against a checklist. Ownership is mapped, names are screened, a category code and risk tier are set, and approval is recorded with its reasons.

  3. 3. Pricing and go-live

    The signed agreement and rate card are attached with effective dates. Settlement account details are verified before the merchant is switched on in your gateway.

  4. 4. Capture and payout

    Capture and fee files are imported each cycle. A batch is built net of fees, refunds and reserves, reviewed by an approver and passed to the bank process.

  5. 5. Reconciliation

    Batches are matched with the sponsor bank statement and partner files. Breaks get a cause and an owner, and clear before the cycle is closed.

  6. 6. Disputes and support

    Chargebacks, refunds and merchant queries are worked from one desk. Evidence is attached, deadlines watched, and outcomes posted to the next payout advice.

Industry reports to connect with

  • Applications by stage, reviewer and missing document
  • Merchants by risk tier, category code and payment mode
  • Payout batches by cycle, with fees, refunds and reserves deducted
  • Reconciliation breaks by cause, age and owner

Questions before implementation.

When should payment service providers consider bank reconciliation?

Use when bank activity needs checking against the books. A statement becomes available for a period.

What should we bring to the requirements discussion?

Bring anonymised examples of Bank transactions; Ledger entries; Matching 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. Match bank statement entries with the ledger. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The module does not authorise payments or decide accounting adjustments.

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. Opening and closing balances reconcile. Use this check when reviewing the first working version.

Talk to us

Discuss bank reconciliation 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