Concur Invoice Capture Processing: Managed vs Client Managed

Concur Invoice Capture Processing is the OCR and machine-learning layer inside SAP Concur Invoice that auto-populates header fields (vendor, invoice number, date, totals, tax) and line-item fields (description, quantity, unit price, expense type categorisation) before each invoice enters the approval workflow. Every Concur Invoice tenant uses Capture Processing in some form. The configuration question is which of three modes runs the verification step that decides whether the OCR layer's output is trustworthy enough to advance.

The three modes:

• Concur Managed Capture is fee-based: SAP staff verify OCR output before each invoice advances in workflow.
• Client Managed Capture is free at the licence line: the client's own team verifies OCR output internally.
• Dual Support is the hybrid that routes part of the volume to SAP-staff verification while leaving the rest with the client team.

Choose Managed when AP capacity, SLA coverage, or audit separation is the constraint. Choose Client Managed when the AP team can verify internally and absorb the staffing, training, and queue-management work. Use Dual Support when only certain regions, peaks, or supplier groups need SAP verification. Consider upstream extraction when line-item-heavy invoices are the real bottleneck.

The decision is a Concur Invoice question specifically, not a generic SAP OCR question. SAP Business One invoice OCR setup, S/4HANA invoice OCR routes, and SAP Ariba PDF and email capture follow different models. Concur Invoice's three-mode model belongs to Concur Invoice.

---

Concur Managed Capture: What the Fee Buys

Under Concur Managed Capture, SAP-employed staff sit in front of the Capture Processing verification queue and confirm or correct each invoice's OCR output before that invoice advances into the approval workflow inside Concur. Your own AP team picks up invoices in workflow with the header and line-item fields already verified by an SAP human. Capture-stage exception triage — the work of resolving low-confidence fields, reading awkward scans, deciphering supplier templates the OCR engine hasn't seen before — moves off your queue entirely.

SAP positions Managed verification under a contracted turnaround SLA, typically expressed in hours from receipt to verified-and-released. The specific hour count varies by contract tier and is not a public number. Overflow handling for peak volumes (month-end supplier statement waves, quarter-close flushes) is negotiated separately, often as a contracted overflow ceiling beyond which a different rate or a queueing behaviour applies.

SAP does not publish list pricing for the Concur Capture Processing fee. The per-invoice rate is quoted per customer, so partner content that cites a number is usually quoting one customer's deal in one geography in one year. What matters is getting the quote unbundled across the variables that drive it:

• Monthly invoice volume tier. Higher volumes draw lower per-invoice rates, but the tier breaks vary by contract.
• Contracted turnaround SLA. A two-hour verified-and-released SLA prices differently from a same-business-day SLA.
• Line-item depth. Header-only verification is one rate; full line-item verification on dense supplier templates is another. SAP staff verifying twenty SKU rows on a single invoice are doing more work than verifying a header.
• Geographic scope of the supplier base. Multi-language and multi-script verification commands a different price than single-region English. A supplier base spanning Latin scripts, CJK, Arabic, and Cyrillic invoice formats demands verifier coverage that English-only does not.
• Integration scope. Custom routing rules, custom exception escalation paths, and bespoke approval-handoff configurations add complexity SAP prices in.

When discussing cost with SAP, ask for the per-invoice rate broken out by line-item depth and SLA tier; explicit overflow and exception-handling pricing; written confirmation of which supplier languages and scripts are covered; and the billing unit, because "per verified invoice" can mean per invoice, page, or line item depending on the contract template.

Managed also shifts capture-stage exception management and OCR-tuning feedback away from the AP team. It is a labour-and-accountability transfer with a price tag; whether that price is worth paying depends on the internal verification alternative.

---

Client Managed Capture: Free at the Licence Line, Real at the FTE Line

Under Client Managed Capture, the OCR layer extracts the same header and line-item fields as it does under Managed — the engine is identical — but your own AP team works the verification queue. Verifiers see each invoice in Concur's verification UI, with field-level confidence scores and a source-document overlay that lets them confirm or correct each field against the original PDF or image. Once a verifier releases the invoice, it advances into the approval workflow. Both modes end at human-verified output; the only difference is who the human is.

That equivalence at the output side is why Client Managed is "free." There is no separate fee on the licence line for the verification step. The cost lives entirely in your team's time, which is why "free" needs immediate qualification.

