nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Help managing an annual recurring bill...

cloudquick

I have a recurring bill (credit card annual fee) that was just paid on June 4th and which is setup as a recurring bill:

Screenshot 2025-06-07 at 10.24.28 am.jpg

And this is what the bill looks like if I go into my recurring bills:

Screenshot 2025-06-07 at 10.22.04 am.jpg

As you can see, the recurring bill is showing as being taken out 6 days ago, BUT it is also showing that it is upcoming on July 1st.

Screenshot 2025-06-07 at 10.22.27 am.jpg

Screenshot 2025-06-07 at 10.22.42 am.jpg

I don't understand why the start date for the yearly recurring bill is now set for July 1st, when it clearly knows that a payment went out at the start of June, and that it's an annually recurring bill.

When I setup the recurring bill, I set it up with a June 1st date, and set the frequency to every year, but it seems to have slipped to July now.

How do I rectify this, and stop it from happening in the future?

Find more posts tagged with

Recurring

Comments

SRC54

Simplifi seems to default to 30 days out. I know this can be confusing. Happens to me all the time.

Just change the start date to June 1, 2026. Then change the recurring month to June. Preview the next occurrence to make sure you have it right.

cloudquick

Hi @SRC54 I don't see how I'm able to change the start date to June 1st. Any date prior to today's date is greyed out:

Screenshot 2025-06-11 at 12.36.31 pm.jpg

SRC54

Not 2025 but 2026. Since your next bill is next June. That should do it.

Or July 1, 2025 but set the annual date in June. Make sure it’s once per year.

cloudquick

@SRC54 thanks, that makes sense, and seems to have worked.

This still seems like a bug though, shouldn't it be reported as such?

Thanks again for your help!

SRC54

Well, not sure it's a bug. When you schedule a transaction as recurring, the most usual scenario is monthly. I just tried to create one by saying create a new recurring and it opened a window with Monthly as the default but I could change it. It will also suggest a date 30 days in advance. You just have to make sure you edit those. But if you are in a hurry and it sets it wrong, it's fairly easy to fix once you get the hang of it.

cloudquick

@SRC54 the reason I'm suggesting it's a bug is because I did set the recurrence to a year when I first created the recurring item. I understand that the default is 30 days, but if I then change that 30 days to a year and it doesn't stick, that seems like a bug to me. But not sure who deicdes such things or how to report it.

SRC54

Got it. Thanks for the clarification. Well certainly if it continues to happen, you should report it as a bug. I find that Simplifi has a lot of glitches partly because it is updated weekly and many of us are testing new features so we are almost, though not exactly, beta testers.

The problem always is recreating the bug; if you cannot recreate it, it's hard to report.

DryHeat

@cloudquick

When I open up a recent past transaction and click on "Mark as Recurring," Simplifi makes two fairly reasonable guesses: (1) that I want the transaction to recur monthly, and (2) that the first recurrence will be one month after the past transaction. I just did this with a June 10 transaction and here is what I got:

I call these "guesses" because (1) sometimes I don't want a monthly recurrence and (2) fairly often the date of the transaction is not exactly the date that I would prefer to use going forward.

If I do want a yearly recurrence, I have to change both the frequency and the date of the first recurrence manually. If I only change the recurrence, the start date remains the same and is pretty much never the date I want:

I understand that you would prefer for Simplifi to make a new guess about the correct start date whenever you change the frequency of the recurrence. That might be helpful if you do a lot of these, although I haven't found setting the correct start date much of a burden myself.

cloudquick

Thanks @DryHeat this is useful information. I will keep this in mind for future occurrences.