Skip to main content

Email digest and daily report

Available on request

A-Cube configures this during onboarding. To request it, contact A-Cube.

Request an hourly email digest to check processing results, a daily CSV report for your systems, or both. A-Cube configures each for your account.

For callbacks to your application, see Transfer webhooks. For complete API examples, follow UBL JSON to KSeF or CSV to SdI.

Email digest​

The digest is sent hourly to configured recipients, with separate emails for successful and failed files. You can receive two emails in the same hour. No email is sent unless A-Cube has configured a recipient address.

Emails use these subjects:

OutcomeSubject
Files that failed❌ A-Cube Transfer: Error during processing of your files
Files that succeeded✅ A-Cube Transfer: Your files have been processed successfully

The body lists files and their results:

CaseWhat the body shows
One successful fileMessage: <message>
One problem for a fileError message: <message>
Several problems for a fileErrors found: <N>, with the first 10 references and messages
Files that succeededItems transferred: <N>, with the first 10 references
No detail for a fileError during file processing

For a CSV row, the reference looks like <file>.csv:row <N>.

For destination validation failures, the email says violations found, see details in the ACube dashboard or via API. Open Invoice transfers for the field and message, or use the tracking API for the violation code and full details. See Violation codes for corrections.

A success email confirms that A-Cube's service for the destination accepted the document, not the destination's later outcome.

Daily report​

A-Cube writes the daily CSV report to reports/ in your home directory. It covers uploads and documents from a configurable period.

ItemValue
ScheduleDaily at 07:00 CEST in summer or 06:00 CET in winter (05:00 UTC)
Pathreports/transfer_report_YYYYMMDD.csv, where the date is the previous day in Italian time
PeriodThe last closed calendar days in Italian time, today excluded. The default is 7 days
FilesTransfer writes no file when there is nothing to report
FormatCSV, UTF-8 with a byte order mark, times in Italian time (YYYY-MM-DD HH:MM:SS)

Reports cover overlapping periods, so consecutive files can contain the same rows. Use ingested_at and completed_at to follow an upload across reports.

Columns​

The report contains these 13 columns, in order:

ColumnMeaning
file_nameThe file you uploaded.
source_typeTechnical label of the upload. Do not use it to tell SFTP uploads from REST API uploads.
upload_statusThe status of the upload.
ingested_atWhen Transfer received the file.
completed_atWhen the upload reached its final status.
upload_errorsReserved. Empty today.
document_file_nameThe file of the document.
document_rolesource, intermediate or target.
document_statusThe status of the document.
transmission_outcomeok or error, on target documents.
transmission_uuidThe identifier of the document at the destination service.
transmitted_atWhen the destination service answered.
violationsThe violations of the document, as CODE: message, separated by ;.

Each row pairs an upload with a target document or a failed document. CSV row failures appear on the source document. Uploads without documents have one row with empty document columns.

See Statuses and where to see them for status definitions. Reports are deleted after 90 days, like other files in your home directory. Download any reports you need before they expire.

Choosing between the two​

  • Use the email digest for hourly processing updates.
  • Use the daily report to import upload and document results into your systems.
  • Use the tracking API to follow an upload during processing.