Attendance and shifts in the factory: what pplPortal automates immediately

At a garment factory in the Vale do Ave with 120 employees, the HR manager was losing 8 hours a week reconciling clock cards, correcting record errors and calculating overtime in spreadsheets. Three errors a month generated fines from the tax authority (AT). The problem was not a lack of discipline — it was that no one can process 120 daily records without software. This guide shows what pplPortal automates straight away, and why most factories that implement it reduce manual work by 90% within 4 weeks.

Why this matters: the real cost of manual calculation

In 2023, the average voluntary turnover in Portugal was 10.6%, with 52% of companies admitting difficulty in retaining talent. One reason no one talks about is operational frustration: when HR spends 40 hours a month on spreadsheets, there is no time to talk to employees, identify climate problems or anticipate departures. Software frees up that capacity.

In addition, the Monthly Remuneration Statement (DMR) to the tax authority requires absolute accuracy. One miscounted overtime hour across 120 people × 12 months = real tax exposure. We see in INFOS projects that factories which automate this reduce AT rejections from 3-5 per year to zero.

What you need before you start

• Access to the current attendance control system (card, biometrics, mobile app or manual).
• Clear definition of the shifts and working hours in place (fixed, rotating, part-time, night).
• Rules for calculating overtime, weekly rest and public holidays — Portuguese legislation + collective agreements specific to your factory.
• List of employees with personal data, professional category and hire date.
• Access to the HR module of your ERP or to the current personnel management file.
• Confirmation that Social Security and the AT have your data up to date (avoids DMR rejections).

Step 1: Map the shifts and calculation rules — the shop-floor truth

Before any tool, document what actually happens. Many factories have shifts on paper, but the reality is different: informal swaps, unrecorded extensions, breaks that vary with production.

Define each shift precisely — start time, end time, break duration, days of the week. Record the exceptions: who works 6 days, who has reduced hours, who is in training. Calculate the cost of an overtime hour (25% uplift on working days after 8 hours, 50% on public holidays and Sundays). Identify the public holidays and the mode of compensation (time off or payment). Confirm the reference period for calculating weekly rest (weekly or monthly, according to your collective agreement).

We see in INFOS projects that this stage reveals, on average, 3 to 5 discrepancies between the contract and practice. Correct them before implementing any system — otherwise, the software will only automate errors. A typical textile factory discovers that the night shift has a 45-minute break on paper, but in practice it is 20 (because production does not stop). If you do not correct this, the system calculates hours that were not actually worked.

Step 2: Choose the attendance capture method

pplPortal integrates with multiple sources. Choose the one that best suits your operation.

If you have biometrics or RFID, pplPortal connects directly via a standard protocol. If you use a mobile app, integration is via REST API. If you still use paper, start by digitising — even if it is a simple form in Google Forms with validation. A food distribution company we implemented started with Google Forms, then migrated to RFID — what matters is having structured data from day one.

Step 3: Configure the calculation rules in pplPortal

This is where the software saves hours. Instead of manually calculating each month, define the rules once and the system replicates them automatically.

Enter each shift with start time, end time and break — the system automatically calculates normal hours. Configure the overtime uplift: 25% on working days after 8 hours, 50% on public holidays and Sundays (in line with the Labour Code). Define the mandatory weekly rest: 1 full day or 2 half-days per week. Activate absence validation: sick leave requires a certificate (deducts 0%), unjustified absence deducts 100%, justified absence deducts 50%. Integrate national and local public holidays — pplPortal has a pre-loaded calendar for Portugal.

Whoever does not document the rules in the software ends up doing manual calculations in parallel — and when there is a discrepancy, no one knows which is the truth. Then there are complaints about the payslip, and HR loses credibility.

Step 4: Validate and correct historical data

Before generating payslips, import the data from the last 3 months and compare it with what the system calculates. Export the attendance records from the previous system (biometrics, card, sheet). Import them into pplPortal in test mode. Generate an attendance report and compare it line by line with the previous payslip.

