Swiss Payroll in Odoo 19 : Step by step demo

Hello everyone. Hello and welcome to this new Odoo Insider, and hello to you again as well. So [laughter], welcome back indeed after two weeks with, let's say, some pre-recorded sessions. Today we are happy to give a new Insider with actually a very special topic, which is a focus on Swiss Payroll for 2026. I mean [snorts], as we have here one of the experts and R&D developer of the module and localization, it will be the chance for us to make a demo and to answer your questions on that localization in Odoo 19. Just for you to know, for the next weeks actually, you're going to get some regular Q&A sessions. So for the people who came to this Insider willing to ask questions about, I mean, the current project or implementation, just keep them for next week, okay? And we will be happy to answer them at that moment. Of course, this session is addressed to the person in Switzerland, but if you are still an Odoo enjoyer and you want just to see exactly how it goes, you know, to make a localization for payroll in Odoo is still the right way to observe it and see how it goes. Well, we are at the beginning of 2026, and so it could be the chance for you to, let's say, switch to payroll for your Swiss company. And actually, if we make just a step back, you might notice that the localization was released like less than a year ago, which is really not a long time, but in such a period of time we got a lot of feedback, a lot of implementation also on the market, which made us improve the tool furthermore. And we were feeling that today was maybe the right time to once again demystify Swiss payroll for all of you that might not, let's say, get the right information or knowledge about it and make sure that your questions and feedback are answered as well. So it's really a chance for you to do that today. One more thing as well is that we have one news today, which is that we are working on the official documentation to implement the Swiss payroll, and today we can share with you a link for, let's say, temporary documentation about it, which takes this following shape. So the idea is that we help you to set it up and to install it, let's say, based on what we will also see today, but also target a lot of specific use cases that we actually met on our own implementation project and when we discuss with the partners that are locally there in Switzerland, with the idea that you can just take a look at this very big list of use cases and try to use them to answer your own cases. Personally, the way I would use it is just to make a control F, you know, and look for specific content. Let's make an example, for example, if I look at time off, for example, here. So I can just dive into the content and see exactly every time that time off is mentioned to see exactly what is the link in between CER and time off at that moment. So it's, let's say, available for everyone. So just keep the link on the side and just look at it, I mean, as much as you can to, yes, answer your own questions. And just as a side note, the goal is to have this in the end in the official Odoo documentation so that we can have, of course, all translations in German, French, and Italian for Swiss people. Indeed. All right. So now I let you speak, Jorgen, and yes, explain what we're going to do today. So our agenda today will be to make you an expert in less than an hour, hopefully. So Swiss Payroll is kind of like a cooking recipe. You can cut carrots, cut tomatoes in different orders, but some stuff cannot be mixed up. You have to set up some things first. The base, which is your insurances, the rates, your source tax institutions, your wage statement templates, certificate salary in French, and your employee information, of course. So the goal here will be first to set up the base. What is the base? The base is to set up your three mandatory insurances, which are the AAS, the CALF, and the L, which is the social insurances, the family fund insurances, and the accident insurance. And the goal here will be to show it live demo. So I will jump right into the database, and here we see the Odoo app switcher, and everything will happen inside here, payroll. So, first step will be to set up your company information. So, we go into settings, general settings, my company here. And we need to first set up the address of your company, which will be in Luzern, Switzerland. That is the first ultimate step of setting up your Swiss Payroll. The second step will be to look at this screen here, which is the general payroll settings, and you have multiple fields and things you can find here. Here are more quality of life settings which help you remind you of your work permits and to have notifications about when they expire and so on. I see here, Jorgen, that we have a choose a payroll localization package. I mean, it's probably for the case where it's not installed yet. I think it's the case on your side. But if we click on the button, what happens actually? What happens? You see all the localization packages that are available, and we see here that the Swiss one is installed here. Mhm. So we are good here in terms of installation of our modules. If you're not sure about if your app is installed or not, you can just go to apps, remove the filter, type Swiss, and you get all the relevant modules. Here we have this one that we should install as well. There we go. Great. Thank you, Anton. So, we have several options regarding accounting. If you want to do SEPA payments, to generate SEPA files to send directly to your bank, you can activate this. Just to know that, of course, to have that feature, you need to have accounting installed as well in the company to set up your bank journal and bank information, of course. And here come our core information about our payroll setting in Switzerland. So we have two fields about your company information, which is the post box where people can send you letters and the identification number, which looks like CH/99 something, etc., with a validation of the number. You have a contact person section. This person will be the one in charge in terms of transmission. So when we transmit to Swissdec and insurances, this is the name that will come up on the receiver side and that the institutions can contact in case of questions or doubts or requiring more information. So let's put Anton there. Of course, he has a Swiss number now. Easy to remember as well. Sorry. Easy to remember. Yeah. [laughter] He bought it for a few francs. And then we have delegate payroll. This might be relevant to a lot of people in this live because a lot of fiduciaries started to use our software. And if a fiduciary is handling your payroll, you have to enable this and mention the relevant information about your company, meaning this company will be the one in charge of doing the payroll of the company here, Odoo Insider. So here you can put all the information of your fiduciary company, and we also have several fields here that most people should not mess with because most people have the default settings. But if you do statistic declarations to the federal office of statistics, you can choose your pay agreement, which you have four options of. Most people are in the individual employment contract. The statistic payroll unit is if you have a pre-existing agreement with the statistic office, then you mention which unit is relevant here. The transmission language, where you define how the institution answers to you. So if you send a declaration, the reply will be in French or in German or in Italian. Let's select French here. The 30-day method, which is kind of a technical feature on how you compute wages and absences monthly, meaning each month will be considered on a 30-day basis or on a number of months or number of days of the month basis. Basically, if

topic uh which is a focus on Swiss Perroll for 2026. I mean [snorts] uh as we have here one of the expert and R&D uh developer of the of the module and localization. it will be the chance for

us to to make a demo and to answer your questions on that um localization in Odo 19. Uh just for you to know for the next weeks actually you're going to get some regular Q&A sessions. So for the people

who came to this insider willing to ask questions about I mean the current project or implementation just keep them for next week okay and we will be happy to answer them at that moment. Of course, this session is addressed to the

person in Switzerland, but um if you are still a NDU enjoyer and you want just to see um exactly how it goes, you know, to make a localization for peril in Odoom is still right way to to observe it and

see how it goes. Well, we are at the beginning of 2036 and so it could be the chance for you to to switch let's say to to perodu for your Swiss company. And actually if we make just a step back we

you might notice that the localization was released like less than a year ago uh which is really not not a long time but in such a period of time we got a lot of feedback a lot of um

implementation also on the market which made us improve the tool further more and we were feeling that today was maybe the right um time to to once again demystify Swiss peril for all of you that might not let's say get the right

information or knowledge about it and make sure that your questions and feedback are answered as well. So it it's really a chance for you to to do that today. One more thing as well is that we have uh one news today is that

we are working on the official documentation to implement uh the Swiss parole and today we can share with you a link uh for let's say temporary documentation about it uh which takes this following shape.

Um so the idea is that we help you to set it up and to install it um let's say based on what we uh will also see today but also target a lot of uh specific use cases that we actually met on our own

implementation project and when we discuss with the partners that are locally there in in Switzerland with the idea that you can just take a look at this very big list of use cases and try to use them to answer your own cases. Um

personally the way I would use it is just to make a control F you know and look for specific content. Let's make an example for example if I look at time off for example here. Uh so I can just

dive into the content and see exactly every time that time off is mentioned to see exactly what is a link in between cer and time off at that moment. Uh so it's let's say available for everyone.

So just keep the link on the side and uh just look at it I mean as much as you can to to yes answer your own questions.

And just as a side note, the goal is to have uh this in the end in the official ODO/ documentation so that we can have of course all translations in German, French and Italian for Swiss people.

Indeed. All right. So now I let you speak Yorgen and yes explain what we're going to do today.

So our agenda today will be to make you an expert in less than an hour hopefully. So Swiss Barrel is kind of like a cooking recipe. You can uh cut carrots, cut tomats in different o orders, but some stuff cannot be mixed

up. You have to set up some things first. The base, which is your insuranceances, the rates, um your source tax institutions, your wage statement templates, certificate salary in French, and um your employee information of course. So the goal here

will be first to set up the base. What is the base? The base is to stop your three mandatory insuranceances which is the aas, the calf and the L which is the social insuranceances, the family family fund uh insuranceances and

the accident insurance. And um the goal here will be to show it live demo. So I will write jump right into the database and here we see the ODO app switcher and everything will happen inside here. payroll.

So, first step will be um to set up your company information. So, we go into settings, general settings, my company here. And we need to first set up the address of your company which will be in Luz Switzerland. That is the first ultimate

step of setting up your Swiss Perroll. The second step will be to look at uh this screen here which is the general peril settings and you have multiple fields and things you can find here.

