Quality & Performance

To help customers assess AzoraOne’s extraction performance and overall quality of service, the following endpoints include a conformity score:

Per-file conformity

Returns a conformity object for each file, showing data quality on a per-document basis—ideal for any file list or detail view.

• Retrieve all files  
• Retrieve a file  
• Retrieve file details  

JSON example

"conformity": {
 "value": 100
}

Average conformity (across all files of a type)

This aggregates the conformity scores of every file of a given type (e.g.  Receipt, supplierInvoice) within the company—ideal for a dashboard or SLA report.

• Retrieve all companies  
• Retrieve a company  

JSON example

"metrics": {
  "averageConformity": 100
}

Availability

The conformity score is only populated when all of the following are true:

• The file has been EXTRACTED
• The file has been BOOKED
• The extraction occurred before the latest booking
• File status is COMPLETE

If any criterion isn’t met, value is null.

Value Range & Interpretation

value runs from 0–100, showing the percentage match between the most recent extraction (pre-booking) and the booked data:

• 100 – Perfect match (all extracted fields align)
• 0 – No match (no fields align)

Only fields present in the extraction or booking count. Empty/missing fields in both are excluded. This applies to both base fields (description, invoiceNumber etc) and account fields(periodicity, project, costBearer etc).

Calculation Logic

If multiple extractions or bookings exist, AzoraOne compares the latest booking against the most recent extraction before that booking.

Field Filtering

Use the conformityFilters query parameter to restrict the conformity calculation to specific fields/properties.

Pass one or more field names as a comma-separated list in conformityFilters. You may pick fields from the SupplierInvoice set, the Receipt set, or both. For each file, the API only applies the fields that are valid for that file’s type. This way, conformity is calculated only on the fields you specify (e.g., description, supplier, accounts) instead of every available field in the extraction/booking data.

• Allowed values by file type:
  • SupplierInvoice: supplier, description, invoiceDate, dueDate, invoiceNumber, ocrNumber, refNumber, orderNumber, ourRef, yourRef, totalSum, vat, accounts
  • Receipt: receiptDate, description, accounts
• Mixed lists are fine.
  If you send both SupplierInvoice and Receipt field values in one call, the filter is applied per file type (irrelevant fields are ignored for the other type).
• If you omit conformityFilters:
  The API compares all non-empty fields present in either the extraction result or the booking request. Fields empty in both are skipped.

Example

conformityFilters=description,supplier,accounts →

• For invoices: compare description, supplier, accounts.
• For receipts: only description, accounts (since supplier isn’t allowed there).