Sales and Sage entries panel

The Hub Fiscal panel installs from the Library and gives you, on top of the Hub Fiscal database, everything you need to see how much is sold, where, and what has been posted to Sage X3. It only reads data: it changes nothing in Hub Fiscal and sends nothing to Sage.

What it includes

Five dashboards

Dashboard	What it is for
Hub Fiscal · KPIs por portal	Documents, net sales, VAT and credit notes for each portal (mitienda.com, .it, .fr, .pt), with the Canary Islands split out inside mitienda.com. Bar chart, donut and a table per portal.
Hub Fiscal · Ventas por país	Net sales by destination country (top 12 plus “Others”), breakdown and daily trend.
Hub Fiscal · Resumen	Overview: totals, documents by status and by fiscal provider, and the latest documents.
Sage · Asientos agrupados	What is sent to Sage: one entry per day, group and type, with its status (sent, pending, failed), the first and last invoice and the number Sage returns. Click a row to see the documents it includes.
Sage · Detalle de operaciones	Search any document by order or invoice number and check whether it is already posted. Click a row to see the full detail of the operation.

Two forms

• Hub Fiscal: buscar un documento: type an order or invoice number and it returns the five most recent matching documents.
• Hub Fiscal: simular la agregación a Sage: pick a day and it calculates how many entries would result, without sending anything to Sage or writing anything in Hub Fiscal. It is always a simulation. If any entry of that day was left pending or failed, it flags it as “to resend” (the real aggregation retries them on its own next run).

The template also brings a portal with a side menu that gathers the seven screens in a single page.

How the figures are calculated

• Net sales = invoices − credit notes, on the net amount (excluding VAT), and only for completed documents.
• Portal: the domain the order comes from. The Canary Islands are split out by shipping postcode (35xxx and 38xxx) inside mitienda.com.
• Not yet posted (on the Sage dashboard): completed documents, from a portal numbered by Hub Fiscal (not those numbered by a third party, such as Bill.pt) that are not in any entry yet. Everything before the posting start day counts here: that is expected.
• The dashboards read the database live, with no copies: what you see is what is there.

Filters

The dashboards have a filter bar: dates (from / to), portal, type (invoices or credit notes) and, depending on the dashboard, entry status, search by order or invoice and Sage status (posted or pending). The portals offered by the “Portal” filter are fixed in the template (mitienda.com, .it, .fr and .pt): edit the filter in each dashboard to set your own store domains. They also work on the public link, and you can save a view with the filter set, for example …/d/<token>?portal=mitienda.it&from=2026-10-01&to=2026-10-12.

Installation

1. Credential. The account must have one Hub Fiscal credential (MySQL type) with the word “Hubfiscal” in its name, for example “MySQL Hubfiscal”. If there are several, the panel warns you. A read-only user (SELECT) is enough.
2. Sage tables. The “Sage ·” dashboards need the aggregation tables in the Hub Fiscal database (schema_aggregation.sql and schema_batches.sql). If they are missing, the dashboard says so with a clear message; the sales dashboards still work.
3. Install the template from the Library. It creates an app with the dashboards, the forms and the portal as a draft.
4. In the two form workflows, choose the Hub Fiscal credential in each Hub Fiscal node.
5. Open the app and, if you want to use the portal, click Portal → Publish.

Fiscal data: mind who sees the links

A published dashboard or portal shows sales amounts to anyone with the link. In production use a security group on the app folder (dashboards and forms inherit it) or leave the dashboards unpublished and open them with your session. See forms and dashboards security.

Self-hosted servers (On-Premise)

The dashboards are fed by a read-only engine route (/api/hubfiscal-panel) that uses the account’s Hub Fiscal credential. An engine older than that version does not have it and the dashboards fail to load: update the engine before installing the template.

Limits

• Each dashboard shows at most the 300 most recent documents that match the filter.
• The dashboards do not write data. The real posting to Sage stays in its own workflow (cron off until it is turned on on purpose).
• The dashboard editor’s “date range” filter does not reach the widgets in the signed-in view; that is why the panel uses two separate fields, “From” and “To”.