Here are more um quality of life settings which um help you remind you of your work permits and uh to have notifications about when they expire and so on. I see here Jorgen that we have a choose a par localization package. Um I

mean it's probably for the case where it's not installed yet. I think it's the case on your side. But if we click on the button, what what happens actually?

What happens? You see all the localization packages that are available and we see here that uh the Swiss one is installed here.

Mhm. So we are good here in terms of installation of our modules. If you're not sure about if your app is installed or not, you can just go to apps, remove the filter, type Swiss, and you get all

the relevant modules. Here we have uh this one that we should install as well.

There we go. Great. Thank you, Anton. So, we have several um options regarding into accounting. If you want to do SEPA payments to generate SEA files to send directly to your bank, you can activate this. Just to know that of course to

have that feature, you need to have accounting installed as well in the company to set up your bank journal and bank information of course. And here come our uh core informations about our payroll setting in Switzerland. So we

have two uh fields about your company information which is the post box where u people can send you letters and the ident identification number which looks like ch/99 something etc with a validation of the of the number. You have a contact person

section. This person will be the the one in charge uh in in terms of transmission. So when we transmit to Swiss deck and insuranceances, this is the name that will come up on the receiver side and that the institutions

can contact in case of questions or doubts or u requiring more information. So let's put Antoan there.

Of course he has a Swiss number now. Easy to remember as well. Sorry. Easy to remember.

Yeah. [laughter] He bought it for a few Franks. And then we have delegate payroll. This is this might be relevant to a lot of people uh in this live because a lot of fiduciaries started to use our software.

And if a fiduciary is handling your payroll, you have to enable this and mention the relevant information about your company. Meaning this company will be the one in charge of doing the payroll of the company here Odance Insider. So here you can uh put all the

informations of your fiduciary company and we also have several few fields here that most people should not mess with because most people have the default settings. But if uh you do statistic declarations to the uh federal office of

statistics, you can choose your uh pay agreement which you have four options of. Most people are in the individual employment contract.

uh the statistic peril unit is if you have a pre-existing agreement with the with the statistic office then you mention uh which unit is relevant here the transmission language where um you define how um institution answer to you so if you

send a declaration the reply will be in French or in German or in Italian let's select French here the 30-day method which is um kind of a technical feature on how you compute uh wages and um absences monthly. Meaning

each month will be considered on a 30-day basis or on a number of months or number of days of the month basis.

Basically, if you have a um an unpaid leave on February, if you select 30-day method, it will be 29 over 30 even for February. If you don't select it, it will take the classical number of days.

So 27 out of 28, meaning the wage will be proated differently. And here uh agricultural company, this is a requirement by Swiss deck. You have to take it and it shows up some other field on the employee which is uh very

simple. So that's the the base of the base that we can save here. [snorts] All right. Great. So now that the settings are done, what is the next step?

Well, that was just the first part of the [laughter] settings. We still have all of this to handle. Swiss Prel is kind of kind of um it takes some time to to get starting, but it's a diesel. Once

it gets started, it doesn't stop anymore. So the second step will be to set up your work locations. So these are the units of exploitation of your company.

Here we can set up just by searching our company partner. So ODO insider it will autofill the address that you filled previously in your company and find your cartoon and the municipality ID. This is the commune number. [clears throat]

Here you have two different fields which are relevant for the transmission. If you don't do statistic declarations, they are not mandatory to fill. But if you do, you have to fill this number which you can find on the registry of

companies uh of Switzerland. You either fill this one or the in-house ID. In-house ID is if you have a again pre-existing agreement with uh the federal office of statistics, meaning that um they give you a number so that

they can identify you easy more easily. You then have two other fields. Weekly hours which are the 100% worktime rate hours required per week and the weekly lessons which is kind of hours but not exactly hours.

Again this is a Swiss deck requirement where they want to make a differentiation between work hours and work lessons. So you always have to specify both. I think this is something that is recurrent in Swiss payroll softwares where you have these two

separately. So we now set up a work location. Perfect. We can set up more if you want but let's keep with this one. Of course we have a pre-agreement with the federal office of statistics because we are big

or do insider first step. Second step will be to set up your wage statements. So what is a wage statement? A wage statement is what we call in French uh certificate.

So this is the thing that every employee gets at the end of the year with the pretty QR code at the top and all the relevant uh informations about what they earned so they can send it to their uh

tax authority to calculate their taxes properly. And the goal here is to set up the main company template.

So most people will be subject to this template and most companies will only have one. But of course we have the flexibility to create multiple ones. If you want a template for this group of people in production for example or and

template for this group of people in the office or for accountants etc etc. Yes. So here the idea is to just spare some time afterwards when we configure the the employees contract. Exactly.

Yeah. And so you can select all the relevant informations that you find in the salary certificate. So to check if you have free transportation uh free meals or lunch that are given by the company, your company car policy, no

company car, the employee pays at least 0.9% per month to be clarified and of course all the relevant options regarding the wage statement. You can also uh specify other fringe benefits that are not um mentioned here or you

can add uh additional text for example uh at the end of the document that is a free text.

So we make a very basic template just to set it up and that was the third step.

Mhm. Third step, we have one, two, three, four, five, six, seven, eight steps. Eight more steps and we're ready to go.

Great. Now we get to the main point, the very funny part that I love doing filling insurance information and rate. This is truly my passion. We'll start with the LI insurance.

So again an issue with u this localization is that we have French terms, German terms and Italian terms but English terms are kind of hard to to come up with. So for now in the English version you see the French one but uh

translation is something we're actively working on so that um each language has a has their correct legal term and we start here with the LI insurance.

So this is your accident insurance. Um and the insurancees usually follow um kind of the same pattern where you have the insurance number. This is the kind of the ID of the insurance that is the number used to transmit data to them uh

through Swiss deck and usually you can find here on this page. Yeah. And actually that link is part of the documentation as well. So you can retrieve it from there. But yeah, so you go on the Swiss deck website and

you have din and here you have the insurance that are ready to receive data that are Swiss deck certified and that you can transmit data through uh electronic means. So for the AS we have this insurance number there. This is the number you'll fill on

this field. Here we are on the ELA. Here are the insurers and you will find the number of your insurance there.

That's a question that I got actually from from customers asking if they let's if those fields are mandatory or not. Uh but yes, they should be like especially insurance number should be found uh under let's say insurance contract,

right? Yes. So the insurance contract that the insurance gave you usually has all these informations.

So the customer number and the contract number, this will identify your company uh in the transmission so that they know who they're uh receiving data from.

So our main uh insurance information is filled. Now we have to fill the different rates that our employees will pay and that your company will pay. In this case for the LRA we have this concept of uh groups where you can have

multiple contracts for groups. A practical example would be um a factory for example where the floor workers will be will have one policy and the office workers will have another policy. So here you might have group A for floor

workers or group B for office workers. Here we'll make a simple case with only one group where everyone has the same policy and you have the classic list view of ODU where you can open each uh record. So we click on the first one and

we can see this. So you have the group unit that you can choose from A to Z that is usually um the letter that your insurance gives you and you have these different fields. So you have the dates the from is from when

is this rate uh applicable? So from January 1 2026 this rate will be applicable and you can also choose to close it. So usually you would do until 31 December 2026 and we have for this year 2026 these

rates applicable. You have the threshold which is the maximum salary that is insured. Usually it's a legal value, doesn't change. Everyone has the same one. You have the occupational part uh insurance, which is the company part, the one that you will pay. We'll set it

to 1%. And you have the nonoccupational part, which is the part that the employee will pay or you will pay half or you will pay full. We'll see later how we can set it up such that uh we can

have the three cases here. Here if we set it in like this we have 1% of occupational part that the company fully pays all the time always and you have 1% nonoccupational part that in this case which uh we have 0% company part the

employee will fully pay but you can also choose to pay half half or you might ask how can I pay it fully well in this case in odu to pay it fully yourself uh through the company we have to set it up

on the employee itself because this constitutes a different uh insurance code where um no deductions are taken from the employee.

So yeah indeed so important to not to note indeed that the company pardon only applies as you explained to the nonoccupational rate. Great.

Okay, that's great. So this is a way to define globally the L group A for your company. So that was the third step. Let's go on with the fourth step which is the LP be in German.

So same process we have a name, we have an insurance code, customer number and contract number.

And we have here uh the different LPE codes of your company. They're not mandatory but sometimes your alpe insurance will give you uh certain codes for example production will be K,000 maybe just to make difference in between department and

that's it that's that's a different solutions uh for uh the insurance um and a new thing that we have here since uh since a few weeks now is uh the LP in percentage age. Um I know that this has been the most

requested feature of previous year where people that were paid hourly. Um usually when you're paid hourly, you don't really know how much LPE you have to pay for the month. So um we introduce the alpe in percentage and this is the general setup that

usually is the same for everyone, but some um convention collective ask you to have different numbers here so you can set it up yourself. always with the same principle of rates from rates to which defines the applicability of these

