Connector Improvement: Stripe Connector: Include 'activity_at' column in balance_transaction schema
AnsweredI am looking to migrate our company's Stripe data analysis from custom python scripts querying the Stripe reports API to consuming from the Fivetran Stripe connector.
I am comparing the reports generated by Stripe to the Fivetran data. The Stripe report that I am reviewing is the 'activity.itemized.2' (https://stripe.com/docs/reports/report-types#schema-activity-itemized-2) report which has two timestamp columns:
- 'balance_transaction_created_at': Time (in UTC) at which the balance transaction affected your Stripe balance.
- 'activity_at': The time (in UTC) to which we attribute this line item. This time is based on the originating activity, such as the date of the originating charge for a post-billed fee. (For activity attributed to a time range—often a full day or a full month—this will be the final second of that range.)
The Fivetran balance_transaction table has the following two timestamp columns:
- 'available_on'
- 'created'
From comparing transactions between the two sources I found that the Stripe report's 'balance_transaction_created_at' field matches the fivetran 'balance_transaction'.'created' column.
Conversely, The Stripe report's 'activity_at' column does not match with the fivetran 'balance_transaction'.'created' column. Nor does it match with any other timestamp within the Stripe connector.
Feature Request: Can the 'activity_at' column from the Stripe report be included in the 'balance_transaction' schema?
-
Official comment
Hi Daniel -
Thanks so much for submitting this feature request! I'm the PM for our Stripe connector. Unfortunately I can't find that exact report. The URL you provided me with doesn't direct me to the specific report. I did find a report called `balance_change_from_activity.itemized.2`. I'm not sure if that is the same thing.
The balance_transaction table we sync comes from the balance transaction API endpoint here. Stripe doesn't have an `activity_at` field on that endpoint, however that actually makes sense given the description you gave for the `activity_at` field. If `activity_at` is the date of the originating charge then you should be able to get the created date for the charge that your balance transaction is related to by joining BALANCE_TRANSACTION to the CHARGE. For instance:
SELECT CH.CREATED, BT.*
FROM CHARGE CH
LEFT JOIN BALANCE_TRANSACTION BT
ON CH.BALANCE_TRANSACTION_ID = BT.IDIf you can help point me to details on that report, that would be great. Also, if i'm not understanding the definition of the `activity_at` field, please elaborate and I will try to see if there is a solution.
Best,
Erin -
Hi Erin,
Apologies. I have had trouble with that link too. The report documentation can be found here: https://stripe.com/docs/reports/report-types and searching for 'activity.itemized.2'. There is then a link to click through to documentation on the columns in the report.
Note: I am not sure why the Stripe documentation behaves this way but you may have to navigate away from and then back to the page using the sidebar menu on the left.

Using the link directly leads to an error.
I can also provide a Python script that queries this report.
Thanks,
Daniel
-
Hi Erin,
Just wondering were you able to get access to the documentation?
The data provided by this column is important for the reporting required by our finance department and it would be good to know whether another solution needs to be found.
Here is a screenshot of the doc in question. Please see the section referencing the 'activity_at' column specifically:

Daniel
Please sign in to leave a comment.
Comments
3 comments