IOSOR Learn
Tax Invoices Are Not the Public Rate Card
Learn why tax invoices in the IOSOR console represent historical financial transactions and VAT compliance rather than the live, dynamic rate card for SMS and OTP services.
Tax Invoices Are Not the Public Rate Card.
Distinguishing Ledger Entries from Pricing Tables
The IOSOR console is designed to separate real-time traffic costs from fiscal documentation. While the Pricing tab displays the current cost per SMS or OTP attempt based on destination E.164 prefixes, the tax invoice represents a historical snapshot of funds added to the wallet. It is critical to understand that a receipt for a USD 20 prepaid floor deposit is a financial instrument for accounting, not a dynamic lookup for per-message routing.
VAT and Tax Compliance in White-Label Billing
Tax invoices are generated to satisfy corporate compliance and VAT requirements. When you fund your account, the system calculates the gross amount. However, the internal balance reflects the net value available for programmatic consumption. This distinction ensures that when an SMS is sent and a DLR is received, the deduction from your balance matches the net rate card exactly.
Prepaid Floor and Transactional Thresholds
IOSOR operates on a strict prepaid model to maintain low-latency routing. The minimum entry point is a USD 20 prepaid floor, which serves as the initial balance for testing OTP flows and SMS delivery. This deposit triggers a tax invoice immediately. Unlike the rate card, which might fluctuate based on global carrier shifts, the invoice is a fixed record of the transaction.
JIT Number Assignment and MRC Logic
Number procurement follows a Just-In-Time (JIT) logic. When you assign a number to your project, the system places a prepaid hold for the first month's MRC (Monthly Recurring Charge). This charge appears in your internal ledger and eventually on a consolidated tax invoice. It is not part of the 'per-message' rate card. The rate card focuses on variable traffic, while invoices capture these fixed costs.
Documentation and Related Resources
To manage your financial data effectively, you must distinguish between the live pricing API and the static PDF exports provided in the billing section. The following resources provide deeper insight into spend management and reporting:
Related: Tax Invoices Must Match Ledger Export · VAT and Payout Rails for Financial Closing · Prepaid hold before first debit.
Start with IOSOR
Navigate to the Billing section in your IOSOR console to inspect historic VAT statements alongside net ledger entries. Use the live Pricing tab or API endpoints to monitor dynamic per-prefix message rates rather than relying on PDF receipts. Confirm your active MRC holds before adding new virtual numbers to maintain accurate accounting boundaries.
IOSOR takeaway
Tax invoices serve exclusively as accounting artifacts for fiscal compliance, recording wallet top-ups, net balance credits, and local VAT assessments. They represent settled financial movements rather than the dynamic, destination-specific rate card applied during real-time traffic delivery.
Do not attempt to audit per-message SMS or OTP route costs using static tax exports. Keep real-time pricing analysis locked to the Pricing tab and treat PDF invoices strictly as proof of payment for your accounting ledger.
Was this guide helpful?
Related guides
- Tax Invoices Must Match Ledger Export
Ensure financial integrity by aligning tax invoices with real-time ledger exports and DLR status verification in your white-label CPaaS console.
- VAT and Payout Rails for Financial Closing
Learn how to export tax-compliant invoices, manage VAT settings, and handle payout rails within the IOSOR console for month-end financial closing.