At Emma, we are on a mission to empower people to manage and control their financial lives better. We launched the product almost six months ago and soon we realised a pattern that was unusual to us. Budgeting and controlling spendings were fundamental, but the ton of feedback we received made us realise that these features were useless if not synced to payday.
Yes, people tend to think in payday cycles, rather than looking at their current incomings/outgoings on a monthly basis. It seemed that 2,000 years of history based on a Gregorian calendar were destroyed by a simple concept:
“I make X and I want to know how to get to the next X.”
Although we were a bit reluctant to ship a payday feature at first, the immense amount of people asking for this via our live chat and social media forced us to get the feature out. For this reason, after having tested “Payday” with several hundreds users, we are now pushing it live to our entire user base.
By setting payday, there will be a new card in the feed, which will count the days left to the next salary, and in Analytics, a new period called “current payday” will show up. In this way, our users are able to track their spending in their current payday cycle and exactly now how much they have left to get to the next one.
Supported payday ranges
The feature supports any kind of payday scenarios:
- Every week
- Every 2 weeks
- Every 4 weeks
- On a fixed date 1st-28th or Last working day of the month
- Dynamic ones: “on the last Thursday of the month”
We also ask users what happens if payday falls on a public holiday or during the weekends. In the majority of cases, if payday is on Monday, but this is bank holiday for example, people tend to get paid on Friday.
We have been working to collect every single public holiday for this year and will keep our databases updated, so we always know when to shift things and get the dates right.
Not supported yet
What we decided not to introduce at first was the ability to see past paydays. At this point, the current payday cycle sits in front of previous calendar months. The reasoning behind this decision comes from the fact:
- this feature can be extremely confusing if paydays change.
- the general public doesn’t think in terms of “how much they have spent 10 paydays ago”. Months are still a good point of reference.
We also don’t support multiple paydays. This has already been requested by some of our early adopters, but we have realised the calendar month works the best with 2 paydays at the same time.
We wanted to publicly thank all our supporters/fans/users who keep pushing us to ship things like this on a weekly basis. We have an intense roadmap ahead and the best is yet to come! đŸ˜‰
Nice!
However, I’d question the statement “The feature supports any kind of payday scenarios”
My company commits to paying me during the last 7 days of each calendar month but does not commit to a specific date within this period. What I would like is for you to auto-detect this income (based on the transaction name/source) and auto-reset the payday cycle when this happens.
Hello,
we already support this use case! Just select last working day and your most recent salary. The app should be able to understand it. đŸ™‚