Worldpay Merchant Statement to Excel: Extraction Guide

A Worldpay merchant statement to Excel job runs through one of two paths, and which one applies to you depends on what Worldpay actually gives you each month. The first path is the Worldpay iQ Reporting & Analytics portal, which exports CSV and Excel files directly — fragmented across separate reports such as Fee Report, Net Settled Sales by Transaction, Session Data, Activity Reports, and Chargeback Performance. The second path is the multi-page PDF statement from FIS that lands as a paper copy, an emailed attachment, or a download from a reseller's portal. Most of the practitioner work in this article addresses the second path.

Both paths converge on the same deliverable: a single working spreadsheet that stitches the cover summary, the per-month fee detail, the dense interchange detail page, the assessments, the adjustments, and the chargeback exposure into one schema you can pivot, filter, and audit against. The categorisation that turns that spreadsheet from an inventory into a fee-audit instrument is the load-bearing distinction this article keeps coming back to: interchange (pass-through, set by the card networks, non-negotiable), card-network assessments (pass-through, also network-set), and Worldpay's own processor markup, which is the only fee layer the merchant can actually negotiate.

If you have iQ access and only need transaction-level data inside the last 24 months, the next section walks the iQ export and tells you where it falls short. If you're working from PDFs only — paper copies from older Vantiv-era setups, emailed attachments, or, more commonly, statements that arrive through an ISO or MSP reseller that doesn't grant you iQ access — the page-by-page anatomy below is the path you need. Operators who run several processors will recognise the same workflow shape from the parallel Heartland merchant statement extraction walkthrough; the labels differ, the structure does not.

The iQ Reporting & Analytics export — and where it falls short

If your account includes iQ access, the export mechanism is straightforward: each report renders in the browser with an Excel icon at the top of the page, and clicking it downloads the underlying data as a CSV or XLSX. The reports you'll reach for most often when reconstructing a statement are the Fee Report (per-month fee detail with category labels and amounts), Net Settled Sales by Transaction (transaction-level deposit detail), Session Data (batch-level settlement records), Activity Reports (daily processing counts and totals), and Chargeback Performance (chargeback cases, retrievals, reserve activity). Run as a set across the same period, these reports cover most of what a printed statement contains.

That phrasing — "most of what a printed statement contains" — is doing real work, because four practical limits separate the iQ exports from a working merchant statement spreadsheet.

The first is fragmentation across reports. There is no single iQ download that gives you a complete merchant statement. Fee detail lives in the Fee Report. Transaction-level deposits live in Net Settled Sales. Chargeback exposure lives in Chargeback Performance. Stitching the fragments back together into one dataset that ties (MID, statement month) across every sheet is a job iQ does not do for you, and it's effectively the same stitching the PDF extraction job produces — just starting from CSV inputs instead of PDF pages.

The second is the 24-month transaction-level limit. iQ exposes transaction-level detail for the previous 24 months only. For an annual fee review across two years that's fine; for a three-year processor RFP, a multi-year tax audit, or a historical effective-rate trend, anything older has to come from PDF statements you've kept on file. The sooner a fee analysis goes back, the sooner the iQ-only path runs out.

The third is the CSV truncation gotcha. Worldpay's own iQ documentation warns that exported CSVs can truncate values in some columns because Excel rounds numeric strings beyond 15 digits of precision. Long transaction identifiers, tokenised PANs, and reference numbers are the typical victims. A bookkeeper who opens the CSV in Excel and saves it without changing column types loses precision permanently in those columns, and the truncated values won't match anything in a downstream system. The fix is to import the CSV as text rather than letting Excel auto-detect numeric types, but the gotcha catches plenty of users who weren't warned.

The fourth limit is the one that surprises people most: many Worldpay merchants don't have iQ access at all. Worldpay sells through a wide network of ISO and MSP resellers, and a reseller-provisioned MID typically routes statement delivery through the reseller's own portal — sometimes a custom dashboard, sometimes a monthly emailed PDF. The merchant never sees iQ. For these accounts, the PDF extraction job isn't an alternative to iQ; it's the only path.

---

The Worldpay PDF statement, page by page

Before walking the layout, a quick word on branding, because a merchant working from a Worldpay FIS statement may be staring at a header that says any of three things. Worldpay merged with Vantiv in 2018 and was acquired by FIS in 2019, and statement templates have rolled forward without forcing every account onto a single design. A merchant who opened an account during the Vantiv era may still receive a Vantiv-format statement years later; a merchant onboarded after the FIS acquisition typically sees an FIS-branded layout with the Worldpay product name; reseller-issued statements sometimes carry the reseller's branding over a pass-through Worldpay structure. The page-by-page anatomy below describes the FIS-era Worldpay layout, which is the most common shape today, and flags the points where older Vantiv pages diverge enough to matter for extraction.

