Ratelists: Moving to the new ratelists

Your prices and wages will move to the new ratelists. We do the move together with you, step by step, and you keep working as usual in the meantime.

This article is for clients who already use OnSinch with the old pricelists. If you are starting with OnSinch now, you work with the new ratelists from day one and there is nothing to move. Start with Ratelists: Feature overview.

What changes

Your rates move from pricelist categories and effects to pricelists (what you charge clients) and wagelists (what you pay staff). Each is built from simple rules: a condition, a unit, a rate and a component.

One place for all rules. Bonuses, night and weekend rates, minimum calls and overtime are rules inside the ratelist, not separate effects.
Components. Each amount carries a label, for example "Basic Hour Wage" or "Night bonus". You see them on payslips, in exports and on invoices.
Revisions. When you change a ratelist that is already in use, a new version is created. Past jobs keep the version they were calculated with.
Rounding per ratelist. Hours and distances can round differently for prices and wages, and even per rule.
Calculator. You can test any ratelist on a sample shift before you use it.

What stays the same

You create jobs, staff them and close shifts the same way. The job form simply offers a Pricelist and a Wagelist.
Orders created before the switch keep their old calculation until they are finished.
Your staff work, sign up and get paid as before. Only the names of some lines on their payslip may change.
We stay with you during the whole move. Nothing switches until you have confirmed the results.

How the move works

The move has six steps. We agree the dates with you at the start.

Preparation. We review your current prices, wages, effects, tags, transport rates and rounding. You collect your current rates and anything that bothers you today.
Kickoff meeting. We show you the new ratelists and agree on the go-live date, who builds, who tests and who signs off. We also decide if we start on a demo environment or directly in your system.
Building. Together we set up your first wagelist and pricelist, rebuild your bonuses as rules, and update tags and transport rates if you use them.
Testing. We test real events, your payroll export or API and your documents. We compare a few past periods under the old and the new rates, and you confirm the differences are expected.
Parallel phase. From an agreed date, new orders use the new ratelists. Orders already created keep the old rates until they are finished. We check in with you regularly.
Full switch. When you confirm everything is correct, we turn off the old pricelists. We watch your first payroll cycle with you.

If a serious problem appears after the switch, we can turn the old pricelists back on until it is solved.

What we need from you

Please prepare these answers before the kickoff. They are the same for wages and for prices.

Your current rates: all job types, levels and seniority tiers.
Supplements: team leads, skills, staff leaders. Added on top of the base rate, or a separate rate?
Minimum call: is there one, for staff, for clients or both?
Overtime: are extra hours paid or charged differently?
Night, weekend and bank holiday work: paid or charged differently?
Overlapping bonuses: can they apply together, or does one rule out the other?
Rounding: do staff hours and client hours round the same way?
Manual workarounds: anything you calculate outside OnSinch today, for example in Excel or by editing invoices.
Exports and integrations: how wages and prices get to your payroll and accounting.
Timing: your preferred go-live date, for example a season start or fiscal year end, and any rate changes coming soon.

The move is also a good moment to simplify. Tell us what you would like to change.

Good to know

Effects are not carried over. We rebuild them as rules in your new ratelists, so check with us which ones you still use.
Tags with prices or wages get new rates in the new format. Tags without money stay as they are.
Exports and API. If you use the wallet export or an API to send wages or prices to payroll, we check together if it needs an update.
More languages. If your system runs in several languages, ratelist and component names need a translation in each of them.
Your staff. Tell your staff about the change in the way that suits you, for example that some payslip lines get new names.
Documents. We help you check or update your PDF calculations so they show the new components.