Income

Income sources track your expected recurring revenue — salary, dividends, freelance payments, rental income, and more. By recording when and how much you expect to receive, the app helps you monitor whether income has arrived on time and gives you a clear picture of your monthly cash inflows.

Adding an Income Source#

Navigate to Income > Add Income to create a new income source.

FieldDescription
NameA descriptive name for the income (e.g., "Monthly Salary", "Freelance Invoice", "Quarterly Dividends").
Expected AmountThe amount you expect to receive each period.
SourceWho pays you (e.g., employer name, client name, investment account).
FrequencyHow often you receive this income. See Frequency Options below.
Expected DayThe day of the month (or week) you typically receive payment.
First payment dateShown for weekly and biweekly frequencies. Optional, but recommended for biweekly income: payments repeat every 7 or 14 days from this date, so it pins down which week a biweekly schedule falls in. Without it, the schedule starts from whichever week you created the entry. The date can be in the past — a payday from last month anchors the schedule just as well.
CategoryThe income category to assign when marking received (e.g., "Salary", "Investment Income").
Receive-To AccountThe account the payment arrives in. Used when marking income as received. It must be an account you can post to, so not one shared with you read-only, and on income someone shared with you it must also be one the income's owner can use.
Auto-Detect PatternA text pattern to match imported transactions against this income source (e.g., "PAYROLL" or "ACME CORP"). When an imported transaction matches, it is automatically linked to this income source.
NotesOptional free-text notes about the income source.

Tip: Setting an auto-detect pattern allows the app to automatically recognize income deposits when you import bank statements, so you don't have to manually mark each one as received.

Frequency Options#

FrequencyDescription
WeeklyEvery 7 days on the same weekday.
BiweeklyEvery 14 days (every other week). Set a First payment date to control which week the schedule falls in.
MonthlyOnce per calendar month on the expected day.
QuarterlyEvery 3 months.
Semi-AnnuallyEvery 6 months.
YearlyOnce per year.

Note: For weekly and biweekly income with a First payment date, the date decides both the weekday and (for biweekly) the week — the Expected Day field is ignored. Occurrences land exactly 7 or 14 days apart from the anchor date.

Income Detection#

Click Detect Income to let the app analyze your transaction history and automatically identify recurring credit transactions that look like income. The detection algorithm looks for:

  • Regular timing patterns (transactions that arrive around the same day each period).
  • Consistent amounts or amounts within a typical range.
  • Credit transactions (deposits) rather than debits.

After detection runs, you are presented with a list of potential income sources to review. Confirm the ones you want to track, and the app creates income sources with the detected pattern, amount, and frequency pre-filled.

Note: Income detection works best when you have at least 2-3 months of imported transaction history for the app to identify patterns.

Marking Income as Received#

Click Mark Received on any income source to record that the payment has arrived. This:

  1. Creates a transaction in the linked receive-to account for the expected amount and category, dated today.
  2. Advances the expected date to the next occurrence based on the frequency. One receipt settles one payment: income two payments behind takes two clicks, and income received early is not marked received again on its expected date.
  3. Shows an Undo notification for approximately 5 seconds, allowing you to reverse the action if clicked accidentally. Undo removes only the transaction this receipt created and puts the expected date back.

An imported deposit marks the income received in the same way when it carries the income's Auto-Detect Pattern, arrives in its receive-to account within 20% of the expected amount, and is dated near the expected date. The receipt is dated the day the money arrived, and the imported transaction is the receipt, so nothing more is booked. If the payment had already been booked, by auto-create or by Mark Received, the imported transaction takes the place of the credit nearest its own date, whichever order the statement lists them in. The category, receipts, tags and notes on the booked credit move across to the imported one.

If the income already holds a credit for the date it is expected, one that Mark Received or auto-create booked earlier, Mark Received asks about that first. Use that payment marks it received with that credit and books nothing new, and Record another payment carries on as normal. A credit you typed in yourself is not recognised, so for a payment you have already entered by hand use Skip instead. A double click counts once, and the button stays disabled until the receipt is recorded. If the page has been open for a while and the income has since been received or skipped, the app says so and reloads the list.

Tip: If the actual amount received differs from the expected amount (e.g., a bonus or deduction), you can edit the created transaction afterward to reflect the correct figure.

Mark Received records the payment in the receive-to account, so it is only offered when you can write to that account. On income someone has shared with you, the account has to be shared with you at Read & Write as well as the income, and the same applies to undoing a receipt. Skip does not touch the account, so it only needs Read & Write on the income itself.

Skipping a Payment#

Click Skip to move the expected date on to the next occurrence without marking the income as received. This is useful when a payment is not coming this time, for example a month with no dividend or unpaid leave, as marking it received would record a payment that never arrived.

Skipping does not create a transaction and does not change the last received date. An Undo notification appears for a few seconds afterwards and puts the previous expected date back if clicked. Skip is not shown on one-time income, inactive income, or income already received this month.

Status Badges#

Each income source displays a status badge indicating its current state:

BadgeMeaning
OVERDUEThe expected date has passed and the income has not been received or skipped. The card has a red edge, as an overdue bill does.
EXPECTED SOONThe income is due within the next 7 days but has not been received yet.
UPCOMINGThe income is expected but more than 7 days away.
RECEIVEDThe income has already been marked as received for the current period.
COMPLETEDA one-time income that has been received.
INACTIVEA recurring income that has been switched off.

Tabs#

The income view organizes sources into three tabs for quick access:

TabContents
All IncomeEvery income source regardless of status (active and inactive).
Expected SoonOnly income sources due within the next 7 days that have not yet been received.
ReceivedIncome sources that have been marked as received for the current period.

Summary Cards#

At the top of the income page, three summary cards provide a quick financial snapshot:

CardDescription
Expected This MonthThe total amount of income expected to arrive during the current month across all active sources.
Received This MonthThe total amount of income already marked as received this month.
Active SourcesThe count of currently active income sources being tracked.

Tip: Comparing "Expected This Month" against "Received This Month" gives you a quick view of outstanding income you are still waiting on.

  • Transactions — Each received income creates a transaction in the linked account.
  • Forecast — Active income sources are factored into balance forecasting.
  • Dashboard — The Income Tracking tile shows expected and received income.
  • Accounts — Income is received into a linked account.

Settings#

Income sources do not have dedicated settings. The feature works with your existing accounts and categories configuration.