---
title: "ERP-5987 — invoice groups, so ERP2's AUTO_ADD_TO_SPECIFIC billing-profile mode has something to point at. Unlike every other feed here, these are per-CLIENT, not per-company: company 25 alone has 895 groups across 348 clients. `clientId` is therefore carried on every row so a selector can filter — a flat list of 895 is not a dropdown anyone can use. Company-scoped rather than taking a client parameter because the ERP2 mirror caches per tenant, not per client, and a per-client feed would mean one request per client on every refresh. Filtering client-side off one cached list is the cheaper shape."
method: GET
path: "/int/v1/erp2/lookups/invoice-groups"
tags: ["Erp2Lookups"]
---

# ERP-5987 — invoice groups, so ERP2's AUTO_ADD_TO_SPECIFIC billing-profile mode has something to point at. Unlike every other feed here, these are per-CLIENT, not per-company: company 25 alone has 895 groups across 348 clients. \`clientId\` is therefore carried on every row so a selector can filter — a flat list of 895 is not a dropdown anyone can use. Company-scoped rather than taking a client parameter because the ERP2 mirror caches per tenant, not per client, and a per-client feed would mean one request per client on every refresh. Filtering client-side off one cached list is the cheaper shape.

`GET /int/v1/erp2/lookups/invoice-groups`

## Headers

- `company-id` string, required

## Response `200`

Success

---

[API](https://skmtc.dev/bilflo/apis/bilflo-api.md) · [All operations](https://skmtc.dev/bilflo/apis/bilflo-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/bilflo/bilflo-api/revisions/1b4e8ebaeace/schema)