@Dash reconcile last month's Stripe payouts against the books for Corven and flag every delta.
Live in Slack or Microsoft Teams
Reconcile Stripe payouts against QuickBooks
A month of card payouts rarely lines up cleanly with the books. Dash matches every Stripe payout against the QuickBooks ledger, explains each difference by cause rather than listing it, and reports the rows it could not match instead of forcing them into a category to make the total balance.
Get started for free Chat with Dash, the AI teammate that works inside Slack and Microsoft Teams.
Thirty-one payouts. Twenty-six match exactly. Five do not, and four of the five have the same cause.
- Four payouts · short by the processing fee · the fee is being booked to a different month than the payout
- One payout · 14 Aug · no matching ledger entry at all
The fee timing is a mapping problem, not a missing transaction. Payouts settle on the day, fees post on the statement date, and the ledger rule files both to the statement date. Every month the last few days of fees land in the following month. It nets to nothing across the year and it makes every single month wrong.
The 14 August payout is different and I have not resolved it. It left Stripe, it is not in QuickBooks, and it is not in the suspense account either.
I have not adjusted anything. The obvious move is to post the missing entry and move on, but a payout with no ledger trace is the shape a bank feed gap makes and also the shape a genuine problem makes, and I cannot tell which from here.
What would tell us which?
The bank statement. If the money arrived in the current account on 15 or 16 August then the feed dropped it and this is housekeeping. If it never arrived, the payout was reversed at Stripe's end and there should be a corresponding debit later in the month, which I do not see.
I can check the moment the August statement is in the drive. Right now the last one filed is July.
Teams @Dash reconcile last month's Stripe payouts against the books for Corven and flag every delta.
Thirty-one payouts. Twenty-six match exactly. Five do not, and four of the five have the same cause.
- Four payouts · short by the processing fee · the fee is being booked to a different month than the payout
- One payout · 14 Aug · no matching ledger entry at all
The fee timing is a mapping problem, not a missing transaction. Payouts settle on the day, fees post on the statement date, and the ledger rule files both to the statement date. Every month the last few days of fees land in the following month. It nets to nothing across the year and it makes every single month wrong.
The 14 August payout is different and I have not resolved it. It left Stripe, it is not in QuickBooks, and it is not in the suspense account either.
I have not adjusted anything. The obvious move is to post the missing entry and move on, but a payout with no ledger trace is the shape a bank feed gap makes and also the shape a genuine problem makes, and I cannot tell which from here.
What would tell us which?
The bank statement. If the money arrived in the current account on 15 or 16 August then the feed dropped it and this is housekeeping. If it never arrived, the payout was reversed at Stripe's end and there should be a corresponding debit later in the month, which I do not see.
I can check the moment the August statement is in the drive. Right now the last one filed is July.