Consolidated Invoicing for Non-Novated Clients

Problem
Catch-e currently generates separate invoices per charge type for non-novated fleet clients — typically one for lease rentals, one for recharges, and one for fuel and tolls. For small clients this is a minor inconvenience, but for larger clients the volume becomes unwieldy. One current example: a client invoiced by cost centre across ~100 vehicles and 5 cost centres receives approximately 15 separate invoices every month (3 charge-type invoices × 5 cost centres), each of which is likely lengthy given the vehicle count. This creates unnecessary administrative burden for the client's AP team (reconciling and processing many documents instead of one), increases the risk of processing errors or missed invoices, and reflects poorly on Catch-e's invoicing experience relative to what a large enterprise client would expect from a mature platform.

Current Behaviour
Invoices are generated and issued separately by charge type (lease rentals / recharges / fuel & tolls), and where a client is set up for cost-centre-based invoicing, this multiplies further — one set of charge-type invoices per cost centre. There is currently no mechanism to consolidate these into a single invoice per client, or per cost centre, across charge types.

Proposed Improvement
Introduce the ability to consolidate multiple charge types into a single invoice per billing entity (client or cost centre), while retaining itemised detail within that invoice so the underlying breakdown (lease rental vs recharge vs fuel/tolls) remains transparent for reconciliation. This should be configurable per client rather than a global behaviour change, since some clients may have accounting or reconciliation processes built around receiving separate invoices by charge type (e.g. different GL coding, separate approval workflows, or separate payment terms/timing for fuel vs lease).

Suggested Scope / Considerations

• Configuration option at client level (and potentially cost-centre level) to select "combined" vs "separate" invoicing by charge type

• Consolidated invoice should clearly section/subtotal by charge type so nothing is lost in translation for clients who rely on that breakdown for internal coding

• Where cost-centre invoicing is used, confirm whether consolidation should also allow combining across cost centres into one client-level invoice, or just combining charge types within each cost centre (the latter would take the example client from 15 invoices to 5)

• Consider impact on existing integrations/exports that may key off invoice type (e.g. if downstream finance systems expect separate invoice numbers per charge type)

• Numbering/referencing convention for combined invoices, and how this interacts with existing invoice numbering sequences

• Migration path for existing clients — likely opt-in rather than retrofitted automatically

• Any GST/tax reporting implications of combining charge types that may currently be treated distinctly