Billing, pricing, and financial evidence

Commercial item classes

• Product: a deployable managed system or subscription.
• Plugin or integration: an optional extension connected to a product or workflow.
• Professional service: audit, rescue, migration, implementation, training, development, or consulting work.
• Support plan: response commitments, channels, included time, and overage rules.
• Infrastructure: compute, storage, backup, network, hardware, or managed hosting.
• Metered usage: messages, transactions, API consumption, AI usage, storage, or another measurable unit.

Why the classes matter

A one-time implementation fee should not behave like a monthly product subscription. Provider usage should not be hidden inside professional-service labour. Support entitlement should not be inferred from a product name. Explicit classes allow the same commercial meaning to survive estimate, proposal, contract, subscription, billing schedule, invoice line, payment allocation, credit, refund, and revenue reporting.

Financial evidence

An invoice is an issued financial record, not a copy of the current catalogue. Payment submissions and provider events are evidence that must be verified and allocated. Credits and refunds remain separate records so corrections do not erase the original transaction history.

Sufrone does not automatically create an invoice from an accepted proposal total when VAT treatment, eTIMS handling, deposit structure, milestone schedule, due date, billing contact, or invoice wording is still unknown.

What clients should verify

• The legal client name and billing contact are correct.
• The invoice references the accepted scope or billing period.
• Currency, tax treatment, quantity, unit price, discount, and total are visible.
• Payment evidence is submitted against the correct invoice and method.
• A dispute describes the specific line, amount, and reason rather than only stating that the total is wrong.