Skip to main content
Download OpenAPI

Multiple locations

Companies with several physical or logical locations (shops, warehouses, points of sale) often need to issue commercial documents from different locations while keeping a single fiscal identity towards the Tax Authority.

This page explains how to represent this scenario when sending a Smart Receipt.

One Business Registry Configuration, many locations​

On the A-Cube side, all receipts for a company are issued through the same Business Registry Configuration (BRC), identified by the company's fiscal_id. You don't need to create a separate BRC, nor a separate fiscal_id, for each location that issues receipts.

To indicate which location actually issued a specific receipt, you can pass the optional address object in the request body of POST /receipts. This lets you keep a single configuration while still tracking, receipt by receipt, where the sale took place.

The address object accepts the following fields:

FieldTypeDescription
street_addressstringStreet name of the issuing location
street_numberstringStreet number
zip_codestringPostal code
citystringCity
provincestringProvince

All fields are optional, as is the address object itself. If omitted, the receipt is issued without a specific location.

Example​

POST /receipts
Content-Type: application/json

{
  "fiscal_id": "1234567890",
  "items": [
    {
      "quantity": 1,
      "description": "demo test",
      "unit_price": 0.01,
      "vat_rate_code": "10"
    }
  ],
  "cash_payment_amount": 0.01,
  "address": {
    "street_address": "Via Roma",
    "street_number": "10",
    "zip_code": "00100",
    "city": "Roma",
    "province": "RM"
  }
}

Since address is passed on each request, you can freely issue receipts from different locations using the same fiscal_id, simply by changing the address object per call — no additional configuration is required on the A-Cube side.

For the full request/response contract, validation rules, and how to manage the receipt lifecycle (void, returns, discounts), see Sending a Smart Receipt and the API reference.

Last updated on