Identify the discrepancies: uncounted overtime hours, incorrectly recorded absences, manual adjustments that someone made and forgot to document. Correct the data in the system before marking it as "validated". This step avoids surprises when the first payslip is generated. A typical textile factory finds 15-30 errors at this stage — nothing serious, but they need correcting before payment. A garment factory discovered that it had been paying overtime to employees who were in training (with no entitlement). The system caught this in the historical data.

Step 5: Automate payslip generation

Once validated, pplPortal automatically generates the payslip based on the attendance records. Configure the base salary, meal allowance, transport allowance and other allowances per employee. The system calculates: normal hours, overtime hours, social security and income tax (IRS) deductions, paid public holidays, allowances. Generate the payslip as a PDF or integrate directly with your ERP — if it is ERP MULTI, the connection is native and the payslip comes out with automatic accounting entries. Validate the payslip before processing: total hours, deductions, net pay.

Step 6: Comply with the Monthly Remuneration Statement (DMR)

The tax authority requires the DMR to be submitted by the 5th working day of the following month. pplPortal automatically exports the data in the accepted format. The system generates the XML file in line with the AT layout (remunerations, deductions, contributions). Validate the data before submitting: NIF, employee number, period, totals. Submit via the Finance Portal or automatic integration (if you have a digital certificate). Keep the submission receipt — important for audit.

Without automation, this process takes 4-6 hours a month. With pplPortal, it is reduced to 30 minutes of validation. A distribution company we implemented was able to eliminate the "external HR consultant" who visited monthly — the software does the work she used to do.

Step 7: Monitor discrepancies and alerts in real time

pplPortal offers real-time dashboards. Configure alerts for employees with more than 10 accumulated overtime hours (legal risk — Portuguese law limits this to 200 hours/year). Absenteeism rate above 5% (an indicator of a climate or health problem). Unjustified absences (to contact the employee on the day). Shift discrepancies (clocking in/out outside the expected time — may indicate lateness or early departure). Missing attendance record (employee did not swipe at the reader — could be forgetfulness or a technical fault).

We see in INFOS projects that teams which monitor these KPIs monthly reduce payslip errors by 85% and improve legal compliance. A metal factory discovered that a worker was clocking in 30 minutes early every day (to accumulate hours) — the dashboard caught this within 2 weeks.

Implementation checklist

• ☐ Shifts and calculation rules documented and validated with operations, HR and an employee representative.
• ☐ Attendance capture system chosen and tested with at least 10 users.
• ☐ pplPortal configured with all shifts, allowances and deductions.
• ☐ Historical data (last 3 months) imported and validated — zero discrepancies with previous payslips.
• ☐ First payslip generated and compared with the previous one (line-by-line validation).
• ☐ DMR tested and submitted to the tax authority — receipt kept.
• ☐ Attendance dashboards activated and assigned to the HR manager with weekly review.
• ☐ Shop-floor team trained on the new system (5 minutes per person, visual guide next to the reader).

Common mistakes and how to avoid them

Mistake 1: Implementing without clarifying the internal rules

Many factories have informal practices — "João always works 30 minutes extra", "Monday is always with a reduced break". If you do not document it, the software cannot replicate it. Solution: meet with operations, HR and an employee representative. Document every exception. If the practice is illegal (e.g. work without recording), correct it before implementing — the software cannot be complicit in irregularities.

Mistake 2: Not validating historical data

Implementing the system and generating the first payslip right away without comparing it with the previous one is risky. If there is an error, you have already paid 120 people incorrectly. Solution: always import 3 months of history, generate comparison reports and correct discrepancies before marking it as "go-live". A garment factory that skipped this stage needed 6 weeks to reconcile errors.

Mistake 3: Forgetting the ERP integration

If pplPortal generates the payslip but someone then copies it manually into the ERP, you lose the automation and create discrepancies. Solution: if you have ERP MULTI, activate the native connection (Multi Connect). If you have another ERP, configure automatic export in a format the ERP accepts (XML, CSV, or REST API).

Mistake 4: Not monitoring overtime and absenteeism