numbers. So that was the third step. Let's go on with the fourth step which is the big a insurance social insurance.

Yeah. And you set it up now because actually it's going to retrieve information from the LA and LP. Yes.

Right. Yes. So in the AS you have to specify which is your main LI insurance and your main LP insurance. So we like to make them we like to do them first uh in this case. So we are in Luzan. So we are

affiliated to Akal Luzian 003.0000 member number 1 23123. And we define here our insurance our LP pay valid from one January this year to one January this year.

And we have here all the different rates uh applicable to your u of course those are national numbers and um should be the same for everyone except for this one which is the administrative fees which are the the percentage of fees

that you pay per employee. So this will be uh the percentage applied to the sum of um amounts that were paid by the employee and by you. So if someone pays 50 Franks of uh AS and you pay equally

50 Franks, this will do one to 1.2% of 100 for your administration fees. I know that some uh companies work or some other softwares work with um the global salary. So you do the you do the math on

the salary itself and not on the payments. But again, this is a 50/50. So some companies work this way, some others work other way. I think you have to do um kind of a conversion of the rate if you want to get the the right

one. Here we have the numbers regarding the unemployment insurance uh which is AC. You also have ACC. I know this is not applicable anymore since uh 2024 I think but again Swiss told us that um it's not applicable

applicable now but it might come back in the future. So we still have to keep it there.

Interesting to know that here I think for some of my customers um errors were coming from the fact that they deleted maybe by mistake lines here. So it's important to always have one valid line for the period of time that you that you

have. And if you delete it, it will block it anyway at the paylip generation.

So there is no issue here. And on the second tab you have other relevant information which is the yearly maximum salary insured for the unemployment insurance.

And same thing for the ACC which is the complimentary unemployment insurance which is not relevant anymore in Switzerland. And you have the monthly um exoneration that you can have as a retired person that is still working. So this is the monthly one. So 1.4k

uh Franks are deducted uh exonerated monthly for retired workers. Great. So yeah, just to keep in mind that all all that we did now was mandatory for everyone like you cannot skip one of these step in the setup.

There might be some exceptions where um some companies might not have an accident insurance or a or um retirement insurance and this can be defined here where if no if you don't have an accident insurance you have to

specify the reason there so that the transmission goes well. All right. Now another mandatory step that uh of course I forgot is the family compensation fund which is usually the same as your a same actually I I heard a few feedback

asking that if it is it really mandatory or not uh but I think it is yeah legally is a need to have one. Yes, of course there's always exceptions and weird company uh structures which will tell you that they don't require one,

but here we're talking 99.9%. So that is usually the normal case. And we have here um some new features that were also added on the family compensation fund which allow you to define if uh the child allowances are paid directly by

the insurance or by the employer. For example, we know that in Janev you can have the pos there's the possibility where the insurance directly wires money to the employees and it's not uh the employee that does it. So you have to

tick this box and you can define here uh the rate defined by your uh by your family compensation fund. So the company rate here will set to 1%. And you also have an employee rate which is not relevant

for any count except one which is valet. So valet has an employee rate and the employee has to pay um to pay uh a deduction here as well.

And the new feature is here where we have the child allowances scale that allow us to kind of automate your child allowance payments where you can define a child policy where from age 0 to 16 you receive a child allowance of 250

Franks and you can also define a supplementary amount. You can define from 16 to 21 an education allowance of 300 for example. And you can also define more flexible policy of uh from child. These fields allow you to say

that from child number three between 0 and 16 this allowance can increase. So we go to 400 here. So from the third child, the third child will get 200 150 Franks extra.

Yes. So the rules are going to apply all together depending on the case. Yes. Exactly.

Great. And here we are done for uh the mandatory steps and we have no we're not exactly done. The mandatory are done.

But if you have uh source tax, we have an additional step to do. But we'll we'll do the non-mandatory ones because a lot of companies are subject to it which is the complimentary accident insurance and the daily sickness

insurance. So in French we call that the LS which again same thing here we are affiliated uh for the L is the same insurance that does everything 1 2 3 1 2 3 and for the solutions for the rates it's a bit more um tricky and

complicated uh we can define here solutions like A1 on which again same principle A1 will be for example the floor workers A2 might be the office workers B3 might be the uh administrative board etc and same principle two fields from

and to which define the applicability of your rate you have the wage from and wage to this is an important concept here you define um the salary that is insured so usually you can have uh a solution that looks

like this. So from 0 to 148, 200 Franks, you will be insured through this solution and you have the possibility to specify the male rates and the female rates. We do one and one and your employer part. I know that some

convention collective require some very weird percentages here where it's for example 63.234 two, three, four, five, six. So, we implemented of course this feature to allow that. And if you want weird numbers there, you can tick this box, custom employer rates, and you can

define yourself uh the rates that you want to pay as the employer. So, it's not exactly 50/50. Here, you define fully yourself uh how much you want to pay uh on your part. We'll keep it simple for now with the classic 50%

employer part. and we save it. So that was one solution. Of course we want an additional solution where um we define what we call s obligator. So this is the to ensure the salary above the one that we mentioned before and we

will make it go through 400,000 franks. So this solution will will ensure it from 148,200 to 400,000.

And we make it a bit less expensive here. Save. And we get here two solutions for LC for the daily sickness insurance. It's completely analogous. It works in exactly the same way. So I will just repeat the process here.

So we have A1 weight from 0 to 142,000 1 and one and we have A2 from 148,2 to 300,000.

0.4 0.4 That is the complete setup if you didn't hire any foreigners. Great. And so what if we actually what if we hire non-Swiss people? Of course if someone is not doesn't have the nationality they have to pay what we

call uh tax at source. So the taxes the withholding taxes are taken directly from his salary. So we have to define here um the different institutions that we will communicate with for monthly transmission.

So we have here in configuration source tax institution and we will create the one of museum. So if you have employees that live um that live there you will communicate through the institution of discont.

If you have an employee that lives in burn you will have to communicate with these of burn. So this is the institution where the employee that is subject to source tax lives in or of course other conditions that uh change

here but it's it's the institution where basically you will pay the with withholding tax.

So we set up one for Luzan here and we have to of course import the rates for um for our institution. So here we have two possibilities. Uh the manual file import that you can find on this link. That was

the process before we made it simple. So you have here all the different rates uh for different counts for 2026 or so.

Yeah, it's one per year. So it's it's every year it changes or it can change the middle of the year like we saw with VO in March. So you click here, you download the file and you upload it. Of course, that is very

annoying to do. So we developed this automatic import feature and you have the possibility to import everything. It will take some time. So I suggest to only import the ones that you really need. And here we import Luzer.

And of course I think they changed the URL for 2026. So let's import it for 25.

Oops. Okay. We have a little technical issue probably. Yes. But at least you still have the manual way to do it if you want to make sure it works.

Let's try with the manual version. Maybe not. Will take some time. I think I see it.

Of course, this is the beginning of the year uh issues. We'll fix that very soon. So, basically, this is how you import your uh your tax files.

And that was all the setup for um uh your database. But if if you come back to to to the website, you know, with the with the rates, there's one from it's written in French actually. That's why.

Yes, it's a zip file, but you need to open it, I guess. Yeah. Extract two.

in the recent on the left. But anyway, I mean anyway, well, if if we ever make a break, uh we'll just moment but uh I mean you got you got the point.

So here manually or or with the with the link uh in as you as you explained it's probably the link has been updated for 2026 that's why.

All right. I think the rates for 2026 are not even out yet in the you cannot import maybe let me try to import everything.

Ah okay. All right. Okay. We can import every cont for 2026. So you have to import everything. We always have a solution.

Yes. [laughter] All right. So and so once it's loaded. So here I think we made all the steps that were needed for the setups. There maybe one more thing I think that we can check in the settings which is just the

the test for the transmission with Swiss deck. Right. Yeah. All right. It takes a bit of time since we're importing every cartoon and everyone has thousands and thousands of different rates. So it can take a few moments.

So if we just take a look at the next step then. Uh yeah. So afterwards now we need to set up the employees right?

Yeah that is the next step is to set up your employees which is I think the most important step where you set up their personal uh informations you set up um their tax informations if they're subject to source tax. You set

up their uh residency address. You set up their um family situation if they have children if they're married, divorced, etc. you set up um of course the most important how they are paid. Do they have a monthly salary salary hourly

salary? Do we have a special kind of salary where they're paid by commission um non-frequent payments? Uh you set up different situation changes that can occur through the year. What's interesting is that previously before 19 like uh we had to do this in two steps

like first year and then the contract. Now everything is kind of mixed up. So we need we have one one place to define everything. So we managed to import our um tax rates. If you want to check them

for yourself, you go to configuration rule parameters and you can see all the different rates for uh a recon.

If you open one just to see what it looks like. It looks like this.

All right. So there's a the the Swiss the Swiss system has very very small brackets. So compared to other countries where Belgium for example we say from 0 to 20,000 you pay this percentage. Switzerland says from uh uh

