By Jung Soo-Min
When franchise operators talk about commission disputes with carriers, the conversation often starts with suspicion. The carrier is underpaying. The portal is wrong. Someone at the carrier level made an error. In our experience working with Korean telecom franchise operators, most disputes that reach the formal escalation stage are not fraud or carrier error. They are documentation mismatches that both parties could have caught earlier if they had been comparing records at the same frequency.
Understanding why the documentation drifts apart is the first step toward preventing disputes. The second is building the documentation habits that keep your records aligned with the carrier's view of the same activations.
How the Documentation Gap Forms
A commission dispute typically starts with a single activation that is recorded differently at the store level and at the carrier level. This happens for several identifiable reasons.
The most common is same-day cancellation or next-day return. A customer activates a handset on Thursday evening. Your POS records the activation, and your staff triggers the carrier portal submission. On Friday morning the customer returns the device. Your POS records the return and reversal. But if the carrier's system has already batched Thursday's activations into the settlement pipeline before the reversal posts, the cancellation may not correctly offset the original commission credit. The carrier's record shows a settled activation. Your record shows a zero-net transaction. The reconciliation produces a gap that looks like a missing commission when it is actually a timing discrepancy in the cancellation workflow.
The second common cause is plan code mismatch. Your staff activates a subscriber on what the customer describes as the 75,000 KRW monthly plan. Your POS records this using your internal plan nickname. The carrier's settlement report references the plan by its official product code, which may not correspond to the nickname your staff is using in the POS notes field. When you reconcile manually, the activation matches on IMEI but the plan code does not match your internal label, so it flags as a discrepancy. Over many activations, this produces a list of "disputes" that are actually just naming-convention mismatches.
The third cause is portal submission timing. Korean carrier channel portals have cut-off windows for same-day commission credit. SKT's T-World Partner, KT's B2B portal, and LG Uplus's dealer portal each have different submission windows. Activations submitted after the cut-off window credit to the next settlement cycle rather than the current day. If your store is busy and portal submissions are done in a batch at end of day, you may consistently have activations shifting to the following settlement period without anyone tracking this systematically.
What Dispute-Resistant Documentation Looks Like
The operators who have the fewest formal disputes share a common documentation practice: they maintain a transaction-level activation log that includes fields the carrier's system also captures, and they compare the two records at least weekly rather than waiting for month-end settlement.
The minimum viable documentation set for each activation is: IMEI, activation date and time, USIM ICCID, subscriber ID (if applicable), plan product code (using the carrier's official code rather than an internal nickname), store identifier, and portal submission timestamp. If your POS does not currently capture portal submission timestamp as a distinct field, this is worth configuring. The gap between activation time and portal submission time is one of the three leading predictors of settlement timing discrepancies.
For cancellations and returns, the documentation standard needs to be higher, not lower. Each cancellation record should reference the original activation IMEI and activation date, the return date and time, the reason code if the carrier requires one (SKT and KT both have formal reason codes for 개통취소), and the portal cancellation submission timestamp. Without the portal cancellation timestamp, you cannot determine whether the cancellation was processed in the same settlement window as the original activation or in the following one.
The Comparison Frequency Problem
Most operators who rely on spreadsheet-based reconciliation do a thorough comparison once a month when the carrier's settlement report is published. This is too late for effective dispute prevention.
Carriers make partial settlement data available on a daily or weekly basis through their partner portals, though the format varies. SKT's T-World Partner portal shows provisional activation records within 24 to 48 hours of submission. KT's portal provides a pending commission view that updates daily. LG Uplus provides a weekly summary that is less granular but still usable for early-warning comparisons.
Comparing your POS records against these provisional views two to three times per week, rather than once at month end, means you catch timing discrepancies and cancellation mismatches within the adjustment window rather than after settlement has closed. Once a month's settlement is finalized, the formal dispute process requires documented justification and typically takes three to six weeks to resolve even when the documentation is strong. Catching the same discrepancy during the provisional period takes a five-minute correction in the portal rather than a formal dispute submission.
When Disputes Still Occur: What Documentation You Need
Even with good preventive practices, some disputes will reach the formal stage. The carrier's formal channel dispute process in Korea typically requires the franchise operator to submit a dispute package that includes the original activation record from the POS with timestamps, proof of portal submission (a portal confirmation number or screenshot with timestamp), and a statement explaining why the operator's record differs from the carrier's settled amount.
The disputes that resolve quickly are the ones where the operator can provide portal submission confirmation numbers that match the carrier's own system. The ones that take longest are disputes where the only evidence is a POS printout without a portal confirmation reference. Carriers reasonably treat a POS-only record as insufficient evidence because the POS records the sale at the store level, but the portal submission is what creates the commission obligation. If you cannot show that the portal submission occurred in the correct window with the correct data, the carrier has no basis to revise the settled amount.
This is why capturing portal submission confirmation numbers as a standard field in your reconciliation log matters more than any other single documentation practice. The POS record proves the sale happened. The portal confirmation number proves the carrier received the submission. Both are necessary; neither alone is sufficient for dispute resolution.
What We Are Not Claiming
We are not claiming that carrier settlement systems are error-free. They are not. SKT, KT, and LG Uplus each have known edge cases where their commission calculation logic produces unexpected results, particularly around mid-month plan changes and device exchanges on subsidized plans. These are real carrier-side errors and they do get resolved through the formal dispute process when documented correctly.
The argument here is narrower: the majority of disputes that franchise operators bring to the formal stage could be prevented if the documentation practice at the store level matched the carrier's documentation standard from day one. The carrier is usually not disputing that the activation happened. They are disputing whether the activation, as submitted, qualifies for commission under the terms of the channel agreement at the submitted rate. Matching your records to the carrier's submission format, comparison frequency, and required fields is the practical work of dispute prevention.
Starting the Documentation Review
If you are managing an active franchise and want to assess your current documentation risk, the most useful starting point is a sample audit. Pull 30 to 40 activations from the past month and verify whether each one has: a portal submission confirmation number, an activation plan code that matches the carrier's official code rather than an internal label, and a portal submission timestamp within two hours of the POS activation time. The percentage of records that pass all three checks is a reasonable proxy for your documentation quality overall. Below 70 percent is worth treating as a systematic problem rather than isolated staff errors.