👉 Overview
A payment adoption means that the costs from one user can be taken over by another user. Optionally, you can specify for which purposes (private, business) the adoption should be applied.
This payment adoption must be created once for each user.
🚗 Examples
Example 1: A user wants the invoice for a business trip to be sent directly to his employer.
In this case, a payment adoption for the purpose “business trip” can be created. Valid from the set start date.
Example 2: Families
The whole family uses the sharing service, but only one person receives the invoices and pays for it. In this case, a payment adoption must be created per family member for the respective purpose.
Dad pays the invoices → no payment adoption
Mum → Payment adoption for purpose “private” by Dad
Child 1 → Payment adoption for purpose “private” by Dad
Child 2 → Payment adoption for purpose “private” by Dad
Example 3: Municipality - When a municipality employee makes a business trip, the invoice should go directly to the municipality.
A carsharing service provides its car to a municipality. The municipality takes care of the costs for its employees. To ensure that this is not charged to the car sharing provider, an additional payer must be created for the municipality.
📚 How to set up a payment adoption
Click on Payment adoptions in the Zemtu menu to see all active payment adoptions.
Click the button on the right top + Add Payment adoption to add a new payment adoption.
How the form looks like:
Payer: | Company XY (Payer who will take over the payments) |
Payee: | Employee / Sponsor / Family member |
Purpose: | Business or private |
Start: | YYYY-MM-DD |
End: | YYYY-MM-DD |
🤷 Questions & Answers
Which billing method is going to be used?
The respective payment method (e.g., Stripe) and the invoice run (monthly, immediate, etc.) that are set up for the user also applies to the payment adoption.
Do I have to enter a payment adoption for every purpose?
Yes, even if the business and private rides are covered from the same payer.
What do I have to consider when an employee leaves?
The end of the payment adoption has to be adjusted manually. After the employee has left the company, the user can be pseudonymized.
Would "Skip payment method check” for a user also prevent the billing?
No, an invoice will still be sent, and if a credit card has been added, authorization and capture will also be performed