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.
Field | Type | Description |
---|---|---|
Org_ID | string | Organization ID |
CreatedAt | timestamp | Date the report file was generated |
EventDate | date | Event date and time (ISO 8601) |
DebitAccount | string | Debit account impacted by accounting entry |
CreditAccount | string | Credit account impacted by accounting entry |
EntryType_ID | bigint | Accounting entry type ID |
Description | string | Event description |
Account_ID | int | Account ID |
Amount | double | Transaction amount |
Program_ID | int | Program ID |
ProgramName | string | Program name |
BrandName | string | Card brand |
Transaction_ID | bigint | Unique transaction identification |
RefDate | timestamp | Date the accounting_events file was created in the bucket |
ProcessingCode | string | Defines the operation type, which is used either in the network or in the non-network operations |
ProcessingCodeDescription | string | Description of the processing code |
Event_ID | int | ID that identifies the business event |
AccountEntry_ID | int | ID that identifies the accounting entry |
DebitCostCenter | string | Debit cost center |
CreditCostCenter | string | Credit cost center |
AuthorizationDate | string | Authorization date in ISO 8601 (yyyy-mm-dd) |
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.
Sample accounting events file (JSON)
{
"Org_ID": "TN-0000-0000-0000-0000-0000-0000-0000",
"CreatedAt": 57676000000000,
"EventDate": "2023-01-18T00:00:00.000Z",
"DebitAccount": "0",
"CreditAccount": "0",
"EntryType_ID": 101,
"Description": "PURCHASE",
"Account_ID": 12345678,
"Amount": 85.18,
"Program_ID": 999,
"ProgramName": "CREDIT PROGRAM",
"BrandName": "MASTERCARD",
"Transaction_ID": 720160876,
"RefDate": 19250276000000,
"ProcessingCode": "00",
"ProcessingCodeDescription": "PURCHASE",
"Event_ID": 98090944,
"AccountEntry_ID": 100181032,
"DebitCostCenter": "0",
"CreditCostCenter": "0",
"AuthorizationDate": "2023-01-18"
}
{
"Org_ID": "TN-0000-0000-0000-0000-0000-0000-0000",
"CreatedAt": 49605000000000,
"EventDate": "2023-01-18T00:00:00.000Z",
"DebitAccount": "0",
"CreditAccount": "0",
"EntryType_ID": 123,
"Description": "WITHDRAWAL",
"Account_ID": 102414567,
"Amount": 10.03,
"Program_ID": 2895,
"ProgramName": "CREDIT - Gold",
"BrandName": "MASTERCARD",
"Transaction_ID": 720158888,
"RefDate": 19250276000000,
"ProcessingCode": "01",
"ProcessingCodeDescription": "LOCAL WITHDRAWAL",
"Event_ID": 98088888,
"AccountEntry_ID": 100179999,
"DebitCostCenter": "0",
"CreditCostCenter": "0",
"AuthorizationDate": "2023-01-18"
}
{
"Org_ID": "TN-0000-0000-0000-0000-0000-0000-0000",
"CreatedAt": 83334000000000,
"EventDate": "2023-01-18T00:00:00.000Z",
"DebitAccount": "0",
"CreditAccount": "0",
"EntryType_ID": 320,
"Description": "CREDIT TRANSFER",
"Account_ID": 12345678,
"Amount": 1000,
"Program_ID": 888,
"ProgramName": "PREPAID PROGRAM",
"BrandName": "MASTERCARD",
"Transaction_ID": 720164231,
"RefDate": 19250276000000,
"ProcessingCode": "007200",
"ProcessingCodeDescription": "CREDIT TRANSFER",
"Event_ID": 98092269,
"AccountEntry_ID": 100182549,
"DebitCostCenter": "0",
"CreditCostCenter": "0",
"AuthorizationDate": "2023-01-18"
}
{
"Org_ID": "TN-0000-0000-0000-0000-0000-0000-0000",
"CreatedAt": 83604000000000,
"EventDate": "2023-01-18T00:00:00.000Z",
"DebitAccount": "0",
"CreditAccount": "0",
"EntryType_ID": 304,
"Description": "DEBIT TRANSFER",
"Account_ID": 12345678,
"Amount": 20000,
"Program_ID": 444,
"ProgramName": "PREPAID PROGRAM",
"BrandName": "MASTERCARD",
"Transaction_ID": 720164235,
"RefDate": 19250276000000,
"ProcessingCode": "007000",
"ProcessingCodeDescription": "DEBIT TRANSFER",
"Event_ID": 98092273,
"AccountEntry_ID": 100182553,
"DebitCostCenter": "0",
"CreditCostCenter": "0",
"AuthorizationDate": "2023-01-18"
}
{
"Org_ID": "TN-0000-0000-0000-0000-0000-0000-0000",
"CreatedAt": 32759000000000,
"EventDate": "2023-01-18T00:00:00.000Z",
"DebitAccount": "0",
"CreditAccount": "0",
"EntryType_ID": 243,
"Description": "PIX CANCELATION",
"Account_ID": 12345678,
"Amount": 20.1,
"Program_ID": 777,
"ProgramName": "PREPAID PROGRAM",
"BrandName": "MASTERCARD",
"Transaction_ID": 720106712,
"RefDate": 19250276000000,
"ProcessingCode": "011001",
"ProcessingCodeDescription": "PIX CANCELATION",
"Event_ID": 98088094,
"AccountEntry_ID": 100178174,
"DebitCostCenter": "0",
"CreditCostCenter": "0",
"AuthorizationDate": "2023-01-18"
}
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.
Updated 7 days ago