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.
- 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.
- 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.
- The deadline is the next thing you see
- Payment terms become a deadline in the ledger of what is due. On the buying side it is automatic — a received supplier invoice books its own payable, a recurring expense generates its occurrences. On the selling side you record it against the invoice. Overdue is computed when you look, never a stale flag someone forgot to clear.
- The bank scores the match
- When the money lands, the bank link pulls the movement and scores it against the open invoices: right direction, exact amount, inside a week. Above the confidence threshold it reconciles by itself; below it, it proposes and a person decides. Closing the deadline stays that person’s click — the product does not pretend to have paid it for you.
The same thread runs elsewhere: a table order closes into the day’s takings, project hours become the invoice, a goods receipt moves the stock and books the goods-in entry behind it. One event, and the registers that follow from it.
