If a client accepts cards from other businesses, sooner or later someone will mention Level 2 and Level 3 data. It usually comes up as a vague promise: pass along a few extra fields with each transaction and the card fees go down. That promise is partly true, but it only holds under the right conditions. This cheat sheet explains what these terms mean in plain language, what a bookkeeper should look for, and where the savings realistically come from.
For a deeper look at the fee side of this topic, see our existing guide on Level 2 and Level 3 processing data and B2B fees. This post is the quick-reference version for the person reconciling the books.
The Short Version
Every card transaction carries a basic set of information: the amount, the card number, the merchant, and the date. That basic set is often called Level 1 data. Level 2 and Level 3 add more detail about what was purchased and who bought it. In exchange, certain commercial and purchasing card transactions can qualify for different interchange rates than they would with basic data alone.
- Level 1: the standard information every card transaction includes.
- Level 2: adds business-oriented fields, such as sales tax amount and a customer reference or purchase order number.
- Level 3: adds line-item detail, such as product descriptions, quantities, unit prices, and shipping information.
Why Card Networks Care About This Data
Commercial and purchasing cards are used by businesses to buy from other businesses. The people who manage those cards, usually an accounts payable team, need to match each charge to an internal record. Extra transaction data makes that matching easier. Card networks created Level 2 and Level 3 programs partly to encourage merchants to supply it, and they typically reward qualifying transactions with different interchange treatment. The exact categories and rates are set by the networks and change over time, so any specific number should be confirmed with the processor rather than assumed.
Level 2 in Plain Language
Level 2 is the lighter lift. In most cases it means including the sales tax amount and a reference number, such as a purchase order or customer code, with the transaction. For a business that already tracks sales tax and issues invoices with reference numbers, the information usually exists already. The question is whether the payment system sends it along with the card transaction instead of leaving it on the invoice.
Level 3 in Plain Language
Level 3 is the heavier lift. It requires line-item detail for each transaction: what was sold, how many, at what price, and often shipping and discount information. This is easier for businesses that sell physical goods with clear product records, and harder for service businesses that bill in less structured ways. Level 3 also tends to be where the more significant interchange differences appear, but only for eligible card types and transaction sizes, and only when the processor supports submitting the data.
Which Clients Are Realistic Candidates
Not every client benefits. A client is a stronger candidate when most of the following are true:
- A meaningful share of customers are businesses, not consumers.
- Customers often pay with corporate, purchasing, or fleet cards.
- Invoice or transaction amounts are larger than a typical retail purchase.
- The business already records tax, reference numbers, and line items in its invoicing or point-of-sale system.
- The processor and gateway can actually pass Level 2 or Level 3 fields.
A client who mostly serves consumers, or who takes payment mostly by ACH or check, is unlikely to see much change. For that group, the comparison in our post on ACH vs. card payments for B2B invoices is usually the more useful place to start.
The Pricing Model Caveat
Here is the point that gets missed most often. Extra data can lower the underlying interchange cost, but whether that saving reaches the client depends on how the processor prices the account. Under interchange-plus pricing, interchange differences generally pass through to the merchant. Under a flat-rate or tiered model, the processor may simply keep the difference, and the client pays the same rate either way. We cover this in more detail in our comparison of interchange-plus vs. flat-rate pricing, and the way tiered accounts classify transactions is explained in our post on qualified, mid-qualified, and non-qualified rates.
What You Can See From the Bookkeeping Side
A bookkeeper rarely sees the data fields themselves, but there are clues in the statement and in the books:
- The statement breaks out commercial or purchasing card transactions separately from consumer cards.
- Some transactions show different interchange categories than others for similar amounts.
- Processing fees as a percentage of volume are noticeably different for B2B sales than for consumer sales.
- The client's invoicing system already stores purchase order numbers and tax amounts, but the processor's reports do not reflect them.
If you are unsure how to read these sections, our guide to reading a merchant processing statement walks through the layout.
Questions to Ask the Processor
- Does our gateway or software support Level 2 and Level 3 fields, and is it turned on for this account?
- Which fields are required, and does our current invoicing system already capture them?
- Is the account priced so that interchange differences pass through to us, or are they absorbed?
- Are there extra fees or setup requirements to submit the additional data?
- Can you show how a sample commercial card transaction was classified before and after the data was added?
Common Mistakes
The first mistake is assuming the data is being sent because the software offers the option. Many systems have the feature but leave it off by default. The second is sending incomplete data. Level 3 transactions with missing or inconsistent line items can fail to qualify, which leaves the client doing extra work for no benefit. The third is promising savings before reviewing the client's actual card mix. If very few transactions are on commercial cards, the potential saving is small no matter how well the data is submitted.
A Simple Way to Frame It for a Client
Most clients do not need the technical detail. A short explanation usually works: when business customers pay by card, sending a little more information about the purchase can sometimes lower the fee, but only if the processor supports it and the account is priced to pass the saving along. Then suggest a quick review of the last few statements to see how much of the volume comes from commercial cards. That keeps your role where it belongs, noticing the pattern and pointing the client to someone who can evaluate it.
A Short Checklist
- Confirm what share of the client's card volume is from business customers.
- Check whether the statement separates commercial card activity.
- Ask which pricing model the account uses.
- Confirm whether Level 2 or Level 3 submission is enabled and complete.
- Revisit the statement after a couple of months to see whether fees changed.
Bringing It Together
Level 2 and Level 3 data are tools, not guarantees. They can reduce the interchange cost on eligible business card transactions, but the client only benefits if the data is actually submitted, the cards qualify, and the pricing model passes the difference through. For a bookkeeper, the practical job is to spot clients with a meaningful share of B2B card volume, ask the right questions, and make sure the savings, if any, show up on the statement rather than staying with the processor.
A Worked Illustration
Consider a client that sells equipment supplies to local contractors and facilities teams. Roughly a third of its card sales come from corporate and purchasing cards, with invoices averaging a few thousand dollars. The client's invoicing software already records tax amounts, purchase order numbers, and itemized products, but the card gateway sends only the basic fields. On interchange-plus pricing, enabling Level 2 and Level 3 submission could change how those commercial transactions are classified, and the lower interchange cost would flow through to the client. On a flat-rate account, the same change might have no visible effect on the client's bill. The data work is identical in both cases. The result depends entirely on how the account is priced.
This is why the first step is always a statement review rather than a software change. Looking at the card mix and the pricing model tells you quickly whether the topic is worth raising with a given client at all.
Keeping Expectations Realistic
Savings from Level 2 and Level 3 data are usually modest in percentage terms, and they apply only to eligible transactions. For a client with high B2B card volume, a small percentage difference can still add up to a meaningful annual amount. For a client with low volume, the effort may not justify the change. Present it as something worth checking, not as a guaranteed fix, and encourage the client to confirm the details with their processor before making any changes to their invoicing workflow.
Where This Fits in a Regular Review
This topic fits naturally into a periodic review of a client's payment costs. When you check the effective rate, the pricing model, and the fee line items each quarter, add one more question: what share of volume comes from commercial cards, and is the account set up to benefit from richer transaction data? Asking it routinely takes a minute and surfaces opportunities that would otherwise stay invisible in the monthly close.
Ready to simplify how you get paid?
Connect payments, invoicing, accounting, and field operations with PayLync.
