Doc adding-tech / public Class ▮ public
ADDING·TECH
Engineering for accounting automation.


RECORDING · ch.01 — document throughput · last 240 min
samples 240 range 0–48 docs/min ▮ live
TITLE

Automation core /
for accounting & ERP integration


ABSTRACT
SUMMARY — We build software middleware that lives between client-facing channels (WhatsApp, e-mail, API) and the ERPs of the Spanish accounting market. Nexa captures every invoice, reads it with a domain-tuned language model, validates the applicable VAT regime — including IGIC, REAV, ISP and intra-EU edge cases — and synchronises it with the customer's ERP in an idempotent fashion. AddingConnected exposes Sage 200 to the whole team without consuming additional licences. The studio operates from Sabadell, Vallès Occidental, since 2020.
PL. II — METRICS
§ 0.2

Telemetry / last fiscal year

Recorded in production across our customer base. Numbers update quarterly; what you see here is the closing snapshot of FY 2025.


I documents/day
12,000
II p95 extract
9.4 s
III auto-sync
94 %
IV ERPs supported
IV+
FIG. 02 — LEGEND

I   Documents/day — peak measured during the fortnight of January declarations (M-303 deadline).

II   p95 extract — 95th percentile latency from PDF upload to validated JSON, measured at the API gateway.

III   Auto-sync — fraction synchronised without human intervention. Highlighted in phosphor.

PL. III — APPARATUS
§ 0.3

Pipeline / four stages

Schematic representation of the document processing apparatus. Each stage is independent, auditable, and recoverable in isolation. Connectors between stages are queues, not function calls — this is what makes the system robust to retries.


CHANNEL · MAIL CHANNEL · WA CHANNEL · API CHANNEL · WEB STAGE · OCR domain-tuned LLM + 9 prompt variants STAGE · VALIDATE 15 fiscal regimes + NIF / arithmetic STAGE · SYNC idempotent ERP write Odoo · Sage · FS PL. III · APPARATUS Document processing pipeline · v.IV DRAWN BY A·T studio SABADELL · MMXXVI p95 · 9.4 seconds
1 Channel aggregator — collects every inbound document and applies a routing key.
2 OCR stage — selects one of nine specialised prompt variants (DUA, IGIC, rental, REAV, multilingual, etc.).
3 Validation stage — arithmetic, VAT lines, NIF, IGIC, ISP and intra-EU rules.
4 Sync stage — idempotent write through one of four ERP connectors.
PL. IV — PRODUCTS
§ 0.4

Two products / one promise


SUBJECT.01 / NEXA
Status · in.production

Nexa

Captures invoices arriving by WhatsApp, e-mail, API, or web portal. Reads them with a domain-tuned language model — choosing one of nine prompt variants per document type — validates the applicable VAT regime (including the messy ones — IGIC, REAV, ISP, intra-EU goods vs services) and synchronises with the customer's ERP idempotently.

  • a Fifteen fiscal regimes covered in a single pass.
  • b FacturaE / UBL with XAdES signature verification.
  • c Automatic re-processing when validation fails.
  • d Multi-tenant by default — built for accounting practices.
▸ spec.nexa
SUBJECT.02 / ADDINGCONNECTED
Layer · sage.200

AddingConnected

Web frontal sitting on top of Sage 200 / Despachos. Consult cartera, banking, stock and tax statements from any device — without consuming additional licences and without blocking the Sage box for anyone else.

  • a Nine modules: banking, cartera, sales, inventory…
  • b AEAT 303 / 347 statements wired in by default.
  • c Multi-company, multi-user, fully responsive.
read.addingconnected
PL. V — CONCLUSION
§ 0.5

If your practice still types invoices,
we have something to discuss.

Thirty minutes of our time. We will demonstrate the apparatus against samples from your sector and tell you, plainly, whether Nexa fits — before you spend a euro.