How it works

How Billspree turns price tags and subscriptions into posted invoices—from first principles through pricing, bill runs, and payments.

Billspree maps the full path from price tags and subscriptions to posted invoices and payments. The sections below follow that flow.

What is a Bill? (First principles)

Before diving into setup or configuration, let’s define what a bill (or tax invoice) actually is.

At its core, a bill is a structured invoice that translates a commercial agreement and a consumption log into a clean customer balance. It is a historical and legal proof of transactions over a specific service period.

A standard Tax Invoice PDF breaks down visually and logically into four distinct sections:

1. Dynamic Document Header (Identification): Contains general identity details such as client company info, tax registrations (VAT/EIN), invoice numbers (INV-ID), billing dates, and the specific Service Period (e.g., May 1 to May 31).
2. The Core Line Items: The line-by-line breakdown of everything being charged:
   • Subscription Base Fees: Static flat rates (e.g., SaaS Pro access fee).
   • Modular Add-On Fees: Stackable extra modules (e.g., premium support pack).
   • Metered Usage Fees: Dynamic consumption lines (e.g., API compute, bandwidth consumed, kWh).
3. Totals & Adjustments: This is where system calculations compound:
   • Summing line subtotals.
   • Subtracting percentage or flat discounts (e.g., high-volume customer discounts).
   • Compounding sales taxes, duties, or corporate VAT based on client regional properties.
   • Calculating the final Total Amount Due.
4. Payment & Footer Metadata: Bank transfer numbers, ACH routing, payment terms (e.g., Net 30), and mandatory legal disclaimers.

The diagram below illustrates how these billing components dynamically connect to populate a compiled Tax Invoice PDF. Customer subscriptions and usage logs feed in from the left, while back-office prices and rules evaluate from the right:

How these elements map to the bill:

• Agreements & Ingestions (Left Side):
  • Subscription Agreement (Card 1): Activates Base & Add-On line items and passes client properties (e.g., SLA Level, user count) to drive descriptions on the invoice.
  • Usage Ingestions (Card 2): Continuously logs consumption—API streams, meter final readings, or direct usage deltas—to populate quantity and usage rows on the invoice.
• Pricing & Structural Blueprints (Right Side):
  • Rate List Components (Card 3): Stores raw unit rates, flat tiers, and pricing values that resolve invoice unit prices.
  • Charge List Components (Card 5): Defines the structural blueprint placeholders that map directly to line totals and adjustments (discounts and taxes).

The ecosystem of a bill

A bill does not exist in a vacuum. Inside any commercial organization, an entire business ecosystem rotates around the invoice. This ecosystem bridges the gap between what sales representatives sell, what operations calculate, what finance collects, and what compliance teams audit.

Capability	Question it answers
Products & Services	What do we offer the world?
Pricing	How do we sell it—and how is the price tag built?
Subscription	Which customer is on that price tag right now?
Billing	How do we produce and manage the invoice?
Payments	How do we collect what is owed?
Revenue Recognition	When do we report revenue to finance?

Products and services

A product or service is what your business offers the world—electricity supply, fiber internet, a SaaS platform, water connection, premium support, or a professional services day. That is the commercial promise: what the customer receives.

That is different from how you sell it. Customers do not buy an abstract product record; they buy at a price—a monthly fee, a per-kWh rate, a tiered API plan, or an enterprise quote with negotiated terms.

Pricing

The price tag is how you sell a product or service. It answers: how much, under which rules, for this customer and this period.

Creating a good price tag is rarely as simple as one number on a sticker. The same product might need:

• Different list prices by region, segment, or partner (multiple rate cards).
• Charging rules—taxes, discounts, surcharges, usage formulas (e.g., VAT on base + metered kWh).
• Terms that change the math—SLA tier, seat count, committed volume (captured on the subscription at signup).
• Usage each cycle and proration when the deal changes mid-contract.

Pricing is the discipline of designing and maintaining those price tags. A live price tag is applied per customer on a subscription; billing then prints the invoice.

Subscription

A subscription is the live agreement between your business and one customer for a priced product or service. It is where pricing meets the customer:

• Which offer they are on: The customer is enrolled on a Base Plan (and any Add-On Plans)—the same packages that carry the rate card and charging rules from pricing. The subscription is the hook that says this account uses that price tag.
• Their version of the price tag: Subscription inputs captured at signup or during the contract—SLA tier, seat count, tax status, region, or committed volume—often determine which charging rules run and at which rates.
• Service lifecycle: Active, suspended, disconnected, or cancelled; start dates and billing cycles tied to the plan’s billing configuration.
• Usage and delivery: Meter readings and usage events accrue against the subscription each period, then flow into pricing together with that customer’s rate card and rules.

The product is what you offer. The price tag is how you sell it. The subscription is which customer is on which tag right now—ready to bill.

