Skip to main content
GullySystem
Financial services

Audit Trail for Payment service providers

Record who changed important business data and when.

Platform

Does this function belong in your operation?

Use when changes to money, permissions or business records need accountability.

A monitored record is created, changed or deleted.

Every change to a merchant’s rate, bank account or reserve is stamped with the user and the time. A compliance reviewer can replay any decision. Old and new values sit side by side.

Bring the records the workflow depends on.

  • Events to record
  • User identities
  • Retention and access rules

Outputs to check

  • Event and change history
  • Restricted audit-review view
  • Exported investigation evidence

Follow the audit trail 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 event coverage

    List the records, actions and systems to be observed.

  2. 2. Capture the event

    Retain actor, timestamp, reference and relevant changed values.

  3. 3. Protect the history

    Apply restricted access and the agreed retention controls.

  4. 4. Investigate a change

    Trace the event sequence without editing the underlying evidence.

  5. 5. Export or retain evidence

    Record authorised access and preserve context needed to interpret the history.

Who uses the module, and who approves?

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

Owner

Looks once, when something does not add up.

Accounts assistant

Settles a difference between the ledger and the print without calling three people.

Your accountant or auditor

Asks how a figure changed and gets the history, which is faster than a reconstruction.

Branch manager

Sees corrections made at the counter, and the reasons given.

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.

Shared user account

Flag the attribution limitation and assign individual accounts before relying on personal accountability.

Missing external event

Record the coverage gap instead of implying that all systems were monitored.

Deletion request

Apply authorised retention and legal review without allowing ordinary users to rewrite event history.

Can this work independently?

An audit trail must receive events from the business processes being reviewed; it is not a standalone source of truth for systems it cannot observe. Roles control review access, and retention rules determine how long event evidence is kept.

Systems and records it connects with

  • Roles and permissions: Named user access and action-level authority.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Finance and accounting reporting: Ledger-based period totals and reconciliation outputs.

Configure, test and introduce the workflow.

  • You list the records where a silent change would hurt: rates, receipts, credit limits, payouts. You get a written note of the fields to be logged and those left out. Start small.
  • Assign named users and confirm which actions are recorded. In a trial environment, change representative records and verify actor, timestamp and before-and-after values. Check that ordinary users cannot alter the history.
  • The owner names the few people who can open it. Access rules are written down, and each of those people has a test login. Access stays narrow. The log runs alongside normal entry. After a month the group meets to see which questions it answered and which fields should be added.

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.

  • Recorded changes identify an actor and time.
  • Reviewers can distinguish earlier and current values.
  • Ordinary users cannot edit the audit history.
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 audit trail?

Use when changes to money, permissions or business records need accountability. A monitored record is created, changed or deleted.

What should we bring to the requirements discussion?

Bring anonymised examples of Events to record; User identities; Retention and access 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. Record who changed important business data and when. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Audit records do not by themselves prove regulatory compliance or prevent unauthorised 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. Recorded changes identify an actor and time. Use this check when reviewing the first working version.

Talk to us

Discuss audit trail 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