Extract Clock-In, Overtime, and Late-Night Hours (出勤・残業・深夜) from Any Japanese Attendance App Screenshot — Without Retyping a Month by Hand
KING OF TIME renders attendance as a dense punch-card grid; freee, SmartHR, and JobCan wrap the same legal categories in modern dashboard cards. Manually typing one employee's monthly record takes about 3 minutes, while this reads the same six fields in 5-10 seconds (18x faster), from any of the four apps, in one batch.
5-10s per screenshot · Up to 99% accuracy on printed text
Six Time Fields a Japanese Attendance Screen Splits That a Western Timesheet Doesn't
Regular, overtime, and late-night hours each hit payroll at a different multiplier, and a Japanese attendance app screenshot is where the apps split them apart. Japan's Labor Standards Act requires employers to record working hours objectively, so each category is tallied separately. Name these six columns once and the AI pairs each value with its Japanese label on any of the four apps.
The date attached to each punch record
24-hour clock-in punch, often corrected by managers afterwards
24-hour clock-out punch; may read past 24:00 on midnight-crossing shifts
Ordinary hours inside the statutory limit (8 hours a day, 40 a week)
Work beyond statutory hours, paid at the 125% tier
22:00–05:00 window, paid at 150% when it overlaps overtime
One attendance screen produces a row like this, with overtime and late-night kept apart rather than merged into a single "Hours" column:
| Work Date | Clock-in | Clock-out | Working Hrs | Overtime | Late-Night |
|---|---|---|---|---|---|
| 2026-07-15 | 09:02 | 21:48 | 8:00 | 2:30 | 0:30 |
More Time Categories Than Any Western Timesheet — Frozen Mid-Approval
Japanese attendance apps pack in time categories a US or UK timesheet never separates: regular hours (所定労働時間), overtime (残業), late-night premium (深夜割増), and holiday work (休日労働) each carry a different pay multiplier, with 125% for standard overtime, 150% for late-night plus overtime overlap, and 135% for holiday work. Managers can also correct punches (打刻修正, dakoku shūsei), so the screenshot captures a moment in the approval pipeline, not a settled fact.
"If you don't have minashi zangyou in your contract, clock in and apply for overtime. Keep a log of your clock ins. If they don't pay, take it …"
— r/japanlife thread on a company with suspicious attendance practices
That comment is standard advice in Japan-related forums: clock in, keep a log, and prove the hours. The app's attendance screen is that log, and a screenshot is the copy that survives a company portal shutdown after you leave. The catch is that these screens were built for managers to review, not for employees to export.
Why Japanese Attendance Screens Break Template Tools
Every category carries its own multiplier on one screen. Regular, overtime, late-night, and holiday work each feed a different rate, and freee's attendance export even splits statutory-holiday late-night (法定休日深夜) into three separate tally columns (休日深夜所定時間, 休日深夜所定外時間, 休日深夜残業時間) for payroll. A template with one "hours" column cannot represent the split.
Punch correction freezes an ambiguous state. Managers edit timestamps after the fact. The screenshot shows the original punch, the approved time, or both, depending on where in the approval pipeline it was captured. A row-anchored parser picks one value and throws the other away.
Two UX extremes render the same law. KING OF TIME shows a dense monthly punch grid; freee, SmartHR, and JobCan present the same statutory categories as modern dashboard cards. A positional template trained on one breaks on the other, and on the next employer's choice of app.
How the AI Reads Japanese Time Records
Name the column in English; the AI matches the Japanese label. Type "Overtime Hours (残業時間, zangyō jikan)" and the model finds the value paired with 残業時間 on a KING OF TIME grid, or on a freee card. The label defines the field, so the layout stops mattering.
Categories stay split, not merged. 残業時間 and 深夜時間 land in separate columns, so a month of mixed regular, overtime, and late-night work stays analyzable, and you can sum overtime independently of regular hours, the way payroll treats them.
One batch across all four apps. A KING OF TIME punch grid, a freee dashboard, a SmartHR card, and a JobCan list fill the same six columns in one export, and a screen without a field leaves that column empty rather than guessing.
From a Mixed-Format Attendance Month to One Filterable Overtime History
Capture the Screen While You Still Have Access
Open the monthly summary: KING OF TIME's 月別データ (monthly data), a freee attendance dashboard, a SmartHR card, or a JobCan list. Screenshot the full record, corrected-punch markers (打刻修正) included. JPG, PNG, or WebP. Leaving a company revokes portal access, so grab the months you might need first.
Name the Six Columns Once
Type Work Date (勤務日), Clock-in Time (出勤時刻), Clock-out Time (退勤時刻), Working Hours (勤務時間), Overtime Hours (残業時間), Late-Night Hours (深夜時間). If a screen shows both original and corrected punches, add "original" or "approved" to the column name to pin the value you want. The AI reads each label-value pair on any of the four layouts.
Download One Row per Attendance Screen
Each screenshot becomes one six-column row: twelve months of KING OF TIME, freee, and JobCan screens become a clean overtime and leave history you can filter, sum, and hand to a labor consultant or use to verify 残業 pay. About 5-10 seconds per screenshot versus 3 minutes of typing (18x faster). Export as XLSX or CSV.
What an Attendance Screenshot Can Prove — and What It Cannot Do
The extracted spreadsheet is a faithful record of what the screen shows. Here is where that is enough, and where the attendance record still needs a human or a payroll system.
When It Works Best
Clear, full-resolution screenshots from any of the four apps. Machine-rendered time records reach up to 99% accuracy on readable punches.
KING OF TIME, freee, SmartHR, and JobCan mixed in one batch. The same six columns work across the dense KING OF TIME grid and freee's card UI, and the AI reads by label meaning, not by layout.
Building a months-long overtime and leave history. Batch twelve monthly captures and compare 残業時間 and 深夜時間 month over month, or across two employers using different apps.
When to Be Cautious
The tool does not compute overtime pay or verify 36協定 compliance. It extracts what the screen shows: it cannot calculate 125% or 150% amounts, apply the 60-hour threshold, or confirm the company's Article 36 Agreement (36協定) caps are respected.
Punch corrections (打刻修正) make the screenshot a point-in-time view. Before approval you see raw punches; after approval, edited ones, sometimes both. Name the column "original" or "approved" to pick one; the AI records what is displayed.
Midnight-crossing shifts (日跨ぎ) and unit formats are extracted as shown. A shift past midnight may display a clock-out past 24:00 (the apps write these as 25:00, 26:00, and so on) or split across two dates, and the AI keeps what the app shows. Some apps print half an hour as 0.5, others as 30分; both are read verbatim, so specify the unit in the column name if you want it normalized.
Frequently Asked Questions
Can I extract Overtime Hours (残業時間) separately from Working Hours (勤務時間) when they sit in different columns on a KING OF TIME screen?
Yes. Japanese attendance apps tally time categories independently: KING OF TIME keeps 所定時間 (scheduled working hours), 残業時間 (overtime), and 深夜時間 (late-night hours) in separate columns, each feeding a different pay multiplier. Type the two column names separately and the AI reads each label-value pair on its own, so Overtime Hours and Working Hours land in distinct columns of the same row.
My manager corrected my punch (打刻修正), so will I get the original Clock-in Time or the approved one?
Whichever the screen shows, recorded as displayed. Punch correction is common in Japanese attendance apps: a manager edits the timestamp after the fact, and the screen may show the original punch, the approved time, or both. If both appear, name the column precisely, "Clock-in Time (original)" versus "Clock-in Time (approved)", and the AI pairs each value with its label. The tool records what the app displays; it does not decide which one you are owed.
My shift crossed midnight (日跨ぎ), so how does a single Work Date handle it?
The AI extracts what the app shows. A midnight-crossing shift appears in KING OF TIME or JobCan either as an entry on the start date with a clock-out past 24:00 (written as 25:00, 26:00, and so on) or split across two dates. A single Work Date column carries the date the app attaches to the record. If your payroll splits hours across dates, add a second column and name it explicitly. The AI will not reassign hours between dates on its own.
One screen prints 30分 and another shows 0.5 for the same half hour, so what format will I get?
The value exactly as the app printed it. Some apps render 30 minutes as 0.5 hours, others write 30分, so your spreadsheet may mix notations. To normalize, add the target unit to the column name, for example "Overtime Hours (decimal hours)", and the model converts 30分 into 0.5 during extraction.
Does the tool verify my overtime is within the 36協定 limits?
No. The Article 36 Agreement (36協定, sanjūroku kyōtei) caps overtime at 45 hours per month and 360 hours per year, with a special-provision ceiling of 100 hours per month, 720 hours per year, and an 80-hour monthly average over any two-to-six-month window. The extracted spreadsheet gives you the raw 残業時間 numbers to check those caps yourself. Summing a month of overtime from the export takes seconds, but the tool does not flag a crossed limit or compute what you should be paid.
Return to the work & HR app screenshot overview for paystub, PTO, benefits, and attendance extraction across ADP, Workday, Sage, and Japanese/Korean HR apps.
On the UK side of the same employment record, gross pay, PAYE tax, and tax code from Sage and Xero payslip screenshots extract with the same column-name approach, but far fewer time categories to split.
And for the money side that attendance feeds into, gross pay, deductions, and YTD totals from ADP and Gusto paystub screenshots round out the US equivalent of this record.