---
title: "Backfill a reported transaction"
method: POST
path: "/v1/transactions/backfill/reported"
---

# Backfill a reported transaction

`POST /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

## Request body

- ReportedTransactionRequest
  - `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

## Response `202`

Accepted - transaction was successfully submitted for processing.

- OperationResultResponse
  - `errors` TransactionErrorResponse[] — List of errors in case the request was unsuccessful.
    - `code` string — Error code of the issue. e.g., field_not_valid
    - `doc_link` string — The link for the error documentation. Follow it to gather more details about the error
    - `field` string — Field from the input request that caused the error, in case of validation errors. e.g. transaction_date
    - `message` string — Error message of the issue. e.g., Date must be in RFC3339 format.
    - `type` string — Error type of the issue. e.g., warning, validation, general, tax_authority
  - `message` string — Information about the failure reason in case the request was unsuccessful.
  - `operation_id` string — Auto-generated unique identifier of a transaction operation returned upon async operation request.
  - `transaction_id` string — The unique external transaction identifier provided with the initial request.

## Other responses

- `400` — Bad 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.
- `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.
- `5XX` — Internal 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.

---

[API](https://skmtc.net/fonoa/apis/fonoa-api.md) · [All operations](https://skmtc.net/fonoa/apis/fonoa-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fonoa/fonoa-api/revisions/cf0ebc843a3f/schema)