PLEASE NOTE: This issue only affects payouts where a collected payment was refunded prior to being paid out.
This article will explain the issue regarding missing payment events within payout breakdowns. It will cover:
- Overview of the issue
- The fix
Overview of the issue
This issue affects all payments successfully collected prior to May 17th 2017 that were then refunded before being paid out i.e. while in a 'confirmed' status.
These payments were left with a net balance of zero prior to the paid out event being created as so consequently did not appear in the payout breakdown on the date they were due to be paid out, and so reconciled against.
The transaction fee total was however, correct for the total number of payments initially collected. This resulted in a visual discrepancy as the fees total was higher than the sum of fees for each payment visible in the payout breakdown.
In the example screenshot below the payout breakdown shows three credits of £200 each. This corresponds with the Gross amount showing in the details section above, totalling £600. However, this is misleading.
As you can see, the GoCardless fees are showing as £8.00 - (remember, our fees are 1% capped at £2). This is because a fourth payment of £200 was charged on the same date as the other three and also due to be paid out. Because this fourth payment was refunded before reaching a 'paid out' status, it was not shown in the breakdown. Nevertheless, it accounts for the Gross amount correctly showing as £600.
To fix these discrepancies, we are backfilling payout events to include both a 'paid out' and 'refunded' payment event for these payments that were refunded while 'confirmed'.
The payout breakdown will then look like this:
As you can see, the fourth payment (in this case for Julie Dow) is showing in both the Credits and Debits sections.
What data is affected?
All payments [that were refunded prior to a paid out event being created], before the 17th May 2017.
How many of my payments were affected?
We can provide a list of affected payment IDs to you via email. Please note that only merchants who have contacted by our team about this issue have been affected.
Why has it only been noticed now?
This was discovered as a result of an investigation into a query we received from a merchant. We hadn't noticed this issue previously as the refund event cancelled out the creation of the upcoming paid out event being in our system. Without the paid out event, there were effectively no discrepancies within our system to identify.
What date is the fix being rolled out?
How will the fix affect me?
In most cases, this will have no affect. However, if you are using an external system to reconcile your payments, you may need to cross check against your own system to ensure the refunds have been accounted for.
Could this happen again in the future?
It's highly unlikely, however our engineering team have advised that there's always a chance that a similar issue could arise in the future. The fix implemented for this particular issue though will ensure these specific discrepancies won't occur again in the future.