Legal and Operational Separation When Sharing Invoicing Infrastructure

Shared infrastructure is fine when controls are explicit: who can issue invoices, which bank account receives settlement, and how intercompany charges are documented. Problems appear when informal processes let one brand’s AR leak into another’s reports.

Minimum control set

1. Chart-of-accounts mapping per entity—even if invoices look similar.
2. Immutable invoice numbers per brand and jurisdiction rules.
3. Owner approval thresholds for discounts and write-offs.
4. Quarterly reconciliation between invoicing totals and accounting ledgers.

Capricon helps design these patterns before scale makes them painful to retrofit.