Zenskar is billing infrastructure. It ingests customer activity, applies the pricing and revenue logic defined in your contracts, generates invoices, collects payments, and produces accounting-ready revenue schedules automatically. The platform is built around a single principle: billing is a data pipeline. Understanding that pipeline is the fastest way to understand Zenskar.Documentation Index
Fetch the complete documentation index at: https://docs2.zenskar.com/llms.txt
Use this file to discover all available pages before exploring further.
The data model
Every object in Zenskar is a stage in the quote-to-cash flow.| Object | What it represents |
|---|---|
| Customer | The entity being billed. |
| Contract | The commercial agreement: what is sold, at what price, on what schedule. |
| Product | A unit of value being sold: a subscription, a usage-based service, a one-time fee. |
| Usage event | A raw record of customer activity: an API call, a query, bytes transferred. |
| Billable metric | An aggregation over usage events, producing the quantity that drives an invoice line item. |
| Invoice | The periodic bill, derived from contract terms and billable metrics. |
| Payment | The settlement of an invoice. |
| Revenue schedule | The accounting record of when and how revenue is earned. |
How a contract drives billing
The contract is the central object. Everything else flows from it. A contract captures:- Who is being billed (the customer)
- What is being sold (products, grouped into phases)
- How much (the pricing model per product: flat-fee, per-unit, tiered, volume, matrix, or combinations)
- When (billing cadence, start date, end date)
- How revenue is recognized (performance obligation policies for ASC 606 / IFRS 15)
How usage-based billing flows
For metered products, Zenskar acts as a data pipeline between your product and your invoices.- Usage events arrive from your system via the Zenskar API, a CSV upload, a connected data source (Snowflake, BigQuery, PostgreSQL, and others), or a scheduled remote SQL query.
- Billable metrics define how those events are aggregated. You configure the aggregation logic once using a visual builder or SQL, and Zenskar recomputes it each billing cycle.
- The billing engine applies the pricing model from the contract to the billable metric, producing invoice line items.
- An invoice is generated on schedule or on demand.
Two parallel workflows
Once a contract is created, Zenskar runs two concurrent workflows.| Workflow | Purpose | Output |
|---|---|---|
| Billing | Execute the payment terms in the contract. | Invoices, credit notes, payment receipts. |
| Revenue recognition | Satisfy ASC 606 / IFRS 15 accounting requirements. | Revenue schedules, deferred revenue reports. |
Where Zenskar sits in your stack
Zenskar connects your product to your financial systems.- Upstream: usage data flows in from your product, data warehouse, or CRM (Salesforce, HubSpot, DealHub, and others).
- Downstream: invoices, payments, and revenue schedules flow out to NetSuite, QuickBooks, Xero, Sage, SAP, or Zoho Books.
- Payment collection: Stripe, Adyen, and Razorpay integrate directly. Zenskar can initiate charges and record receipts without leaving the platform.
- Tax: Avalara AvaTax and Anrok calculate sales tax at the invoice level automatically.
Where to go next
Quickstart
Add a customer, ingest usage, and generate your first invoice.
Contracts
Understand how contracts drive billing and revenue recognition.
Usage & metering
Learn how usage events flow into billable metrics and invoices.
Revenue recognition
See how Zenskar automates ASC 606 / IFRS 15 compliance.