Structure
Map data from an ERP, business application or export to a usable model.
ACAPI by Akabar Développement
The compliance and integration engine behind FactureCare.
ACAPI prepares, checks and structures invoice data to produce results that FactureCare, an ERP or a partner application can use.
Guided integration · demonstration · pilot
ValidationReportJSON
Canonical data Versioned profile
{
"status": "FAIL",
"rulesetVersion": "ma-2026-draft",
"findings": [{
"code": "AKB-VAL-005",
"severity": "ERROR",
"fieldPath": "seller.taxId"
}]
}What ACAPI does
From source data to usable results.
Four connected functions in a single engine, without imposing a single business-facing interface.
Check
Apply business and compliance rules grouped in a versioned rules profile.
Explain
Return a status, findings and recommendations that teams and systems can use.
Transform
Produce a working UBL format when validation succeeds or only returns warnings.
How it works
An engine at the centre of a defined integration chain.
The source system extracts the data. Mapping aligns it with the ACAPI model. The engine then applies a rules profile and returns structured results.
Each stage and responsibility is defined before the pilot.
Source system responsibility
ERP / business application
CSV / Excel
Preparation and mapping
Extraction / connectorData access and transport
MappingField correspondence
ACAPI modelCanonical data
ACAPI engineChecks and rules profile ma-2026-draft · versioned
Results and destinations
Structured resultsStatus · errors · warnings · recommendations
TransformationTarget format when the scenario and checks allow it
FactureCare
ERP / partner application
Rules profiles
Versioned and explainable checks that can evolve with requirements.
A profile groups the rules executed for a given context. Its version appears in the report so that each result can be linked to the reference used at the time of the check.
This traceability is not a certification, exhaustive coverage or official validation.
Profile used in demonstrations
- Profile
- ma-2026-draft
- Status
- Preparatory
- Use
- Demonstration · pilot · data preparation
Simplified responseJSON
{
"status": "FAIL",
"valid": false,
"blocking": false,
"rulesetVersion": "ma-2026-draft",
"findings": [{
"code": "AKB-VAL-005",
"severity": "ERROR",
"category": "PARTY",
"fieldPath": "seller.taxId",
"message": "The seller tax identifier is required",
"recommendedFix": "Provide the seller ICE or a compatible taxId"
}]
}Structured results
A response that teams and systems can read.
ACAPI returns more than a verdict. The report can associate a code, severity, category, affected field, explanation and recommended correction.
Overall status and blocking state Applied profile version Structured findings and recommendations
One engine, two uses
Clear for business teams. Integrable for technical teams.
For business teams
Understand what is blocking and what needs to be corrected.
- Readable check status
- Identified findings and fields
- Actionable recommendations
- Explainable results in FactureCare
For ERP vendors and integrators
Connect existing data to a structured engine.
- Canonical data model
- API and structured errors
- Mapping and versioned profiles
- Guided integration according to the project
Integration modes
Integration options matched to the system and pilot.
ACAPI is not presented as a public self-service API. Access, mapping and data flows are reviewed with Akabar Développement before integration.
Project-based API
API integration is assessed and scoped according to the architecture, data and use case.
Files & batch processing
CSV or Excel data can be imported, mapped and checked in batches as part of a guided scenario.
Mapping to the canonical model
A mapping profile connects source fields to the invoice model expected by ACAPI.
Qualified demonstration & sandbox
Technical access is prepared as part of a demonstration, pilot or qualified project.
Boundaries and responsibilities
An integration scoped before production rollout.
Responsibilities are defined between Akabar Développement and the partner according to the existing system, deployment mode and pilot scope.
Your system
Looking to integrate ACAPI with your system?
Let’s start with your architecture, data and use case.