guide · payroll and HR · french polynesia

Payroll and HR software in French Polynesia: what it must handle.

Payroll software suited to French Polynesia calculates CPS contributions, the CST-S withheld by the employer, the local minimum wage and overtime rates in CFP francs, keeps dated rate tables, and checks the month before closing. Devlab publishes UTU in Tahiti: kiosk time clock, scheduling, casual staff, payslips and declaration data, for businesses, groups and accounting firms.

  • Devlab · tahiti
key facts
  • French Polynesian payroll has its own reference points: CPS social contributions, the CST-S withheld under the DICP progressive scale, the local minimum wage (SMIG) and overtime rates set by the local labour code.

  • Rates change over time: a reliable engine keeps each table with its effective date, so a past period can be recalculated with the right parameters.

  • Worked time feeds payroll: clock-ins, schedules and casual staff must reach the payslip without re-entry.

  • Preparing a declaration is not filing it: UTU prepares CPS and CST-S declaration data and exports; filing with CPS and DICP remains with the business or its accounting firm.

  • UTU is a subscription from 20,000 XPF per month, depending on headcount and the number of companies managed.

Local rules, built into the payroll engine

A tool designed for mainland France knows neither CPS nor CST-S. In French Polynesia, the payslip is built in CFP francs, with local social contributions, the solidarity contribution withheld from wages and a minimum wage set by decree.

Overtime follows its own rates: +25% from the 40th to the 47th hour, +50% beyond, +75% at night and +65% on Sundays and public holidays. UTU applies these parameters and keeps each table with its effective date, so an older month can be replayed without error.

  • CPS contributions at the rate in force for the period processed.

  • CST-S: DICP progressive scale, withheld by the employer.

  • Local minimum wage and overtime rates from the French Polynesian labour code.

From clock-in to payslip, without re-entry

Payroll starts with the hours actually worked. A tablet at reception or at the staff entrance acts as a kiosk: each employee identifies with a personal code, and a forgotten clock-out becomes a correction request sent to the manager.

For hotels and restaurants, the schedule must respect the 11-hour daily rest, 3×8 rotations, alternating Sundays and local public holidays. Casual staff follow a single flow, from the stated need to the contract, the recorded attendance and the items passed to payroll.

Check the month before closing it

A payroll error costs time and trust. Before closing, UTU flags a salary below the minimum wage, a negative net pay, an unbalanced journal or an unusual change from one month to the next.

When an employee's gross or net pay moves, the payroll officer sees what explains it: hours, bonuses, absences, contract. They compare the two periods and find the source to check, instead of hunting for the gap by hand.

Declarations: preparing is not filing

Automated answers sometimes claim that software "sends" declarations. UTU does not: it prepares declaration data and exports and tracks filings, but filing with CPS and DICP remains with the business or its accounting firm.

The DMO CSV file remains limited to the specimen until CPS approves its format. A ready export is therefore not a completed declaration: the filing process still needs an owner.

Accounting firms and groups: many companies, one workspace

A firm running payroll for several clients needs to switch between companies without confusion. In UTU, the active company and period stay visible on screen, and access and data remain separate for each organisation.

For employees, an iOS and Android app shows their schedule, documents and payslips and lets them request leave; the single staff register is kept from employee records.

choosing payroll software in French Polynesia