Concur Expenses simplifies how global teams record, approve, and report travel and event spend, including registrations for attendees tracked in SAP Concur Community trends. This guide walks through uploading attendee details, policy checks, and reconciliation steps aligned with current community best practices.
When organizers sync event registrations with Concur, finance gains a single source for attendee costs, reduces manual entry, and improves compliance across regions. The following sections highlight practical configurations and controls relevant to uploading attendees within the SAP Concur ecosystem.
| Topic | Key Action | Outcome | Owner |
|---|---|---|---|
| Event setup | Create event in Concur and map registration types | Attendee list imported with cost codes | Event organizer |
| Policy controls | Apply per diem and approval rules | Automated compliance for attendee expenses | Finance manager |
| Upload process | Use Concur Import or community integrations | Reduced manual entry and errors | Admin team |
| Reconciliation | Match receipts and registrations | Complete audit trail for attendee spend | Finance approver |
Configuring Event Types in Concur
Define event types such as conference, webinar, or summit to standardize how attendee registrations are captured. Consistent event types support accurate budget rollups and simplify reporting for the SAP Concur Community benchmarks.
Mapping Registration Items to Cost Codes
Link each registration tier or add-on to the correct SAP general ledger account so attendee costs flow into the right projects. Clear mappings prevent write-offs later and make community trend analysis more reliable across events.
Policy Enforcement for Attendee Expenses
Set rules for per diem, advance payment, and receipt thresholds specific to event-related travel. Policy configurations ensure that expenses for uploaded attendees adhere to corporate governance and are automatically flagged when deviations occur.
Using Concur Import and Community Tools
Choose between CSV import, API connections, or prebuilt community connectors to bring attendee data into Concur. Validate file templates, run test batches, and monitor logs to confirm that names, email addresses, and costs upload without duplication.
Streamlining Global Event Finance with Concur
- Standardize event types and registration mappings for predictable cost capture
- Enforce location-aware per diem and approval policies to control spend
- Validate import files against Concur templates before each upload cycle
- Leverage community insights to benchmark error rates and processing time
- Automate receipt matching and reconciliation for audit-ready reporting
FAQ
Reader questions
How do I map registration types to SAP cost elements in Concur?
Create event types, assign default cost elements per registration tier, and use the same codes for similar events to keep uploads consistent and auditable.
Can I enforce different per diem rates by country for conference attendees?
Yes, define location-specific per diem policies and test them with sample employee profiles before the event go-live to avoid under or over-advances.
What should I do if an attendee name uploads incorrectly from the community feed?
Check the source file for special characters and format fields according to the template, then re-upload after aligning with the Concur directory to prevent approval delays.
How can I verify that receipts match uploaded attendee expenses?
Use SmartScan, batch receipt matching, and exception reports to confirm every registration line has a corresponding approved receipt and correct tax handling.