from 4351 to 4,040 you pay this percentage. So you have a very well defined uh brackets for the country which kind of makes sense but it's it takes a bit of more bit more time to import in the system.

So yeah, so let's go on with our uh employee management. How do you get through your employees? You have two ways to do it. You have this screen which is employees and of course payroll. You go to employees there. So

we already have one employee one which uh we have different tabs here to get all the relevant informations of your employee. So the first tab is the work.

So here you define the job position or dear Antoine is a CEO. [snorts] He's his own manager of course he's a work address and some additional features of ODU which where you can define the usual work locations and a note for the employee. You also

have different fields here for his email uh different tags that you might want to add. CEO, you you might want to add a very good employee this way. But all of these are still linked to professional information of

course. So here it's the email address of the of the employee but in the company.

Yes, you have his resume, his uh skills if you want. Of course, we're not dive through uh into into detail here. We are here to talk about payroll about very interesting stuff. And here you have um usually the tabs we will focus on for

doing payroll are personal, payroll, insurance and wage statement. These four will define everything you need to uh pay your employee correctly. So you have the birth information with his first name, last name, the social insurance number, his birthday

here and his uh gender. I I have a question here. Maybe it's a bit a bit early but why not asking it still you know like we we have to fill information but still we can save I mean

we can sell the changes that we do. However, I guess that some of the information that are here are needed, you know, for for per computation. So, you decided not to make them mandatory required.

How do you know if you need something or not? Basically, um once you run your u your paylip, your pay runs, if something that is missing um is required and that you need it, um you will see a big yellow box above the

paylip saying uh you're missing this field for the transmission. So you will know if some informations are missing.

Of course we we can make a test a test afterwards just to show you. Yeah.

So his nationality he's Belgian he's working with an annual permit in Switzerland and of course he's subject to source tax and he's not a crossber commuter. His private address he conveniently works right next to the office.

[snorts] up and it autofilled the contour and the commune. It's interesting because here I guess once again that you might mention that afterward but that here the content that I live where where in let's say is going to be used for the computation of

the source text exactly but it could happen that I don't live in Switzerland maybe I work there are there are multiple cases so you have the case where you live in Switzerland in a certain count and you don't have the

nationality so that is where you pay you will pay your uh withhold in tax you could be a crossber commuter and live in France for example, and then the source tax con will be the one of your work location and you could

also be uh living in France but having a weekly residence address in Switzerland. So the source taxon will be the one of your weekly residence address.

All right. So you have a few different cases of how this works. Everything is explained in the Swiss deck documentation. So you can go here in the ampulas and you have very beautiful graphs [snorts] about how it works.

So you have different uh trees decision trees that you can take to uh fill in the right code.

But of course to the to to to get the right source tax cont this is done automatically by odu by the by checking if you live in Switzerland you live in a bordering country you have a weekly work

address as [clears throat] great and just for you to know it's it's also part of the documentation about where you can find it that that explanation in the book and usually um the way fields work here is if uh something is selected other

fields will appear that you need to fill for example here um his marital status is set to single but if I was if he was married you would have um on the right on the right his marriage partner

information that you would have to fill for a tax at source so let's keep it single for now for simplicity something something something that could seem weird here that I mean saying single since start date you know could

be but it's still needed to do so it's still needed you still need to say uh from when is this uh status valid since you could have uh status changes in the middle of the year that could require a a code change for example.

Mhm. And you also have his children information where you can add all the relevant information of the child. So if a child let's call him John he was born today this month.

And you have different fields here that we added since we talked earlier about automation of uh child allowances. So if the child receives allowances uh you will get automatic automatically computed um until one is uh these are these allowances uh due and also for the

education allowance. So until 31 January 2042 he will receive child allowances and you can also define the status of the child which will um do some other extra computation in the back to determine which uh child rate he needs

to take. [snorts] So that was the case if he had a child. Let's not put one for simplicity. And here you have as we talked earlier about the statistic declaration. This is not relevant to everyone but some companies

have to report um statistics about their company. So a statistic declaration is um a declaration that says I have these employees they work uh these jobs this amount of hours per week um they are subject to this contract type etc etc.

So these are the information for example about his holidays per year on a full-time rate of course. So this is the amount of days per year if he was working 100%. The amount of public holidays uh per year his study level

um his job type. So this is again fields that are defined by Swiss deck. So if he's top management, middle management etc. he's top management. Of course, flex profiling is um not mandatory, but again, if you have a pre-aggreement with

the statistic office, they will give you um some categories, for example, admin, which will group them in different categories so that the institution can uh process them easier. And uh two different fields that say if he's a staff for public administrations or if

he's an interim worker. I I just take advantage of that moment to to highlight the use of the question mark next to the field that can bring some useful information for example for the holidays uh like here interesting to know that

it's actually number of holiday days at 100% occupation rate uh so yes think about you know checking also that kind of information because it can help understanding I mean the interface as well so on a lot of fields you will find this

question mark that will uh give you extra information about what to fill in this field of course this is something that we continuously is continuously improve. The goal the goal in the end will have to will be to have a a

question mark on every single field that will explain you in details what exactly it means what you need to fill and what are the consequences of uh of this field and you also have at the end uh different relevant documents that you

can upload for example the ID card driving license etc etc and you also have here uh visa and work permit uh that is uh used a lot in Switzerland and it's uh relevant here with this warning. So based on what you fill in on the uh visa

or work permit uh information, you can have warning warnings about when it will expire etc.

And maybe a question here um that might interest some people and actually I think I saw that question in the chat as well, but it's the right moment to to see it. Um let's imagine, you know, that I get one new child uh during the year

in in March. uh make no sense but anyway how would you recommend us to to create that information? Should I use the versioning of odo 19 to create a new current at the moment with a new information or should I just update my

child tab you know with the new new child. So on the back end it kind of it it will be kind of the same result but for u reporting purposes we have in odo 19 this new way of creating uh what we call

versions. So what a what is a version? A version is um you can see here on the timeline it's kind of a timeline of your employee where you defined from when this information is valid. So here we have from 1st of January you will have

all these informations are valid from 1 of January. So for your case we would need to click the plus button here and add for March.

So 1 of March add the child here and he will be present in March but not in January. Great.

Let's delete that one. Okay. And of course it's applyable on all the fields that are let's say Swiss related.

They it's applied to all the fields that are uh timesensitive. Mhm. So uh if you change your name this will be relevant throughout u all the history. Um if you made a mistake on the birthday it will be changed everywhere.

But some fields that are timesensitive such as the address such as your salary or other benefits they will be versioned um through through this timeline. Great.

So that was his personal information. We now have to set up his uh payroll information which is kind of the interesting part here where you will define what he earns and uh what kind of benefits he has on top

of that and his work hours his uh work location etc. So we start with the workload sheet location. We only have one. So it's odo insider. The employee reference is an this is kind of the fingerprint of the employee um when you

transmit data. So you can put anything you want. It's it's a way to to connect employees um from system to system. So if if you transmit the data in a previous software with this number, it's interesting to put again the same number

in ODU so that uh insurance and institutions can uh identify them uh more easily.

Of course, it makes sense but that reference should be unique by employee. Yeah, it should be unique and if you try to uh have the same number for two employees, you will get a warning on that.

You have the pay slip language. Uh of course here we only have English since we didn't install French, German, and Italian yet. But you can as uh in o install these languages extra. Uh maybe can show me how this can be done. You

add languages here. So French, German and Italian. Italian. Here we go. If you go back to employees, we can now select uh maybe doesn't work with the Swiss ones [snorts] or maybe refresh the page from time to time it. Yeah,

let's see. There we go. We just needed to refresh the page. Let's put the normal French.

And here we have his um occupation. So from when did he enter the company? He started the company on 1st of January.

And he's in a um sedate contract. So he's on a permanent contract with a monthly salary and he's a Switzerland employee. He has a monthly wage of how much do you want?

Uh 10K. 10K. Very reasonable. We save the information. And that will be the basic information. We can choose if he's subject to the 13 month or if he wants an extra 14 month. Let's just give him a 13 month for now. You can choose

the contractual rate of the 13 month. This is equivalent to um one whole salary at the uh moment of payment.

Here you have the relevant schedule informations. So you have the current occupation rate and the weekly hours. These are filled usually automatically by the work location. But if one works 50%, you can choose to either put 20 here

which will recomputee this to 50 or you can choose to put 50 here and uh put it manager yourself 20 there. Important to note here because we received the questions like like for example let's say that I am in 50% of occupation rate

um I mean I need to adapt at the same time my monthly salary of on my on my contract.

This is um a feedback that we got a lot. This is a decision that we made at the start. Maybe a wrong one. Maybe this is something that we can adapt in the future. The salary that you see here

will be the salary paid. So if I put uh 20 there and a work time rate of 50%. Um it will still be 10,000. So this is not the full-time equivalent wage. Of course, this is something that we're

