Billing Responsibilities

Billing

Billing owns reusable instructions and notices, reviewed run populations, execution outcomes, recurrence configuration and installment arrangements. The owned objects and exposed operations above define this module’s boundary. Current code remains hosted by Accounting; the recorded target is a separate Billing backend in the combined Accounting and Billing console.

Run instructions are saved at creation, and execution names an accountable person whose authority is checked again for batches. Uniqueness, receipts and installment keys protect their stated local scopes. Committed business effects remain after later failure. Run deletion and workspace purge can remove history, so ordinary run retention is not a promise of permanence.

The module exposes staff operations and a trusted Commerce arrangement subset, two query datasets and a workspace export. It registers no business events, model tasks or Submissions bindings. The listed invariant references describe its guarantees without broadening them into a promise of complete delivery or one transaction for an entire run.

Platform supplies job execution, saved-query selection, communications, grants and workspace orchestration. Accounting supplies the current invoice transaction and shared configuration, financial, product, idempotency and scheduling dependencies. CRM supplies party and recipient facts through direct reads. Commerce owns purchasing and the down-payment boundary; the recorded target also gives it installment invoice creation. Those remote migration contracts remain unfinished.