A defensible way to think about the FTE-hours load is to multiply seconds-per-invoice by monthly volume, with the seconds-per-invoice band reflecting your supplier mix. For straightforward header-only invoices on familiar templates with high OCR confidence, verifiers typically spend somewhere in the range of thirty to sixty seconds confirming and releasing. For line-item-heavy invoices (manufacturing supplier statements, professional services breakdowns, logistics line detail), the band stretches to ninety seconds to three minutes, sometimes more. The variance is driven by line-item count, OCR confidence on the specific supplier templates, and how familiar the verifier is with the supplier base. At a monthly volume of 5,000 mixed invoices, the math lands somewhere between a half and a full FTE just on capture verification. The numbers are illustrative — your actual figure depends on supplier-base complexity, OCR-tuning maturity, and verifier experience — but they make the point that the licence-line "free" understates the operational reality.

The seconds-per-invoice math misses second-order costs: shift coverage for multi-region invoice arrival, verifier training and turnover, OCR-tuning ownership, and the audit trail of who verified what. Those are internal controls and staffing questions, not licence-line questions.

The throughput ceiling is the team's throughput. Client Managed handles whatever volume your verifiers can process in their working hours, no more. Steady-state volume is fine. Peak-period spikes — month-end supplier statement waves, quarter-close invoice flushes, annual-contract-renewal billing surges — hit the verification queue first. If the team is sized for steady state, the queue depth at peak becomes an approval-cycle bottleneck that propagates downstream into payment-cycle delay and supplier-relationship friction.

Client Managed is a legitimate choice for firms whose AP teams are already sized for verification work, whose supplier base is consistent enough for OCR tuning to compound, and whose audit posture prefers verification inside the firm. The verification load is also shaped by intake design: digital mailroom decisions for AP intake determine how much of the queue is true verification work versus filtering that should have happened before capture.

Client Managed is real work, sized realistically. Read against a Managed quote, the comparison gets honest only when both sides are loaded honestly.

---

Dual Support: When the Hybrid Actually Applies

Dual Support runs both modes side by side inside one Concur Invoice tenant. Routing rules direct part of the volume to SAP-staff verification under Managed Capture while the rest stays with the client's verification queue. Four operational patterns make the hybrid worth running.

Geographic split. Some country or regional supplier bases route to SAP-staff verification; the rest stay Client Managed. The pattern fits firms with one or two regions where the supplier-base mechanics make Managed disproportionately valuable — local-language tax documents that the in-house verifier population is not staffed to read, or jurisdictions where invoice-format variation defeats template-based OCR tuning — while a dominant English-language supplier base in the home region handles efficiently with internal verification.

Volume overflow and peak coverage. Steady-state volume is verified by an in-house AP team sized for that load. Above a contracted threshold, additional invoices route automatically to SAP-staff verification. This protects approval-cycle SLAs through month-end and quarter-close without permanently sizing the AP team for the peak-month volume that only happens four times a year. The economics are particularly clean for firms whose volume curve is sharply seasonal rather than steadily increasing.

High-complexity invoice subset. Line-item-heavy invoice categories — manufacturing supplier invoices with dozens of SKU rows, professional-services invoices with detailed time-and-materials breakdowns, logistics invoices with per-shipment line breakdowns — route to SAP-staff verification, while header-only or low-complexity supplier invoices stay Client Managed. The pattern targets the per-invoice spend at the invoices where line-item OCR is hardest, without paying the Managed rate on the long tail of simple invoices where in-house verifiers are perfectly adequate.

Supplier-tier routing. Strategic-supplier invoices, where a delayed or mis-captured invoice damages a relationship or breaches a contract SLA, route to Managed. Long-tail supplier invoices stay Client Managed. The criterion is business risk on individual invoice accuracy rather than invoice complexity per se.

Dual Support's cost is operational, not just per invoice. Routing rules need maintenance as the supplier base changes, billing reconciliation has to distinguish Managed volume from Client Managed volume, and exception playbooks fork by route. The firm is running two verification models inside one tenant.

Dual Support is the wrong answer when the volume is small-to-mid and the supplier base is homogeneous. The routing complexity outweighs any per-invoice saving, and the firm ends up paying operational overhead for hybrid mechanics it doesn't actually need. It is also the wrong answer when the AP function explicitly wants a single verification model for audit clarity — auditors testing a single verification model walk through one control; auditors testing Dual Support have to test two control models and the routing logic that decides which invoice goes through which.

