AddisFly - Attendance & Overtime — Why Your Hours Look Wrong

Six of the open complaints in the register are this: "attendance issue", "attendace & overtime issue", "I worked all night and it shows nothing". Almost every one turns out to be one of five causes, and you can tell which in about five minutes.

How a day is actually calculated

Attendance is built from your check-in pairs, not from your first and last tap:

  • Worked hours = the sum of each in→out pair. A gap in the middle (lunch, going out) is not counted.
  • Regular hours = up to your shift's end time.
  • Extra hours = time worked past your shift's end. This is what becomes overtime.
  • Late minutes / early-exit minutes are measured against the shift on that day's Attendance record — not against the shift you think you were on.

Shift times as configured today:

Shift Hours
Booking — Day (Early) 08:00 – 17:00
Booking — Day (Late) 09:00 – 18:00
Booking — Saturday (AM) 08:00 – 12:30
Booking — Saturday (Late AM) 09:00 – 12:30
Booking — Saturday (PM) 12:30 – 17:00
Booking — Night (Pre-Midnight) 17:00 – 01:00
Booking — Night (After-Midnight) 00:30 – 08:30

Overtime rates

When the extra hours fall Rate
Morning / afternoon / evening 1.5×
Night 1.75×
Your weekly off day 2.0×
A public holiday 2.5×

Overtime beyond 60 minutes needs approval before it is paid. Below that it is approved automatically. Approval is the step that usually delays payment — 154 requests worth about 354 hours are sitting unapproved right now. "Pending" does not mean lost.

The five causes, in the order to check them

  1. The wrong shift is on the day. This is the most common. If the Attendance record says Saturday-Half-Day on a Wednesday, your lateness and overtime are both measured against 12:30 and everything looks wrong. Check the shift field on that day's Attendance.
  2. A missing check-out. One tap missing and the day cannot be paired, so hours come out short or the day reads Absent. File an Attendance Request for that date; do not re-tap days later.
  3. The overtime is waiting for approval. Open your Overtime Request list and read the state: Draft, Pending, Approved, Rejected. Pending is with your approver.
  4. A night shift crossing midnight. A shift that starts in the evening belongs to the day it started. Attendance for it is posted the next day by design — roughly a one-day lag, not a loss.
  5. The day was treated as a holiday when it was not (or the reverse). Holidays are per branch: Addis and Mekelle have different lists. If a branch-only holiday sits on the shared list, a normal working day pays as holiday overtime, and that gets corrected later.

What to send when you raise this

A complaint that says only "attendance issue" cannot be worked and will come back to you with questions. Include:

  • the date (or dates),
  • what you actually worked — first in, last out, and any break,
  • what the system shows — hours, status, or the overtime figure you expected,
  • what you expected instead.

The clearest example in our register is ISS-2026-00198: "I worked from 8:00 AM Monday until 6:00 AM Tuesday." That is a usable report — it names the dates and the hours.

Who fixes what

Problem Who
Wrong shift on a day, missing punch, wrong status HR
Overtime pending approval Your approver, then Finance
A holiday on the wrong branch list HR
Pay already issued against a corrected day Finance — corrections go through the current period as an arrear, never by editing a paid slip