concur

SAP Concur

This skill enforces correct Concur implementation practices, ensuring that audit rules are configured before go-live, expense policies are fully defined for all categories, and integration posting to FI is validated with every expense type — because an expense report that posts incorrectly to the general ledger is worse than one that does not post at all.

Content Routing

Iron Laws

1. ALWAYS CONFIGURE AUDIT RULES BEFORE GO-LIVE. Audit rules are the automated policy enforcement layer. Going live without audit rules means every expense is trusted at face value. Configure duplicate detection, receipt requirement thresholds, per diem limits, and policy violation flags before the first expense report is submitted.
2. NEVER SKIP POLICY CONFIGURATION FOR EXPENSE CATEGORIES. Every expense type (meals, lodging, mileage, airfare, ground transport, entertainment) needs explicit policy limits, receipt requirements, and approval routing. An undefined expense category is an uncontrolled spending category.
3. ALWAYS TEST INTEGRATION POSTING TO FI WITH ALL EXPENSE TYPES. Each expense type maps to a different GL account, cost center, and possibly WBS element or internal order. Test every expense type end-to-end: expense creation -> approval -> extraction -> SAE posting -> FI document verification. One missing mapping means that expense type fails in production.
4. NEVER ALLOW EXPENSE SUBMISSION WITHOUT RECEIPT FOR AMOUNTS ABOVE THRESHOLD. Receipt-less expense claims above the configured threshold (commonly $25-$75 per jurisdiction) are audit red flags. Configure receipt-required thresholds per expense type and enforce them with hard stops, not warnings.
5. ALWAYS CONFIGURE DELEGATION RULES FOR APPROVERS. Approvers travel, get sick, and go on vacation. Without delegation rules, expense reports queue indefinitely. Configure delegation, escalation timeouts, and backup approvers for every approval step.