SAP Concur vs Ottimate

Requirement evaluated: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

For a 3-person AP team at a $120M services company, SAP Concur Invoice enforces segregation of duties through three structurally separate roles assigned per user by a Company Administrator. The Invoice AP User role covers invoice creation and submission; the SAP Help Portal Permissions documentation explicitly states that the Invoice Processor role 'cannot create and submit invoices,' blocking any processor from also acting as the submitter. A separate Approver/Manager role handles the approval step; the system prevents self-approval (an approver cannot approve their own submitted documents). …

Limitations: The Approval Routing configuration includes a toggleable setting called 'Allow Invoice Processors to process their own invoices,' meaning the submitter-cannot-process control is configurable rather than permanently locked, and must be deliberately disabled to enforce the restriction. …

Requirement evaluated: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

For a 3-person AP team where no single person should enter, approve, and pay an invoice, Ottimate provides separately configurable permission layers at each stage of the invoice lifecycle. Invoice entry, invoice approval, and payment execution are three distinct permission sets: administrators assign approval rights by role or individual user through Invoice Approval Policies in Admin Settings, and VendorPay carries its own separate Payments Approval Policies with a dedicated 'Approve Payment' permission that was explicitly split from the 'Expedite Checks' permission in a 2025 platform update. …

Limitations: For this buyer's 3-person AP team, the most material gap is that the 'person who enters cannot approve' control is not a system-enforced hard block: an admin can configure the same user to upload and approve invoices, and the auto-approve-if-uploader setting, if enabled, actively bypasses the separation. …

Requirement evaluated: Support for Sage Intacct dimensions: Location, Department, Class, Project, Customer, and custom dimensions

For a $120M services company on Sage Intacct, SAP Concur Invoice supports dimension coding at the invoice line-item and allocation levels through its custom fields framework: administrators create named custom fields in Concur Invoice and map them to Intacct dimension lists (GL accounts, vendors, and dimensions are pulled into Concur via the bi-directional integration). …

Limitations: User-defined (custom) dimensions added in Intacct after go-live require manual reconfiguration in Concur's custom fields framework because custom fields cannot be created or updated via API, creating ongoing administrative friction and risk of coding errors whenever the buyer's Intacct dimension structure evolves. …

Requirement evaluated: Support for Sage Intacct dimensions: Location, Department, Class, Project, Customer, and custom dimensions

For a $120M multi-location services company running 2 Sage Intacct entities, Ottimate operates at cost-allocation stage (pre-processing step 5) by coding invoice line items to multiple GL dimensions before export to Intacct. Ottimate's own Sage Intacct integration page directly answers the custom-dimension question: <cite index="38-1">"Yes, Ottimate supports mapping across customized dimensions and metadata fields configured within Sage Intacct entities."</cite> The mechanism works at line-item granularity, not just header level: <cite index="48-1,48-3">Ottimate captures custom header and line item fields, then codes it all to multiple dimensions on the GL with zero to minimal training requi …

Limitations: Ottimate's vendor page confirms custom dimension support but does not specify whether dimension lists are pulled dynamically from Intacct's API in real time or require periodic manual re-sync when new dimension values (e.g., a new Location or Project) …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M multi-location services company evaluating AP automation vendors, SOC 2 Type II certification is a threshold requirement and SAP Concur clears it with a current, independently audited report. The most recent report on the SAP Trust Center is the 2025 H1 edition: <cite index="13-1,13-2,13-3">it covers the audit period April 1, 2024 through March 31, 2025, assessing the trust principles of Security, Availability, and Confidentiality.</cite> Critically for this buyer, the scope is not limited to SAP's broader cloud infrastructure: <cite index="11-5">"SAP Concur's travel and expense management solutions in scope for this SOC 2 Audit are: Concur Standard/Professional/Premium Editions, …

