Clocked In but No Workday or Available Limit Increase: Causes and Solutions

Short answer: After clocking in, workers need to distinguish three stages: the action has been recorded, the record has appeared in the system, and the workday has been approved. Only completed and approved work can be included in the calculation of the amount available through earned wage access. Therefore, clocking in successfully but seeing no increase in the available limit does not necessarily mean the workday has been lost.

If the data is not visible, check the correct workplace, date, and shift; determine whether the attendance data comes from the app or the client's attendance sheet; wait for the appropriate synchronization cycle; check the approval status; and then send evidence to the correct point of contact. Do not create multiple records to "make up" for missing work, as this may create duplicate data and make reconciliation more difficult.

> Note: Synchronization times, attendance approval SLAs, and support procedures may vary by business. Users should follow the information and instructions displayed in the app at the time of use.

First, identify the situation you are experiencing

Do not use a single statement such as "my workday is not showing in the app" for every situation. The more accurately the status is described, the more quickly the support team can identify the bottleneck.

Data flow from clock-in to the earned wage access limit

```mermaid
flowchart TD
A["Attendance data generated"] --> B["Match worker, client, date and shift"]
B --> C["Record pending approval"]
C --> D["NK supervisor or client approves"]
D --> E["Approved work and eligible day"]
E --> F["Deduct amount already received and held amount"]
F --> G["Update available funds"]
```

Only one incomplete step in the chain can prevent a worker from seeing an increase in the available limit. Therefore, check the process from left to right rather than looking only at the final amount.

Where does earned wage access get attendance data from?

(See 6 attendance methods on earned wage access.)

The system has verified three groups of data sources. Each source has a different processing speed and workflow.

1. Direct clock-in through the earned wage access app

The app supports selfie + GPS, geofencing, dynamic QR codes, Bluetooth beacons, WiFi, and the Check In/Check Out buttons. A record is created in real time when the action is valid.

"Real time" means the data is recorded immediately; it does not mean the workday is automatically approved. The record must still go through the verification process.

2. Client attendance sheet through Google Sheets

Clients can enter or export attendance data to Google Sheets for the system to retrieve. The verified synchronization schedule is approximately once every 30 minutes; supervisors have an option to synchronize immediately.

If a client has just updated the sheet, the worker may not see the change before the next synchronization cycle. The 30-minute interval is the current technical schedule, not a guarantee that every record will appear within exactly 30 minutes—the data must also be valid and match the configured structure.

3. HR data from Nhan Kiet ERP

The ERP provides worker lists, clients, employment start/end dates, and management relationships. The verified synchronization schedule is 03:00 daily.

The ERP is not simply an "attendance sheet." If a worker's profile has not entered the system, has been linked to the wrong client, or has an incorrect employment status, the attendance record may not connect to the account currently being used to log in.

What are the key data-matching identifiers?

(For background concepts, see What is approved work?.)

The system does not identify workers by name alone because multiple people may have the same name or names may be written differently. Two important verified identifiers are:

• Citizen ID number: identifies the worker and is used for login and matching the profile, payslip, and attendance records;

• Client attendance code: connects the worker to the attendance record for the correct workplace.

Clients are identified by company_id/the client code from the ERP. When a worker works for multiple clients, attendance must be linked to the correct client; it should not be combined arbitrarily.

15 reasons you clocked in but no workday or available limit increase appears

1. The action was not successfully submitted

A weak network connection, closing the app too quickly, or disabled device permissions may cause the user to tap the button without the server receiving the record.

How to resolve it: Open your attendance history first. If there is no record and the app confirms that the previous attempt failed, try again once using the correct attendance method.

2. The wrong client or workplace was selected

Workers who work at multiple locations may accidentally clock in under the wrong client. The record then may not appear on the screen being viewed or may not match the shift being calculated.

How to resolve it: Check the client name, location, attendance code, and shift on each record.

3. The wrong configured attendance method was used

