Process
After the user successfully makes a payment, the merchant applies to the tax cloud platform for issuing an electronic invoice based on the order title, generating a PDF/OFD with a QR code, delivered via email or SMS. After the full electronic invoice promotion, the interface and elements continue to evolve, and must be updated following policy changes.
Integration
The IoT Order Center transmits product codes, tax rates, and buyer tax numbers; retry on failure and the red flush process must be complete.
Archiving
Electronic accounting archives must meet retention period and tamper-proof requirements.
IoT orders and invoicing elements
Modules and card-type products often involve a combination of "one-time hardware sales + periodic billing for connection services." The order center needs to distinguish between goods and service tax rates, invoicing timing, and units of measurement to avoid issuing invoices for data packages at hardware tax rates by mistake. For prepaid top-ups and postpaid bills, the invoice amount should match the payment transaction, refund corrections, and coupon allocations. When devices are returned, red-ink adjustments or issuing a red-letter information form must be done simultaneously. During the parallel period of fully electronic invoices and tax control equipment, interface fields, document formats, and verification methods may operate in dual tracks. The system must ensure compatibility and gradual switching to prevent invoicing backlogs during peak periods from affecting the user experience.
Coordination with module project delivery
Government and enterprise clients often require that invoices correspond one-to-one with acceptance forms, contract numbers, and project numbers. For IoT projects that deliver modules and installation services in batches, billing should support milestone-based invoices or consolidated invoices, with batch and site information reflected in the remarks column. When interfacing with financial shared services or ERP systems, pay attention to separating price and tax, cost center, and revenue recognition rules; cross-border business also needs to handle withholding taxes and import VAT certificates. Automated reconciliation should verify exceptions such as 'paid but not invoiced' and 'invoiced but not collected' daily to reduce month-end manual adjustments and tax audit risks.
Engineering Practice Supplement
Starting from 'e-invoices,' common on-site issues often focus on 'indicators meet lab standards but are difficult to replicate in the field.' Besides RF and protocols, check power grounding, connector contacts, and firmware race conditions. On the cellular side, it is recommended to collect RSRP/SINR, cell reselection, and PDP reestablishment records; on the application side, there should be clear strategies for retries, idempotence, and queue persistence. When involving data security and compliance, specify the collection scope, storage location, retention period, and third-party sharing in privacy policies and contract attachments to avoid high costs for fixing issues after deployment.
Layout files and tax classification codes
An electronic invoice is a structured document covered by a digital signature, not an image whose wording can be edited at will. The signature covers the buyer, the seller, the tax classification code, quantity, unit price, tax, and the price-plus-tax total. OFD and PDF are the usual carriers. Verification checks the original layout with the tax authority or a regulated service; opening an email attachment does not replace that check. A module order often puts hardware, installation and commissioning, and connectivity on one contract, and those three items do not share a code, tax rate, unit, or allowed invoicing time. A prepaid balance, gifted data, and the amount actually paid after a coupon split also cannot be written through as hardware sales.
Automatic invoicing is available only when the order center already supplies a stable buyer name or taxpayer ID, the split between price and tax, and the time the business occurred. An enterprise title without a tax ID is rejected. A natural-person buyer usually does not need a tax ID, but the name should match the payment account so a later credit note still refers to the same person. Hardware fits a blue invoice after shipment or acceptance; recurring service is invoiced on the billing cycle. While a tax rate changes, an exemption filing changes, or an adjustment crosses a month, hold the documents for finance confirmation and do not keep submitting them automatically.
Idempotent callbacks and credit-note reissue
The interface most easily treats “the request went out” as “the invoice exists.” Saving only an HTTP success, without the layout hash and the signature receipt, leaves no proof of which invoice was issued when the user later downloads a blank file. If a timed-out retry has no idempotency key such as order number plus invoicing request number, the tax-control or fully digital channel issues another blue invoice once the queue clears. If a reversal only changes the local order and never receives red-letter confirmation, the tax side still treats the original blue invoice as valid, and the books keep an amount that was issued but never reversed.
A data package coded as hardware, or a unit written as “set” rather than “use” or “month,” will not match the contract at filing. The success callback and refund reversal from aggregated payment belong in the same check; do not invoice when the amounts disagree. The archive should keep at least the original layout, the signature-check record, and the contract number. The email body alone is not enough. Limit concurrency on a batch reissue so a channel timeout is not mistaken for failure and submitted again. An invoice QR code is not the code used for QR code payment; the two encodings differ.
Automatic invoicing handles only documents whose title, tax ID, price-tax amount, and timing are complete. During a policy change or a cross-month adjustment, leave them in the confirmation queue. A retry uses the order number plus the request number so a timeout does not create a second blue invoice. A credit note follows confirmation from the tax side; a local status change does not void the original. Archive the original layout with the verification result. Keep classification codes and units separate for data and hardware. Limit concurrency on batch reissue: a queue timeout is not permission to submit again at once.