SwanPay Audit (1214 onwards)

Created by Migration Bot, Modified on Fri, 23 Oct at 11:25 AM by Migration Bot

Originally written by John Hardwick, last updated Apr 30, 2026, on the Swan Retail knowledge base (FRS).

Part of: Financial Reports


This report lists all payment requests sent to SwanPay within a given date range.

image-20241104-120107.png

Crystal report name SwanPay Audit 2

Payments shown with a black font successfully completed with the payment value being recorded in SwanFRS.

Payments shown in a red font were sent to the SwanPay system but did not complete and therefore there is a potential the payment was taken from the customer and therefore needs manually inserting into SwanFRS.

Please check with the SwanPay portal to establish the payment status of the transaction before manually processing a payment in SwanFRS.

If, in the unusual event that a payment does not complete, the report will show the POS ID irrespective of technical selection choice.

Records shown with a light yellow background relate to manually processed payments linked to the SwanPay transaction via a specific payment reference. (I.e. Manually posted payments using the Ref specified in this report to tie the manual payment to the Swanpay transaction).

Individual payment transactions are omitted in ‘Total Only’ Mode.

Differences are shown alongside each group total (where applicable) in a red font.

Void and voided transactions are shown with a salmon background. (voided is the original tender which is cancelled via the void).

When showing technical data, per tender, the report shows the ‘idempotency’ and ‘POS ID’ references which may be requested by support when investigating issues.

When processing ‘manually keyed card payments, the report displays an M alongside the Payment reference

image-20250122-124602.png

Selection Criteria

Run time choices, user selectable.

  • Trading location

  • Date Range

  • Grouping

    • Location / Transaction Date / PED

    • Location / Transaction Date

    • Location / PED / Transaction Date

    • Location / PED

    • Location

  • Details

    • Show Individual Payments

    • Show Group Totals Only

  • Show Technical

    • Yes - include reference data required when investigating anomalies.

    • No

  • Include

    • All Transactions

    • Exceptions Only (Payments send to SwanPay but not recognised in SwanFRS)

    • Completed Only (Exclude exceptions

  • Show Technical Data

    • Yes / No

  • Include

    • Sales Only

    • Refunds Only

    • Voids Only

    • All Transactions

Selecting No to this year only produces a comparison line below each grouping showing values for last year for the same week.

Print Sequence

As indicated by blue numbered squares in the report example.

1 Location

2 Transaction Date or PED (subject to selection)

3 PED or Transaction Date (Subject to selection)

4 Payment Transaction (Detailed mode only)

Report Totals

As indicated by yellow numbered squares in the report example.

1 PED or Transaction Date (subject to selection)

2 Transaction Date or PED (Subject to selection)

3 Payment Location

4 Report

Printed Fields

Fields printed on the report.

  • Payment Processing Location

  • Transaction Date (where selected)

  • PED (EPOS ID) (where selected)

  • Idempotency key (where selected)

  • Payment Date / Time (Detailed mode only)

  • User / Operator (Detailed mode only)

  • Sales Order ID (Detailed mode only)

  • Customer’s Name (Detailed mode only)

  • Payment Request Value (Detailed mode only)

  • Tender Type (Detailed mode only)

  • Payment Reference (Detailed mode only) - as keyed in SwanFRS.

  • Payment ID (Detailed mode only) - SwanFRS’s Payment reference

  • Transaction Type

  • Date Reconciled (Detailed mode only)

  • Date Posted to Accounts (Detailed mode only)

  • Payment Request Total

  • Payments in SwanFRS Total

  • Manually entered Adjustment Total

  • Shortfall Total

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article