Each client selects the appropriate attendance method. A Check In/Check Out action does not automatically replace QR scanning if the workplace is configured to use QR.

How to resolve it: Confirm the instructions at the workplace and see Article 32 on the six attendance methods.

4. Clocking in outside the shift window

QR codes and shift rules may restrict the permitted time. Overnight shifts that cross midnight must also be assigned to the correct business date, rather than simply using the calendar date shown on the clock.

How to resolve it: Record the actual time, shift name, and screenshot of the notification; contact the supervisor if the shift schedule in the system is incorrect.

5. The record is waiting for synchronization from Google Sheets

The client has entered the attendance data, but the system has not yet reached the cycle for retrieving the new data.

How to resolve it: Check the latest update time; wait for the appropriate synchronization cycle or ask the supervisor to use the immediate synchronization function when necessary.

6. The attendance sheet does not match the configured data format

The system supports multiple formats, such as symbol grids, daily time grids, overnight shifts, U.S.-style dates, and 12-hour time. However, the data must still match the reader configuration set for the client.

Changing a column name, adding a new merged cell, using an unfamiliar symbol, or changing the date format may prevent part of the data from being recognized.

How to resolve it: If multiple workers are missing attendance after the Sheet template was changed, the client or technical team should check the sheet format; do not ask each worker to clock in again.

7. The attendance code does not match

The attendance row may exist but contain a different code from the one linked to the worker's profile.

How to resolve it: Compare the code in the client's attendance sheet with the code in the NK profile. Corrections should be made at the correct source by the responsible person, rather than simply changing the displayed name.

8. The ERP profile has not synchronized or is linked to the wrong client

New workers, workers who have recently transferred locations, or returning workers may not yet have the correct synchronized status.

How to resolve it: Nhan Kiet HR should check the citizen ID number, employment start date, client, active status, and latest ERP synchronization.

9. The record has appeared but has not been approved

Clocking in creates input evidence; an Nhan Kiet supervisor or the client must confirm that the work is valid. The approval step is completed when an authorized party provides valid approval.

How to resolve it: Check the status and send the request to the correct approver. Do not ask the payment team to "increase the limit" while the work is still pending approval.

10. The record was rejected

Possible reasons include an incorrect location, incorrect shift, missing Check In/Check Out time, an unacceptable image, or data that does not match the actual situation.

How to resolve it: Request the rejection reason, provide additional evidence, and follow the adjustment procedure. Do not create multiple new records to hide the original record.

11. Approved work was edited and returned to pending approval

The system has a control mechanism: when the check-in time, check-out time, or shift of an approved record is edited, the status automatically returns to pending approval and the before-and-after changes are logged.

How to resolve it: Check who made the edit, what was changed, and request re-approval. This is a mechanism to prevent silent changes, not a loss of work.

12. You are viewing today or a future date

Earned wage access blocks today if the day has not been finalized and blocks future dates so that workers cannot receive money for work that has not actually been completed.

How to resolve it: Distinguish an attendance record for an ongoing shift from a finalized workday. Wait for the shift/day to be completed and pass the approval step.

13. Approved work is subject to a reserve hold

A client may configure a hold on the latest N workdays and/or 10.5% when the advance reaches a threshold. The held amount remains the worker's earned wages and is processed in the payroll cycle, but it is not yet available for early access.

How to resolve it: Review the workday details, amount already received, and held amount. Do not refer to the held amount as a fee.

14. The newly generated amount has not reached the minimum threshold

The default minimum amount per transaction is VND 50,000. A small amount of work may already have been calculated, but the total available amount may still be below the threshold required to create a request.

How to resolve it: Check the detailed amount rather than looking only at the receive-money button. Configuration thresholds should be confirmed by NK when published.

15. The worker has already received the available amount for the period

The calculation deducts the amount already received during the period. When additional work is approved, the available limit increases only by the new amount after deducting the held amount; it does not return to the original total earned wages.

