Announcing o11's backing from Y Combinator.](/content/blog/announcing-backing-from-y-combinator/index.html)

# AI for SAP Concur

## AI that triages the expense queue.

- Flag policy violations before they reach approvers.
- Route reports to the right owner the first time.

### Expense Report: April Customer Trip
**ER-7794**
**Not Submitted**

**Total:** $1551.40  
**Currency:** USD  
**Amount Due:** $1089.10

| Date       | Vendor                          | Type   | Amount   | Receipt | Status  |
|------------|---------------------------------|--------|----------|---------|---------|
| 4/10      | United Airlines                 | Air    | $462.30  | 📎      | Approved|
| 4/10      | Lyft (PDX → hotel)             | Misc   | $42.10   | ✕       | Pending |
| 4/10      | The Drake                       | Lodging| $312.40  | 📎      | Pending |
| 4/11      | Riverwalk Bistro                | Meals  | $84.20   | 📎      | Approved|
| 4/12      | Polo Lounge (group dinner)      | Meals  | $612.40  | 📎      | Exception|
| 4/12      | Lyft (hotel → PDX)             | Misc   | $38.00   | ✕       | Pending |

**Report Total** $1551.40

### o11 for SAP Concur: an AI agent layer for travel and expense

o11 is an AI execution layer that runs inside SAP Concur. The agent triages reports, flags policy violations, and routes approvals — without sending a finance ops lead into the queue to manually sort hundreds of line items by submitter.

If you have searched for **AI for SAP Concur**, a **Concur AI agent**, or an **alternative to the Concur AI Assistant** for actual workflow execution, the difference comes down to one question: does the AI explain a single report or operate the whole queue.

### What teams use o11 for in SAP Concur

- **Expense report triage.** Sort the queue by risk, age, approver fit, and submitter pattern instead of opening every report.
- **Policy-violation flagging.** Catch limits, missing receipts, and category mismatches before reports sit in a queue.
- **Approver routing.** Send each report to the correct cost center, manager, or finance reviewer the first time.
- **Receipt and source matching.** Read attached receipts, vendor emails, and card feeds to back up each line.

### Why o11 differs from Concur-native AI

The Concur AI Assistant and built-in audit features focus on the single report a user is currently looking at. They explain and suggest, but the queue-level work — the part that actually buries finance ops — still ends with a human clicking through filters. o11 operates on the queue. The chat is the control surface, Concur is where reports move.

### Built for teams that live across systems

Concur is one part of a much larger T&E stack — usually paired with the corporate card program, ERP, accounting close calendar, and an inbox of vendor receipts. o11 is positioned to act across all of them. A flagged report becomes a coded GL entry, a Slack ping to the submitter, and a clean line item in the close pack without the analyst stitching tools together by hand.

### Where SAP Concur teams typically start with o11

- **Finance ops** with queue triage and policy enforcement.
- **AP teams** with reimbursement coding and posting prep.
- **Approvers and managers** with auto-prepared report summaries.
- **Travel program owners** with vendor pattern monitoring.

### How o11 respects SAP Concur permissions

The agent operates with the user’s own role and group. Approval workflows, role-based access, and audit rules apply exactly the way they do in the UI. Nothing is bypassed. That is what makes o11 deployable in regulated finance orgs that cannot trust a tool that runs as an over-privileged service account.

### FAQ

#### Does it auto-approve?

Only when policy and limits clearly allow. Otherwise it routes.

#### Will it touch receipts?

Yes. It reads attached receipts and matches them to lines.

### Ready to see o11 inside SAP Concur?

[Book a demo](/content/demo/index.html)