> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/accounting-configs/list-all-products-with-a-store-specific-account-number.md).

# List all products with a store specific account number

List the products that have a store specific account number configured.

Only products with an override are returned — this is the configuration, not the product catalogue. Products without an override use the account number configured centrally on the product, or the product group and VAT configuration for the store.

An override is not applied for every product kind. On a product sold under the VAT margin scheme it is listed here but has no effect on the accounting report, Navision, 24Seven or VismaNet — the sale still books to the margin sales and margin VAT accounts. Unimicro, VismaBusiness and XLedger do not implement the margin scheme, and will book the sale to this account instead. On a package wrapper product the override has no effect — the wrapper is not booked at all, only its components are, and an override on a component does apply. On a Flow gift card product the account is used as the gift card settlement account, not a revenue account.

There is no delta query. Overrides are few (typically 10-50 per store), so an accounting integration should fetch the full list per store.

Required permissions: ACCOUNTING\_CONFIG

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"AccountingConfigs","description":"AccountingConfigs"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"responses":{"AccountingConfigsProductListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","required":["items","paging"],"properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/AccountingConfigsProductResponseSchema"}},"paging":{"$ref":"#/components/schemas/Paging"}}}}}}},"schemas":{"AccountingConfigsProductResponseSchema":{"title":"AccountingConfigsProductSchema","type":"object","required":["productUid","sku","productName","account"],"properties":{"productUid":{"$ref":"#/components/schemas/UID"},"sku":{"type":"string","description":"The product's SKU"},"productName":{"type":"string","description":"The product's name"},"account":{"description":"Account number","type":"string"}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"Paging":{"description":"totalCount The total number of items in the result set.\n\npageSize The number of items per page.\n\npageNumber The current page in the result set.","properties":{"pageNumber":{"type":"integer"},"pageSize":{"type":"integer"},"totalCount":{"type":"integer"}},"required":["totalCount","pageSize","pageNumber"],"title":"Paging","type":"object"}},"parameters":{"pageSizeQuery":{"description":"The number of items per page in a result set.","in":"query","name":"pageSize","required":false,"schema":{"type":"integer"}},"pageNumberQuery":{"description":"Reference to a specific page in a result set.","in":"query","name":"pageNumber","required":false,"schema":{"type":"integer"}}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/accountingConfigs/products":{"get":{"summary":"List all products with a store specific account number","tags":["AccountingConfigs"],"responses":{"200":{"$ref":"#/components/responses/AccountingConfigsProductListResponse"}},"operationId":"get-tenants-stores-accountingConfigs-products","description":"List the products that have a store specific account number configured.\n\nOnly products with an override are returned — this is the configuration,\nnot the product catalogue. Products without an override use the account\nnumber configured centrally on the product, or the product group and VAT\nconfiguration for the store.\n\nAn override is not applied for every product kind. On a product sold\nunder the VAT margin scheme it is listed here but has no effect on the\naccounting report, Navision, 24Seven or VismaNet — the sale still books\nto the margin sales and margin VAT accounts. Unimicro, VismaBusiness and\nXLedger do not implement the margin scheme, and will book the sale to\nthis account instead. On a package wrapper product the override has no\neffect — the wrapper is not booked at all, only its components are, and\nan override on a component does apply. On a Flow gift card product the\naccount is used as the gift card settlement account, not a revenue\naccount.\n\nThere is no delta query. Overrides are few (typically 10-50 per store),\nso an accounting integration should fetch the full list per store.\n\nRequired permissions: ACCOUNTING_CONFIG","parameters":[{"$ref":"#/components/parameters/pageSizeQuery"},{"$ref":"#/components/parameters/pageNumberQuery"},{"name":"productUid","in":"query","schema":{"$ref":"#/components/schemas/UID"},"description":"Only return the override for this product."},{"name":"sku","in":"query","schema":{"type":"string"},"description":"Only return the override for the product with this SKU."}]}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/developers/api-documentation/accounting-configs/list-all-products-with-a-store-specific-account-number.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.