Dates are treated differently for "payout" balance movements vs. other types of balance movements. Why is this the case?
Specifically, whilst other movements use the 'created_at' date we case the 'payout' balance movements to choose the 'available_on' date if available; if not, it's only then we revert to the 'created_at' date.
We'd love to be able to capture monthly opening and closing balances for our Stripe accounts. How can we do that via the Fivetran Stripe connector?
We had a look over the same daily_overview.sql as referenced above and this line stand out:
daily_balance_transactions.daily_net_activity + daily_balance_transactions.total_gross_payout_amount)/100.0 as daily_end_balance
Both the daily_net_activity and total_gross_payout_amount totals look to me like outgoings, so if this is determined as the daily_end_balance what are they subtracted from to begin with?
Or are we saying that we provide this data in the modelled table as the total outgoing balance and, along with the data like total_sales/total_refunds, our clients can then run further models on top of these to understand balances across their accounts?
Specifically, whilst other movements use the 'created_at' date we case the 'payout' balance movements to choose the 'available_on' date if available; if not, it's only then we revert to the 'created_at' date.
We had a look over the same daily_overview.sql as referenced above and this line stand out: daily_balance_transactions.daily_net_activity + daily_balance_transactions.total_gross_payout_amount)/100.0 as daily_end_balance Both the daily_net_activity and total_gross_payout_amount totals look to me like outgoings, so if this is determined as the daily_end_balance what are they subtracted from to begin with?
Or are we saying that we provide this data in the modelled table as the total outgoing balance and, along with the data like total_sales/total_refunds, our clients can then run further models on top of these to understand balances across their accounts?