LedgerBox

Convert merchant statements to Excel or CSV

Upload the processing statement your payment processor sends each month and download a clean spreadsheet: every fee line as printed, sorted into four categories, and the effective rate the statement never states.

13
Summary fields, verified
±$0.01
Fee total check tolerance
4
Fee categories, rules based

What comes back · sample

Schema vv1

Processor
fiserv
Processor as printed
Fiserv Merchant Services
Period start
Apr 01, 2026
Period end
Apr 30, 2026
Gross card volume
$184,206.55
Transaction count
2,914
Total fees
$4,512.88
Effective rate
2.45%
Interchange
$3,140.22
Assessments
$255.44
Processor markup
$798.22
Other fees
$319.00
Fee taxonomy version
2026-08.1

Fee lines = printed total

Rows CSV · Summary CSV

Field names are the LedgerBox extraction schema for merchant statements, version v1. Sample values are illustrative.

How to convert a merchant statement

  1. Upload the statement

    The monthly processing statement as your processor sends it, digital or scanned. Interchange-plus statements that run to a dozen pages read as one document, and a single drop takes up to 20 files.

  2. We read every fee line

    Processor, period, gross volume, and transaction count from the header. Each printed fee line in its own row with the amount as printed. Those rows must add up to the statement's own fee total, or the document is flagged.

  3. Download the fee CSV

    One row per fee line and per card-brand volume, plus a summary row carrying the four category totals and the effective rate. Ready for Excel or Google Sheets.

Merchant statement anatomy

A sample interchange-plus processing statement, and how LedgerBox reads each part before anything is computed from it.

The period is the denominator

Gross volume, transaction count, and every fee belong to one billing period, and a rate only means something when all three come from the same one. Both period dates are extracted as their own fields rather than inferred from the fee rows.

Every printed line stays a line

An interchange table can run to a hundred rows across several pages. Each one lands as its own row with the description exactly as printed. Nothing is summed, merged, or rounded on the way in.

The printed total is the check

The statement prints its own total fees, and the extracted fee lines have to add up to it within a cent. A statement that does not reconcile comes back flagged, which is how a misread page or a missing table announces itself.

Four categories, from a versioned table

Each fee line is sorted into interchange, assessments, processor markup, or other fees by a rules table, not by the model. Interchange and assessments are pass-through costs; markup and the monthly items are the part a merchant can negotiate. The table carries a version, and the version is written onto the document, so a reclassification later is identifiable rather than silent.

Merchant statement conversion FAQ

How do I convert a merchant statement PDF to Excel or CSV?

Create a free LedgerBox account, upload the statement, and download the CSV. The free trial covers your first statement with no credit card, and sharing LedgerBox with a colleague opens enough pages for a year of them.

Which processors are supported?

Square, Stripe, Clover, Toast, and Fiserv are the named ones, and any other processor's statement converts too, keeping the processor name exactly as printed. LedgerBox reads the statement rather than matching a processor template.

What is my effective rate?

Total fees divided by gross card volume for the period, the one number a processing statement does not print. LedgerBox computes it in the code from the extracted totals, never in the model, and only after the fee lines have been checked against the statement's printed total.

How are the fee categories decided?

By a versioned rules table matching the printed description: interchange, assessments, processor markup, or other fees. The rules are written against real statement descriptions, the version is recorded on every document, and a description no rule covers is marked as such rather than guessed silently.

What if the fee lines do not add up?

The document comes back flagged with the difference rather than exported as clean. That check is the whole accuracy story for this type: a page that failed to read, a table that continued somewhere unexpected, or a fee line missed all surface the same way.

Is my statement data secure?

Documents are encrypted in transit and at rest, processed in isolated storage, and never used to train models. You can delete uploaded documents at any time and they are permanently removed.

Just want the number without an account? Check your effective rate free

Ready to convert your merchant statements?

Upload a statement and download every fee line in under a minute. No card required.

Get started free