DECA ERP capabilities

Manage the full lifecycle of the electronic Administrative Control Document from the web or your ERP: preparation, collaboration, issue, access and retention.

Try the demo View ERP integration

At a glance

The main capabilities, each explained in one sentence.

01

Create and edit DeCAs

Create standard and NTS-format documents manually or automatically.

02

PDF, QR and stable URL

Every issued document has a PDF, QR code and permanent public link.

03

Pending trips

Register a trip first and add its date, registrations or goods later.

04

External collaboration

The carrier completes authorised fields through a private link.

05

Multi-stop operations

One DeCA can contain shipments with their own origins, destinations and goods.

06

Full history

Keep PDF versions and see what changed, when and by whom.

07

Operational master data

Customers, carriers, drivers, vehicles and saved locations.

08

Users and permissions

Access separated by company, customer or carrier, with scope controls.

09

Email notifications

Notify the driver with a link and QR code automatically or on demand.

10

Search and export

Filters, sorting, mobile cards, CSV and bulk PDF downloads.

11

REST integration

A documented API for ERP, TMS, invoicing and fleet systems.

12

Bilingual responsive web app

The full application works in Spanish and English on desktop, tablet and mobile.

Capabilities in detail

Functional detail to assess how DECA ERP fits into your operation.

Document lifecycle

A document can start as a pending trip and be completed when definitive information becomes available.

  • Create, edit, duplicate, cancel and complete documents.
  • Company numbering plus a global internal identifier.
  • A new PDF version is generated after changes.
  • Standard documents and the alternative NTS FORMAT.

PDF and collaboration

The company decides who prepares the trip and who completes its operational details.

  • PDF with QR code and stable public access URL.
  • The PDF remains available through its public URL after the trip is completed, beyond the seven calendar days specified by the regulations.
  • Separate private completion link; this link closes when the trip is completed.
  • Permission for date and registrations only, or extended to goods.
  • The link can be revoked and remains unchanged while active.

Routes, stops and goods

The same document supports simple trips and routes with several collections or deliveries.

  • Multiple shipments in one document.
  • Origin, destination, reference and notes per shipment.
  • Several goods lines for each leg.
  • Quantity, unit, weight, packages and pallets where applicable.

Entities and resources

Regular data is maintained once and reused when documents are created.

  • Entities marked as customer, carrier or both.
  • Drivers with contacts and notification preferences.
  • Tractor units, trailers and other vehicles.
  • Saved locations, farms, origins and destinations.
  • Excel or CSV import for customers, vehicles and drivers.
  • Manual creation or ERP synchronisation.

Drivers and communications

A driver can be assigned to a trip without publishing unnecessary personal information.

  • Up to two drivers assigned to a DeCA.
  • Name and note shown in the PDF only when authorised.
  • ID, telephone and email excluded from the public document.
  • Email with link and QR code, recording time and recipients.

Control, history and access

Activity is traceable and previous versions remain available.

  • Immutable PDF versions and a current document.
  • Comparison of headers, drivers, routes and goods.
  • Search by participant, tax ID, registration, route or reference.
  • Filters by different dates, status and planning.
  • CSV export and bulk download by period.
  • Internal retention for the longer of 15 months after the journey or 24 months after creation, while the service is active.
  • Global and per-DeCA sent email logs.

Companies, users and access

Each service holder keeps its data separate and defines each user's scope.

  • Master data and document isolation by company.
  • Users with full or limited access.
  • Restrictions by customer and carrier.
  • Checks also apply to direct document IDs.
  • Bilingual, responsive application.
  • Browser access with no installation.

API for ERP and TMS

Integration automates the workflow without replacing the web application.

  • Create, update, retrieve and search by external reference.
  • Private URL returned when the trip is first created.
  • Status, history and current PDF retrieval.
  • Synchronisation of master records and saved locations.
  • Dedicated endpoints for multi-stop and NTS documents.
  • OpenAPI, Swagger, examples and VB.NET with Access demos.

Three ways to work: use the full web application, connect your ERP through the API, or combine both. Web changes are available to the external system on its next document query.

See how it fits your operation

Try the complete workflow or review the integration documentation.

Request a demonstration