Equinox — ERP by Altovar

The whole business, in balance.

Invoices and their deadlines, stock and its suppliers, tables, rooms, work orders and the people who run them. Equinox keeps them in one system, on European infrastructure — so when one thing moves, the books move with it.

Talk to us See the modules
The Equinox web application: the dashboard of a demo company, with the navigation sidebar listing the installed modules and widgets summarising documents, deadlines and activity.
Equinox — the dashboard of a demo company, real application
Measured, not promised

The depth is a fact.

Data schema
366 models counted in the database schema, not estimated. Ledger entries, stock lots, table orders, room nights, work orders — each one a first-class record, not a spreadsheet tab.
E-invoicing
SDI, both ways issues and receives electronic invoices through the Italian exchange system, follows every outcome, and quarantines what fails instead of losing it.
Built-in AI
Pay per use a prepaid balance per company, drawn down job by job. When it is empty the AI stops. Nothing spends in your name.
Where it runs
EU application and data live on Altovar infrastructure in Europe, and every record belongs to exactly one company tenant.
The modules

Twelve modules, one memory.

Everything below exists in the product today — none of it is roadmap. The modules share one database, so a sale in the dining room and a delivery at the warehouse end up in the same books.

And further in: fleet, rentals, price lists, approval workflows, document archive, email campaigns, knowledge base.

One thread through the books

From quote to reconciled payment.

The reason to run one system instead of five is what happens between the steps. In Equinox the space between a quote and its money is not an export file — it is the same record, changing state.

  1. A quote becomes an invoice

    The document engine carries one record from quote to order to invoice: same lines, same customer, a number drawn from the ledger sequence. Nothing is retyped, so nothing diverges.

  2. The invoice goes to the exchange

    Equinox builds the XML, transmits it to the exchange system, and follows the response. A rejection comes back as work to fix, in quarantine — not as silence discovered at month end.

  3. A deadline starts counting

    Issuing the invoice creates its payment deadline: amount, direction, due date. The calendar shows what is owed and what is expected before either is late.

  4. The bank confirms it

    When the money lands on the account, the bank link pulls the transaction and matches it to the invoice. The deadline closes itself — reconciled, not remembered.

The same thread runs elsewhere: a table order closes into the day’s takings, project hours generate the invoice, a goods receipt updates stock and the supplier balance in the same movement. One event, every book updated.

On the floor

It runs the room, not just the office.

Equinox keeps going where back-office suites stop: at the till, in the dining room, at the front desk. Operations and accounting in the same product, so service and books never disagree.

At the till
Register sessions and Z reports, coupons and gift cards, receipts printed on the fiscal printer.
In the dining room
Orders taken by table on the floor plan and sent to the kitchen display; reservations with their own rules; a menu guests open by QR code.
At the front desk
Arrivals on the tape chart, check-in to check-out, folios that become invoices, housekeeping that knows which room is next.
The Equinox restaurant module: the floor plan of a demo venue with tables and their current state, as used to take orders during service.
Restaurant floor plan — demo venue
Built-in AI

AI inside the work, on a meter.

There is no chatbot bolted on the side. The AI drafts documents, imports messy lists, reads receipts, searches across modules and takes voice — inside the permissions of whoever asked.

In the flow of work

Draft a proposal from a deal, turn a supplier PDF into stock lines, classify leads, edit the menu by asking. It acts where you already are, not in a separate tab.

A meter, not a subscription

Each company holds a prepaid balance and every job draws from it, with the price shown. When the balance is empty, the AI stops: it cannot spend what you did not load.

Under your permissions

The assistant holds the same permissions as the person using it, gated module by module. What you cannot open, it cannot read.

The platform

One platform underneath.

Equinox stands on the Altovar platform — the same identity, tenancy and permission model that carries the rest of what we build.

One identity

You sign in through Auris, the Altovar identity service. Accounts and sessions are governed in one place, not per application.

The tenant is the boundary

Every record carries its company. Running more than one company means switching tenant, never mixing books.

Permissions by action

Rights are granted per action on a resource: who may issue invoices is a separate question from who may read them.

Bring the books together.

Tell us what your company runs on today. We will show you Equinox on your kind of data — and be straight about what it does not do.

Write to sales All Altovar products