This guide explains how your reports and reconciliation change when you move from Pass-through payout to Sales day payout.
With Pass-through payout, Adyen adds funds to your payable batch when the card scheme or payment method settles the transaction. As a result, funds from a sales day can be spread across several payout batches.
With Sales day payout, Adyen groups all transactions from a sales day into a single payable batch. We then pay out the batch after a fixed payout delay, regardless of when the card scheme or payment method settles these funds to us. This means that Adyen can settle a transaction's funds to your payable batch before the card scheme or payment method settles those funds to Adyen, making your cash flow and day-based reconciliation more predictable.
Changes to the Settlement Details Report
When using Sales day payout, the Settlement Details Report includes four additional journal types to record adjustments when the card scheme, payment method, or acquirer fails to settle or clear a transaction. Possible scenarios are described in Journal flows.
These entries are not new payments or refunds. They adjust a previous Settled or Refunded entry so that your payable balance matches the funds Adyen receives or pays out.
Additional journal types
| Journal type | Booking | Meaning |
|---|---|---|
| CaptureFailed | Debit | Capturing funds has failed for a transaction. Adyen will not the receive funds from the card scheme or payment method. A debit booking will be made to the next payout, to recover Adyen's pre-financed transaction amount. |
| RefundFailed | Credit | A refund to a card or payment method has failed. If your account has already been debited for the refund, a credit booking is made to the next merchant payout (because Adyen will not have to pay for the refunded amount). |
| SettledReversed | Debit | A debit that reverses a Settled transaction for which Adyen hasn't received the funds from the card scheme or payment method within 30 days of capture. No action is needed; adjustments to your balance happen automatically. If Adyen receives the funds after 30 days, you will see an additional Settled booking. |
| RefundNotCleared | Credit | A refund hasn't been settled because the acquirer hasn't processed the refund 30 days after initiation. However, the customer has received the funds. No action is needed; adjustments to your balance happen automatically. If the refund is processed after 30 days, you will see an additional Refunded booking. This journal type was formerly called RefundNotProcessed. |
Download a sample Settlement Details Report to see how these journal types are booked.
Journal flows
The following journal flows show:
- The entries that can appear in the Settlement Details Report (SDR) after you move to Sales day payout.
- The related record type in the Payment Accounting Report (PAR).
- The status of the payment in your Customer Area.
- Whether a webhook is sent for that journal type.
Captures
| Scenario | Description | SDR entry | PAR record type | Customer Area status | Webhook |
|---|---|---|---|---|---|
| Standard capture | The net transaction amount is successfully captured and credited to your payable batch. | 1. Settled (credit) | 1. Settled | 1. SettleScheduled | 1. CAPTURE 1 |
| Capture failure before the value date | 1. You authorize a payment. Expecting a capture, Adyen credits the payment amount to your payable batch. | 1. No entry. The capture reversal happens before a Settled entry is booked. | 1. Settled | 1. SettleScheduled | 1. CAPTURE 1 |
| 2. If the acquirer later reports a capture failure before the value date, Adyen then debits your payable batch to reverse the advance. Because the reversal is resolved before the value date, these journal entries do not appear in the Settlement Details Report. |
2. CaptureFailed | 2. CaptureFailed | 2. CAPTURE_FAILED | ||
| Capture failure after the value date | 1. You authorize a payment. Expecting a capture, Adyen credits the payment amount to your payable batch. | 1. Settled (credit) | 1. Settled | 1. SettleScheduled | 1. CAPTURE 1 |
| 2. If the acquirer later reports a capture failure after the value date, Adyen then debits your payable batch to reverse the advance. Because the reversal is takes place after the value date, these journal entries appear in the Settlement Details Report. |
2. CaptureFailed (debit) | 2. AcquirerPayoutFailed | 2. AcquirerPayoutFailed | 2. CAPTURE_FAILED | |
| Delayed scheme settlement that clears after 30 days | 1. You authorize a payment. Expecting a capture, Adyen credits the payment amount to your payable batch. | 1. Settled (credit) | 1. Settled | 1. SettleScheduled | 1. CAPTURE 1 |
| 2. The acquirer fails to settle the funds within the 30-day pre-financing window. Adyen then debits your payable batch to reverse the advance. | 2. SettledReversed (debit) | 2. SettledReversed | 2. SettledReversed | 2. No webhook | |
| 3. The acquirer settles the funds late, after day 30. Adyen credits the payment amount again to your payable batch. | 3. Settled (credit) | 3. Settled | 3. SettleScheduled | 3. CAPTURE 1 | |
| Delayed scheme settlement that fails after 30 days | 1. You authorize a payment. Expecting a capture, Adyen credits the payment amount to your payable batch. | 1. Settled (credit) | 1. Settled | 1. SettleScheduled | 1. CAPTURE 1 |
| 2. The acquirer fails to settle the funds within the 30-day pre-financing window. Adyen then debits your payable batch to reverse the advance. | 2. SettledReversed (debit) | 2. SettledReversed | 2. SettledReversed | 2. No webhook | |
| 3. The acquirer confirms definitive non-settlement. The payment moved to the CaptureFailed status. Because the funds are already debited, there is no additional booking on the settlement details report. | 3. No additional entry is added to the Settlement Details Report. | 3. CaptureFailed | 3. CaptureFailed | 3. CAPTURE_FAILED | |
| 1 No specific webhook is sent for the Settled event. At capture, a CAPTURE webhook is sent to the acquirer. | |||||
Refunds
| Scenario | Description | SDR entry | PAR record type | Customer Area status | Webhook |
|---|---|---|---|---|---|
| Standard refund | 1. The refund amount is successfully processed and debited from your payable batch. | 1. Refunded (debit) | 1. Refunded | 1. RefundScheduled | 1. REFUND 1 |
| Refund failure before the value date | 1. You send a refund request. Expecting a deduction, Adyen debits the refund amount from your payable batch. | No entry. The refund reversal happens before a Refunded entry is booked. | 1. Refunded | 1. RefundScheduled | 1. REFUND 1 |
| 2. If the acquirer later reports a refund failure before the value date, Adyen then debits your payable batch to reverse the advance booking. Because the reversal is resolved before the value date, these journal entries do not appear in the Settlement Details Report. |
2. CaptureFailed | 2. RefundFailed | 2. REFUND_FAILED | ||
| Refund failure after the value date | 1. You send a refund request. Expecting a deduction, Adyen debits the refund amount from your payable batch. | 1. Refunded (debit) | 1. Refunded | 1. RefundScheduled | 1. REFUND 1 |
| 2. If the acquirer later reports a refund failure after the value date, Adyen then debits your payable batch to reverse the advance booking. Because the reversal is resolved after the value date, these journal entries appear in the Settlement Details Report. |
2. RefundFailed (credit) | 2. AcquirerRefundFailed | 2. AcquirerRefundFailed | 2. REFUND_FAILED | |
| Delayed refund clearing that clears after 30 days | 1. You send a refund request. Expecting a deduction, Adyen debits the refund amount from your payable batch. | 1. Refunded (debit) | 1. Refunded | 1. RefundScheduled | 1. REFUND 1 |
| 2. The acquirer fails to settle the funds within the 30-day pre-financing window. Adyen then credits your payable batch to reverse the advance booking. | 2. RefundNotCleared (credit) | 2. RefundNotCleared | 2. RefundNotCleared | 2. No webhook | |
| 3. The acquirer settles the funds late, after day 30. Adyen debits the payment amount again from your payable batch. | 3. Refunded (debit) | 3. Refunded | 3. Refunded | 3. REFUND 1 | |
| Definitive refund failure after 30 days | 1. You send a refund request. Expecting a deduction, Adyen debits the refund amount from your payable batch. | 1. Refunded (debit) | 1. Refunded | 1. RefundScheduled | 1. REFUND 1 |
| 2. The acquirer fails to settle the funds within the 30-day pre-financing window. Adyen then credits your payable batch to reverse the advance booking. | 2. RefundNotCleared (credit) | 2. RefundNotCleared | 2. RefundNotCleared | 2. No webhook | |
| 3. The acquirer confirms definitive non-settlement. The refund moved to the RefundFailed status. Because the funds are already debited, there is no additional booking on the settlement details report. | 3. No additional entry is added to the Settlement Details Report. | 3. RefundFailed | 3. RefundFailed | 3. REFUND_FAILED | |
1 No specific webhook is sent when the refund is successfully settled. A REFUND webhook is sent when your refund request for a captured payment is processed. It gives no insights on the successful acceptance of the operation by the external payment method.