CMS Direct Debit, Retry & Settlement Ledger
Reconcile outstanding claims, overpayments and contract fees.
Review retry candidates and dated cash. Korea-based CMS context, checked November 20, 2026. Amounts use KRW.
What does the CMS direct debit ledger reconcile?
A CMS submission, a bank debit result and a deposit into the collecting business account are separate events.
An accepted request does not establish a successful debit, and successful debits do not necessarily settle on the same day.
This calculator links invoices to successful, failed, pending and returned debit events so that collections and contract fees can be checked separately.
It is designed for small operators collecting Korean tuition, membership fees or rent by recurring account debit.
Before renewing a contract or accepting a monthly statement, check whether failed requests are billed, a retry created an overpayment, a return was omitted or settlement remains outstanding.
Use the result to identify the claims requiring attention as well as to reconcile the total.
Amounts use KRW.
Separate billed amounts, requests, successful debits and settled cash before saving the review checklist.
Prepare records for one billing period
A reconciliation must cover one confirmed fee billing period and one consistent ledger scope.
The base fee is applied once to the entered dataset, so combining several months does not reproduce monthly billing.
Align the contract period, result-file coverage and settlement statement before confirming the scope.
- From invoices: anonymous claim ID, billed amount and payment due date.
- From result files: attempt ID, claim link, event date, status, amount and the original event ID for a retry or return.
- From contracts: final tax-inclusive block price, included count, billing block size, base fee and total minimum fee.
- From settlement statements: deposit dates, return deduction dates and each plan's fee deduction date.
A return of a debit from an earlier billing period, or a reconciliation spanning multiple months, requires a separate period adjustment in the provider ledger.
Do not combine those records here and treat the result as a final bill.
Contracts charging separately for transmitted and received messages also fall outside this simplified event-count model.
Example rates are synthetic and are neither market averages nor a provider tariff.
Claim inputs and confirmed debit consent
Identify each invoice claim
Use an anonymous code to identify one claim.
Different invoices for the same payer need different codes, while multiple attempts against one invoice must link to the same claim.
IDs are checked for duplicates after trimming surrounding whitespace and ignoring case.
Record consent as a checked fact
Choose confirmed, unknown or revoked based on the evidence you hold.
This records your review; it does not determine whether a consent document is legally valid or authorize a debit.
An outstanding claim with unknown or revoked consent is withheld from the retry candidate list.
Enter up to 20 claims, with IDs of at most 40 characters.
Claim and event amounts must be whole KRW from 1 to 1,000,000,000.
The due date determines whether a claim is due for candidate review; it does not calculate late interest or establish a legal payment deadline.
Link successful, failed, pending and returned events
Enter up to 60 events.
Each successful, failed or pending attempt counts as one debit request.
A return counts separately as a return and does not create another request.
Failed and pending amounts are requested or awaiting a result, so they contribute no confirmed collection.
A retry links to an earlier failed attempt
Set the parent event ID to a preceding failed attempt on the same claim.
A successful or pending event cannot be the parent of a retry.
The calculator checks the linked claim, status and dates independently of the order in which rows were entered.
The retry itself is counted and collected according to its successful, failed or pending status.
A return links to a successful debit
A return requires the original successful event ID on the same claim.
Its date cannot precede that success, and cumulative returns against a success cannot exceed its original amount.
Record the actual amount for partial debits and partial returns.
Correct missing parent events or excessive return amounts before using the final reconciliation.
Net collection, outstanding and overpaid formulas
- Net collection per claim = successful debits − returns
- Outstanding = max(billed amount − net collection, 0)
- Overpaid = max(net collection − billed amount, 0)
- Net settlement per plan = total net collection − contract fees
Outstanding and overpaid balances are calculated per claim and then summed separately.
An overpayment on one invoice must not conceal an unpaid balance on another invoice.
Matching total billed and total collected amounts therefore does not prove that every payer is settled correctly.
Net settlement can be negative when fees exceed collections; the calculator does not replace that result with zero.
Request, success, failure and return fees
Plans A and B use the same event ledger.
For each plan, enter separate included counts, billing block sizes and final prices per block for requests, successes, failures and returns.
For a free category, explicitly enter a zero price rather than leaving it unknown.
A failed attempt can incur both a request charge and a failure charge when that is how the contract is written.
Apply blocks before the total minimum
Category fee = ceil(max(count − included count, 0) / block size) × price per block
Total fee = max(total minimum fee, base fee + request fee + success fee + failure fee + return fee)
For 5 events with 2 included, a 2-event block and a KRW 300 block price, the remaining 3 events require 2 blocks: KRW 600.
Included quantities apply independently to each category.
The minimum used here is a floor for the entire fee, including the base fee.
Different minimum-order rules, message charges, waivers or refund adjustments require a separate comparison with the provider statement.
A return does not automatically reverse earlier request or success counts.
Check the contract for returned-payment charges and any refund of fees.
Enter actual final tax-inclusive contract amounts; the calculator does not add VAT again or invent a universal tax or refund rule.
Dated cash differs from fee-inclusive net settlement
For a successful debit or a return, enter the deposit or deduction date confirmed in the settlement record.
A settlement date before its event is invalid.
An empty date leaves the associated cash amount unresolved.
Dates on or before the as-of date belong to statement-confirmed cash; confirmed settlement dates after it belong to scheduled cash.
A debit event dated after the as-of date cannot be entered as if it had already occurred.
Check the fee deduction date separately
Enter a separate fee deduction date for each contract.
Known prices can establish the cost and fee-inclusive net settlement even when the deduction date is unknown, but the final dated cash total remains withheld.
A scheduled deposit is not money already in the bank.
Keep confirmed receipts and scheduled receipts separate when planning operating cash.
Worked example: matching totals can hide unpaid claims
Use an as-of date of 2026-11-20 and three anonymous claims.
A is billed KRW 100,000, has a KRW 100,000 success, another KRW 100,000 success linked to an earlier failed attempt, and a KRW 20,000 return.
B is billed KRW 50,000 with one failed attempt.
C is billed KRW 30,000 with one pending attempt.
These synthetic records demonstrate reconciliation errors and do not recommend initiating another debit.
| Claim | Billed (KRW) | Collected (KRW) | Outstanding (KRW) | Overpaid (KRW) |
|---|---|---|---|---|
| A | 100,000 | 180,000 | 0 | 80,000 |
| B | 50,000 | 0 | 50,000 | 0 |
| C | 30,000 | 0 | 30,000 | 0 |
| Total | 180,000 | 180,000 | 80,000 | 80,000 |
Both billed and collected totals are KRW 180,000, yet B and C remain outstanding by KRW 80,000 while A is overpaid by KRW 80,000.
If B is due, its consent is confirmed and it has no pending event, B becomes one retry-review candidate.
C is held for its pending result instead of being offered for an immediate duplicate request.
Compare the example fees and settlement cash
The ledger contains 5 requests, 2 successes, 2 failures, 1 return and 1 retry linked to a failure.
In these synthetic tax-inclusive plans, all included counts are 0, block sizes are 1 and total minimum fees are 0.
Do not count the return as a sixth debit request.
Plan A: KRW 2,100 fee
Base 1,000 + requests 5×100 + successes 2×200 + failures 2×50 + returns 1×100 = KRW 2,100.
Net settlement = 180,000 − 2,100 = KRW 177,900.
Plan B: KRW 1,700 fee
Base 500 + successes 2×600 = KRW 1,700.
Request, failure and return prices are explicitly zero.
Net settlement = 180,000 − 1,700 = KRW 178,300, which is KRW 400 above A.
If the first KRW 100,000 success has been deposited and the KRW 20,000 return deducted by the as-of date, statement-confirmed cash before fees is KRW 80,000.
If the second KRW 100,000 success has a confirmed settlement date of 2026-11-23, it remains future scheduled cash on 2026-11-20.
With both plan fees hypothetically deducted on 2026-11-20, cash through the as-of date is KRW 77,900 for A and KRW 78,300 for B.
The overall KRW 177,900 or KRW 178,300 net settlement is not the current bank balance.
Review retry candidates in this order
- Correct duplicate IDs, unlinked events, excessive returns and invalid dates.
- Check each outstanding balance and due date; keep claims that are not yet due separate.
- Obtain results for pending attempts before risking another request.
- Verify consent records and any account correction in the original evidence and provider system.
- Review only claims that are outstanding, due, consent-confirmed and free of pending attempts.
The candidate list contains at most one row per claim and is neither debit authorization nor a prediction of success.
Check failure reasons, payer instructions and payments received by other methods against the actual ledger.
The calculator does not query balances, validate accounts, assess legal consent, initiate debits or execute returns.
Unknown values, errors and partial subtotals
A blank is unknown, not an explicit zero.
Fee prices and included counts may be zero; block sizes must be at least 1.
Negative amounts, decimals, exponent notation and malformed comma groups are rejected, and dates must be real calendar dates in YYYY-MM-DD format.
Incomplete or invalid ledger rows withhold final totals and the retry candidate list.
Collections from valid events may appear as a provisional partial subtotal, but that does not establish that the whole ledger is complete.
A missing contract field is not silently replaced by another plan's value or a free rate.
Move between steps and rows to edit inputs without losing them.
After opening the worked example, restore your inputs to return to the previous draft and selected row.
Replace an entire amount and verify that the corresponding result updates.
Save the reconciliation and use it for review
The TXT report is generated from current inputs when saved.
It includes source inputs, results, errors and withholding reasons, billed event counts, plan fees, dated cash and the follow-up checklist.
Keep original invoices, result files and settlement statements alongside it and clearly distinguish synthetic examples from actual records.
Saving the file does not modify a provider ledger or a bank debit list.
Monthly statement review
In a month with more failures, check whether both request charges and failure charges increased.
Do not remove a returned success from billing without checking the contract adjustment rules.
Renewals and cash planning
Apply both contracts to the same actual ledger.
Compare settlement timing, return handling and included scope as well as prices, and avoid committing cash solely against scheduled deposits.
Use anonymous codes instead of names, account numbers or identity numbers.
Example restoration keeps the current draft in page memory rather than providing automatic permanent storage.
Downloaded reports are still business records: check where you store them and whom you share them with.
Frequently asked questions
Why is a claim outstanding after the request was accepted?
Only confirmed successful debits add to collection.
Failed or pending requests are not receipts, and returns reduce earlier successful collections.
Can a failed request incur a fee?
It depends on the contract.
Request and failure prices are separate here, allowing both charges when applicable.
The model assumes neither that all failures are free nor that all are charged.
Does a return cancel the success fee?
Not automatically.
A return reduces net collection without removing the earlier request or success count.
Check the provider statement for any separately agreed refund or waiver.
Is everything settled if outstanding and overpaid totals match?
Do not offset balances between claims.
The example has billed and collected totals of KRW 180,000 each, but still has KRW 80,000 outstanding and KRW 80,000 overpaid.
Can I debit every retry candidate immediately?
The list is for review.
Recheck original consent, payer instructions, failure reasons, pending results and receipts through other channels, then follow the provider procedure.
The calculator neither authorizes a debit nor predicts its success.
What if a settlement or fee deduction date is unknown?
Leave it unresolved instead of guessing a business-day schedule.
Known costs remain distinct from dated cash.
Missing required dates withhold the final cash total.
Can I combine this month's return with last month's debit?
Final fee reconciliation across different billing periods is not supported.
Reconcile period-specific returns and fee adjustments in the provider ledger separately.
Detailed transmitted/received message billing is also outside this event model.
Should plan prices include VAT?
Enter actual final tax-inclusive contract prices.
The calculator does not add VAT using a statutory rate.
Also confirm that the contract's minimum fee is a floor for the entire base-plus-category fee, as defined here.
Sources, 2026 context and the next check
Official sources were checked on 2026-11-20.
The KFTC CMS terms page displays an effective addendum dated 2025-08-09.
Relevant provisions include Articles 14–15 on fees and workload, Article 25 on registration, results, deposits and partial debits, and Article 27 on dishonored returns.
Direct KFTC terms must not be automatically transferred to every intermediary contract.
- KFTC CMS terms and fee FAQ dated 2023-04-03: contractual billing and separate charge/deduction timing
- KFTC CMS service and Hyosung FMS CMS: service scope and reprocessing functions
- Electronic Financial Transactions Act, Article 15: statute ID 010199, MST 290247, promulgated 2026-09-29, effective 2026-10-02; debit consent context
- Enforcement Decree, Article 10: statute ID 010366, MST 285727, promulgated and effective 2026-04-28; consent methods
Current articles were checked directly through the National Law Information OPEN API, but the calculator does not assess legal validity of entered consent.
The 20th/25th dates in Article 16 of the CMS terms concern recollection of intermediary fees from participating institutions; they are not retry dates for customer invoice claims.
Recheck public sources quarterly and verify actual prices, allowances, return adjustments and settlement dates for every contract and bill.
Compare the saved report with original records
Enter claims and events, inspect unpaid, overpaid and unresolved cash amounts, then save the reconciliation.
For different decisions, use POS rental versus purchase TCO, accounting software plan billing or cash runway.
This collection and fee check does not replace accounting entries or bank debit execution.
Related calculators
- POS Terminal Rental vs Purchase TCO CalculatorCompare one POS terminal rental contract with two purchase quotes across deployment, payment-network fees, software, maintenance, replacement, downtime, exit terms, residual value, and present-value TCO.
- Accounting Software Plan Billing CalculatorCompare actual accounting plan quotes, required features, company codes, sites, ledgers, users and usage limits in KRW.
- Cash Runway CalculatorEstimate how long available cash can support a business under current revenue and expense assumptions.
- SKU Stocktake Quantity & Confirmed Cost CalculatorReconcile book and physical stock by SKU, separate shortage and surplus costs, and save a prioritized recount list. Amounts use KRW.
- Margin Rate CalculatorCalculate profit margin, markup, selling price, cost, and gross profit for products or services.