The workflow
Settlement reconciliation in four steps
Unsoft connects your POS and carrier settlement feeds, compares them automatically, flags the gaps, and feeds the results into a staffing model. Each step runs every morning without manual input.
Connect your data sources
Unsoft reads your POS system directly and pulls settlement exports from each carrier portal: SKT, KT, and LG U+. The connections run once during setup; after that, data comes in automatically on the carrier's settlement schedule. You do not export or upload anything.
For stores that submit till records manually, a simple import format accepts the standard ledger column order used by most Korean POS systems. The normalization layer handles the column name differences between carriers and translates everything into a common schema before comparison begins.
Compare till records against carrier credits
For each activation your POS logged yesterday, Unsoft finds the matching line in the carrier's settlement export and checks that the credit amount agrees. The comparison runs on activation serial number, plan code, and date to avoid false positives from similar transactions.
Matches are marked clean. When the carrier amount differs from the till record by more than the configured tolerance, the row is flagged as a gap. Activations that appear in the till record but have no corresponding carrier line within the settlement window are marked pending and rechecked the following day.
| Activation | Till record | Carrier credit | Status |
|---|---|---|---|
| SKT-041987 | ₩22,000 | ₩22,000 | Match |
| SKT-041992 | ₩35,000 | ₩35,000 | Match |
| KT-088341 | ₩48,000 | ₩42,500 | Gap |
| KT-088349 | ₩27,500 | ₩27,500 | Match |
| LGU-022104 | ₩19,000 | ₩19,000 | Match |
Project staffing from settlement and traffic data
Reconciliation output feeds into the staffing model. Activation volume by day-of-week and by carrier tells you where the demand is concentrating. Unsoft combines that with foot traffic data to generate a seven-day staffing projection with a daily headcount recommendation.
Saturday gets a separate weighting factor because promotional spikes from carrier campaigns compress the useful activation window. The forecast adjusts when a carrier announces a weekend promotion in the upcoming settlement cycle.
Review alerts and act on gaps
Each morning the dashboard shows a summary of gaps found across all connected stores. Each alert includes the store code, the carrier, the gap amount, and a recommended action. Most gaps fall into one of three categories: pending settlements that resolve in the next cycle, plan code mismatches, and genuine underpayments that require carrier follow-up.
The alert summary exports to a CSV or pushes to your operations channel. Stores with recurring gaps of the same type surface automatically in a weekly pattern report so you can address the upstream cause rather than handling each instance individually.
Ready to run this on your stores?
Request early access and we will walk you through a connection setup for your first store location.
Request early accessSetup takes under 30 minutes for a single-store operator.