---

The Core Trade-Off: Cost, Throughput, Accountability, Audit

Managed and Client Managed use the same OCR engine and both end at human-verified output. The real trade is who does the verification work, who owns peak throughput, who is accountable for capture errors, and what controls wrap the process.

Managed puts the verifier outside the AP team, gives peak handling a contracted SLA, and makes SAP accountable for verification-stage cleanup. Client Managed avoids the per-invoice fee, but the firm owns verifier staffing, queue depth, OCR tuning, training, and root-cause analysis on repeated miscaptures.

For SOX-relevant firms, audit posture can decide the mode. Managed gives cleaner separation because SAP staff verify OCR output but do not approve or release payments. Client Managed can still work, but it needs documented compensating controls. PCAOB AS 2201 says auditors evaluate whether compensating controls mitigate control deficiencies at a level of precision sufficient to prevent or detect a material misstatement. In AP capture, that usually means controls such as dual review on material OCR corrections and rotation of verification duty across staff.

---

The Fourth Path: Upstream Extraction Into Concur

The fourth path is to extract invoice data upstream of Concur, then load the structured payload into Concur through the platform's import-invoice paths. The Capture Processing mode still exists in tenant configuration, but the volume routed through Concur's native OCR drops sharply for the categories where OCR correction work is most expensive.

The case is specific: Concur's native OCR is strongest on header fields and weakest on dense line-item tables. Manufacturing supplier invoices, professional-services time-and-materials bills, logistics invoices, energy bills, and utility invoices concentrate verification work at line-item depth. For those categories, both Managed and Client Managed verification can become expensive correction work.

An AI-powered invoice data extraction layer purpose-built for line-item capture changes that economics. The upstream layer extracts header and line-item fields into Excel, CSV, or JSON, and Concur ingests the structured file through its import path. A finance operator specifies the required columns once; the output shape stays stable across the batch.

This is a supplement, not a Concur replacement: Concur remains the approval, matching, payment, and supplier-master system. Capture-stage exceptions land at the upstream layer, while Concur handles approval routing, three-way match, GL rules, payment scheduling, and supplier controls.

The trade-off is real: the upstream layer is a system to procure, integrate, monitor, and maintain. It earns its complexity when line-item-heavy invoices are a meaningful share of volume. For header-mostly invoices, the three Concur-native modes are usually the right scope.

For more on the underlying capture problem, see the broader guide to invoice line item extraction. The point in a Concur context is not to replace the AP platform; it is to offload the invoice categories where capture verification consumes the most AP time.

---

Choosing Among the Four: A Decision Logic Keyed to Your Firm

There is no single right answer. The decision is keyed to five variables:

• Monthly volume: below roughly 1,000 invoices per month, either pure mode can work; from 1,000 to 10,000, the Managed quote and verifier headcount model need to be compared carefully; above 10,000, Dual Support or upstream extraction often enters the discussion.
• AP team capacity: established verifier teams can make Client Managed work; lean AP teams or teams scaling through supplier churn often buy time with Managed.
• Supplier-base complexity: single-region, single-language supplier bases favor Client Managed; multi-region, multi-language, multi-currency supplier bases often justify Managed or Dual Support.
• Line-item complexity: header-mostly invoices fit the Concur-native modes; line-item-heavy categories are where upstream extraction earns consideration.
• Audit posture: Managed gives cleaner external verifier separation; Client Managed needs compensating controls if SOX scrutiny applies.

Representative patterns:

• High-volume manufacturing firm with line-item-heavy invoices and a mature AP team: upstream extraction into Concur, leaving Concur-native modes for residual header-only flow.
• Global enterprise with a multi-region supplier base and SOX exposure: Dual Support with geographic routing - Managed for high-complexity regions, Client Managed for the home region with documented compensating controls.
• Mid-market firm with steady header-mostly invoices and a small AP team: Managed, because the fee buys verification labour the firm does not otherwise need.
• Mid-market firm with the same volume but a larger AP team: Client Managed, with documented controls if SOX applies.

The durable instruction across all of these is simple: get the Managed quote with the variables unbundled, model the fully loaded Client Managed cost honestly, and put upstream extraction on the table for line-item-heavy volumes. The right answer is the one defensible against those three numbers at your firm's actual volume and supplier-base profile.