Pismo can run batch jobs to generate report files, including those that report daily account limits and those required by financial regulations. These reports are available upon request.

Report file generation and paths

Report files are generated periodically. The schedule and frequency (daily, weekly, and so on) varies depending on how each report is set up. In most cases, a report is not generated if no records are found that match the filter conditions.

Reports are transmitted to your organization's dedicated cloud storage bucket. To receive the report files you need, contact your Pismo representative.

📘

Cloud storage

Most of Pismo’s clients use Amazon Web Services (AWS) S3 buckets as their cloud storage containers, so this section assumes you're using AWS. However, Pismo does support other cloud services, such as Google Cloud Platform (GCP) and Microsoft Azure. Contact your Pismo representative for information about using a cloud service other than AWS.

Files are written and saved according to type (daily, monthly, or full) and date. The full type is explained below. The URL takes the form [path to S3 bucket]/reports/[job_name]/[type]/[date values]/[filename].parquet, where [filename] represents a PySpark hash.

For example:
s3://pismo-dataplatform-tn -55317847-57cd-45a3-8aed-a8dadd63cc6b/reports/accounting_events/type=daily/year=2020/month=1/day=10/[filename].parquet
In this example, the value for job_name is "accounting_events". You can find the value for job_name in the documentation for the specific report file.

🚧

The date partition values in the report correspond to the last available data date, not to the date when the job was executed. For example, for a daily job that runs on March 11, the date partition values correspond to March 10.