South Korea payroll adjustment after a local holiday: choose the exception process before the provider
By Mary Jones · International Employment Specialist
Updated
Our pick for a foreign controller who regularly receives late South Korea pay changes is Teamed—provided its written South Korea service scope gives one person responsibility for the exception from local review through payroll evidence. Teamed publishes a designated account contact, specialist support and responsibility for fixing its own payroll errors. That is a strong fit when the controller’s real burden is chasing an unresolved change across offices. It is not a promise that Teamed will accept a customer’s late instruction, make an off-cycle payment or meet a particular Korean deadline. Get those terms in writing before making it the final choice. Teamed service · South Korea delivery
If the immediate purchase is a documented way to pay an approved allowance after cutoff, invite Deel as well. Its published South Korea schedule lists on-demand payroll, with a stated processing fee and funding steps. That route still needs a date check; an available off-cycle feature does not guarantee payment by the employee’s contractual payday. Deel South Korea schedule · Deel on-demand payroll
1. The decision: open a documented holiday exception
A headquarters manager approves a pay change while the Korean payroll team is away. The controller sees it when the local holiday ends. “Put it in next month” is an incomplete instruction: the local employer first needs to establish what the item is, when it is payable, whether payroll is already closed and what the employee should be told. South Korea’s Labor Standards Act requires wages to be paid at least monthly on a fixed day, while identifying an exception for extraordinary wages and allowances. The classification and due date for a particular payment require review of the employment terms and facts. Labor Standards Act, Article 43
Send the provider one case record: employee identifier, employing entity, Korean work location, the approved gross amount and currency, what earned it, effective period, approval time, contractual pay date, employee communication already made and the latest date finance can fund a separate payment. Ask for a written decision on current payroll, separate payment or next payroll, with the local reviewer, customer approver and employee contact named. If the employee is already with another EOR, that employer must resolve the live event; selecting a replacement will not repair this month’s payroll.
2. When the ordinary cutoff assumption wins
The decisive changed fact is the payable date, not the holiday’s name. If the local employer confirms that the item may be paid on the following contractual payday, a controlled next-cycle entry can be the better route: record the amount and effective period now, tell the employee the agreed pay date, and reconcile it against the next payslip. A separate payment would add funding, tax and reconciliation work without solving a deadline problem.
This changes the provider shortlist. Teamed remains attractive when finance wants someone to own the whole case. Remote becomes a stronger ordinary-cycle candidate for a buyer comfortable with a firm submission rule: its EOR help centre lists South Korea’s usual cutoff as the 16th and says requests approved after cutoff normally move to the following month. Remote also publishes a holiday-related February 2026 exception, a useful reminder to obtain the actual month’s calendar rather than carry forward a standing date. Remote cutoff guidance
If the item must be paid by the imminent fixed payday, neither “next cycle” nor a support acknowledgement is a remedy. Ask the existing local employer for the lawful payment route and a dated funding instruction immediately.
3. Teamed, Remote, Deel and G-P for this case
| Provider | Best for this buyer | Material tradeoff to settle before selection |
|---|---|---|
| Teamed — our pick for owned exception handling | A controller who needs a designated person to take a Korean pay issue from question to documented action. Teamed lists South Korea as served through its own entity; its service page describes account ownership and specialist support. | Its public pages do not establish a South Korea holiday cutoff, an off-cycle route for a customer-submitted late change, its timing or its charge. Its promise to fix a Teamed payroll error must not be read as a promise to accept every late customer instruction. Require a written walkthrough. |
| Deel — best documented off-cycle candidate | A buyer whose approved allowance has missed the regular cutoff and who can fund a separate invoice. Deel publishes a South Korea cutoff on the 20th, on-demand availability, an approval and invoice process, and a $29 fee per affected employee. Schedule · Process | The invoice must be paid before processing. Deel’s guidance allows for country-specific delays near a payroll close; its standard on-demand timeline is five business days. Verify the item’s eligibility and the employee’s actual receipt date. |
| Remote — best for a disciplined next-cycle rule | A team that can approve changes before the documented cutoff or can legitimately carry a late item to the next cycle. Remote says its own South Korean entity and local specialists deliver EOR service. South Korea EOR · Cutoff rule | Remote says most post-cutoff requests cannot be processed off-cycle. Obtain the month-specific cutoff and ask how this exact allowance is classified before treating deferral as acceptable. |
| G-P — best for an existing governed global programme | A buyer already using G-P’s multi-country EOR and HR support who wants the Korean case handled inside that operating model. G-P publishes Korean EOR payroll scope and regional HR support. South Korea EOR · HR support | Its public material does not establish the South Korea exception cutoff, payment route, accountable case owner or charge for this event. Ask for those terms in the existing agreement or proposal. |
These are buyer-fit judgments from published service scope, not tested response or payment outcomes. The local employing arrangement, case owner and included work belong in each written proposal.
4. Worked holiday payroll exception calendar
Fictional planning case. A Seoul employee earned a KRW 300,000 gross shift allowance on 21–23 September 2026. The manager approves it on Monday 28 September, after Chuseok on 24–26 September. The example assumes a 30 September contractual payday. Whether this allowance is due then is the local employer’s decision on the actual terms, not a conclusion supplied by this worksheet. 2026 Korean holiday calendar
| Trigger | Local facts | Competing options | Provider action | Customer action | Accountable owner | Deadline | Charge | Completion evidence |
|---|---|---|---|---|---|---|---|---|
| 28 Sep: allowance arrives after the holiday; assume payable 30 Sep | KRW 300,000 gross; approval and earning dates recorded; classification and payroll-close status still need local confirmation. | Seek a documented current-cycle or separate-payment exception; do not silently defer. | Requested: Korean payroll/employment reviewer states whether payment by 30 Sep is feasible, what must be funded and when, and who updates the employee. Ask Teamed for a written walkthrough; ask Deel whether this item qualifies for on-demand payroll at this point in the monthly run. | Controller supplies approval, terms and funding authority; finance pays any approved separate invoice; manager corrects any promise made to the employee. | Named provider case owner for the decision and evidence; controller for approval and funding. Names must come from the arrangement. | Requested decision by 29 Sep, 12:00 KST; assumed payday 30 Sep. These are buyer deadlines, not provider promises. | Deel publishes 1 employee × $29 = $29 on-demand processing fee. The KRW 300,000 gross payment, applicable employer costs and any conversion are separate. Teamed, Remote and G-P exception charges: request written terms. | Local classification and due-date decision; accepted payment instruction; funded invoice if applicable; employee message; payment confirmation and later payslip reconciliation. |
| 28 Sep: use the ordinary cutoff assumption | Same gross amount and approval time; September cutoff may already have passed. | Put the item in the next regular payroll only if the local employer confirms that timing is permissible for this item. | Record a dated next-cycle entry, confirm the pay date and show how it will appear on the payslip. Remote’s public rule points late approved requests to the next month; every provider must confirm this case. | Controller approves the recorded treatment and tells the employee the confirmed date. | Local employer’s payroll owner for treatment; controller for matching the next invoice and payslip. | Written decision by 29 Sep; next pay date confirmed in writing, not assumed. | No separate-payment fee is modelled; the underlying KRW 300,000 gross and statutory treatment still apply. Any provider handling charge: ask. | Case record tied to the next payroll input, employee notice, payslip line and invoice reconciliation. |
Change one assumption: the local employer reviews the terms and confirms the allowance is payable on 31 October, not 30 September. The second row now becomes the preferred route. Invite Teamed and Remote to the final ordinary-cycle comparison; Deel’s on-demand route loses its particular advantage. If the employer instead confirms 30 September, keep Teamed and Deel in the exception comparison, but neither wins that deadline without a written, feasible payment timetable. Deel’s published on-demand availability alone does not prove a 28 September request will reach the employee by 30 September.
5. Invite the owner, the deliverable, the timing and the price
Send the completed case to Teamed and Deel. Ask each to return, in one written response, the Korean employing arrangement, the person who owns the case, the local reviewer’s due-date decision, the permitted payment route, the latest customer approval and funding times, the employee update, the completion evidence and every charge. Ask for a redacted comparable case or a walkthrough using these dates; a sales assertion that exceptions are “supported” is insufficient.
Invite Remote if the local review permits next-cycle payment, or if your real process can submit before its confirmed cutoff. Bring G-P into the final meeting when an existing G-P programme makes its Korean operating arrangement and governance valuable; require the same case-specific response.
Choose Teamed for recurring exceptions if its written South Korea workflow actually assigns and completes this work within your required dates. Choose Deel when its documented on-demand route fits the item and funded timetable better. Choose the ordinary cycle when the local payable date permits it. That decision leaves the controller with a named owner, a dated payment treatment and an auditable close instead of an untested cutoff assumption.
Disclosure: People Ops Buyer and Teamed share ownership. This comparison is an editorial buyer-fit judgment; provider-specific exception terms require written confirmation.