thinking about to improve that a lot of companies and some softwares work that way where if you put 10,000 here and 50% there, you expect 5,000 on the pay slip.

But for now, this is the amount that you get on your printed pay slip. So, let's see keep him at 100%.

That was his uh work time rate information. Of course, you have the case where you don't really know uh how many hours per week the employee will work. So, we can check this box which is the irregular working time. So, this is

for example for a security guard that uh might work only on call uh when he's needed. So, you don't really know uh when what his weekly work hours will be. So, you check in this box. And of course this is

relevant information for um uh mainly for the computation of the source tax and you have at the bottom uh kind of the most interesting part.

Yes, where you can add what we call the monthly wage types. So the month what are monthly wage types? There are additional salaries, additional inputs that will um appear every month on the pay slip. So you can have truly we have

hundreds of them. So this is everything we have. Um we can have for example a monthly uh commitment allowance of uh 300 Franks. You can choose to give it a different name.

Yes. So this will be the name that will be displayed. This will be the name on the base lip.

And you could have for example what else can we put him a residence allowance of 150 Franks per month.

So as you as you say it's per month that's what we define here will be applied every single month where we generate bas. Yeah, we also have the possibility to add nonmonetary amounts.

What do we mean by that? We can see on this column the unit of what this wage is. But we don't only have monetary amounts. We could have for example um paid overtime hours at this rate. And you see here hours and we say that

Antoan does 10 hours every month that are paid overtime and that will be calculated as well. Do I need maybe a stupid question but do I need to activate like my hourly hour salary in this case if you want to of course

there's ways to compute automatically the equivalent hourly rate of um monthly salary but um for now it is not implemented yet. This is something that uh we got feedback from and we'll try to implement because it's it's a bit tricky since uh you can

have multiple ways of defining uh an equivalent hourly rate. So for now it is a manual input where you can check the hourly here and define the relevant uh hourly rate.

All right. So we'll do this example for another hourly paid employee. So another type of unit that we have is the percentage of course.

Yeah of course. Um we have um a wage type called here is it's called general a deduction in percentage. What is this used for?

very important. This is something that you should note. It's used for all the different uh deductions that are specific to certain count. For example, um in Janev you have lamat 0.04%.

And here the unit is a percentage. You can also define the company part at 0.04%.

This is how you define um generic deductions uh for your employee. And we had uh in the past only those two available. So this triggered some um potential accounting issues where you could not define credits and debits for

different uh deductions. For example, you could have uh another one. Which one? Um uh P for me.

Be careful that you took actually the same one. Yeah, I don't this is part of the example.

Okay. This this what this is what you used to do in the past. So in the accounting you would have this one and this one merged into one which was an issue. So to solve that we added um we actually added

a few of them so that you have some uh some uh maneuver space uh in terms of accounting. I heard that this is not enough. Maybe we might need more. So I guess we will have to add more in the

future for this. Great. I mean this table here is really where we got most of the questions and feedback I think during the year and that's why I think also the documentation can be useful for you because there are a lot of examples of

use cases that we met on the on the market and how we actually answer them by using those wage types. Maybe one thing more is that here I think we define monthly wage type as you said that going to be applied every month. Is

there a way to set one wage type for one single month? Let me first um because I think I forgot. Let me first introduce what a wage type is because I think we kind of skipped that point. So what is a wage

type? A wage type is um a payment something that is added to the salary, some line on the pay slip that will have uh different characteristics in terms of uh what you pay on it in terms of insurance, what you pay on it in terms

of source tax and where it is displayed on the salary certificate on the wage statement. to check all the available wage types in Odo. You have in configuration wage types and here you'll see all the relevant information of uh

my wage types. So you can see the debit and credit accounts. You can see um here I think it's because I zoom too much.

Yeah, you will see all the this is kind of the uh DNA the fingerprint of uh each wage type. So if you see salary by task you can see that this is added to the gross it is subject to a payments. It is

subject to L payments, LC, EGM, source, STS where it is taken in the wage statement section and different things relevant here which is um you will see you have all the explanations there about what this means. So if you do a

statistic declaration this will be taken into account in uh this category. if it's um if it uh contributes to the 13th month, if it contributes to the 13th month for hourly employee, if it contributes to the vacation payments and

uh I think you have a few other ones where uh you can set up different LP information.

So here I guess that everything is preset up but of course uh I can already forecast question in the chat asking can I create my own one?

Yes, can I do my own one? So for for the moment, no, you cannot create a new one. But I'm pretty sure most people when they try to create a new one, it just means that they didn't find it in there. So they didn't really

search for the one that they need and they might think, "Oh, I need this new one." Of course, there has been instances in the past where we um we didn't have a specific one and we added it. So if I get the fe feedback a few

times that this one is missing and we really need it. This can be done through either contacting support or business analysts saying that this is a wage type that is really needed for a lot of companies and ODU will add it and it

will be updated instantly from our side and and can we okay so that's for let's say creating a new one and so a feedback can be created as simple as simply as you know as creating a support ticket to

do um is is it possible I mean for them a question that we received as well to just edit an existing one you know to to adapt some parameters. Of course, we have the debit and credit account that

could be adapted for debit and credit can be adapted. There's a few there's a few fields that can be adapted. For example, I know that for the vacation payments, some um again convulsion collective have different rules. So, you

could say that in your company um this one is subject uh this one contributes to uh the vacation pay. So, you can take it there without an issue. But if you start to mess with other fields there um

it will be on your side that an error has been made and it will probably be uh this is reset back to the standard every day no matter what changes you make. So you cannot really make changes on the

core stuff here uh above. So that was uh for the question of what a wage type was and what you see actually on uh this small list.

This is actually all the inputs that are possible in your uh monthly pay. So Antoan asked this is the monthly recurring ones. How can I make punctual ones? How can I say u in March you will get a commission of €10,000? Well, this

is done through this menu. You have this little uh money sign here. onetime payments.

Maybe you can zoom zoom back a bit more. Sorry. We go back. Maybe not so much.

We go back to Yes. 150. Great. So, we go back to um this button here, one time payments.

And you have here a calendar view where you choose where the monthly wage tab will be uh will be appearing. So I want for March a commission for his uh extra work of 4,000 and same system you can add a a

customized um name on the base slip. We save it here and we have there the commission. Uh so it could be any day of that month.

It could be any day of that month. It doesn't matter. It's just the calendar view is made in this way in Odo. So you just pick a day in the month and it doesn't really matter.

And uh you have here this is a new menu that exists. You have a way to check all the wage types of all your employees through uh here reporting monthly wage types and you can see uh to who it was assigned

and um the amounts and you can see if it's a one-time payment or recurrent payment and of course you have all the capabilities of autoo filtering and searching. So I can group by type. I can see all my recurring

payments. I can see all my what payments. I can group by employee. And you have all this uh and of course you have the pivot table that you can uh export or insert in spreadsheets. You also have one possibility

if you want to add wage types for um a lot of employees at the same time. For example, if you have uh a big team of salesmen and you would like to say you have a big spreadsheet of uh commission

amounts, you could use the ODO import feature to say that for these employees, you will import um a commission of different custom amounts from your spreadsheet.

All right. So, I think we went through um the whole payroll section. Yeah. Okay. Seems good.

What's next then? Next we will define your insuranceances. So we configured pre previously uh different insuranceances. We now have to set them up on the employee.

So we set up his we can say if he has a special status. So if he's um for for for now this is a manual process where you have to define youth for example that is for people that are under 18

year old. This is a feedback as well that we get often to maybe compute this uh automatically based on the birth date. This is something we're looking into because it can be a bit errorprone to set up this manually.

Mhm. You have the exempted feature where if an employee makes less than 2,200 around that, I'm not sure about the exact amount, he's not subject to a vious uh uh compensations or if he's retired and he has the right to the monthly

1,400 exoneration or this is a new thing that comes with uh the ELM 5.1 certification. This is a new um a new law that passed uh recently where you can be retired but renounce to your uh monthly uh deduction. Meaning that if

you want to um aggregate more money towards your pension later, you can say I'm at the retirement age but I choose to not take my uh uh exoneration. So this is what you would choose here. But of course, Antoine is still young, so

he's not retired yet. We choose his compensation fund, his group. Well, here we come back to what we discussed earlier, right?

Here we come back to our uh insurance, accident insurance. So, we discussed previously here that you can choose to pay zero or 50 there and you might want to pay 100%, you might want to pay everything for your

employee. This is done through this section where you choose the LA solution type. So on the configuration you define a group but you have a group and a type.

What is a type? A type is something that is general to all companies that says this is um the policy of this employee regarding his solution. So you can be type zero meaning not insured. For example, uh the board of IND

administration might not be insured against uh work accidents. You have the classic one which is uh occupational and nonoccupational insured with deductions meaning that you will pay what you defined here.

Mhm. So you will get the deduction of the nonoccupational part at 50%. Or you can be occupational and nonoccupational insured without deductions.

