Level 3 Data in Business Central: The Key to Cutting B2B Card Fees

Level 3 Data in Business Central: The Key to Cutting B2B Card Fees

Ask a CFO at a B2B or GovCon firm what drives their credit card processing costs, and most will point to the rate they negotiated with their processor. That number sits right there on the statement, easy to spot and easy to argue over. The number doing more damage sits somewhere else entirely: inside the ERP, in a data field most finance teams have never had a reason to examine closely.

This spring gave that data field new weight. Visa retired its legacy Level 2 interchange program for corporate and purchasing cards, folding it into a stricter data-validation framework that rewards complete, invoice-quality detail and penalizes anything partial, according to PYMNTS's coverage of the phaseout. Firms that treated Level 3 as optional, or assumed their processor handled it automatically, are finding out this year whether that assumption held up.

What Level 3 Data Processing Actually Means

Level 3 is the most detailed tier of transaction data that Visa and Mastercard accept for commercial and purchasing card payments. Level 1 covers the basics: card number, amount, merchant name. Level 2 adds tax amount and a customer or purchase order code. Level 3 goes further still, capturing line-item detail that mirrors the invoice itself: product or service codes, quantities, unit price, freight, and line-level totals.

The card networks reward this extra detail because it lowers their risk. According to Mastercard, interchange rates are a core component of the fee merchants pay for card acceptance, and the networks structure those rates to reflect how much verified detail travels with a transaction. A transaction that arrives with full line-item context is easier to reconcile and audit than one that shows up as a lump sum, and that lower risk translates into a lower rate for the merchant.

For a company processing a modest volume of commercial card payments, that difference might not register. For a wholesale distributor invoicing multiple SKUs on a single purchase order, a professional services firm billing by project code, or a government contractor moving high volume through purchasing cards, the gap between a qualified and a downgraded rate compounds into real money over a year of card volume.

Why B2B and GovCon Firms Are Exposed to This More Than Most

Consumer-facing businesses have little reason to think about Level 3 because their customers pay with personal credit cards, which do not qualify for the program regardless of the data submitted. B2B and GovCon sellers are different. Their customers pay with corporate cards, purchasing cards, and GSA SmartPay cards, all of which are eligible for the lowest tier of rates if the seller can supply the required fields.

That eligibility is also where things go wrong. A downgrade happens whenever a transaction misses the required threshold, and the card networks default it into a more expensive category. Common triggers include a missing product description, a quantity or unit price that does not match the invoice, an absent or incorrect commodity code, or a tax-exempt flag that fails to pass through cleanly. None of these are dramatic errors. They are the kind of small gaps that show up constantly when line-item data has to move manually from an invoice into a payment terminal or gateway, whether the buyer is a federal agency or a commercial account.

Contractors selling through SEWP, DoD ESI, or GSA schedules feel this acutely because federal purchasing card rules apply to every transaction regardless of contract size. Our companion piece on how missing Level 3 fields trigger downgrades for GovCon contractors goes deeper on those specific programs. The same exposure shows up on the commercial side too: a distributor running a multi-line equipment order or a services firm invoicing a retainer with several billing codes hits the same wall if the ERP and the payment step do not share data cleanly.

Where the Invoice Data Actually Lives

The core problem is structural, not procedural. Level 3 requires product codes, quantities, and line-item totals that already exist on the invoice sitting inside the ERP. Most payment setups sit outside that system, which means someone has to re-key that same data into a separate gateway or terminal by hand. Every re-entry point is a chance for a mismatch, and mismatches are what trigger downgrades.

This is precisely where Business Central changes the equation. Microsoft's own documentation on enabling customer payments describes how payment services in Business Central are built as extensions that plug directly into sales documents, rather than as bolt-on tools that require a separate system of record. When payment processing runs natively inside Business Central, line-item detail can travel with the invoice automatically instead of being re-typed into a second interface. Product descriptions, quantities, unit costs, tax treatment, and commodity codes stay attached to the transaction because they were never separated from it in the first place.

For a company running Level 3 through Business Central natively, the practical benefit is straightforward: fewer downgrade triggers, because there is no re-entry point where a description gets dropped or a quantity gets fat-fingered. For a GovCon seller, it also means tax-exempt status and commodity coding are captured correctly for every purchasing-card sale, which matters as much for audit exposure as it does for the rate itself.

What Finance Leaders Should Actually Check

Most finance teams have never audited their Level 3 qualification rate, largely because their processor statement does not make it visible in any obvious way. A useful starting exercise is pulling a sample of recent commercial card transactions and asking the processor directly what percentage qualified at the top tier versus a downgraded one.

It is also worth asking a more basic question: does the current payment setup pull line-item data from the ERP automatically, or does someone need to enter it separately for every transaction? Under the newer validation rules, card networks can also revisit a merchant's status monthly and move it between verified and non-verified based on data quality, which means qualification is no longer a one-time setup task. Every busy month, every staffing gap, and every new hire on the AR team is now a fresh opportunity for downgrades to creep back in. This is the same question we raised in Rethinking Payments as a CFO in 2026, and it remains one of the more revealing questions a finance leader can ask their processor directly.

Where This Heads Next

With the legacy Level 2 pathway now gone for corporate and purchasing cards, the margin for treating enhanced data as optional has narrowed further. Firms that already run Level 3 natively inside their ERP absorbed that shift without much disruption. Firms still relying on manual entry, or on a processor that never flagged the change, are more likely to see their effective rates climb without an obvious explanation on the statement.

For B2B and GovCon finance teams evaluating their Business Central payment setup, the most useful next step is usually a direct conversation about what percentage of transactions currently qualify at the top tier and what would need to change to close that gap. Some teams find that gap smaller than expected once they see real numbers from merchants who have already closed it.