API Integrations · Elic / AGT

Elic / Spectrum Invoice API

Direct integration between Odoo Accounting and the Spectrum e-invoicing platform: invoices and credit notes validated, signed and submitted automatically, with status, QR codes and rejections synced back to Odoo.

Client
Elic / AGT
Category
API Integrations
Platform
Odoo 17 Accounting + Spectrum e-invoicing API
Duration
6 weeks
Team
3 specialists

0%

first-time acceptance rate

0%

automated submissions

0

manual uploads

The challenge

Elic / AGT had to submit invoices to the Spectrum e-invoicing platform. The finance team was exporting invoices from Odoo and uploading them manually, re-keying data whenever an invoice was rejected.

They needed compliant, automatic submission that wouldn't disrupt their existing invoicing workflow.

The system

Validated, signed and submitted on posting, with the platform's response stored in Odoo.

Posted
Validated
Signed
Submitted
Accepted
Accepted

Tax Invoice

INV/2026/04182

Bill to

Northline Trading

Issue date

06 Oct 2026

ItemQtyAmount
Industrial filters (box of 12)41,920.00
Hydraulic hose 3/4" × 10m61,140.00
On-site installation1650.00
Subtotal
3,710.00
VAT 15%
556.50
Total
4,266.50
Signed payload → Spectrum
POST /einvoice/v1/documents
{
"documentType": "INVOICE",
"number": "INV/2026/04182",
"issueDate": "2026-10-06",
"buyer": { "taxId": "3101•••••0003" },
"total": 4266.50,
"signature": "MEUCIQ…"
}
Platform response
202 Accepted
{
"status": "ACCEPTED",
"uuid": "a7f3c0e2-…-91bd",
"qr": "AQ5Ob3J0aGxpbmUg…",
"validatedAt": "2026-10-06T09:14:22Z"
}

Illustrative view with representative data.

Problems & solutions

Problem 1

Strict schema validation

Many invoices were rejected for missing tax IDs, wrong unit codes or rounding differences.

How we fixed it

A pre-submission validator checks every invoice against the API schema and business rules inside Odoo and shows the user exactly what to fix before posting.

Problem 2

Signing and secure credentials

Submissions required certificates and tokens that had to be stored and rotated safely.

How we fixed it

Credentials and certificates are stored encrypted per company, tokens are refreshed automatically and access is restricted to finance administrators.

Problem 3

Platform downtime

When the external API was unavailable, invoices piled up with no visibility.

How we fixed it

Submissions run through a persistent queue with retries, and a status board shows pending, accepted and rejected documents with reasons.

What we delivered

  • Automatic submission of invoices and credit notes on posting
  • Pre-submission schema and business-rule validation
  • Secure certificate and token management
  • QR codes and platform references printed on invoices
  • Status sync: accepted, rejected and cancelled
  • Retry queue and compliance status dashboard

How the system flows

  1. 1Invoice posted
  2. 2Validated in Odoo
  3. 3Signed & submitted
  4. 4Platform response
  5. 5QR & reference stored
  6. 6Status reported
Impact

Key operating metrics before the project and after go-live.

Rejected submissions

-93%
Before14%
After1%

Time per invoice submission

-100%
Before4 min
After0 min

Days to resolve rejections

-90%
Before5 days
After0.5 days

Tell us about your challenge. A solutions architect will reply within one business day with ideas, not a sales pitch.