The statement opens with a cover or summary page. This is the executive view: the legal merchant name and MID, the statement period, total volume processed for the month, total deposits net of fees and chargebacks, and a breakdown of fee totals by category — typically a few summary buckets such as interchange, assessments, processor fees, and other adjustments. Some statement layouts also surface a stated effective rate at the cover level, computed by Worldpay; treat it as a useful reference point rather than the audit number, since the categorisation we apply later is more conservative. In the destination spreadsheet, every cover page produces a single header-row record per (MID, statement month).

Next comes the per-month fee detail, which is where the larger share of practitioner attention belongs because it's where most negotiable fees actually live. This block lists transaction-fee charges (per-authorisation fees, per-settlement fees, batch fees), per-card-brand assessments at the summary level, and the recurring monthly fees that quietly stack up: PCI compliance fee, the much larger PCI Non-Compliance fee that triggers when the merchant hasn't completed an SAQ, monthly minimum processing fees, statement fees, network access fees, regulatory product fees, and any quarterly assessments that bill in this particular month. In the spreadsheet this section produces one row per fee line item, with columns for fee category, fee description, count, rate, amount, and the fee-layer flag we'll define in section six.

Third is the interchange detail page, often two or three pages of dense table content listing every card category processed during the month — Visa, Mastercard, Discover, and Amex broken out by reward tier, regulated and unregulated debit, corporate, commercial, and a long tail of niche categories. Thirty-plus rows per month is normal; for a busy merchant with mixed channels (card-present, e-commerce, keyed) the row count climbs higher. Each row carries a transaction count, a dollar volume, a percentage rate, and a per-item charge, and produces a corresponding row in the interchange detail sheet of the destination spreadsheet.

After interchange comes the assessments block. These are the card-network assessment fees treated separately from the interchange table — Visa Assessment, Mastercard Assessment, Discover Assessment, Amex's network fees, plus the small per-item network fees (NABU, APF, Visa Acquirer Processing Fee, Mastercard NABU and Cross-Border Assessment, Discover Data Usage Fee). They are pass-through and non-negotiable, but worth their own block in the spreadsheet because totalling them separately makes the interchange-versus-assessments split visible in a fee audit.

The adjustments and billback section is shorter on most statements but matters disproportionately. It lists downgrades — transactions that didn't qualify for the interchange rate originally booked and are being trued up to a higher category — billback adjustments for fees the network revised after the original month closed, and any one-off corrections. A given month's statement often shows adjustments that reference activity from one or two months earlier; the multi-month rollup discipline addresses this directly.

Finally the reserve and chargeback section closes the statement. Chargeback case fees, retrieval request fees, reserve adjustments, and any holdback on settled funds appear here. The columns differ from fee-line records (case identifiers, original transaction dates, reason codes), so this content lands in its own sheet rather than being mashed into the fee detail. For most merchants this section is short or empty in a clean month; for high-risk verticals it can dominate the statement.

Reading the interchange detail page

The interchange detail page is where a Worldpay statement actually earns its complexity. Every card category the merchant processed during the month appears as its own row, identified by an interchange program name (Visa CPS Retail, MC World Elite Consumer Credit, Discover PSL Rewards High, Amex OptBlue Tier 1, regulated debit categories, corporate and commercial card categories), followed by the volume processed at that category, the interchange rate as a percentage, the per-item charge in dollars and cents, and the resulting interchange amount. Thirty rows per month is normal; busy or omnichannel merchants regularly see fifty or more.

The categorisation is set by the card networks, not by Worldpay. Visa, Mastercard, Discover, and Amex each maintain published interchange tables that assign every transaction to a category based on card type (consumer credit, rewards, corporate, regulated debit), entry mode (card-present chip, card-present swipe, card-not-present, keyed), industry code, ticket size, and other variables. The reason a single statement shows so many categories is that a merchant's transaction mix touches many of those variables across a month — which is precisely the data point a fee-audit consultant cares about.

In the destination spreadsheet, the interchange detail page maps cleanly to a Worldpay interchange detail to spreadsheet view with seven columns: card brand, interchange category name, transaction count, dollar volume, interchange rate (percentage), per-item amount, and total interchange dollars for the row. One PDF row produces one spreadsheet row. The card brand column is what makes the dataset useful downstream, because filtering or pivoting by brand reveals where the money is actually flowing — most merchants discover that two or three card brands dominate their interchange total and the rest is a long tail.