What does what does without deductions mean? It means that nothing is deducted to the employee for his accident insurance. But someone has to pay. So it will be the company here that pays at 100% no matter what you define in your

settings there. Or he could be only occupational insured. This usually happens for example for employees that work less than eight hours a week. There will only be insurance against work accidents. So in this case neither the company nor the employee will pay um

nonoccupational accidentizations cization. So we take the classic one here of one and we can choose here his additional insuranceances which are the additional accident insurance or the daily sickness which are the only one that that can actually not set but the rest for now

was the rest for now is mandatory but you could have um of course exceptions but here uh we we have to set his additional ones. We defined two types of solutions for each. Here you can maximum define two solutions.

So we define here A1, A2, A1, A2 for both. So that was the main ones. Now we have to define his uh pension insurance that we define there. And we have here a lot of options.

So um this is re relevant for transmission when did he enter the company? This is computed based on the occupation dates that we defined earlier. uh we have the LPE codes. So this is the code that we defined

previously. Antoan is in production and you have here the LPE payments. So Antoan um is paid monthly. Not too complicated. You can you can know how much uh he will pay uh through your insurance. So we can define um an

employee contribution and an employer contribution. But we can also have what we said earlier this amount in percentage. So for example you can say 10% and 10%. You might ask 10% of what exactly? Well this is the magic behind the feral engine. it

will be 10% of the um LP basis which is computed with uh different rules and um it might not be exactly 10% of the gross salary obviously because some wages might not be um might not contribute to the LPP some wages might be exempt from

it so this might differ from your gross but um of course everything is done uh automatically for you in the back Of [cough] [clears throat] course, Antoan is uh we said earlier that he's a Belgian citizen. He doesn't

have Swiss nationality. So, he has to pay his withholding taxes immediately in the pay slip. What that means is that as I said earlier, when you tick some boxes, check some options, some new stuff might appear that you might need

to fill in. For example, if I untick this, the source tax tab will disappear.

But if I put it back, we get this back here. So there's always this kind of hide what you don't need logic in uh or in our employee kind of a dynamic overview indeed an interface. Yeah.

Yeah. So of course withholding tax is uh kind of complicated. So um we have here uh all the different informations that we need to fill. So we have the tax scale type which is the most common one where you choose what

he's subject to. Here he's a so scale for single single people. You have the eligible children deduction. So um why do you need to fill this manually? Why not just take the children on the menu there? Because in some cont you might

have weird rules where you have one kid but it counts for two so you put two here. So we kind of chose to let this key manual. [clears throat] So uh we don't guess by magic. Uh you have

different informations about the code here if you subject to the Swiss church tax which will change the code here from A0 to a zy and you have you can here specify that this code was uh specially approved by

the administration there. You also have uh different informations here such that the such as the religious demonation which is required for the monthly transmission to the uh tax office. You have the working days in Switzerland which usually is 20 over 20.

But if you work 10 days in Switzerland and 10 in France, you will only be subject to withholding taxes on the 10 days that you worked in Switzerland.

We have also this new feature where you define the telework percentage. This is only relevant to French cross borders where it's mandatory to transmit since uh um I think it's mandatory from this year. I'm not sure but this is something

that will come where you define for example for French cross borders what percentage of work was done from home.

Mhm. You can also define if um you have other jobs somewhere else because this impacts the computation of source stacks and you can say for example that you can specify the details here. You either don't know or you know that he works uh

50% air wells or you can say around uh a gross um monthly income somewhere else. For example, you have you make 3,000 um Franks in another job.

So everything on this window will kind of impact the computation of uh source stacks. I think there was a question in the chat indeed about that small table at the bottom with the mutations.

Yeah. What could it be linked to? So this is um um these are the mutations that we have. Of course this is relevant to transmission.

We have entry, withdrawal and mutation. So based on what changes uh on your employee um things will appear here. Um for example uh there should appear entry in company here.

If I do a declaration here um for my monthly transmission of January uh it will say that uh Owan joined the company now and he's subject to source tax now in my company and if I change some informations for

example regarding marital status I can try here I'm not sure I think I'm missing some setup somewhere if I change his marital status there I got married happy me happy Yes, you have here that this thing that appeared automatically which is a

mutation of his civil status valid from 1st of February of course automatically computed from the timeline up there.

So and afterwards it will be used as you mentioned for the transmission. Exactly. When you do the transmission of February, of course, we have to change the code as well since you got married, you became B.

And uh on the transmission of February, you will uh it will be said to the tax administration that changed his civil status for this month.

All right. Uh well I think there is one more thing now to define on the employees. Yes, we're still missing the wage statement.

Um again maybe it's a bit annoying to define it yourself every time. So we're thinking about uh automatically assigning the main one to each employee every time so that we can avoid the mistakes. But here you can choose uh the

previous template that we defined. So one certificate that will get filled with all the informations that we we defined earlier but we have the flexibility to make some small adaptations for you. So I will not give you free meals or lunch you will be

hungry uh at 12. So here we define a specificity for one there. I have a question because I think previously when we were on the definition you when we created the template uh I saw a button at the top uh mentioning update all the

read templates. So obviously if you define your template uh at the beginning then you create 100 employees and you realize oh I made a mistake there. Do I have to go change it manually on every employee? Of course

not. We have this button here that will update uh every employee that uses this template with uh the corrected uh information.

Great. I think we are good [clears throat] in terms of setup. All right. So now if I assume good so we should go for the pive generation. We can go for the pace of generation but we can also create a few more employees

with uh different uh other different stuff or thing is that I think we have only 40 minutes remaining. So let's go on with the baselip generation.

So how does it work? Um in the baselip menu you have this new thing called pay runs. New pay run for the month of January.

Continue. We select our employee and we have here our parent with relevant informations. So we can see here.

Great. Okay. I forgot to set up this. Well, we can talk about the warnings.

Yeah. [snorts] So we said earlier that if you make mistakes, they will appear here in bright yellow. So in this case it's not really a mistake related to payroll but it's a mistake related to our uh the accounting side where we didn't define a

journal account on um on our uh structure structure. So we can define here the salary journal salaries. Oops.

Yeah. Save. And so it it automatically disappears. It automatically disappears. If you don't see anything here you don't have any obvious mistakes. Let's imagine that I forgot there to input for example what could we forget um residence or

residence yes you will see here missing and taxon so you go back to the employee personal [snorts] yes and let's go back to uh to normal.

Something that is really important here is that warnings should be very important for the users like you need to fix it all of them before.

Yeah. And you will see it here on this column issues that uh shows you globally uh which paylip are which employees are problematic here and which ones do you need to fix.

Great. So we have the paylip there. We have uh different tabs. Um you have here the monthly wages which is the wages related to what work he has done. So you have the monthly salary but you could have other ones such as uh hourly

salary, overtime, salary in case of illness, accident etc. You have a lot of them actually.

I have maybe a question as we mentioned that part. I think I'm going to be sick next week.

Uh or can I record that uh efficiently? Efficiently you can uh either do it preemptively. So you have the time off button here and you can say that uh um this week you're putting a time off. So you have different time off options. You

have unpaid leave, illness. There's a a few time offs that have impact on the salary.

So yeah, it is the illness leave from 12 to 16 5 days. And we have um a few options here regarding your time off.

So we have the continued pay. So this determines what percentage of the salary will be paid during this period. It could be 100%, it could be 80% based on your insurance policy. You can define also the disability percentage. So this

takes the uh prrated amount and prrates it again. Mhm. So this gives you a bit more flexibility.

Let's say that we are 100 for both. We submit the request and if we go back to uh our pay run you will see that automatically uh the wage got uh prorated. So you see that here you have the you have the salary in

case of illness of this amount and you have the normal salary. If we had done let's cancel this one create it again. If we had done 50%.

We can see here that it took the what you should have been paid and divided it by two um with the factor here.

Great. Uh of course here we can do it and it's as you said dynamic because the basic is still in draft but if it was confirmed of course you would not be able to if it was confirmed obviously you cannot

um change the amounts. So the way to add the time off after your pay run was closed is either to cancel um the pay slip and recreate it or just to defer you defer the time off to the next

month. Here we see all the relevant um uh inputs that we defined previously. So you have the LPE contributions. You have the different um allowances that we defined earlier and the generic deduction.

You have the detailed fully detailed salary computation where you can see every single computation line.

There's a lot of them here. It could make people a bit afraid but of course they need to know that this is just for their own purpose to understand.

This is the this is a bit of a backend look of what happened um in the computation. I think this is very useful for uh fidiciaries for example that want to check numbers check that everything was completely computed correctly but of

course on the final pay slip not everything will appear not everything will appear we can print it and we have here the final pay slip.

So we have the name, address, a few informations and uh what the employee will receive at the end.

Interesting to know that actually you define that I was speaking French. So you the basic is not displayed and printed in in French.

Yes, of course there's a few uh do we have any non-ransation one? I think this one this one is still okay but yes we might have some uh for example when we add a wage type mid year um there might

