By Kim Sang-Yoon
Opening a Korean telecom retail franchise involves two parallel tracks that need to be completed before the first activation can happen: the physical and branding setup that the franchisor guides you through, and the operational backend that most new franchisees underestimate. The physical setup has a clear checklist from the franchisor. The operational backend does not, and gaps in it show up in the first month's settlement as unexplained discrepancies, failed portal submissions, and reconciliation delays that take weeks to trace back to a setup error.
This is a guide to the operational backend: what to set up, why each piece matters, and in what order to tackle them before you take your first customer.
Carrier Portal Access: The Absolute First Step
Before POS setup, before staff training, before inventory, you need working portal access for every carrier you will carry. In Korea that means some combination of SKT T-World Partner, KT B2B Partner Portal, and LG Uplus Dealer Portal, depending on your channel agreements.
Portal access requests go through the carrier's channel partner management team and are processed against your dealer code, which you receive after signing your channel agreement. The processing time varies: SKT accounts are typically active within three to five business days. KT and LG Uplus can take up to ten business days if there is a queue at their channel registration team. If you are opening near a month-end when channel activations are being processed, expect delays.
Do not wait to request portal access until the physical store is ready. Submit the access request the day your channel agreement is signed. Portal access that arrives after your opening date means your first week of activations will either be processed through a temporary access credential (which creates reconciliation problems later) or delayed entirely while you wait for credentials.
When your portal access arrives, verify it immediately: log in, confirm that your dealer code is correctly associated with your store's physical address and tax registration number, and verify that the commission rate schedule shown in the portal matches the rate schedule in your channel agreement. Discrepancies here are much easier to resolve before you have activated any subscribers than after month-end settlement when you need documentation to support a rate dispute.
POS Configuration for Reconciliation
The POS system is often configured by the POS vendor or franchisor without explicit reconciliation requirements in mind. The default configuration captures what you need for sales tracking. It may not capture what you need for carrier settlement reconciliation.
Before you accept the POS configuration, verify that the following fields are being captured at the time of each activation transaction: IMEI (for device activations), USIM ICCID, the carrier's official plan product code rather than a free-text description, portal submission timestamp, and portal submission confirmation number. The confirmation number field is the one most commonly missing from default POS setups because it requires the staff to copy the confirmation from the carrier portal into the POS record after submission, and many POS configurations do not prompt for this.
If your POS does not support a portal confirmation number field, the workaround is a paper or spreadsheet log that captures this information alongside each day's activation records. This is manual work but is significantly better than having no confirmation record at all. The confirmation number is your primary documentation if you need to dispute a commission settlement later.
Also configure your POS export to produce consistent output format from day one. Decide on IMEI format (numeric string, no spaces, no dashes), date format (YYYY-MM-DD), and plan code convention, and document these decisions. If you expand to additional locations later, having a documented export standard means you do not have to re-solve the reconciliation matching problem for each new store.
Till Reconciliation Procedure
The till reconciliation procedure is the daily process of verifying that cash, card transactions, and POS records agree. In telecom retail, till reconciliation is more complex than in a standard retail environment because revenue has two components: point-of-sale revenue (device price, accessories, initial fees) and carrier commission (settlement credit paid by the carrier, typically with a two-to-five-day lag).
For the point-of-sale component, standard retail till procedures apply: cash drawer count at close, comparison against POS cash receipt total, investigation of any variance greater than your acceptable threshold (typically 5,000 to 10,000 KRW for a small-volume day).
For the carrier commission component, the till reconciliation extends to a daily check of what the carrier portal shows as provisionally credited versus what your POS records show as submitted activations from the same day. This is a two-minute check, not a full reconciliation. You are looking for any activation that your POS shows as submitted but that is not visible in the carrier's provisional settlement view within 24 to 48 hours. An activation that is absent from the provisional view after 48 hours is worth investigating immediately: either the portal submission did not go through correctly, or the carrier's system rejected the activation for a validation reason that needs to be corrected before the settlement window closes.
Document the till reconciliation procedure in writing on day one, including who is responsible for the carrier portal check, when it is done, and what action is taken for variances. Staff turnover in retail is high. A written procedure means the reconciliation practice persists when the person who learned it leaves.
Settlement Reporting Flow
The settlement reporting flow is the cycle by which you receive carrier settlement reports, reconcile them against your POS records, and close the books for the period. Setting this up before opening means defining: where settlement reports are stored, who downloads them and when, who performs the reconciliation, and what reporting you need from the reconciliation to manage the business.
For a single-location franchise with one or two carrier agreements, the minimum setup is a shared folder structure for settlement reports, a standard file naming convention (carrier code, period, download date), and a reconciliation template that maps the carrier report columns to your POS export columns. The mapping work is a one-time investment that saves significant time every month.
Build this mapping before you have any real transaction data. Pull a sample settlement report from each carrier's portal (carriers typically have sample or test reports available for new dealers during setup) and map each column to its corresponding field in your POS export. Document where the column names differ. This mapping document becomes the reference for anyone who needs to understand the reconciliation process and the configuration input if you ever move to an automated reconciliation system.
Staff Training on Reconciliation-Critical Steps
Most staff training for telecom retail franchise openings focuses on product knowledge, carrier plan features, and the handset lineup. The reconciliation-critical operational steps are often covered briefly if at all. This is a mistake that shows up in the first month's settlement data.
The three operational steps that staff need to follow precisely for reconciliation to work are: entering the correct plan product code in the POS at the time of activation (not a nickname or approximation), copying the portal submission confirmation number into the POS record before closing the transaction, and processing cancellations through the portal in the same session as the POS reversal (not leaving portal cancellations for end-of-day batch processing).
Training staff on the why behind each of these steps, not just the what, produces better compliance. Staff who understand that a missing confirmation number means they cannot dispute a commission error in 30 days are more likely to treat it as a mandatory step than staff who are told to fill in a field without context.
The First Month as a Calibration Period
No matter how carefully you set up the operational backend before opening, the first month will reveal gaps. Accept this as a calibration period rather than a failure. The reconciliation discrepancies you find in month one are the data points that tell you where your setup has gaps: a POS field that is being left blank, a portal submission step that staff are skipping, a column mapping that does not account for a plan type you did not have in the test data.
Treat each discrepancy as a process signal rather than an accounting error to be manually corrected and moved on from. Document what type of transaction produced the discrepancy, which field or step in the process was the source, and what process change or configuration fix eliminates it going forward. The franchise operators who have clean reconciliation six months after opening are almost always the ones who did this systematic investigation in month one rather than patching discrepancies manually and moving on.
Month two should be measurably cleaner than month one. If it is not, the calibration period is not over and the process gaps have not been fully identified yet. Keep investigating until you have a reconciliation process that produces clean settlement close-out without manual intervention for the majority of transactions. That standard is achievable within three months for most single-location franchises if the setup work described here is done before the first activation.