The system calculates, but no one looks at the alerts. Result: employees accumulate 50 overtime hours in a month (legal risk) and no one knows. The absenteeism rate rises to 12% (a sign of a problem) and no one acts. Solution: assign a dashboard to the HR manager with weekly review. Configure automatic alerts (email or SMS) when a limit is reached. A textile factory implemented this and discovered that absenteeism was concentrated in one specific line — it then discovered that the line supervisor had left and no one had filled the vacancy.

Mistake 5: Not training the shop-floor team

If employees do not know how to record attendance in the new system (biometrics, card, app), there is rejection and errors. Solution: run a 5-minute session with each shift. Leave a visual guide next to the reader. Have a "power user" per shift to answer questions. A distribution company we implemented had 3 shifts — it trained one worker per shift, and those 3 became system ambassadors.

What comes next

Once attendance and shifts are automated, most factories discover they can move on to scheduling and skills management — linking production targets to HR data, identifying who is performing below expectations, and anticipating problems before they affect the line. pplPortal also offers pplAdvanced (schedules and skills), recruitment and performance appraisal — all with predictive AI for turnover and absenteeism. See how other Portuguese factories use this to reduce operational costs and improve climate.

Frequently asked questions

Does pplPortal work with any attendance control system?

pplPortal integrates with biometrics, RFID card, mobile app and even digitised paper sheets. Integration with biometrics or RFID is direct via a standard protocol. If you use a mobile app, the connection is made through a REST API. If you still work with paper, it is recommended to digitise first, even if it is a simple form with structured validation.

How long does pplPortal take to implement in a factory?

It depends on the capture method. Biometrics takes 2-3 weeks, RFID 1-2 weeks, mobile app 1 week. Mapping the shifts and calculation rules comes before any tool and is critical to success. Validating historical data (last 3 months) is mandatory before generating payslips.

What is the cost of implementing biometrics?

The initial investment in biometrics is between €2,000 and €5,000. It includes equipment and maintenance. Despite the higher cost compared with RFID, it offers impossibility of falsification and fully automatic recording. Some employees may have privacy reservations, which requires clear communication from the company.

What is the Monthly Remuneration Statement (DMR) and why does it matter?

The DMR is the mandatory statement to the tax authority with remuneration data. It requires absolute accuracy, especially on overtime hours. One miscounted hour across 120 people over 12 months generates real tax exposure. Factories that automate reduce AT rejections from 3-5 per year to zero.

What information do I need to have before starting with pplPortal?

You need: access to the current attendance control system; a clear definition of the shifts and working hours (fixed, rotating, part-time, night); rules for overtime, weekly rest and public holidays in line with Portuguese legislation and collective agreements; a list of employees with personal data and hire date; access to the ERP's HR module; confirmation that Social Security and the AT have up-to-date data.

Why is it important to map the shifts before implementing software?

Many factories have shifts on paper but the reality is different: informal swaps, unrecorded extensions, variable breaks. Mapping reveals, on average, 3 to 5 discrepancies between contract and practice. If you do not correct them beforehand, the software only automates errors. For example, a 45-minute break on paper may be 20 minutes in practice — the system would calculate hours that were not actually worked.

How much time does pplPortal save in manual work?

At a garment factory with 120 employees, the HR manager was losing 8 hours a week reconciling cards, correcting records and calculating overtime. Most factories that implement pplPortal reduce manual work by 90% within 4 weeks. This frees up HR for strategic tasks such as talent retention and organisational climate.

Sources

• Portuguese Labour Code (Law no. 7/2009, of 12 February, amended by Law no. 23/2012) — regulation of working hours, overtime, weekly rest and public holidays
• Monthly Remuneration Statement (DMR) — Tax and Customs Authority (AT), accuracy requirements and tax compliance
• ISO/IEC 27001:2022 — security of personal data in attendance control and biometric systems
• National Statistics Institute (INE) — Turnover and Labour Market Statistics in Portugal (2023)
• Collective Labour Agreement — Textiles, Clothing and Garments (ACTVC) — sector-specific regulation of shifts and overtime compensation