Concur is SAP's travel, expense and invoice management cloud. The licensing surface runs across Expense, Travel, Invoice and the supporting Concur Service Administration. The principal commercial mechanics are per-user, per-report and a hybrid transaction-based model. The buyer's position depends on the deployment shape.
Concur sells under three principal commercial mechanics, depending on the buyer's deployment shape. First, Standard Edition, a small-business tier with bundled per-user pricing and limited customisation. Second, Professional Edition, the mid-market and enterprise tier with per-user subscription, additional configuration options and integration with SAP and third-party financial systems. Third, the high-volume transaction-based model, used by very large buyers and named users with specific transaction-volume profiles.
The buyer-side decision between the three mechanics is rarely free; Concur's published commercial structure tends to land each buyer on a specific tier based on company size and configuration complexity. The procurement question is whether the published tier is the right tier for the buyer's actual usage profile, and what the negotiation room is at signing and at renewal.
The full reading on the SAP application catalogue sits in the SAP pillar, with parallel application reads in Ariba and procurement licensing and Fieldglass contingent workforce.
The per-user subscription licenses the named user population that submits expense reports or travel itineraries through Concur. The per-report model bills against the count of submitted reports, regardless of which named users submit them. The two models can converge or diverge materially depending on the buyer's report-frequency profile.
A buyer with a large user population that submits expense reports rarely (a typical position for buyers with field-based or sales-team-heavy workforces) reads better against the per-report model. A buyer with a smaller user population that submits frequent reports reads better against the per-user subscription. The Admodum methodology audits the buyer's actual report-frequency distribution against the two commercial structures and recommends the model that prices the actual usage at the lowest defensible rate.
Where the buyer is on the wrong model, the renewal is the moment to migrate. The migration negotiation runs against the validated usage data, not against the publisher's marketing literature.
Concur Travel licenses the travel-booking population separately from the Expense population. The two surfaces are technically integrated, but the licences are distinct; a buyer running both modules has two subscription line items.
The Travel module additionally reads against the buyer's travel-management company relationship (typically with a major TMC such as American Express Global Business Travel, BCD Travel or CWT). The TMC integration may carry additional transaction-based fees that read alongside the Concur subscription. The full commercial picture spans both Concur and the TMC, and the procurement runs the renewal against the consolidated number.
Where the buyer's travel volume is low or seasonal, a partial deployment (Expense only, or Expense plus light-Travel configuration) may price more defensibly than the full Travel module.
Concur Invoice licenses the accounts-payable team that processes supplier invoices through Concur. The module overlaps in commercial position with Ariba Invoicing, with the SAP S/4HANA AP capability and with third-party AP-automation tools (Tipalti, Stampli, AvidXchange).
The buyer's procurement question is which AP automation surface is the right surface for the workflow. Where SAP S/4HANA is the financial system of record and Ariba is the source-to-pay surface, Concur Invoice reads as a third overlapping capability that may not be commercially justified. The deduplication question is the renewal-cycle work.
Where the buyer is replacing a legacy AP solution and the wider SAP estate is light, Concur Invoice may be the right entry point. The decision runs against the wider SAP renewal cycle.
Concur renewal sits inside the wider SAP commercial relationship. The renewal posture depends on the user-population audit, the report-frequency profile, the travel-volume read, the module-deduplication question against Ariba and S/4HANA, and the wider portfolio negotiation.
The methodology runs three independent reads against the publisher's renewal proposal: the user-population reconciliation against the subscription count, the report-frequency analysis against the commercial mechanic and the module-deduplication audit against the wider AP-automation surface. Each read informs the negotiation position.
The renewal engagement runs under one of three Admodum frameworks: fixed fee, contingency / gainshare or annual retainer.
Five checks for the buyer running into a Concur decision: audit the actual report-frequency distribution against the commercial mechanic. Read the Travel and Expense modules as a consolidated commercial picture with the travel-management company. Deduplicate Invoice against Ariba and S/4HANA where the surfaces overlap. Open the renewal across the wider SAP portfolio, not in isolation. Run the negotiation on the validated usage data, not on the marketing position.
For the wider SAP reading, return to the SAP pillar, visit the SAP knowledge hub, or open a private conversation with a senior Admodum SAP advisor through /contact/.
A senior Admodum SAP advisor will run the methodology through with your CIO, CFO, procurement team or audit response team on a private call. The engagement runs as fixed fee, contingency or annual retainer. Active SAP audits route directly to the Audit Defence programme.