Without a subscription, you have a catalog and a price list but no one to bill. Billing takes subscribed accounts and turns them into invoices each cycle.

Billing

Billing is the operational cycle of creating, reviewing, and finalizing customer invoices.

• Bill runs and billing cycles: Generating invoices for a period (monthly, weekly, etc.) for all customers on a schedule.
• Invoice compilation: Bringing subscription data, rated charges, and branding into a tax invoice—often via a Word (.docx) template with merge fields.
• Draft review and adjustments: Correcting meter reads, manual line items, or credits on draft bills, reprocessing totals, then posting when accurate.
• Consolidation and grouping: One invoice per customer or separate bills by department, service, or cost center.
• Disputes and credit notes: Formal corrections after issue when the customer or finance challenges a charge.

Billing answers how the invoice is produced and locked—not how cash is collected.

Payments

Payments cover collecting cash (or recording remittance) against what billing issued.

• Payment methods: Cards, ACH, wire, wallets, or cash recorded against an invoice.
• Gateways and automation: Secure checkout, saved payment methods, and automated charge on due date (e.g., via Stripe).
• Dunning and collections: Reminders, retries, grace periods, and late payment fees when invoices go unpaid.
• Allocation: Matching payments to open invoices and updating customer balance and AR.

Payments answers did we get paid for this bill—not how revenue is recognized in the general ledger.

Revenue recognition

Revenue recognition is a finance and accounting discipline—related to billing, but not the same thing.

When cash is collected or an invoice is issued, finance must decide when to recognize revenue under accounting standards (such as ASC 606 or IFRS 15):

• Deferred revenue: A customer pays $1,200 upfront for an annual service; finance recognizes revenue over twelve months as the service is delivered—not all on day one.
• Service period matching: Usage or delivery in April is recognized in April’s books, even if the bill is issued in May.
• Audit trail: Every recognized amount should trace back to a contract, bill line, and (where applicable) usage or delivery evidence.

Revenue recognition answers when this counts as revenue on the P&L—often handled in the general ledger or a dedicated revenue module, alongside billing.

The Billspree stack

Layer	What Billspree does
Pricing	Pricing Template canvas, rate cards, charging rules, Base and Add-On plans
Subscription	Enroll customers, capture subscription inputs, lifecycle, usage against each account
Billing ops	Bill runs, draft → adjust → post, B2B consolidation, invoice templates
Payments	Stripe, dunning, AR (rev rec often stays in your GL today)

Pricing in Billspree

Step one is the Pricing Template—your canvas for one product or service (e.g., residential electricity, business SaaS, fiber internet).

On the canvas (template)	On each price tag (pricing modules)
What can be priced—slots for fees, usage, taxes, credits	The actual rate card (Rate List) and charging rules (Charges Rules)
Which customer terms apply (SLA, region, seats)	Values and formulas filled in per plan
No dollar amounts, no formulas	Composed into sellable Base Plans and Add-On Plans

One template, many price tags: mix and match rate cards and rules into different plans without rebuilding the product line from scratch. Each billing cycle, the active plan’s pricing modules apply that tag using subscription data and usage.

Subscriptions in Billspree

Subscriptions are not optional—they are how pricing meets each customer before billing ops runs.

A subscription binds a plan’s price tag to one customer: which Base or Add-On offer they are on, their subscription inputs (SLA, region, seats, etc.), lifecycle (active, suspended, cancelled), and the usage that accrues each period. Pricing modules rate that subscription; bill runs turn the result into invoices.

Billing ops in Billspree

Billspree supports two billing shapes that often need different tools elsewhere:

Mode	Typical need	How Billspree helps
B2C-style	One organization billing thousands of retail customers—each account should get its own bill with minimal manual work	Scheduled bill runs, batch processing, draft → adjust → post, and clear per-customer invoices
B2B-style	One business customer with many subscriptions but finance wants one consolidated invoice (or bills split by cost center)	Consolidated or grouped invoicing—multiple active subscriptions rolled into a single tax invoice, or separated by your rules

Shared across both: Word (.docx) invoice templates, term-based bill runs, and adjustments on drafts (meter fixes, manual lines) before post.

Payments in Billspree

Payments are intentionally straightforward:

• Stripe for card checkout, automated charges, and retries.
• Dunning on plans—grace periods, reminders, late fees.
• File uploads where bulk work is faster—subscriptions, usage, and related operational data (see Usage and subscription import flows).
• AR for invoices, credit notes, and recording payments against open balances.

Revenue recognition in Billspree

Posted bills include the line items and service periods finance needs as a source of truth. A dedicated revenue recognition capability in Billspree is still in development; today, recognition is typically handled in your general ledger (e.g., BookSpree) or external finance tools aligned to posted invoices.