The reading discipline that pays off is recognising which categories carry the highest rates. Premium rewards and corporate cards sit at the top of the interchange table — categories like Visa Signature Preferred, Mastercard World Elite, and corporate purchasing programs routinely run above 2.50% plus a per-item fee, sometimes well above. Standard consumer credit (CPS Retail, Core, Merit) sits in the middle. Regulated debit, capped by the Durbin amendment, sits at the bottom — typically 0.05% plus around 22 cents per transaction. A boutique retailer or hospitality merchant whose customer base skews toward premium rewards cards will see a materially higher interchange total than a grocery store on identical volume, and the spreadsheet is what makes that visible.

One extraction reality is worth naming directly: the interchange detail page is where naive PDF-to-Excel converters fail most visibly. The dense table layout, the embedded program-name abbreviations, the rate-format inconsistencies (some statement layouts show 1.65% plus $0.10 as a single column, others split percentage and per-item into separate columns), and the column-wrapping in narrow PDF table cells all defeat layout-only converters that lift the visual grid as text. Honest extraction reads each row semantically — recognising that a string like VS CPS RTL DB is a Visa CPS Retail Debit category, that the next two numbers are rate and per-item, and that the trailing dollar figure is the interchange amount — rather than guessing from grid coordinates. This is the single most common reason a generic PDF-to-Excel tool produces a Worldpay output the merchant immediately has to re-key.

---

A spreadsheet schema that earns its keep

The deliverable for the extraction job is a multi-sheet workbook with consistent join keys and column shapes that every other downstream task — fee audit, deposit reconciliation, GL coding, RFP packs — pivots off of. A single flat dump of all line items into one giant tab fails this test, because the column shape that makes sense for a fee-detail row makes no sense for a chargeback case or an interchange category. The Worldpay statement audit fees spreadsheet that earns its keep uses six sheets, each with a defined column set and a shared (MID, statement month) join key.

Statement summary sheet. One row per (MID, statement month). Columns: MID, statement month, total volume, total deposits, stated effective rate (when the cover page shows one), sum of interchange, sum of assessments, sum of markup, sum of total fees. This is the header record every other sheet joins back to, and the row count is small — twelve rows per MID per year — so it stays human-readable.

Fee detail sheet. One row per fee line item from the per-month fee detail page. Columns: MID, statement month, fee category (PCI compliance, PCI non-compliance, statement, batch, network access, regulatory product, monthly minimum, transaction fee, and so on), fee description as it appears on the statement, count, rate, amount, and a fee-layer flag (interchange, assessment, or markup). The fee-layer flag is the audit-prep column the next section's categorisation rule populates; without it, this sheet is a fee inventory rather than a fee-audit instrument.

Interchange detail sheet. One row per interchange category, derived from the interchange detail page walked in the previous section. Columns: MID, statement month, card brand, interchange category, transaction count, dollar volume, rate percentage, per-item amount, total interchange amount.

Assessments sheet. One row per network assessment line. Columns: MID, statement month, card brand, assessment type (e.g., Visa Assessment, NABU, Mastercard Cross-Border, Discover Data Usage Fee), count, rate, amount.

Adjustments sheet. One row per downgrade, billback, or adjustment. Columns: MID, statement month (the month the adjustment posts, which often differs from the month the original transaction occurred), adjustment type, original month referenced where the statement provides it, count, amount.

Chargebacks and reserve sheet. One row per chargeback case, retrieval request, or reserve adjustment. Columns: MID, statement month, case identifier, original transaction date, reason code, amount, reserve held.

The hidden-fee inventory is what makes the fee detail sheet load-bearing. The line items most likely to be removable through negotiation hide here, and they hide in plain sight, under the labels Worldpay actually prints on the statement. PCI Non-Compliance typically runs $19.95 to $79 per month and triggers when the merchant hasn't completed an SAQ; it's almost always removable by completing the questionnaire. Minimum Processing Fees in the $15 to $50 per month range bill the gap whenever processing volume falls below a contractual minimum. Quarterly PCI fees bill once every three months, often $99 to $129. Statement fees, batch fees, and network access fees are smaller line items but recurring. Regulatory product fees are sometimes legitimate pass-through and sometimes processor margin in disguise. Early Termination Fees rarely appear on a routine statement, but when they do they can run into the thousands and warrant their own conversation with the processor. Naming each by its statement label is what lets the merchant grep their PDFs (or the fee detail sheet) and find every instance.

For merchants without iQ access — the reseller-MID case is common — and for any merchant working from multiple months of dense PDFs, AI-powered merchant statement extraction is the path from a stack of monthly Worldpay PDFs to the categorised fee table the schema above describes. Invoice Data Extraction takes a batch of statement PDFs along with a natural-language prompt that names the schema you want — sheets, columns, fee-layer flag, hidden-fee labels — and produces a structured Excel or CSV output with every row carrying a back-reference to its source page in the original PDF. A prompt that maps cleanly to the schema in this section reads roughly like: "Extract Worldpay merchant statement fee detail. One row per fee line item. Columns: MID, Statement Month (YYYY-MM), Fee Category, Fee Description (as printed), Count, Rate, Amount, Fee Layer (classify as Interchange, Assessment, or Markup using the rule that any fee not clearly attributable to a published interchange or network assessment is Markup). Skip the cover summary page and the chargeback section — those go to separate sheets." The same prompt produces the same structured output across every MID and every month, which is what makes the multi-month rollup discipline mechanical rather than manual.

Interchange, assessments, and processor markup: the three-layer categorisation

Every fee on a Worldpay merchant statement belongs to one of three layers, and the audit value of the spreadsheet depends entirely on classifying every row correctly. The categorisation is the rule that turns a fee inventory into the data a merchant or consultant uses to analyze Worldpay merchant statement fees and decide what to negotiate.

Interchange is set by Visa, Mastercard, Discover, and Amex through their published interchange tables. The acquirer collects it from the merchant and pays it through to the card issuer. From Worldpay's perspective it is pass-through — money in, money out, no margin. From the merchant's perspective it is non-negotiable: no processor switch reduces a Visa CPS Retail rate, because Visa sets that rate. Interchange totals are driven entirely by the merchant's transaction mix (card type, entry mode, ticket size, industry code) and the network's tables, both of which sit outside the merchant-processor relationship.

Card-network assessments are also set by the networks and paid by the acquirer to the network itself rather than to the issuer. They cover the network's own infrastructure and brand fees. They are pass-through, non-negotiable, and significantly smaller than interchange in dollar terms — typically a few cents per transaction plus a small percentage of volume — but predictable and worth their own column in the spreadsheet for clarity.

Processor markup is everything Worldpay (or the ISO/MSP that resells Worldpay) sets and keeps. This is where the merchant's negotiating leverage lives. Markup shows up in a few different shapes: the discount-rate markup added on top of interchange (the plus in interchange-plus pricing, the qualified or non-qualified markup in tiered pricing), per-transaction processor fees beyond the network per-item, monthly fees, and the hidden-fee inventory named in the previous section — PCI non-compliance, minimum processing, statement, batch, network access, regulatory product fees. Markup is the only layer that responds to negotiation, processor competition, or removal through compliance steps such as completing an SAQ.

Why does the categorisation carry so much weight? Because interchange dominates the dollar total. GAO's 2025 study of federal payment card fees found that interchange fees accounted for nearly 90 percent of the payment card processing fees paid by more than 85 federal entities in FY 2023, on a base of about $784 million in total card fees. The federal-government dataset isn't identical to a small-business profile, but the structural finding is the same point fee-audit consultants make from their own samples: across the broad market, interchange is the bulk of what a merchant pays, and it's the bulk the merchant cannot move. The remaining slice — assessments and markup — is where the audit's attention earns its keep, and isolating the markup from the assessments inside that slice is the work that makes negotiation feasible.

Operationally, the rule lives in the fee-layer flag column on the fee detail sheet and the interchange detail sheet. Every row in the interchange detail sheet flags as interchange. Every row in the assessments sheet flags as assessment. Rows in the fee detail sheet require judgment, and the conservative rule is the right one: flag as assessment only when the fee is clearly a published network charge (Visa Assessment, Mastercard NABU, Discover Data Usage Fee, Amex network fees, the recognised acquirer-processing fees); flag everything else as markup. Some line items are genuinely ambiguous — a regulatory product fee can be a real pass-through to a card network's regulatory program or processor margin in regulatory costume. Treat ambiguous items as markup until the processor produces evidence they're pass-through, because the merchant's negotiating position is stronger when the assumption defaults that way and easily corrected when documentation arrives.

Once every row carries a layer flag, a single pivot table over the fee detail and interchange detail sheets gives the merchant their three-layer breakdown for the month: total interchange, total assessments, total markup. Sum across three or twelve months and the markup number — the negotiable portion — is the data the merchant takes into a processor conversation or hands to a consultant.

---

The multi-month rollup discipline

A single Worldpay statement is a snapshot, not a fee profile. Several categories of fees only appear in one of three months, and any analysis built on a single month's extraction misses them. The discipline is to extract a minimum of three consecutive monthly statements per MID before drawing fee-audit conclusions. Six months strengthens the picture; twelve months is what a serious processor-comparison RFP or a year-end fee review wants. Three is the floor.

The fees that hide in single-month extraction fall into a few patterns. Quarterly PCI fees bill once every three months, so they're absent from two of three statements; a January-only extraction misses them entirely if the quarterly cycle hits February. Billback adjustments post in the month the network finalises a downgrade, which is typically one or two months after the original transaction occurred — December's downgrades often appear on the February statement. Downgrade fees follow the same retrospective pattern. Annual or semi-annual fees are rarer but real: some regulatory product fees and compliance assessments bill once a year, and a single-month sample has a roughly 1-in-12 chance of catching them. One-off adjustments include refunds of misapplied fees, card-brand pass-throughs that net out across months, and retrieval requests resolved late.

For franchise and multi-location operators the pattern compounds. Several MIDs each produce their own monthly statement, and the same three-month minimum applies per MID. The consolidation step — joining MID-level rollups into one operator-wide spreadsheet that lets the parent compare locations on the same fee categories — is its own task, and we cover the practitioner mechanics of how to aggregate merchant statements across franchise locations in a sibling walkthrough.

The reason the schema in the previous section carried (MID, statement month) as the join key on every sheet is the multi-month rollup. Without those keys, stitching three months of fee detail into one pivot is a manual paste job that breaks at the second statement. With them, a pivot table over fee category and fee layer, summarised across N months and M MIDs, produces the operator-wide fee profile in seconds. The schema does the work; the rollup is what the schema was designed for.

---

Downstream uses of the categorised spreadsheet

Once the multi-sheet workbook exists with three or more months of categorised data, several practitioner tasks fall out of it directly.

Effective rate calculation. Sum total fees across all three layers and divide by total volume for the headline effective rate as a percentage. The categorisation makes a more honest second number available: markup divided by volume, the markup-only rate, which is what processor-comparison conversations should actually focus on. A merchant whose headline effective rate is 2.85% and whose markup-only rate is 0.65% has a meaningfully different negotiating position from one whose headline is 2.85% but whose markup-only rate is 1.40%. The same categorised data drops into a fee-audit consultancy engagement or a competing processor's RFP — both want volume profile by card type and current fees by layer, which the spreadsheet already produces.

Bank deposit reconciliation. The summary sheet's total deposits column reconciles against the merchant's bank statement at month-end. Variances usually point to one of three things: chargebacks that posted between batch settlement and bank credit, holdback or reserve adjustments that withheld a portion of settled funds, or timing differences where a late-month batch settled into the following bank-statement period. The mechanics of running this reconciliation cleanly across statement and bank are walked in the sibling guide on how to reconcile card processor deposits to your bank at month-end, which builds on the same summary-sheet structure used here.

QuickBooks GL coding by fee category. The fee detail sheet's category column maps to the merchant's chart of accounts — bank charges, merchant service fees, regulatory compliance, depending on the firm's coding policy. A bookkeeper who needs to import Worldpay statement into QuickBooks no longer enters each fee line manually; they tag the fee detail rows with GL codes and import the categorised rows in one pass, with the source-row references in the spreadsheet pointing back to the page in the original PDF for any audit trail need.

1099-K reconciliation. Each January, Worldpay issues a 1099-K reporting the merchant's gross card receipts for the prior year. The merchant's books need to reconcile against that figure, and discrepancies are common — refunds netted differently, returns recorded in different periods, multiple MIDs aggregated against a single tax ID. The summary sheet's total volume column rolled across twelve months produces the merchant-side number that meets the 1099-K side, and the sibling walkthrough on how to reconcile your 1099-K gross totals to your bookkeeping addresses the recurring patterns where the two sides diverge.

Period-over-period reconciliation. With consistent column shapes month over month, the Worldpay statement reconciliation Excel work comes down to comparing one month against another — March's fees against February's by category — to spot fee creep, new line items the processor has quietly added, or shifts in the interchange downgrade rate that signal a transaction-mix change worth investigating. The categorised structure makes this scannable rather than painstaking.