Accounting events report files

The accounting events report contains the accounting events from the previous day. The files for this job are saved in your designated cloud storage container in the /reports/accounting_events/ subfolder. See Report file generation and path for more information.

The following table lists the accounting events report fields.

📘

The report's decimal values are rounded to the hundredths.

FieldTypeDescription
Org_IDstringOrganization ID
CreatedAttimestampDate the report file was generated
EventDatedateEvent date and time (ISO 8601)
DebitAccountstringDebit account impacted by accounting entry
CreditAccountstringCredit account impacted by accounting entry
EntryType_IDbigintAccounting entry type ID
DescriptionstringEvent description
Account_IDintAccount ID
AmountdoubleTransaction amount
Program_IDintProgram ID
ProgramNamestringProgram name
BrandNamestringCard brand
Transaction_IDbigintUnique transaction identification
RefDatetimestampDate the accounting_events file was created in the bucket
ProcessingCodestringDefines the operation type, which is used either in the network or in the non-network operations
ProcessingCodeDescriptionstringDescription of the processing code
Event_IDintID that identifies the business event
AccountEntry_IDintID that identifies the accounting entry
DebitCostCenterstringDebit cost center
CreditCostCenterstringCredit cost center

Sample accounting events file

The report file is delivered to the storage container in parquet format. The following examples are in the CSV, JSON, and HTML formats for readability.

The file contents are the same for any type of program related to the records. The credit, debit, or prepaid program records differ only in descriptions and codes. For more information on standard processing codes associated with Pismo program types, see processing codes and transaction types.

CSV: The attached sample_accounting_events.csv file illustrates the file layout and provides sample contents of the accounting events file. The file layout here corresponds to the layout of the .parquet file.

JSON: The following example illustrates sample contents of the accounting events file in JSON format for readability.

HTML: The following example illustrates the file layout and provides sample contents of the accounting events. The file layout here corresponds to the layout of the .parquet file.