How to resolve it: Reconcile the transaction history, approved work, daily rate, and held amount.

5-minute self-check process

Step 1: Check whether the record exists

Open your attendance history and select the correct client, date, and shift. If a record exists, do not clock in again.

Step 2: Identify the data source

Confirm whether the workplace uses the earned wage access app, the client's Google Sheet, or another synchronized system. This determines whether you need to wait for an update cycle.

Step 3: Read the status

• No record: check the action, source, code, and synchronization;

• Pending approval: contact the approver;

• Rejected: read the reason and provide additional evidence;

• Approved: move on to checking the available-limit calculation.

Step 4: Check whether the date is eligible

Confirm that the date is not today before finalization or a future date. For overnight shifts, check the assigned business date.

Step 5: Open the amount details

Reconcile approved workdays, daily rate, amount already received during the period, and reserve hold.

Step 6: Contact the correct point of contact

Do not send every issue to one department. Attendance data, worker profiles, client configuration, and payments have different owners.

Who should you contact for the fastest resolution?

Template for requesting a missing-workday check

> I need help checking my attendance data in the earned wage access system. Full name: …; employee ID/attendance code: …; client/workplace: …; date and shift: …; actual Check In/Check Out time: …; attendance source: app/Sheet/client system; current status: …; latest update time: … . I have checked the correct workplace but still cannot see the record/the available limit has not changed. Please have the responsible team check and provide the reason.

Attachments should show the date, time, status, and error message; please hide the citizen ID number, account number, and unrelated data.

Responsibilities of each party in the attendance data chain

(See also: Why is the earned wage access limit zero or not increasing? and Earned wage access process from clock-in to reconciliation.)

Workers

• Use the correct attendance method, location, and shift;

• Check the history after clocking in;

• Report discrepancies promptly and provide truthful evidence;

• Do not clock in for someone else or use location-spoofing tools.

Nhan Kiet supervisors

• Monitor records pending approval;

• Handle exceptions and provide reasons;

• Check attendance codes and client assignments;

• Coordinate with clients when source data is incorrect.

Clients

• Maintain attendance sheets and on-site configuration;

• Approve or reject with valid grounds;

• Record data changes;

• Do not edit approved attendance without an explanation.

Operations/technical team

• Monitor synchronization;

• Alert users to changes in sheet formats;

• Log errors;

• Enable traceability from the source record to the calculation result;

• Do not make assumptions when the data source is unclear.

What should the system display so workers can understand it themselves?

A transparent attendance screen should show:

• Data source;

• Client/workplace;

• Date and shift;

• Check In/Check Out times or attendance symbols;

• Status: recorded, pending approval, approved, or rejected;

• Person/team currently responsible for action;

• Latest synchronization time;

• Reason the data is not included in the available limit;

• Edit and approval logs;

• A pre-filled check-request button containing the record ID.

Notifications should clearly state the next action. For example:

> The workday for September 2 is waiting for client confirmation. The record has been received by the system but has not yet generated available funds. You do not need to clock in again. If the working hours are incorrect, submit an adjustment request before the workday is approved.

Conclusion

"Clocked in," "record created," "work approved," and "available funds generated" are four different statuses. Understanding this chain allows workers to identify the actual issue instead of assuming that work has been lost simply because the available limit has not increased.

Check the following in order: correct client—correct source—correct synchronization cycle—correct attendance code—correct approval status—correct eligible date—correct limit calculation. If the issue remains, send the record ID and evidence to the correct point of contact. A transparent process should make it possible to trace data from the original source through the approved workday to the final amount.

References

• Law on Personal Data Protection No. 91/2025/QH15

• Decree No. 356/2025/ND-CP guiding the Law on Personal Data Protection

---

Author: Ngô Nhã Kỳ — editor, Nhan Kiet Manpower Supply Co., Ltd.

Consultation for businesses: Hotline 0937.022.655 · Email info@nhankiet.vn · Earned wage access solutions for businesses