Keep reseller purchases, allocations and balance in one ledger

Separate the purchase record from the credit record

The confirmed packs are 100 credits for $199 USD, 300 for $499 USD and 1,000 for $999 USD. A purchase record should identify the quantity, full USD amount, date, seller confirmation and receipt reference. A credit record should identify when that quantity actually appeared in the panel. Those dates or states can differ, so do not treat a payment receipt as proof of a credited balance.

Keep both units explicit. Use a USD amount column for money and a signed credit-movement column for units. Avoid a single field called “balance” that sometimes means money and sometimes credits. The resulting ledger should be understandable without knowing a particular client’s password or private playlist.

Use a stable event record

Give each real movement a local reference, timestamp with time zone, event type, supporting panel or seller reference, signed credit amount and resulting balance. An allocation should record the requested product or duration privately alongside the actual observed deduction. Do not calculate that deduction from an assumed annual conversion.

If a panel action has been requested but not confirmed, keep it pending outside the confirmed-movement total. Otherwise a repeated click or a second operator can turn a delayed action into a duplicate. A useful status vocabulary is requested, confirmed, questioned and reversed; use the states that accurately describe your own process rather than treating all requests as completed.

Reconcile a deliberately fictional example

The quantities below are invented ledger movements solely to demonstrate addition and subtraction. They are not Hot IPTV deduction rules, client-month conversions, panel behaviour or a real transaction history. Use actual confirmed movements in an operational ledger.

Find the mismatch without changing the history

In that fictional example, the expected closing quantity is 300 + 100 − 20 − 17 + 2 = 365 credits. Compare it with an independently observed panel balance at the same point. If the panel shows a different value, the difference is a question to investigate, not permission to replace the opening balance until the totals agree.

First check whether the comparison times match. Then check for an unrecorded purchase, duplicate movement, pending action, reversal or data-entry sign error. Match each suspected entry to its actual supporting reference. If the reason remains unknown, record the discrepancy and ask for a provider explanation; do not manufacture an adjustment to make the spreadsheet look settled.

Post corrections as new evidence

When an operator corrects an entry, retain the original event and add a clearly linked reversal or adjustment with its reason and confirmation. The signed values should explain the path from the old balance to the corrected one. Keep a separate note if only a descriptive field was wrong and no credit movement occurred.

For a shared operational workbook, agree who records a confirmed action and how another person can review it. Avoid concurrent edits that overwrite transaction references. Keep a dated backup before a reconciliation correction. None of these record-keeping steps replaces the panel’s actual terms or establishes that a disputed movement must be reversed.

Keep unresolved commercial rules outside forecasts

Credit-to-duration, trial and renewal deductions, credit expiry and adjustment terms have not been verified by this website. Ask for the actual applicable table and a written explanation before forecasting customer quantities or selling a specific entitlement. A pack’s arithmetic unit cost does not fill those missing fields.

Store panel credentials, personal client details and private account values outside any publicly shared ledger. Use internal nonpublic references for client records and give access only to the people who need it. A clean reconciliation should answer what arrived, what moved and what remains, without exposing the means to operate the account.