Data models

Data Formats, Precision, and Validation

Failure to adhere to the defined standards will result in data processing errors, which can lead to unexpected behavior or request rejection.

Data Encoding

All data must be UTF-8 encoded to support international characters and ensure compatibility.

Example: "name": "José Álvarez" (properly handles accented characters in UTF-8).

Date and Time Formatting

ISO 8601 format is used for all dates unless otherwise specified. All dates are in UTC.

Example: 2020-06-25T08:31:24.379Z (ISO 8601, UTC timestamp).

Currency codes

ISO 4217-1 alpha-3 is used for all currency codes.

Example: USD (two decimal places, USD currency code).

Country codes

ISO 3166-1 alpha-3 is used for all country codes.

Example: JPN (Japan).

Precision and Rounding Rules

Numeric fields support up to four decimal places, rounded to two for display, validation, and calculations.

Example: 12.3456 (four decimal places) rounded to 12.35 (two decimal places).

eezi's API supports more than two decimal places for invoice fields, ensuring accurate totals, taxes, and discounts—critical for high-volume transactions and compliance with industry regulations. However, some tax reporting formats may require only two decimal places. Therefore, eezi automatically rounds totals and tax amounts as needed for validation and as required by destination formats.

Invoices

We support invoices for various countries. Read more on the generic eezi invoice modal, which covers the base invoice fields and the supported invoice variants here.

Credit Notes

We support credit notes for various countries. Read more on the generic eezi credit note modal, which covers the base credit note fields and supported variants here.