Billing & Invoicing

Billerang turns rated transactions (RTs) into invoices through bill runs. The platform has a single universal API for creating and running bill runs (POST /api/v1/billingRuns). Both one-off (exceptional) runs and cycle-based monthly runs use the same endpoint, with the run type auto-derived from the scope.

The billing pipeline

A bill run selects eligible RTs for a scope, aggregates them into invoice lines, produces invoices, and validates them. Invoices that fail validation move to a quarantine child run for review.

Key pages

Page	Use when
Bill Runs	You want to create, schedule, or understand a bill run. Covers scope, dates, process modes, and the full payload.
Aggregation Rules	You want to control how RTs are grouped into invoice lines. Every knob is documented with worked examples.
Split Billing	You want the same RT set to produce multiple invoices per BA (by payment method, by invoice type, etc.).
Quarantine Review	You need to review or release invoices that validation rejected or flagged suspect.
Billing Engine Internals	You want to understand WO → RT → IL → invoice end-to-end.

Quick start

curl -X POST "https://api.billerang.com/api/v1/billingRuns" \
  -H "Authorization: Bearer $TOKEN" \
  -d '{
    "billingAccountCodes": ["BA_001"],
    "invoiceDate": "2026-05-13T00:00:00Z",
    "lastTransactionDate": "2026-05-13T23:59:59Z",
    "processType": "FULL_AUTOMATIC",
    "runOptions": { "autoValidate": true }
  }'

Returns the validated bill run with the produced invoices. See Bill Runs for the full reference.