Product features

Billing features that stay
out of your way.

OctaBMS is intentionally narrow. It does invoicing, payments, reminders, recurring billing, reports, and template design extremely well, then gets out of the way.

4
RBAC roles
100%
API coverage
∞
Tenants
<1s
PDF generation

Capability map

Built like a system

Live platform

Control plane

One product, two surfaces

The dashboard gives teams a visual control plane while the API keeps integrations deterministic and scriptable.

Security

Built for tenant boundaries

Every interaction stays inside a tenant scope. That keeps reporting, reminders, and exports predictable.

Operations

Less manual bookkeeping

Invoices, reminders, and payment updates move through the same model, so there is less duplicate work and fewer reconciliation gaps.

What you get

A narrow product can be the strongest product

The best billing software is opinionated. These blocks are designed to keep workflows fast without making the UI feel stripped down.

API-first by default

Every core action is exposed as a clean REST endpoint. Use bearer tokens for UI sessions and X-API-Key for system integrations.

Strict multi-tenant isolation

Tenant-scoped data, tenant-aware rate limits, and account uniqueness enforced at the platform edge.

Granular RBAC

Role and permission checks stay aligned between API, dashboard, and background jobs.

Template editor studio

Build invoice layouts with drag and drop blocks, responsive previews, and reusable template components.

Recurring automation

Monthly, quarterly, and yearly schedules generate invoices and reminders without babysitting.

Reporting that matters

Outstanding, aging, tax summaries, payment registers, and exports built for operators and accountants.

Workflow

Designed for operators, accountants, and developers

The same platform can feel simple to a finance team and precise to an engineering team because the controls are separated, not mashed together.

Team roles

Super Admin, Admin, Accountant, and Viewer each see only what they should.

Money flow

Invoice, pay, void, export, and report all share one transaction model.

Automation

Recurring schedules and reminder workers handle the repetitive parts in the background.

Proof

Numbers that make the rest of the page believable

A few platform numbers that summarize the product design philosophy.

4
RBAC roles
100%
API coverage
∞
Tenants
<1s
PDF generation