be some delay in the translation to other languages but usually it comes pretty fast. So that was the the printed pay slip.

So we check that everything is fine. What do we do? We create the draft entry and yeah once we confirmed it we have other warnings for uh this paylip. We have missing bank account. So for you uh we

still have to define the bank account on your employee and that's because of course the next logical step is to proceed with the payment.

Yes. So if you have sepa activated for example and you want to generate your sea file that you send to your bank you need to specify the bank account. here we didn't install it so we just marked them as paid. So that was the process to

run your uh January uh month. So that was the whole pay flow. We now get to the interesting part which is the transmission.

So we defined our insuranceances, we define our work location, we define our source tax institutions, we define our employee uh his personal information, how he's paid, his specific in uh insuranceances. We now have to um send this data to our institutions. So

everything happens in this button transmission and you have um a few of them. So it's divided in um two kind of transmissions. You have the ones that you do monthly and you have the ones that you do yearly at the end of the

year. So the monthly ones are the entry withdrawal mutations. Not everyone has to do it but it's called the EMA declaration. Basically what it means is that you declare to the Aves CF and LP that this employee entered, this

employee left or this employee um changed his personal informations. And of course all of this is done um automatically from what you filled in in his personal information. So all you have to do is prepare data, select the

relevant month and year. you can do a test transmission beforehand so that this is not um um sent in real production.

So what does it mean test transmission? If you check it and click on declare it means that if you check it and declare salary it will be kind of um a fake just a fake send a fake transmission to

the institution that will not process the this data at all. So here we can declare the salary and what we see here is the declaration object. We have one action possible is to get its status because it just got

sent and we need to check it status. One important thing is that every transmission um that is sent and received is logged in the chatter. So you have the exact transmission file that was used to the institution and the

exact transmissions file that was received from the institution. So this gives a um a nice auditing uh logs of everything. So we send it. We now get the status and we can see that it's finished for the uh it was a success success

success and you have different options regarding the transmission. You could have um um for example if you do for Pepe success we can see the details here of what happened uh or employees for the calf uh we have an extra step.

We need to do a completion. So what does completion mean? It means that clicking this button will redirect you. Of course, this is a sandbox, so it's not real production data. But usually, if you click completion, it will redirect

you to the website of your insurance where I need to fill in maybe some extra information. And you can always fetch the result success. You have all the different warnings that were sent from uh the uh insurance and uh all the declaration

information. You could also have what we call a a dialogue message. So this is a feature that I'm kind of proud of. Um [snorts] a dialogue message is the institution that send a message for you to fill im

directly into ODU. So you can see here the message that was sent by the institution.

Madame Mu blah blah blah and you can fill in uh different informations there. So this can be um this is super flexible. So the institution can create any type of message, send it to you and you reply back in Odo directly.

Great. So that was the global idea of how transmission works just to because there is one button that I did not see. No, come back to declaration. The the first one yeah the replacement declaration but what so replacement declaration means you

made the declaration but you realize that you forgot an employee. Okay, you made a mistake. So what you do is you make a new one, check this button, this box, and you decide I want to substitute this declaration by this new

one for January. So that was for the what we call the EMA. Of course, not everyone does it, so it might not be relevant to everyone.

Now you have the source tax uh declaration for January. Antoan is Belgian is a Belgian citizen. he paid taxes to the cont of lousern. So we prepare the data here and we detect that we have one employee that is subject to

a source tax here. We can do here what we have is uh the possibility to generate the report. So we click the button there.

Will it be yes loaded in the chatter? Yes, that's right. And it will be loaded uh in the chatter for this month. And this is the classic Swiss deck um report that you see in every uh payroll software because we all

have to use the same format here. So you can see uh onto one here his entry in the company, his occupation and time and uh the amount of source tax that he paid for this month.

As I think about it, um transmission that we are doing now should be done by customers users I would mean in production database, right? Yeah. not in testing. So, but they can do test transmission in production.

Um actually in production what you can do is test transmissions but if you are for example an OSH user and um you have staging branches then you can easily generate the reports here as well. This is something that we added extra we

added the possibility to generate reports in testing environments. So all right this is fine there but in production you can do test transmission beforehand if you're not sure about uh uh your data. So same process here. All transmissions are equivalent to each

other. You declare the salary. You get a status and you see every time the the relevant institution for that uh declaration. So you can either complete here or you can fetch the results. And if you fetch the results, it says

release is missing. It means that you still have to go through uh your uh website the website of your institution fill in the extra info and wait again for the response.

And the third monthly u declaration is the statistic declaration. Um again same principle we have here all the relevant statistic data. We have a better statistic report but um sadly Swiss didn't yet make a report for um this version of ELM we are waiting for

it. So in at the moment where it's released you will be able to uh generate the statistics report but currently this report type is not yet supported by uh by Swiss deck.

So in this menu you you can see that we also have u the sax corrections. What does that mean? It means that maybe Antoine, you didn't tell me the truth in January and you were actually married and uh you should not have been a but b

on your code. So what we can do what we have to do is to correct it on the next relevant month. So we create what we call uh sax correction for reason liar and this is what you call a correction.

We have the correction type here. So this is a correction that we um do on the company side that we create ourselves because we realized there was a mistake. The institution didn't catch it yet. So we have to do it on our end.

And we have two possibilities of doing a automatic correction or a manual one. Automatic one is preferably easier.

Let's first change onto's information because he lied. So, he's actually married. Let's do this fast.

We fill in his spouse information. that his part doesn't have income. We go back to the correction for Antoan reason he lied.

Yeah. And so the correction is of course applied before we actually already generated the base for January. If if it was the case, we could January was applied. It was paid. It was not transmitted with source stack. You

cannot do uh retroactive stuff in the past. You cannot cancel. It's already paid. So what you have to do is to correct in the next relevant month. So we select January.

We can see the original code and automatic means that it will take all the previous slips apply the current information and recomputee everything such that we have the original old amount that is corrected and the new amount uh for the current month command

corrected. So we confirm that's all you have to do and once we generate did we change his uh B here not yet we do B when we create the parent of February pro one we will see in the pastlip that a

correction is associated with it and if we print it we will see an adjustment that was made for Antoan. So actually um this is beneficial for him since he's married. He pays less taxes. So he's refunded for what he paid extra in the

previous month. And you can see um the details in debug mode of what happened on the source stacks in the back end. So basically you have the old amounts that were all cancelled recomputed with the correct information and added back and the difference is

paid in the next relevant month such that when you validate your parent and you do the transmission for February, you will see that the old amount was uh cancelled.

Mhm. And the new one for that month is readded. So you have the new code, the new amounts uh that he should have paid.

Great. Okay. Good. So this is how a correction work. If you need to do um weird changes, if you want to do manual changes, you have to select manual. You can choose the relevant pay slip and you can choose to change every amount

manually if you wish to. But for uh usual uh processes usually it's you forgot you you took the wrong code or you had the wrong count. So you do automatic uh correction uh in this way.

So that was the monthly transmissions. We now have uh the yearly one, the big interesting one that happens in uh from December to January.

We didn't generate uh the whole pay slips for the month but it's not an issue.

Here I got a question about this because you know it's a yearly declaration but still we need to select the months. What does it mean in practice?

It means in practice that um it will um this is kind of um to be used as an internal tool. So if you select here uh June is to have the reports from January to June with the relevant salaries but

kind of the year to date. Yeah, you can have the year-to- date information of your reports and um you don't have to transmit it. You can use it as a reporting tool to generate your reports.

So, um you will have here um all the relevant uh institutions. So, for the year yearly report, we have the social insurance, family composite food, accident insurance, additional accident and daily sickness. You have the different uh crossber details. We don't

have any cross border in company so it wasn't checked. And we have the wage statements.

I have a question here. I think that that I heard also in the past. Uh when we generate that declaration, we do it for all the employees of the company. We cannot choose one specific employee that you want to generate.

So it is a bulk declaration for everyone in your company. So you can choose to select the report. Let's generate them one by one.

Yes. Yes. And so every time they are added in the chatter as a we don't see it because we are a bit zoomed but you can see them here at the bottom. If we are like this maybe you

can see more clearly. Mhm. There. So we have for each report the classic one you see in every software here.

And the prettiest one, the W statement that we can see here generated automatically with uh Odo.

Great. Yes. Perfect. So again, same process. declare salary get status and we have all the relevant information for all the responses that were uh received by the institution.

I have maybe a question what is the create eiv file button at the top.

So this is kind of a um technical process. Mhm. So in the case where the Swiss deck transmitter itself doesn't work, so there's a downtime from Swiss itself, what we can do is a manual upload of uh our declaration. So the EAV file

in the chat. Yeah, in the chat there is um basically the declaration itself. So you download it and I think it's uh I'm not sure about the website itself.

Um, I think there's a there's a link somewhere. There's there's a link of Swiss deck. I need to find it. I will put it in the documentation where you upload this file and basically it's like you it's the

