Understand the Bursar system
These pages explain the boundaries and domain model behind Bursar. Read them in order when you are evaluating the system or designing an integration; use the how-to guides when you need implementation steps.
Read the concepts in order
- Architecture defines the application boundary, capabilities, transaction model, and extension points.
- Credit accounting explains accounts, lots, leases, allowances, and the append-only ledger.
- Pricing model shows how operations, measures, rate cards, and rules produce an exact charge.
- Plans and access explains entitlements, quotas, allowances, credit policies, and admission controls.
- Billing and commerce connects provider events to offers, subscriptions, plan assignments, and credit grants.
- Configuration and catalog revisions brings those domains together in one validated, versioned document.
Browse concepts
Architecture
The Bursar facade and its capabilities — credits, catalog, accounts, billing, and commerce — over the Postgres schema, with migrations and tenant isolation.
Credit accounting
Understand accounts, the append-only ledger, credit lots, leases, allowances, and the invariants that connect them.
Pricing model
Understand how operations, measures, rate cards, and price rules produce exact decimal charges.
Plans and access
Understand how plans combine allowed operations, rate cards, allowances, entitlements, quotas, credit policies, and admission controls.
Billing and commerce
How billing connects the credit ledger to a payment provider — offer catalog, normalized events, and auto-recharge guardrails.
Configuration
Understand how one validated BursarConfig document defines pricing, credits, plans, commerce, and immutable catalog revisions.
Continue with an implementation task
Open the how-to guides to provision tenants, protect monetary operations, manage credits, connect subscriptions, or integrate agent tooling.