Backfill a reported transaction

post

https://example.com/v1/transactions/backfill/reported

Submit a transaction that was previously reported to the tax authority with a different eInvocing solution. Otherwise called "backfill": the transaction will be available for reference in our systems

Body Params

country_code

string

required

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

Validations:

Required property
Country code must be uppercase ISO 3166-1 alpha-2.

direction

string

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

Validations:

Maximum length: 20
Values allowed are (ignore case): SENT, RECEIVED

issue_date

string

The date when the transaction was issued by an external application.

Validations:

Must be an RFC3339 format date

tax_authority_id_1

string

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

Validations:

Maximum length: 150

tax_authority_id_2

string

Secondary transaction identifier returned by the tax authorities.

Validations:

Maximum length: 150

transaction_date

string

required

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

Validations:

Required property
Must be an RFC3339 format date

transaction_id

string

required

Unique external transaction identifier provided by the customer. Used as idempotency key. e.g., MY_EXTERNAL_IDENTIFIER_0001.

Validations:

Maximum length: 150
Required property

transaction_number

string

Unique and usually sequential identifier of a transaction displayed on the document and reported to tax authorities. e.g., invoice number for debit scenario or credit note number for credit scenario. e.g., IE00000001

Validations:

Maximum length: 50

Responses

401

Authentication failed - missing or incorrect subscription key

429

Too many requests were sent for a short period of time. Try again a bit later.

Language

Credentials

Header

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

202Accepted - transaction was successfully submitted for processing.

400Bad customer request - some of the provided information is incorrect or mandatory data is missing. Check the message and errors section of the response for more details.

5XXInternal server error. Its not you, its us! We are experiencing a rare and unexpected system disruption. Retry again later. The message field of the response will contain more information for the cause. Feel free to contact us.