Multi-brand fashion group automates payment and settlement reporting

1The problem

• Each brand had its own merchant accounts on the payment platform — every reporting cycle meant logging in again and again.
• Reports came as one CSV per merchant; combining them into a single Excel per report type was repetitive copy-paste work.
• The weekly and monthly cycles spanned multiple brands and many merchants — slow, and easy to merge wrongly.
• A failed login or a page that would not load stalled the whole run until someone noticed.

2What we did

1. 1An attended robot started on demand from UiPath Assistant; a mapping table drives every run — date range, which brands (one, two, or all), and report type (payments, settlements, or both).
2. 2For each brand account the robot logs into the Adyen customer portal and works through every merchant on the list.
3. 3Payment reports: it filters the requested date range and exports the CSV for each merchant.
4. 4Settlement reports: it downloads the aggregate settlement details for each merchant.
5. 5All CSVs merge automatically into one Excel per report type — a single header, no manual merging.
6. 6Failures self-manage: a failed login or an unloaded page skips to the next brand and writes the details to a log Excel; empty results are logged with merchant and date range.
7. 7Maintained across four years — migrated browsers when policy changed and made the configuration dynamic so different teams manage their own runs.

3Inside the Platform