Get a transaction

Activity code is a standard classification of productive economic activities. It can be used to represent EAC (Economic Activity code), a standard classification governed by ISIC and NACE (https://joinup.ec.europa.eu/collection/eu-semantic-interoperability-catalogue/solution/statistical-classification-economic-activities-european-community/about), or other similar concepts.

e.g., 10.32 is Manufacture of fruit and vegetable juice

Indicates whether the transaction is a backfill.

Business model of the transaction. Can be either B2B or B2C depending on the customer type.

ISO 3166-1 alpha-2 uppercase country code the transaction is taking place in.

ISO 3166-2 uppercase code of the principal country subdivision (province, state, region) the transaction is taking place in.

Primary currency code of the transaction represented as ISO 4217 3 letter uppercase currency code e.g. USD.

The source of the transaction data: API, CSV, TA, SUPPLIER or DIGITAL_EXCHANGE.

A flag to be used in a migration phase. It signals in which format amounts should be parsed. If true amounts are parsed as decimals, if false amounts are parsed as an integer representing the minor currency unit.

Document representing a transaction can be sent or received. Allows businesses to report both inbound and outbound transactions for VAT deduction purposes. Default: SENT.

RFC3339 timestamp when the transaction document was generated.

RFC3339 datetime string representing an ending point in time.

Describes the frequency of reporting invoices to tax authority, used with SUMMARY invoice types.

RFC3339 datetime string representing the point in time when transaction is issued.

Language of the transaction document represented as ISO 639-1 uppercase language code. Required when document generation is enabled. Defaults to EN (English) if not provided.

A text note attached to a transaction. Notes are HTML enabled and will be displayed on the visual document. e.g., This is my HTML <e>enabled</e> note.

The unique Fonoa identifier of a transaction request/operation.

A value describing the operation regime for the transaction if applicable. e.g., export - indicating the transaction should be reported as cross-border transaction.

A value describing the details of the operation regime specified on the transaction. e.g., provide export type supported by the tax authority.

RFC3339 datetime string representing the deadline until which the payment must be made.

A country-specific QR code displayed on a visual document usually used to verify the validity of the document against the Tax Authority. e.g., Croatian QR code - https://porezna.gov.hr/rn/?zki=3b767891212f678bd9f697b6a06f2191&datv=20231226_1929&izn=9915

The external transaction identifier of the original transaction the credit is referencing. e.g., MY_ORIGINAL_IDENTIFIER_0001

The transaction number of the original transaction the credit is referencing. e.g., 0001

RFC3339 timestamp when the transaction was reported to the tax authorities.

A pool of transaction numbers issued by tax authorities to pick the transaction number from.

The transaction shall be assigned one of the numbers from this pool when reporting it to the tax authorities.

Usually series can be opened and closed at any time and there can be multiple open series at the same time.

e.g., 2022_01

The transaction signature generated by an external application.

The date of the transaction signature generated by an external application.

RFC3339 datetime string representing a starting point in time.

Status of the transaction.

Main transaction identifier returned by the tax authorities. e.g., JIR in Croatia.

Secondary transaction identifier returned by the tax authorities. e.g., ZKI in Croatia.

Decimal representing total transaction amount with precision up to 9 digits. If you are using the legacy integer representation for this field refer to this documentation on how to migrate to decimals: https://docs.fonoa.com/reference/amounts-and-rounding

Decimal representing sum of item net values with precision up to 9 digits. Does not include discounts. If you are using the legacy integer representation for this field refer to this documentation on how to migrate to decimals: https://docs.fonoa.com/reference/amounts-and-rounding

Decimal representing sum of all taxes applied to the transaction items with precision up to 9 digits. If you are using the legacy integer representation for this field refer to this documentation on how to migrate to decimals: https://docs.fonoa.com/reference/amounts-and-rounding

The channel through which the transaction was conducted, such as in-person, online, telephone order, etc.

RFC3339 datetime string representing the point in time when transaction is executed.

External transaction identifier provided by the customer.

Locally compliant transaction number.

Represents the type of document that needs to be issued depending on the transaction debiting or crediting effect on the TA. Possible values are: DEBIT, FULL_CREDIT, CANCELLATION, DEBIT_ADJUSTMENT, CREDIT_ADJUSTMENT

Type of the transaction that usually depends on transaction value and business model (B2B or B2C).

The two most common types are FULL and SIMPLIFIED.

An extension of transaction number including unique keys such as fiscal year and supplier information. Used by marketplaces to disambiguate duplicate transaction numbers. e.g., 2022-SUP001-000001