same process as doing here declare salary but you do it outside of the software because the transmitter has an issue on Swiss site. So we have to do it manually. So this is a requirement that they added in the case of downtimes

where you can create these decoration files manually and upload them on a specific website designated for that.

[snorts] So good about it. [clears throat] Oh, we also have um another transmission which is the yearly one to the LPE which can happen in January or um in April sometimes where you declare uh your LP basis for your monthly employees and um

you can declare the salary get a status you get an answer from the LP pay itself and this allows you to actually receive receive the amounts directly from the insurance and you can import them through this button. Of course, this is

not production data so it will not work but you can for your monthly employees import the contribution of your employees immediately in the contract.

[snorts] We also have the possibility to correct salary certificates if you transmitted them in December but you realize that uh you made a mistake in an option.

You have the option to choose the previous declaration original date uh the rectification type. So it can be a global replacement or an individual replacement for each employee.

[cough] Okay, it seems good. I think we discussed the world transmission topic. Yeah. And I mean there is 15 minutes left.

Maybe we can dive into the questions and see. I think we answered a part of them already. Um but okay, let's start with the first one from Terry.

Yeah. So that was um what I mentioned earlier you have this admin fees thing. So what we said is that um this amount is uh on the cotization and not the salary. So if you work on a salary basis and they give

you a rate for the salary you would have to do a a rule of three I think to convert the rate uh since um we can convert the rate from salary to cisization. is just a a little math equation to do it. It's it's a bit

annoying. I think in the future we'll add the possibility to uh choose if you want to do it on the salary mass or the payments itself. Okay. Okay. So just for everyone to to know, so Terry question was about yes the basis amount I think

for that admin fees percent either like the total salary or the cotization salary but yeah okay that's clear and second point about the the family compens yeah that's it I think.

Yeah easy. Yeah. Family conver here as I said here the the question asks for a third child. So from the third child 0 to 16 child allowance 400 and you have here supplementary amount 100. Yeah.

Yeah. It should answer the question as well. Okay. And another question from Lauron about restaurants and yeah a specific commercial collective.

The percentage depends on the salary and not the age do you mean? Well, for now I don't think uh this can be handled through odo. I think I've I've seen a ticket about this uh in the past where

you have kind of matrixes of where the percentage is applied to the salary and the age because usually uh the LP percentage says from 18 year old to 25 you pay this percent from 25 to 35 you pay this percent. But for now this is

not handled uh you know do yet. No. All right. Um, next question from Terry.

Um, yes, where can we change the family data? I think that part we Yes, we mentioned it with the versioning also.

It's everything happens in the versioning. So, you see here the date of the current version. So, this information is relevant from January 1.

If you want to make a change for March, you say in March and you just change your information there.

So single up. So in March single and in uh January married. So you can follow here um the changes that were made.

Mhm. And you can see them on the list view and add of course any field you want uh in there to see kind of what happened during the year.

All right. Next question from AM asking about the LPS FAM. Uh can it can it be let's say encoded with the 5474?

Well uh LPF first of all is uh will not be declared to Swiss deck. How it works for the AS is that Swiss deck only is interested where is it?

Swiss is only interested by the salary. So the whole salary that he received subject to a so the the amounts paid itself are not transmitted to the institution. The only thing that is transmitted is the salary itself. So um

there's no issue here to transmit LPV since it's not transmitted in the first place.

All right. Okay. So so they can use that that's to wage types to to encode it then.

Yeah. Um another question from Terry that we answered at the beginning about which fields are mandatory for the employees.

You will see uh on the baslip big yellow banner saying and also on the parent uh on the issues here if something is missing or it's wrong.

Mhm. All right. Uh Lik has asked three questions I think. First one is about you mentioned about the wage types. Is it possible to create new ones? um asking for for example let's say if they have some flexibility I think it's more

mostly general feedback but our answers was mostly for now we don't recommend to create new we don't recommend doing it but if you're technically well well informed and um if you maybe consulted it with me uh uh before but you can easily create

one it's possible to create it if uh you set up in a certain way it will be transmitted in that way so in that case you will not break the system and you will not break the certification but you

have to know that um if you create something it will not it will not be updated by us. So if something changes in the law, you're in charge of updating yourself if um this wage type change for example.

Another question that you ask is about let's say the I mean as as you mentioned at the beginning of December we made an update of uh of the Swiss uh deck module.

Yeah. In ado and yeah I think it's more a feedback about how to communicate uh the updates and how they are done. It's for now we are still let's say improving oursel on that side. We try to communicate as much as possible. Um

first of all in terms of uh legal updates and certification updates everything happened from the everything always happens from the first version where it was certified meaning 17. So if we do a legal update it will be updated

from 17 and onwards every time. And uh this happened through the standard Odo update process which happens every Monday or in case of really urgent needs. It will be of course deployed immediately with our uh infrastructure team. So um yes there's a communication

issue here with our updates. We can uh we have in the plans to make a um a release note release note section maybe in the documentation section where um every single update that is done um is clearly stated uh what happened what was

changed and maybe what will change in the future for planned updates. But it's right today. One practice that we can still advise uh could be to think about uh of course maybe not every week but okay if you ever doubt if you are still

up to date just to update then the the ELM module in the apps uh to make sure that you are with the last uh available version.

Yeah. Okay. And question about the ELM 5.4 5.5. Yeah. So released we released 5.1 and 5.3 recently. Uh I read the specifications of 5.4. 4 5.5 but I think it's um smarter to wait 6.0. The draft release has been sent to us about Elm

6.0 that will come at the end of the year. So maybe it's better to focus to keep it like this for now and wait in the future to do the uh 6.0 certification maybe in the future where um it will include 5.5.44

and other additional features. So of course if uh this module is a success we'll obviously uh keep updating the standards for uh payroll in Switzerland.

Great. Um have a question from Siri as well asking how to import I think wage types let's say massively for each employees we we show it also as well.

Yes, well we define it here for example uh I didn't show an hourly uh employee but if someone is paid by hour 40 here you have to define uh in a recurrent manner the paid hours for this employee

for example 144 but if this changes we said earlier that they can be defined through one-time payments and onetime payments can be imported here so you would have to import your Excel here with uh the column employee B the waist

type paid hours and the amount of paid hours and if you import this import this every month you will have uh the monthly paid hours for each one of your employees indeed. So that's if you prepare like your Excel file uh pre let's say

beforehand you can just then fill it in every month and then import it very easily. So yeah you just have to get familiar with the import export mechanism of ODO and this should be fairly uh fairly easy.

All right. Uh Nicholas was asking as well a question. Could you please also show us the reporting? In particular, I would like to see the payroll run reporting and the complete monthly monthly payroll data.

Uh yes. So I think the most uh the prettiest one where you can see everything is um reporting basic lines. So here you have the year-to- date information of the current year of every single wage type uh in your database.

So you can see here for each month uh every amount that was generated uh you can insert this in a spreadsheet do pivots do groupings everything basil you can filter also on an employee for example employee is equal to one and I will

check all the pay slips of one here. So this offers uh all the capabilities of uh of uh ODO pivot reporting. We also have a few reports here. You have the monthly summary.

So we can aggregate by company or by employee and you can download the PDF here. It's true that I should have showed this kind of interesting. You will see the monthly summary.

You also have uh the master data. What is this? This is everything that was relevant to your company at this moment.

So you have two things. The master report and the wage type report. The master report is all your uh insurance information with all the different rates that you defined. And the wage type report is the current state of wage

types at that moment uh in regards of what uh they should be uh uh subject to in terms of insuranceances.

What's the purpose of such reports? Is it like for audit or it is for audit? It is for historic historical purpose to have a kind of a PDF trace of everything. But of course in odo these things can be achieved

through pivot views as well. But uh Swiss deck makes it mandatory to have somewhere to define it uh as a PDF. And you also have the individual accounts um for your employees and so you have the individual account

of the indiv individual account for the whole company. So I think this takes a bit of time.

Yeah, I think it's a crown that's going to So basically it's the document. It's it's it's basically this document but for the whole year and uh with every uh single wage type and you'll have one globally for the company and one for

each single of your employees. What do we have else? Yeah. Yeah. Okay. You also have the occupations um where you can see um here everyone that entered or left your company. So Antoan entered in January 1. If I had another employee um

there that entered another moment you can see there or if Antoan got out and entered back you will see two lines here for Antoan uh for his different occupations.

So those are kind of the reporting capabilities right now of uh of peril. Great. Well um I think we just arrived at the end of the Swiss related question. I still see questions in the chat you know about some other topics as

a reminder that we I mean we won't skip your questions but you can address them for next week you know because it will be a regular Q&A session at at that moment. Uh but I think that for today

and for Swiss it's that's it. Thank you very much again for your time for uh answered all that question and uh yes we then we we see each each other next week let's say for the next Ou insider and uh

and yes have a nice day.