A worked example: purchases, statement, repayment
This simplified example assumes no earlier card debt, fees, interest, refunds or other purchases. Amounts are in AED; the same recording distinction applies in other currencies.
| Event | Budget entry | Total expenses | Card amount owed |
|---|---|---|---|
| Buy groceries for AED 200 | AED 200 grocery expense on the card | AED 200 | AED 200 |
| Spend AED 150 on transport | AED 150 transport expense on the card | AED 350 | AED 350 |
| Statement closes at AED 350 | Check the statement and record the amount due and due date | AED 350 | AED 350 |
| Repay AED 350 from your bank account | Transfer AED 350 from the bank account to the card | AED 350 | AED 0 |
Your bank account has AED 350 less cash after repayment. Your expense report still shows AED 200 of groceries and AED 150 of transport, rather than AED 700 of spending.
Apply the example in Stash
- Create the cash account and credit card account you will track.
- Record or review each imported purchase against the card, including its category, amount and currency.
- Review category spending against your budget plans. The card’s unused credit limit is not cash you own.
- Use the issuer’s statement to check the amount due and due date. Protect the cash needed for that payment in your plan.
- Record repayment between the cash account and card. If you imported a payment alert too, check that it represents the same payment rather than a second expense.
- Reconcile your totals and investigate any missing purchases, fees or credits.
Explore Stash’s credit card spending tracker or learn how credit obligations affect available money.
When your numbers differ
- An older balance: the amount owed can include debt from before the current budget period. It is not all new spending.
- Fees or interest: these can add genuine expenses beyond purchases. Check the statement.
- A refund: review it as a credit relating to the original purchase, not a repayment you made from your bank account.
- A purchase after closing: it may increase the current balance without belonging to the statement currently due.
- Two imported alerts: a push message and email can describe one event. Confirm a single transaction.
If a statement amount looks wrong, resolve it with the issuer’s records before relying on the budget estimate.
Transaction date
The transaction date is when the purchase occurred and normally when the expense belongs in category reporting. A later posting date can affect the statement cycle, but should not erase the original spending date.
Statement cycle
A statement groups posted card activity between closing dates. Purchases near the boundary may fall into a different cycle than expected, so the card issuer's statement remains authoritative.
Statement amount and due date
The statement amount is the obligation created for that cycle; the due date is when payment is expected. Minimum payment, full statement balance and current card balance are different figures and should not be substituted for one another.
Avoid double counting repayments
If purchases were already categorized as expenses, the card repayment is a transfer that reduces cash and card liability. Counting it again as an expense doubles reported spending. At the same time, the budget must reserve enough cash to make the payment.
Use statements for reconciliation
Notifications and emails are useful for fast capture, but the statement is the issuer's cycle record. Reconcile imported purchases, fees, credits and payments against it, especially before relying on a due amount.