Adyen MerchantPayout: reconcile the row without counting twice
Updated · 3 min read
MerchantPayout is a journal type inside Adyen’s Settlement details report, not a separate report. To explain it, compare the report’s non-payout components within the same merchant account, batch and net currency. Adding the payout row to those components counts the transfer twice.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Generate the merchant batch report
- With the appropriate merchant reporting role, open Reports → Settlement details → Manage report → Manual.
- Choose Current account and Single batch for the identified merchant batch.
- Generate and retain the report with Merchant Account, Batch Number and Net Currency.
- Identify MerchantPayout as the output row and retain the non-payout component selection separately.
Adyen’s manual-report guide documents generation. The Settlement details specification defines the journal and amount roles; a company-level external-acquirer report is a different source.
Within the file, distinguish transaction journal types from MerchantPayout. Its Net Debit is the payout being explained. The Modification Reference can include the TX…XT reference, batch and account information visible in the bank description. Compare the actual values and destination rather than treating a sample reference shape as a unique match. Source: Net Debit and Modification Reference definitions.
Exclude the output row from its own components
The synthetic batch exercise stipulates 1,000 in non-payout net credits and non-payout debits of 30 and 70. Those explain a 900 MerchantPayout Net Debit. Including that 900 debit again in the component calculation reduces the apparent residual to zero but destroys the distinction between the transfer and its funding components.
| Synthetic merchant M1 / batch B1 / EUR | Amount | Role in the bridge |
|---|---|---|
| Non-payout net credits | +1,000 | Funding component |
| Non-payout debit | −30 | Funding component |
| Other non-payout debit | −70 | Funding component |
| Net of selected components | 900 | Explains payout amount |
| MerchantPayout Net Debit | 900 | Output to compare, not another funding component |
Subtracting the output 900 from the component net gives zero, but that is not a zero-value payout. The receiving bank observation still needs independent evidence.
Keep Net Currency with every amount and Merchant Account with Batch Number. The same batch number in a different merchant account is not the same report population. Do not mix transaction currencies or assume every entry is a sale. Brazil installment-specific instructions and external-acquirer reporting require their own evidence outside this bounded example.
Verify bank receipt independently
Retain the report, payout row, component selection and bank reference together. A generated report does not establish that the receiving bank has posted the funds. Unmatched currencies, references or unexplained journal items stay open. The exercise tests signed arithmetic, key scope and double-count prevention; no report generation or Adyen payment was executed.
For a PDF-only bank source, download LocalExtract. It processes one PDF locally to date,description,amount CSV; it does not access platform accounts or synchronize accounting records.
Official sources and scope
Documentation checked October 16, 2026. Official reference 1 — lead-02 · Official reference 2 — adyen-transactions · Official reference 3 — adyen-manual
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy