Heartland Merchant Statement to Excel: Extraction Guide

Heartland merchant statements download from the Heartland InfoCentral merchant portal as PDFs, and the structurally distinctive section inside each one is the Fee Summary, where every transaction fee is listed and broken out by card brand: Visa, Mastercard, Discover, and American Express. If you have a stack of monthly InfoCentral PDFs and need the Fee Summary out as structured data, this article is the workflow.

Extracting a Heartland merchant statement to Excel produces one row per fee-line per card-brand per statement. With the data in that shape, the merchant or their bookkeeper can sort by category, sum across months, and reconcile fees against bank deposits. The same schema serves three jobs that operators on Heartland keep running into: monthly fee review, multi-location rollup across MIDs, and fee audit ahead of a processor RFP or a switch decision.

The anatomy of a Heartland merchant statement

The cover summary on page one is the single-number view: total deposits, total sales volume, total fees, and on some Heartland statement formats an effective-rate figure printed alongside. The cover answers "what did this month cost me as one number." Everything below it is where the detail that supports the number actually sits, and where the spreadsheet schema later in this article does its work.

The Fee Summary is the structurally distinctive part of a Heartland statement and the section operators come back to most often. It is laid out as a per-card-brand block: a Visa block, a Mastercard block, a Discover block, and (for merchants on AmEx OptBlue) an American Express block. Each block contains rows for the discount rate Heartland charges, the dues and assessments owed to the card networks, the processor markup component where applicable, and per-item counts. Each row carries both a dollar amount and a transaction count, which is what makes the section auditable: every fee can be traced back to the volume it was computed against.

The Interchange Detail section sits alongside the Fee Summary and breaks interchange down by card type rather than by brand. Interchange is a pass-through cost set by the card networks (Visa, Mastercard, Discover, Amex), not by Heartland, and the statement reports it in named card-type categories — CPS/Retail credit, regulated debit, corporate, the various rewards tiers — each with its own rate and its own per-item count. Those rates and counts feed back into the Fee Summary totals; the Interchange Detail is the supporting line-by-line.

Adjustments, late-fee assessments, billback adjustments, downgrade adjustments, and refunds appear in their own section when they apply. They show up irregularly, only in the months they're triggered, which is one of the reasons a single-month view of a Heartland statement can be misleading. Chargebacks and retrievals are reported separately, with the per-chargeback fee and retrieval-request fee appearing as their own line items.

Merchants whose American Express acceptance runs on AmEx Direct (the OnePoint program) rather than OptBlue receive AmEx fees on a separate Amex-issued statement with its own structure rather than on the Heartland statement. The same row-grain discipline applies on the AmEx side, where the extracting an American Express statement to Excel workflow takes over.

The spreadsheet schema for a Heartland statement

The row grain that makes a Heartland statement analyzable is one row per fee-line per card-brand per statement period. That choice matters: it preserves every dimension the operator might want to slice on later — period, MID, location, card brand, fee category — rather than rolling anything up at extract time. Once the data is at that grain, sums across months are mechanical, comparisons across MIDs are mechanical, and joins to bank-deposit data are mechanical.

The columns to build into the sheet:

• Statement period — month and year, formatted consistently so it sorts.
• MID — the merchant identifier printed on the statement.
• Location — a human-readable label for the MID; non-essential for single-MID merchants, load-bearing for multi-location operators.
• Card brand — Visa, Mastercard, Discover, Amex (where on OptBlue), or "all" for fees that aren't card-brand-specific (account-level fees, gateway, equipment).
• Fee category — discount, dues and assessments, processor markup, monthly access, gateway, equipment, PCI, adjustment, chargeback, interchange. The closed set of values is what makes pivots clean later.
• Fee name as printed — the verbatim string from the statement. This is the auditability column: every row can be traced back to the source line by name.
• Transaction count — the per-item count from the statement, where applicable.
• Base amount — the volume the fee was computed against, where the line carries one. Some fees (monthly access, annual reporting) have no base amount; leave blank.
• Fee amount — the dollar amount on the statement line.
• Effective rate — computed, not extracted. Fee amount divided by base amount, where both are present.

