Money basics

Billing cycle, statement date and due date: how they fit together

How a credit card billing cycle, statement date and due date fit together, shown on one timeline with two purchases made two days apart.

Editorial illustration for Billing cycle, statement date and due date: how they fit together

The billing cycle is the stretch of days the card bundles into one bill, the statement date is the day that bill is drawn up, and the due date is the later day by which you pay it. A purchase falls on the bill of whichever cycle it lands in, which is why two swipes two days apart can be due a month apart.

What is the order of events in one cycle?

Picture a card whose statement date is the 15th. Every cycle runs from the 16th of one month to the 15th of the next. On the 15th the issuer totals everything and produces the statement. A few days later, commonly in the first week of the following month though your card sets its own gap, comes the due date.

  1. Cycle opens: the day after the previous statement date.
  2. Purchases post to the card throughout the cycle.
  3. Cycle closes on the statement date, and the statement is generated.
  4. You get a window to pay, ending on the due date printed on that statement.
  5. The next cycle is already running while you pay the last one.

Which bill does a purchase land on?

Take a hypothetical card with statement date 15 April and due date 5 May. Two purchases of ₹4,000 each are made, one on 14 April and one on 16 April.

PurchaseCycle it falls inStatement dateDue dateDays from swipe to payment
₹4,000 on 14 April16 March to 15 April15 April5 May21 days
₹4,000 on 16 April16 April to 15 May15 May5 June50 days

Count the days: from 14 April to 5 May is 16 days left in April plus 5 in May, so 21. From 16 April to 5 June is 14 days left in April, 31 in May and 5 in June, so 50. Same card, same amount, same merchant, a gap of 29 days between the two due dates.

Why does a purchase sometimes appear on the "wrong" statement?

The date you swiped and the date the merchant's charge is posted to the card are not always the same. A purchase late on the cycle's last day, or one from a merchant who settles slowly, can post a day or two later and slide into the next cycle. Your statement usually shows both a transaction date and a posting date, or only one of them. Check which your issuer prints, and keep your own record by the day you actually spent.

What should you track by which date?

Use two dates for two questions. Spending belongs to the purchase date, because that is when you made the decision. Cash belongs to the payment date, because that is when your bank balance drops. A monthly budget that sums purchase dates will show 16 April spending in April even though the money leaves in June.

How does this show up when you import a statement?

Cards often issue statements on a fixed day, so importing right after each statement date keeps your record in step with the cycle. In SpendixAI you choose the card account before importing, and each row stays attached to that card; you review the rows before saving, which is a good moment to check that the dates look like purchase dates.

A simple rhythm

  • On statement day: import the statement and check the total against the printed figure.
  • Within a few days: set aside the amount due so the cash is ready.
  • Before the due date: pay and mark the payment as settling the card, not as spending.
  • Mid-cycle: look at the running spend so the next bill holds no surprises.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports