The key point: Liftago should not be treated as a copy of Bolt or Uber without checking the actual service structure. The correct answer depends on the real platform mix, not on the label alone.
This page owns one exact job: explain when Liftago needs a genuine regime audit and what changes when Bolt or Uber are added into the same business. If your trigger is already clearly Bolt-specific, go to Bolt identified person instead.
1. Why Liftago cases are different
Some driver platforms create an obvious identified person trigger from the start. Liftago often requires a more careful reading of the service relationship before the regime is decided.
2. Three practical scenarios
- Liftago only: first confirm the real service flow before assuming identified person status.
- Liftago + Bolt/Uber: the mixed case often brings the identified person layer in through the foreign platform.
- Liftago + other foreign services: the trigger may come from the wider business stack, not only from the ride platform itself.
3. What the safe process looks like
- Separate documents by platform.
- Check the regime for each service source.
- Close the monthly picture consistently.
- Track the annual turnover and VAT thresholds in parallel.
4. What to open next
- If the mixed case clearly includes Bolt: Bolt identified person.
- If the business is already near wider VAT decisions: Bolt and VAT in the Czech Republic.
- If you want the service path instead of more reading: Uber and Bolt bookkeeping.
Send your Liftago and other platform mix
We will tell you whether you need a pure audit, identified person registration or a wider monthly VAT process.