Doing this by hand for one statement is tractable — an hour or two for a small merchant. Doing it for six monthly Heartland PDFs across three MIDs is a different exercise. Line counts vary by card brand, by adjustment type, and by month; per-item counts and rates have to be keyed accurately or the effective-rate column is meaningless; and the resulting spreadsheet usually needs a second pass before it can be trusted to defend a fee number to a CFO or a competing processor. The error rate on hand-keyed rates and counts compounds quickly across a stack of PDFs.

The leverage point is at extraction. With a structured-extraction tool you can extract Heartland merchant statements automatically into the schema above in one pass — the per-card-brand discount and dues-and-assessments lines, the interchange detail, the adjustments, and the chargeback rows arrive as fee-line-level rows ready to drop into the spreadsheet, with the source file and page number preserved on each row so it can be checked back against the original PDF. The job becomes loading the file rather than rekeying it, which is the difference between a workflow you'll actually run every month and one that gets deferred until a switch decision forces it.

The same extraction pattern works across a portfolio of Heartland locations: the file count changes, but the row grain stays one fee line per card brand per statement. Franchise operators can use the franchise-wide merchant fee aggregation playbook for the dedicated-MID and per-location rollup details.

The Heartland fee inventory worth cataloging

The Heartland-specific fees that surface across a year of statements live in a handful of categories. The list below names them as they tend to appear, with notes on cadence so the audit-fees spreadsheet does not miss lines that appear only in some months.

• Account-level monthly fees. Customer Intelligence Suite Fee, monthly access fee, statement fee. Per statement, regardless of volume.
• Annual fees. Annual Reporting Fee. Appears once a year per location, on whichever statement carries the bill — a key reason single-month views miss real cost.
• Gateway fees. Heartland Mobile and Heartland Restaurant gateway access charges, where the merchant uses the corresponding product. Per statement, per gateway, where applicable.
• Equipment line items. Terminal lease or equipment rental charges, where the merchant has Heartland-supplied hardware. Per statement, per device, where applicable.
• PCI compliance. Quarterly PCI fee, with a separate non-compliance fee when the merchant is out of attestation. Quarterly cadence.
• Per-transaction fees. Discount rate (the processor markup component, expressed as a percentage of volume), authorization fees, and downgrade or billback adjustments when transactions clear at a tier above their qualified rate.
• Chargeback fees. Per-chargeback fee, retrieval-request fee. Triggered by dispute events, not periodic.
• Pass-through. Interchange (set by the card networks, not by Heartland) and dues and assessments (also set by the card networks). These are the largest lines on most Heartland statements and they are not Heartland's margin.

The distinction between a Heartland charge, a card-network pass-through cost, and a hybrid is worth drawing explicitly. The discount rate is Heartland's; dues and assessments belong to the networks; interchange belongs to the issuing banks via the network rate tables. On most Heartland statements interchange is the largest single cost component, which means a fee audit that focuses on the discount rate alone is auditing the smaller half of the bill.

Interchange itself is shaped by regulation as well as by network rate tables. Under the Regulation II interchange fee standards issued by the Federal Reserve Board, an issuer subject to the interchange fee standard may not receive an interchange fee that exceeds $0.21 plus 0.05 percent of the transaction value, plus a $0.01 fraud-prevention adjustment if eligible. That cap applies to debit transactions on covered issuers and is the reason debit interchange on a Heartland statement looks different from credit interchange — the same statement format reports both, but the underlying economics are not the same.

Why a single month understates real cost

Several material Heartland fees only show up in some months. Quarterly PCI fees appear once a quarter. The Annual Reporting Fee appears once a year per location. Billback and downgrade adjustments arrive whenever transactions clear above their qualified tier. Refunds and chargeback adjustments depend on the dispute and refund events that triggered them. None of these are exotic; all of them are predictable across the year, and none of them are visible from a single statement.

The consequence is that a single-month effective-rate calculation will systematically understate the cost of acceptance. A merchant who divides one month's fees by one month's volume gets a number that is lower than the year-rounded figure — sometimes by several tenths of a percentage point on a smaller-volume merchant, where the fixed quarterly and annual line items represent a meaningful share of total cost. That difference is the gap that turns up when a competing processor's quote looks better than the actual side-by-side warrants.

For an honest fee picture, six months is the practical minimum. Six months catches at least one quarterly PCI cycle, most of the billback patterns, and enough monthly variation to reveal the noise floor. For a processor RFP or a serious renegotiation conversation, twelve months is the right horizon — it captures the Annual Reporting Fee, smooths seasonal volume distortions, and produces a dataset a competing processor cannot easily dismiss as cherry-picked. A Heartland statement reconciliation in Excel built on twelve months of structured rows is the dataset most fee conversations and most processor-to-bank reconciliations should start from, because period-over-period checks and category-over-category checks both need the row grain present across months.

Once the schema is populated, the audit workbook needs four pivots: fees by statement period, fee mix by category, cost by card brand, and MID/location totals for site-level allocation.

Seasonality and batch behavior are the other reasons the horizon matters. Restaurant volume tracks the local season and weekend pattern, and tips flow through the batch, so Heartland statement volume and POS food-and-beverage revenue will not match without explicit tip reconciliation. The mechanics of tying daily POS settlement to bank deposits across Toast, Clover, and Square apply in the same shape because the timing issue belongs to card settlement, not only to those POS brands. A six-or-twelve-month rollup absorbs the seasonal variation; a single month picks an arbitrary point on the curve and treats it as representative.

The rollup discipline isn't an Excel exercise. It is what makes a fee analysis defensible to a CFO, to a competing processor in an RFP response, or to a Heartland representative in a renegotiation.

What to do with the data once it is in Excel

Once the row-grain schema is populated and rolled up across the chosen horizon, four downstream uses follow directly. Most operators come to the extraction work because they need at least one of them; the schema serves all four without rework.

Effective-rate calculation. Total fees divided by total volume across the rollup horizon gives the merchant's true effective rate. The cover-page effective-rate figure on a single statement misses the quarterly PCI cycle and the annual reporting fee, so it is systematically lower than the multi-month figure. The honest number is the one a CFO or a competing processor will challenge, which is why it should be computed off the rollup rather than copied off the cover page; the step-by-step mechanics of calculating the effective processing rate from merchant statements belong in the analysis workbook built from those rows.

Bank-deposit reconciliation. The Heartland statement reports gross sales, total fees, and net deposits per period; the bank account shows the deposits as they actually arrived. Reconciling the two ties the processor settlement to the GL and is where most discrepancies surface — timing differences across month-end, holdback adjustments, chargeback offsets applied against gross, refunds netted on the deposit rather than itemized. The mechanics of tying merchant card deposits to the bank at month-end — the gross-vs-net walk, settlement-timing carve-outs, and a variance decision tree for multi-processor splits — are worked through end to end in their own piece. The broader workflow of reconciling the bank statement to the GL covers the bank-side discipline that complements the processor-side rollup.

GL coding and accounting integration. Once each fee row carries a fee category, the spreadsheet maps cleanly onto a chart of accounts. Discount and interchange typically post to a cost-of-payments line. Gateway and equipment fees post to their own GL lines (often technology or operating expense, depending on the merchant's chart). PCI and chargeback fees post to compliance and dispute categories. The cleanest way to import a Heartland statement into QuickBooks is to roll the schema up to a journal entry per fee category per statement period and post that — the line-by-line statement detail bloats the GL with rows that are interesting only for audit-trail purposes, and those can stay in the source spreadsheet indexed by statement period and source page. The same shape works for Xero, Sage, NetSuite, and any other GL that ingests journal entries: one credit to the bank settlement clearing account, one debit per fee-category GL line per period.

Processor-comparison RFP packs. A six-to-twelve-month rollup of the schema is the dataset competing processors quote against in an RFP. Hand a competing processor a clean spreadsheet rather than a stack of PDFs and the response comes back faster, more accurately matched, and harder for either side to dispute later. The same row-grain discipline applies to the incumbent quote on the other side of the comparison — pulling a Worldpay (FIS) merchant statement into the same fee-audit schema lets the two processors be compared line for line rather than headline rate to headline rate. The same dataset supports the broader work of payment reconciliation across processor and bank, which is where the RFP-time analysis lives in the operator's normal monthly close once the new processor is selected.

Once the data is in Excel, the next move is whichever of the four uses the operator opened the file to do.