Credit Card Statements in MyFam360 — How the Cycle Closes Itself

The most common reason people lose money on credit cards isn’t fraud or annual fees. It’s the minimum-due trap — paying just enough to keep the card current, while the rest of the balance revolves forward at 30–42% per annum interest. Six months of min-paying a ₹40,000 balance is enough to add ₹6,000 in finance charges to your year.

The MyFam360 statement view is designed to make this trap impossible to ignore. This post explains how statements work — what gets created automatically, what gets frozen, what gets warned about, and when you’d want to enter a statement manually.

If you haven’t added a card yet, start with the Credit Card Manager foundation post.

---

The Scheduler That Does the Work for You

MyFam360 runs a daily job at 02:00 UTC called materialize_statement_month. The job walks every active credit card in the database. For each card whose billing-cycle day matches today’s day-of-month, it does the following:

1. Compute the cycle window — from the last cycle close (or card creation date if it’s the first cycle) to today.
2. Sum expenses — iterate the mirror account’s expenses inside the window with a Python Decimal accumulator. (Critical Learning v1.43: never use SQL func.sum() over EncryptedDecimal columns — the values are encrypted at rest and SQL can’t aggregate ciphertext.)
3. Compute minimum due — using the issuer’s standard formula (typically 5% of statement balance plus any past-due amount).
4. Insert a CreditStatement row — with total_due, minimum_due, cycle_start, cycle_end, due_date, and status='open'.
5. Set paid_amount=0 initially.

The whole thing is idempotent: if today’s cycle has already been materialised, the job no-ops.

You don’t have to do anything. Open the app on the day after your cycle closes and the new statement is sitting there.

---

What a Statement Looks Like

The StatementView panel shows, per statement:

Field	What it means
Cycle window	Cycle start → cycle end dates
Total due	Sum of all expenses inside the cycle
Minimum due	Issuer-formula min payment
Paid amount	Sum of all payments recorded against this statement
Status	open / min_paid / paid / overdue
Due date	Payment due day, projected from cycle close + grace period
Risk band	green / amber / red, based on due_date - today

The two banners worth knowing:

Min-Paid Amber Banner

If paid_amount >= minimum_due and paid_amount < total_due, the statement status becomes min_paid and an amber banner appears showing the projected finance charge. The charge is computed using your card’s apr (or a default 36% if not configured) applied to the revolving balance for the cycle.

This banner is the single most important UI surface in the Credit Card Manager. Issuers print the minimum due in tiny text and the total due in large text, then hope you only look at one. MyFam360 puts the cost of choosing the wrong one in front of you.

Projected-Exhaustion Banner

If revolving the current balance forward plus your last-90-days spend pattern projects to push the card over its credit limit before the next cycle, a banner with the projected exhaustion date appears. This is useful when you’re already carrying a large balance and want to know how much headroom you have left before the issuer starts declining transactions.

---

When To Use Manual Statement Entry

There are two scenarios where the auto-materialised statement isn’t what you want:

Scenario 1 — Mid-Cycle Card Import

You add a card to MyFam360 on the 20th, but its billing cycle closed on the 15th. The auto-materialiser won’t run until next month. If you have the issuer’s actual statement (from the bank’s app or email PDF), you can enter it manually.

Tap Manual Statement on the card detail page. The form asks for:

• Statement month — normalised to YYYY-MM-01
• Cycle start and cycle end
• Total due and minimum due — copy from the issuer’s statement
• Due date

The flow rejects duplicate (card_id, statement_month) pairs, so you can’t accidentally create two statements for the same month.

Scenario 2 — Cycle Day Mismatch

Some issuers have variable cycle days (e.g., your statement might close on the 12th or the 14th depending on weekends). If MyFam360’s projected close date doesn’t match the actual issuer date, you can delete the auto-materialised statement and enter the real one manually.

Or — easier — adjust the card’s billing_cycle_day to better match the issuer’s average.

---

The Calendar Click-Through

The Calendar page renders a credit_due_date event on each card’s payment due date. Tapping that event on a desktop or mobile calendar opens the Record Payment modal directly, with the statement pre-loaded.

This is a small UX detail with a big effect: the most common journey through the app — “I got the SMS that my HDFC bill is due, let me pay it” — collapses from five taps to one.

---

Notifications That Hang Off Statements

Five credit-card events run on a dedicated dispatcher at 02:30 UTC (a few minutes after the materialisation job). Two of them are statement-driven:

• credit_due_soon — fires T-3 days and T-1 day before due date for any statement still in open or min_paid status.
• credit_overdue — fires T+1 day and T+7 days after the due date if status is still not paid.

Both events are idempotent per (family_id, statement_id, event_key, dispatch_date), so you won’t get duplicate reminders for the same statement on the same day.

---

What Doesn’t Get Materialised

A few things deliberately don’t happen during materialisation:

• Annual fees — those are handled by a separate scheduler (covered in the annual fees post).
• Rewards — the rewards engine reads the underlying expenses live; rewards aren’t pre-computed and stored in the statement row.
• Promo offers — promo emails are handled by their own daily job (see the promo email post).

This separation matters because each of those subsystems has different idempotency and audit requirements. Bundling them all into one big “close the cycle” function would make every scheduler harder to reason about.

---

What This Means For You

The statement system in MyFam360 is mostly invisible when it’s working. You add a card, log expenses, and one day a statement appears showing what you owe.

The one moment to pay attention: when the amber min-paid banner appears. That’s the app telling you the issuer is about to make money off you. Either pay the rest of the balance, or look at the projected finance charge and decide consciously that revolving is worth it for this cycle.

---

See Also

• Credit Card Manager Foundation in MyFam360
• Recording a Credit Card Payment with the Impact Preview
• What’s New in MyFam360 — the Roundup