By Park Ji-Hoon
For a single-location franchise operator working with one carrier, a spreadsheet-based reconciliation system is honest. You export the SKT settlement report, paste it into your tracking file, compare the activation count to your POS record, flag any delta, and move on. The whole process takes maybe thirty minutes at end of month. It works.
The problem is that this one-store, one-carrier picture is the exception, not the norm. Most franchise operators expand. They take on a second location, then a third. They add a second carrier agreement when KT or LG Uplus offers a better commission rate on a new device line. At some point the spreadsheet system that felt fine at one store becomes the source of the biggest headaches in the operation.
Where Spreadsheet Reconciliation Actually Breaks
The failure mode is not dramatic. Nobody's spreadsheet explodes. What happens instead is a slow accumulation of friction that the operator often attributes to something else, typically "staff issues" or "carrier inconsistency."
Consider a franchise group with three locations, each carrying two carrier agreements. That is six settlement reports to download monthly. Each carrier formats its report differently: SKT's T-World Partner export uses different column names than KT's B2B portal, which in turn exports fields in a different order than LG Uplus's partner portal (which has changed its export format twice in the past eighteen months). If you are doing any kind of VLOOKUP or INDEX-MATCH in Excel to align your POS data with the carrier report, you have probably built those formulas by hand and have to rebuild or patch them every time a carrier updates its column structure.
Across three stores and six agreements, you are managing six different formula sets. If each store's POS exports in a slightly different template because different staff configured them at setup time, you now have eighteen alignment points. Any one of them breaking quietly will produce a gap that looks like a commission shortfall until someone spends two hours tracing it back to a renamed column.
The Three-Store Inflection Point
Three stores is the number we hear most often as the point where operators start reporting that reconciliation feels unmanageable. Before three stores, the volume is low enough that careful manual work catches errors. After five stores, operators usually have a dedicated person doing reconciliation, which introduces a different problem: institutional knowledge about which carrier columns map to which fields lives in one person's head and in their personal spreadsheet conventions.
The math is straightforward. A five-store, three-carrier portfolio generates approximately 15 settlement reports per month. If each takes 45 minutes to reconcile with the corresponding POS data, that is 11 to 12 hours of structured reconciliation work monthly, excluding the time spent chasing discrepancies. At 10 stores that becomes 22 to 25 hours. The labor cost is real, but the bigger cost is the error rate: manual data alignment across that volume will produce keying errors or format-mismatch errors, and a single missed discrepancy on a SKT activation commission can represent 30,000 to 80,000 KRW depending on the device tier.
What the Migration Actually Involves
Moving away from spreadsheets is not primarily a software purchase. It is a data-standardization project with software at the end of it. The sequence matters.
The first step is establishing a canonical format for your POS exports. If different stores configured their POS systems independently, their exports will have inconsistent field names, date formats, and identifier schemes for the same underlying data. Before any automated matching can happen, you need every store's POS to produce consistent output: activation date in YYYY-MM-DD format, IMEI without spaces or dashes, plan code using the carrier's standard code rather than an internally assigned nickname.
The second step is understanding which fields in each carrier's settlement report correspond to the fields in your POS export. This is a one-time mapping exercise that feels tedious but is the foundation of everything downstream. SKT's 개통일 field corresponds to your POS activation_date. KT's 단말기일련번호 corresponds to IMEI. LG Uplus calls the same field 기기시리얼 in some report versions and 단말시리얼번호 in others. Mapping these explicitly, in writing, means that when a carrier changes its column name, you update one mapping table rather than rebuilding formulas across a portfolio of spreadsheets.
The third step is establishing a primary matching key. IMEI is the most reliable key for device activations because it is globally unique and present in both POS records and carrier reports. USIM ICCID is the right key for SIM-only activations. Plan change transactions require a different approach: you match on subscriber identifier plus plan code plus activation date, since there is no device IMEI involved.
What Breaks During Migration
The transition period creates its own reconciliation problems, and operators who do not anticipate them end up with a gap month where neither the old system nor the new one has complete data.
The most common issue is historical data quality. If your POS records from the past twelve months have inconsistent IMEI formatting (some with dashes, some without, some with leading zeros dropped), an automated matching system will report far more unmatched records than actually exist. Cleaning three to six months of historical POS data is not optional if you want the system to produce usable match rates from day one.
The second common issue is partial automation. Some operators automate only the most painful part, typically the SKT or KT reconciliation, while keeping LG Uplus on spreadsheets because the volume is lower or the format changes more often. This creates a two-speed system where errors in the manual portion still require the same manual investigation time, but now without the context of the automated records sitting alongside them.
We are not arguing that spreadsheets are inherently wrong for small operations. For a truly single-store, single-carrier franchise with stable export formats, the manual approach may remain adequate for years. The argument is about scale: if you are managing more than three locations or processing more than 150 activations per month across your portfolio, the error rate and labor cost of pure spreadsheet reconciliation will exceed the cost of a structured system.
The Month-End Close Signal
The clearest sign that an operator has successfully migrated is a change in the month-end close experience. On a spreadsheet system, the last three business days of the month typically involve concentrated scrambling: downloading final settlement reports, patching formula errors, chasing staff for missing POS entries, and arguing with carrier channel managers about discrepancies that should have been caught two weeks earlier.
When the matching pipeline is running correctly, those discrepancies surface in the first 48 to 72 hours after each carrier's daily settlement file is available. An activation that shows in your POS but not yet in the carrier report is visible immediately as a pending match rather than invisible until someone manually reconciles. An activation that the carrier settled at a different commission rate than expected shows as a delta on the day it posts, not at month end.
That shift from batch reconciliation to continuous matching is the operational change. The software is just the mechanism that makes continuous matching possible at portfolio scale.
Where to Start If You Are Managing the Migration Now
If you are at three to five stores and currently on spreadsheets, the highest-ROI first step is a POS export audit. Pull the last 90 days of activation records from every store and check IMEI formatting consistency, date format consistency, and plan code conventions. The number of format variations you find will tell you how much pre-work the migration requires before you can trust automated matching results.
If you are already past five stores and the spreadsheet pain is acute, prioritize the carrier mapping exercise. Spend one full day documenting exactly which column in each carrier's current settlement export corresponds to each field in your POS record. That mapping document becomes the configuration input for any automated system and is also the reference that lets you update the system quickly when a carrier changes its export format, which they will.