Limitations: SAP also published a SOC 2 Remediation Update for the same April 2024 to March 2025 period, indicating the third-party auditor noted findings; <cite index="17-1,17-2">this summary reflects remediation updates from findings noted by the auditor, and any reference to remediation is SAP's internal assessment to be submitt …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M services company evaluating AP automation security, Ottimate's dedicated AP Security and Compliance product page directly addresses this requirement. <cite index="11-13">Ottimate states it is 'SOC 2 Type 1 and Type 2 certified,'</cite> with <cite index="11-14,11-15">Type 1 evaluating whether security and privacy controls are correctly designed at a point in time, and Type 2 evaluating whether controls are designed and functioning properly over a specified period.</cite> The certification covers the AP automation platform itself: <cite index="11-7">Ottimate explicitly describes its product as 'SOC2 Type 1 and Type 2 compliant AP automation' with industry-standard encryption and se …

Limitations: No publicly visible trust center with a dated report or compliance monitoring badge (e.g., Vanta, Drata) was found, so the buyer cannot self-serve to confirm report recency. …

Requirement evaluated: Cash flow forecasting based on approved and pending payables with due date distribution

For a 3-person AP team processing 1,800 invoices monthly across two Sage Intacct entities, SAP Concur Invoice offers several reporting components that touch cash flow visibility, but they do not combine into the forward-looking, status-segmented forecast the buyer describes. The platform includes a default accrual report that shows every invoice in the system along with its current status, location, and approver, and this report can be scheduled for automatic distribution to stakeholders. …

Limitations: For this buyer, the material shortfall is the absence of a native, pre-built cash flow forecast view that unifies approved and pending-in-workflow invoices into due date buckets; the available accrual and aging reports address workflow status and payment batch management separately, but not the combined forward-looking …

Requirement evaluated: Cash flow forecasting based on approved and pending payables with due date distribution

