Integration overview
Connect the integration
Configure Tag, Taxes & Categories
Set up SAP S/4HANA
Adding tags
Export an expense
Integration overview
The integration supports the following:
- Automatically exports Pleo expenses to S/4HANA
- Transfers receipts, invoices and other attachments for all exported expenses
- Automatically synchronises the following Cost Objects from S/4HANA with Pleo tag groups:
- Cost Center
- WBS
- Internal order
- Blocked Cost Objects are not synced
Step 1: Connect the integration
- In Pleo, navigate to Settings
- Go to Accounting
- Select SAP S/4HANA
- Follow the prompts to copy the API key and paste it into SAP S/4HANA
Step 2: Configure Tag, Taxes & Categories
- Tax Codes
- In Pleo, navigate to Settings
- Go to Accounting
- Within the Tax codes section, enter the tax information available in SAP
- Tax type: Standart / Reverse
- Name: SAP Tax name
- Code: SAP Tax code
- Tax rate: SAP Tax rate
- Categories
- Go to Categories
- Click Create Category groupand enter the following details:
- Account: SAP General Ledger account with account types primary costs or secondary costs
- Name: SAP General Ledger account name
- Tag groups and tags
- Click Create tag groupand enter their names. Recommended group names:
- CostCenter
- InternalOrder
- WBS
- Click Create tag groupand enter their names. Recommended group names:
Step 3: Set up SAP S/4HANA
The set-up in SAP S/4HANA is typically done by your SAP Consultant or developer. Provide them with:
- The preparation guide:
- The SAP S/4HANA integration package - request this from Pleo Support or your Pleo Customer Success Manager
Once they have completed the steps in the guide continue with step 4.
Step 4: Adding tags
- In Pleo, navigate to Settings
- Go to Accounting
- Click Tags
- Click on the created tag group created and add the tags
Step 5: Export an expense
After setting up the integrations it's important to export an expense to see if the integration is configured correctly.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article