Travel costs and distance
For each gig GigGuru works out the driving distance between your departure address and the location, and puts it on the draft invoice as a travel line: the kilometres there and back times your mileage rate.
What you set
Section titled “What you set”- Home address — your default departure address. On the web under Settings → Profile → Home address, in the iPhone app under Settings → Profile.
- Rate per kilometre — what you charge per kilometre. On the web under Settings → Profile → Travel costs, in the app as Travel rate under Settings → Profile. If you have not filled it in, GigGuru uses €0.23 per kilometre.
- Bill travel expenses, per client under Settings → Employers. With this off, that client gets no travel line on the invoice, no travel time in Moneybird and no ride in Rompslomp. The page of such a gig says travel is not invoiced to this client.
An example: a gig 46 km from home at €0.23 per kilometre gives a line of 92 km × €0.23 = €21.16.
Where GigGuru routes to
Section titled “Where GigGuru routes to”- Departure: the departure address on the gig itself, if you filled one in (because you are leaving from a hotel, say). Otherwise your home address.
- Destination: the gig’s location. If a client’s calendar only names a room, such as “Grote Zaal”, switch on Always travel to this address for that client and fill in the default address. GigGuru then routes every gig from that client to that address.
GigGuru uses OpenStreetMap to find addresses and calculates the route by road. Addresses in the Netherlands, Belgium and Germany are found. If a venue name comes before the address, as in many calendar feeds, GigGuru strips it off itself.
Calculated once, then kept
Section titled “Calculated once, then kept”A distance is calculated once and stored with the gig. It is only recalculated when one of the two addresses changes: a client changes the location in the feed, or you move and update your home address. A different name for the same place, with the same street and postcode, does not count as a change.
A distance you enter yourself is never overwritten. If you fill in a distance or travel time in the job form, it stays, even when an address changes later. GigGuru cannot tell whether such a number is right, and replacing yours would be the worse mistake.
The calculation happens during the accounting sync, for gigs that have ended. On a first sync with many gigs GigGuru calculates at most 30 at a time; the rest follow on the next sync.
“Travel distance could not be calculated”
Section titled ““Travel distance could not be calculated””After a sync, the result lists which gigs got no travel costs and why. The messages are in Dutch:
| Message | What it means | What to do |
|---|---|---|
| Vertrekadres … is niet gevonden | Your home address or the gig’s departure address is not in OpenStreetMap | Enter street, number, postcode and town in full |
| Adres van … is niet gevonden | The gig’s location is not an address that can be found | Enter a street, postcode and town on the gig, or use Always travel to this address for the client |
| … heeft geen locatie | The gig has no location | Add a location |
| Geen vertrekadres bekend | You have no home address and the gig has no departure address of its own | Set a home address in your profile |
| … kon tijdelijk niet worden opgehaald | The free map service did not answer | Nothing: it is retried on the next sync |
| Reisafstand voor … opdrachten is nog niet berekend | Too many new gigs for one round | Nothing: it happens on the next sync |
See also Connecting your accounting and Rates per client.