For a multi-location services company with 1,800 invoices per month and 2 Sage Intacct entities, Ottimate provides the components of payables cash flow visibility through three separate reporting surfaces rather than a single consolidated forward-looking forecast. First, the AP Aging by Invoice report shows all unpaid invoices segmented by aging bucket, with each invoice's approval status (pending vs. approved) and outstanding balance visible per location and vendor, which covers the buyer's need to see due date distribution across both approved and pending payables. Second, the Approval Aging report (an Advanced Report, available via Ottimate's Advanced Reports add-on tier) …

Limitations: Ottimate does not appear to offer a single unified cash flow forecast dashboard that combines pending (pre-approval), approved, and scheduled payables into one forward-looking outflow timeline with configurable date buckets (e.g., 7/14/30/60/90 days); the buyer must reconcile three separate report surfaces to replicate …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

Your team currently keys every invoice by hand into Sage Intacct; Concur Invoice's Invoice Capture feature directly replaces that step. Vendors email invoices to a dedicated Concur-issued address (e.g., CompanyName_invoicecapture@concursolutions.com), or physical mail is scanned and uploaded; the system then applies OCR and machine learning to auto-populate the invoice record. …

Limitations: Payment terms extraction is not documented as an OCR-captured field in Invoice Capture; Standard Edition sets them to a fixed Net 30 regardless of what appears on the invoice face, which would require your AP team to manually override terms for any vendor with different contractual terms. …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a multi-location services company receiving invoices by both email and physical mail, Ottimate's capture pipeline works as follows: mailed invoices are scanned and uploaded as PDF, JPG, or PNG files via the dashboard or forwarded to a per-location Ottimate email address for automatic ingestion; <cite index="23-1,23-3">Ottimate accepts JPG, JPEG, PNG, and PDF formats, and the most common path is scanning paper invoices into PDFs and uploading via dashboard or email.</cite> Once ingested, <cite index="8-11">Ottimate employs machine learning algorithms to extract and categorize data from invoices, regardless of their format, and then automatically matches them to purchase orders and deliver …

Limitations: Ottimate's strongest line-item extraction heritage is in hospitality and food-service invoice types (SKU, pack size, unit of measure), and its help center documentation on field granularity focuses on those verticals; for the buyer's non-PO invoice types (utilities, insurance, subscriptions), payment-terms extraction i …

Requirement evaluated: Clear exception categories: price variance, quantity variance, missing PO, missing receipt, duplicate, vendor mismatch

For a 6-location services company running 1,800 invoices per month across two Sage Intacct entities, Concur Invoice's exception management centers on its configurable PO Matching Rules engine. Administrators define rule groups for two-way matching, three-way matching, and receipt confirmation, each with configurable tolerance thresholds expressed as a percentage or unit amount above the PO value; when an invoice breaches a threshold, the system triggers an exception message and can warn or block submission. …

Limitations: The entire matching and exception framework in Concur Invoice applies only to PO-linked invoices; the buyer's 45% non-PO volume (utilities, subscriptions, insurance) …

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a multi-location services company processing recurring utility and rent invoices, Ottimate's duplicate detection operates on a fixed, globally-applied rule set. The system flags invoices across three severity tiers: exact duplicates (same Invoice Number, Vendor, Location, Invoice Type, Total Invoice Value, and Invoice Date), likely duplicates (same set of fields with any amount variance), and possible duplicates, which is the tier most relevant to recurring billing scenarios. …

Limitations: Your scenario specifically requires per-vendor duplicate sensitivity configuration so that recurring billing vendors that legitimately reuse invoice numbers do not trigger false-positive flags while fraud protection remains intact for the rest of your vendor base. …

Requirement evaluated: International wire payments to 8 overseas vendors with multi-currency support

For a $120M services company needing to pay 8 overseas vendors in multiple currencies, Concur Invoice's native payment network does not cover international wire transactions. As documented by SAP Concur's own Director of Global FSI Partnerships, the platform historically handled payments 'only within the US and Canada,' with any international payment falling outside the system and requiring separate, manual bank processing. To close this gap, SAP Concur partnered with TransferMate, an independent third-party payments company, whose 'PaymentsHub' product can execute cross-border payments in 130+ currencies across 160+ countries and embed within Concur Invoice's approval flow. …

Limitations: International wire and multi-currency AP vendor payments require contracting with TransferMate, a separate third-party company, as Concur has no native international payment rails of its own. …

Requirement evaluated: Virtual card program with rebate revenue; we want to shift 30%+ of spend to virtual card

For a multi-location services company currently running bi-weekly check runs and monthly ACH batches, Ottimate's VendorPay module delivers a fully native virtual card program integrated directly into the AP approval workflow. Once an invoice clears approval, <cite index="14-19">after an invoice gets approved, VendorPay issues a one-time virtual card number funded for the exact amount</cite>, which the supplier processes like a standard credit card payment. …

Limitations: Ottimate does not publish specific rebate rate tiers in public documentation, so the actual cashback percentage the buyer receives is a commercial negotiation; the buyer should request a rebate schedule tied to projected vCard spend volume during contract discussions. …

Requirement evaluated: Centralized vendor master synchronized bidirectionally with Sage Intacct

For a 2-entity Sage Intacct environment like yours, SAP Concur's native Financial Integration Service pulls vendor records, GL accounts, and dimensions directly from Sage Intacct into Concur in near-real-time: <cite index="21-1">SAP Concur automatically collects all account codes, dimension lists, and vendors directly from Sage Intacct,</cite> and <cite index="15-7">customers can sync at the Top Level or up to 10 entities to one SAP Concur company/entity.</cite> In the other direction, processed invoices post back from Concur to Intacct automatically after approval. However, the write-back path for net-new vendor records created inside Concur (rather than originated in Intacct) …

Limitations: For your team's specific need, the material gap is the Concur-to-Intacct direction for vendor records: new vendors created or updated inside Concur rely on a scheduled extract or a manual import step before they appear in Intacct, rather than an automatic real-time push. …

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For your 3-person AP team processing 1,800 invoices/month, Ottimate addresses several vendor-facing needs through a combination of point-specific tools rather than a single unified self-service portal. Banking detail entry works via an AP-initiated email invitation: once your AP team flags a vendor for ACH in the Vendors module, the vendor receives a secure link, completes their banking fields, and creates a login at vendor.plateiq.com, with micro-deposit verification taking 1-3 business days (Ottimate Help Center: 'Vendor ACH Verification', 'How do I Invite Vendors to Accept ACH Transfers'). …

Limitations: W-9 and W-8 collection is not present in Ottimate's documented capabilities at any tier or price point, which means your team would need a separate process (email, PDF, or a third-party tool) to collect and store tax compliance documents for new vendors — a direct gap against your critical requirement. …