KiteHR

All featuresMoney

One person, several clients, every hour paid and billed.

For people who work on contracts for clients: each engagement keeps its own currency, pay rate and bill rate. Hours booked on its projects become pay in the payroll month and a file of hours for the client.

What you get

  1. 01

    Several at once

    Per hour, per day or a fixed amount a month, in any currency, with rates that change on a date and keep their history.

  2. 02

    Time that knows the engagement

    Hours on a project count for the engagement that covers it. When two cover the same project, the person picks one on the timesheet.

  3. 03

    Exchange rates handled

    Pay in each engagement's currency, or converted with the European Central Bank's daily rate, or with your own rate for a legal entity and day.

  4. 04

    Hours for the client

    Export a client's approved hours for a calendar month, with bill rates and totals per currency, as CSV or Excel.

Per hour, per day or per month

An engagement is one contract a person works on for a client: a name like "Acme · backend development", a client, a currency, a start and an end, and the projects it covers. Several can run at once.

  • Per hour: approved hours times the rate of each day.
  • Per day: a day with hours counts as one, or as half a day up to half the engagement's own hours per day (7.5 h, say).
  • A fixed amount a month, prorated over the days it runs by the legal entity's rule; hours are still booked and shown.
  • Rates by date: a new rate from 1 December splits the month, each day at its own rate.
  • An optional bill rate beside each pay rate: what the client is invoiced.
  • When the pay rate changes, the person is told, with the amount in KiteHR and never in the email.

Pay in the payroll month

Each engagement gets its own line in the person's payroll month, in its own currency: the hours or days, the rate, the amount, rounded once.

The person's ordinary pay stays in the legal entity's currency next to it. Totals are shown per currency and never added together.

  • One line per engagement, with "38 h at USD 50.00 from 1 Nov" when a rate changed mid-month.
  • A rate change mid-month splits the line into segments, still one exact sum.
  • Payout per person: in each engagement's currency, or converted into one currency.
  • Conversion day: the last working day, the legal entity's pay day, or a fixed day of the month.
  • Hours counted for an engagement leave the ordinary hourly pay, so no hour is paid twice.
  • A timesheet approved after the lock arrives once in the next open month, as "From earlier months", at its own day's rate.

Exchange rates you can trace

KiteHR fetches the European Central Bank's daily reference rates by itself and converts through the euro. Every converted amount keeps the rate it used, its day and its source.

  • ECB rates every working day, for about 30 currencies.
  • A weekend or holiday uses the last published rate before it.
  • Your own rate for a legal entity and a day, like your bank's, shown as "Override" with who set it.
  • For a currency the ECB doesn't publish, like KWD or AED, you enter the rate where it's missing.
  • Frozen at the lock: "1 USD = 0.923957 EUR, 30 Nov, ECB". A later correction never moves a locked month.
  • The person sees their payouts with the rate, its date and its source; never the bill amounts.

Paid by another legal entity

A services company in your group can pay a client contract while the person stays employed by another legal entity. Choose "Paid by" on the engagement and its lines go to that legal entity's payroll month.

  • Built for HR service firms: a consultant employed by one company, placed with clients through another.
  • Someone the paying legal entity doesn't employ gets an engagements-only line there: no base pay, time off or claims.
  • A chosen payer stays, even if the person moves to another legal entity.
  • Once hours of a locked month count for it, the payer can't change: end the engagement and add a new one.

Hours for the client

From the payroll month, export each client's approved hours for a calendar month that has ended: client, engagement, person, dates, hours or days, bill rate and amount.

  • By calendar month, whatever your payroll's cut-off day.
  • Totals per client and currency, never across currencies.
  • "May still change" while hours of that month wait for approval.
  • Hours approved after a month was exported come once, in a later export, as "From earlier months".
  • Both engagement files, for the client and for your payroll provider, are kept with the payroll month.

The clever bits

  • An hour is paid once

    Hours that count for an engagement leave the person's ordinary hourly pay. Late hours are carried once, never twice.

  • No lock on a guess

    A month can't lock while a rate it needs is missing or only an estimate. Enter your own rate, or wait for the ECB's.

  • Two engagements, one project

    When two engagements cover the same project, the timesheet asks which one counts, and can't be sent until each row says.

  • No surprise on payday

    A new pay rate tells the person, in KiteHR, from the day it starts.

Spend Friday on people, not paperwork.

Self-serve sign-up opens soon. Tell us about your company and we'll show you KiteHR and set you up ourselves.