Download Worldpay iQ Statements for Reconciliation

To download Worldpay iQ statements, use the existing merchant's iQ account, confirm the merchant scope and reporting month, then retrieve the monthly processing statement. Keep activity reports and tax forms as separate deliverables rather than treating every financial export as the same document.

Regions' official iQ overview confirms monthly-statement downloading for its Worldpay merchant service. This guide uses public documentation checked on November 9, 2026; it does not report a customer's download or a tested BrowserAct iQ collector.

Establish the merchant scope first

Use the portal route supplied by the existing Worldpay merchant provider or account administrator. Worldpay has multiple products and regional services, so a working login to another Worldpay system does not establish the iQ access needed here.

For the collection request, identify the merchant account, relevant location or MID, and statement period. If the team works across several merchants, build that list from the finance request rather than from whichever merchant is visible when the portal opens.

The University of Kentucky's merchant-finance guidance gives a concrete customer example. Its departments obtain online access through their merchant-services function and use iQ for recent and previous monthly statements. That supports a real reconciliation task, but it is not a universal account-administration procedure for every Worldpay merchant.

Retrieve the monthly processing statement

The public sources confirm statement retrieval without establishing one current button-by-button menu for every iQ version. Follow the statement facility shown in the authorized merchant account.

1. Sign in to the applicable iQ merchant account.
2. Confirm the merchant or MID covered by the request.
3. Locate the monthly processing statements available for that merchant.
4. Select the required reporting period and retrieve the statement.
5. Save the file to the approved archive and inspect its merchant and period.
6. Retrieve activity reports separately if the reconciliation also requires them.

Do not infer a universal bulk ZIP, fixed history window or multi-MID Download All feature from the fact that past statements are available. Inspect those controls in the actual account before relying on them for a recurring workflow.

If the document opens in a viewer, ensure it was also saved. A visible statement is a useful review step, not proof of a completed file handoff.

Select the right financial record

The same portal can contain records that look similar while supporting different questions.

For your own reconciliation, record the date basis. Transaction, settlement, bank-posting and statement dates can differ. Downloading another date range until the totals happen to match is not a reliable substitute for understanding the accounting period.

Check report permissions when statements are missing

A login that can display transactions may not have all the report access needed for statement retrieval. Confirm the merchant scope first, then the statement-report permissions with the existing account administrator.

The Merchant Central iQ integration guide, updated in October 2026, distinguishes Merchant Statements report access from Partner Statements access for residual reporting. That is an integration-specific configuration guide, not a reason to create an administrator for a basic reading task.

It also distinguishes a statement being available at the processor from being imported into Merchant Central. If an existing integration lacks an older month, first determine whether the document exists in iQ. Repeatedly rerunning an integration cannot create a statement that is unavailable in the underlying account.

Record the missing item precisely: merchant, reporting period, document type, whether it was listed, and where retrieval stopped. Keep credentials and security-question answers out of that exception record.

Archive by merchant and statement period

A useful register includes merchant reference, statement period, document type, retrieval status and saved-file location. If a transaction export supports the same review, list it separately so the accountant can see which artifacts are complete.

After saving the document, reopen it and inspect the identifiers. File count alone is a weak completeness test: one duplicate statement can mask one missing merchant. Keep the expected merchant-and-period list as the basis for acceptance.

For a repeat run, return to unresolved items instead of collecting the entire month again. If a corrected statement appears later, preserve the relevant version history and the reason for its replacement.

Use automation for a defined collection gap

An existing reporting integration may already provide the needed records. Check its merchant coverage, statement availability and file handoff before replacing it with a browser job.

BrowserAct offers reusable Cloud Bots for allowed browser tasks. A particular iQ collector still needs its current login, merchant permissions, actual statement file and repeat-run behavior verified. No tested iQ template or automated retrieval result is supplied here.

The vendor-portal collection guide explains the expected-document checklist. The CLI, MCP and Cloud guide helps a technical team choose an execution route. Once the scope is clear, review BrowserAct's workflow options for the repeated work left after native reporting.