Definition
A settlement statement is a detail statement generated on the settlement cycle (for example, monthly or weekly). It includes purchase detail, sales detail, and the settlement and profit sharing amount. Agents and distributors use it to reconcile. It supports export and payment records, and it meets finance and audit requirements.
Settlement Statement Content
- Purchase detail: Card count, plan count, purchase amount, and purchase time for what the agent bought at the agent price.
- Sales detail: Order count, sales amount, and the matching cards and plans, confirmed by sales attribution.
- Profit-sharing amount: The profit share payable, calculated from the profit-sharing ratio, minus any part already settled through payment splitting.
- Payment record: Payment time, payment method, and transaction number, so reconciliation and audit are possible.
Business Process
After the end of each settlement cycle, the platform automatically aggregates data to generate the settlement statement, which agents can view and export on the agent self-service portal. Payment is executed after enterprise financial review is confirmed, and the payment status is updated back to the settlement statement. In case of disputes, the system supports raising settlement statement disputes and manual adjustments.
Settlement Statement Format
The settlement statement usually includes a header (agent name, settlement period, generation time), a purchase details table (number of cards, data plans, amount, time), a sales details table (order number, sales amount, attributed card), a profit summary (amount payable calculated according to profit-sharing ratio ), and payment records (payment time, method, transaction number). It supports export to Excel and PDF, making it convenient for agents to reconcile accounts and archive. The settlement statement is the record that carries settlement and profit sharing. It is different from payment splitting, which shares profit at once. The settlement statement fits periodic settlement in the agent purchasing model.
Settlement Statement and Reconciliation
The settlement statement is provided for agents and distributors to reconcile accounts, which is different from operator reconciliation (the cost check before the enterprise pays the operator). The settlement statement is the carrier for channel profit sharing, which agents can view and export through the agent self-service portal . After corporate finance verification, payment is made, and the payment status is written back to the settlement statement. In case of disputes, the system supports the submission of settlement statement objections and manual adjustments. Settlement statements are generated according to the settlement period and differ from bills (C-end user billing), as settlement statements are intended for channels.
Settlement Statement Content
The settlement statement includes purchase detail (card count, plan count, and amount bought through agent-price procurement), sales details (orders confirmed by sales attribution ), profit sharing amounts (calculated according to profit sharing ratio ), and payment records. It supports exporting to Excel and PDF. The settlement statement is the carrier for settlement profit sharing , different from payment splitting (instant profit sharing). The settlement statement is one of the core outputs of IoT Cloud Platform channel management.
Each detail line must trace back to an order
A settlement statement is the list of amounts payable and amounts to be deducted for one channel in a period that has already been closed. It is not a copy of a usage report. The purchase section lists the settlement price, quantity, and purchase-order number of cards or plans. The sales section lists the user order number, the card identity, the amount paid, the profit-sharing rule version that applied, and the share that was calculated. The deduction section lists refunds, overpayments from the previous period, and amounts already transferred out by a payment split. Every line can be opened back to the original order or purchase order. A total with no lines cannot be checked by the channel, and finance cannot explain in an audit where the number came from.
The amount columns have to separate the share payable, the amount already split, and the amount still to be paid. The amount still to be paid equals the share payable minus the amount already split minus the deductions. Drop any one of the three and money already split out is paid again. Currency and tax are written in the header. Lines do not mix tax-inclusive and tax-exclusive amounts. The exported table and the document on the page use the same version number, so a later re-summary on the page does not leave the channel holding a stamped copy that is no longer the document in the system.
A dispute must not overwrite the original figures
When a channel disputes a line, the original settlement statement stays in the generated state. The adjustment is an appended line or a reversing line, and it cites the original line number. Editing the original document directly makes the file already exported disagree with the system. A dispute holds only when the original order, the payment record, or the ratio snapshot can show that the calculation was wrong, not when the channel wants the figures recalculated under a new policy. After review passes, the difference enters the next period or is combined before this document is paid. Which of the two applies has to be visible in the document status.
Writing the payout back records only the payment time, the method, and the payment reference. It does not change the share calculation in reverse. A failed payment stays awaiting payment. It cannot be marked settled. SimtoLink issues this kind of document as the deliverable of settlement and revenue sharing. It is stored apart from the consumption bill for the end user. An agent settlement statement is not sent to the user who bound the card, and the title of a user invoice is not written into channel settlement.
Amounts already split out need their own column
In the same period, some orders were already split to receivers at payment time, and others still wait for the enterprise to pay. If the settlement statement has only one share total, finance pays that total a second time. The document should be split into three columns: amount payable, amount already split out by the payment channel, and amount still to be paid. Only the amount still to be paid is the payment for this run. A line already split out carries the channel split-bill number, so it can be matched to the payment reconciliation file. A period whose amount still to be paid is zero is still issued, to show that this sale is already settled and was not omitted. SimtoLink settlement statements use these three columns to separate instant sharing from a periodic payout. The export carries the document version number. The version the channel checks must be the same as the payable version in the system. A recalculation on the page must not replace figures already exported. The payment reference is written back only on the record still to be paid. It does not change the payable column or the already-split column.