Enterprise invoicing
Contracts, purchase orders and net terms
What it is
Self-serve products charge a card on a subscription. Enterprise customers pay invoices instead: annual or multi-year contracts, purchase order numbers, net 30 or net 60 terms, payment by bank transfer, and pricing that changes over time with ramps and true-ups. Billing has to model the contract, not just the plan.
Enterprise procurement often can't pay by card at all. And contracts your billing can't represent end up managed in spreadsheets, which is where invoices go wrong.
What it takes
About 6–10 engineer-weeks to build in-house, or 2–4 using Stripe Billing, Chargebee, Maxio or Salesforce CPQ.
Answer these first
- Finance: Which contract terms do we actually sell today?
- Finance: Who edits invoices by hand, and how often?
- Sales: What can sales change in an order form without approval?
- Engineering: How does a signed contract switch on features in the product?
- Legal: Do our terms support purchase orders, net terms and auto-renewal?
- Support: Who answers when a customer disputes a line on an invoice?
This page works best with JavaScript on. Every answer also has its own address, like /what/scim.