Transfers
Transfers track the movement of money between your own accounts — whether recurring (like a monthly savings transfer) or one-time (like moving funds to cover a bill). They keep both accounts in sync by creating linked debit and credit transactions.
Overview#
A transfer represents money moving from one of your accounts to another. Unlike bills (which are outflows to external payees), transfers do not change your net worth — they simply redistribute funds across your accounts. The app manages both sides of the transaction so your balances stay accurate. Because a transfer is neither income nor spending, linked transfer pairs are also left out of the dashboard totals and the reports when viewing all accounts.
Creating a Transfer#
Navigate to Transfers > Add Transfer to create a new transfer.
| Field | Description |
|---|---|
| Name | A descriptive name for the transfer (e.g., "Monthly Savings", "Credit Card Payment", "Rent Account Top-Up"). |
| Amount | The transfer amount. |
| Amount type | Shown when the destination is a Credit Card or Line of Credit account: Fixed amount (the default) or Statement balance — see Paying a Credit Card Statement. |
| Source Account | The account money is withdrawn from (debit). |
| Destination Account | The account money is deposited into (credit). |
| Frequency | How often the transfer recurs. See frequency options below. |
| Due Day | Adapts to the frequency: the day of the month (1–31) for monthly and longer frequencies, or the weekday (1 = Monday … 7 = Sunday) for weekly and biweekly transfers. A one-time transfer has no due day; it takes a Due date instead. |
| Start date | Optional, for recurring transfers. For weekly and biweekly transfers it anchors the schedule — transfers repeat every 7 or 14 days from this date, which is what pins down which week a biweekly transfer falls in (the date can be in the past). For other frequencies the first transfer occurs on or after this date. |
| Due date | One-time transfers only, and required: the date the transfer is due. It can be in the past. |
Both accounts must be ones you can post to, so an account shared with you read-only is not offered. On a transfer someone has shared with you, a new source or destination must also be one the transfer's owner can use, so the owner can still pay it. Paying, skipping or reverting a transfer writes to both accounts, so those buttons only appear when you can write to both; see When Mark Paid is not offered, which also covers a transfer whose destination is no longer shared.
Frequency Options#
| Frequency | Description |
|---|---|
| Weekly | Every 7 days on the same weekday. |
| Biweekly | Every 14 days (every other week). Set a Start date to control which week the schedule falls in. |
| Monthly | Once per calendar month on the due day. |
| Quarterly | Every 3 months. |
| Semi-Annually | Every 6 months. |
| Yearly | Once per year. |
| One-Time | A single transfer on a given date, with no recurrence. |
One-Time Transfers#
One-time transfers represent a single planned movement of funds. A one-time transfer is scheduled by its Due date rather than a day of the month, and the date can be in the past. After you mark a one-time transfer as paid, it automatically deactivates. It remains visible in your transfer history but no longer appears in the active list or generates reminders.
One-time transfers appear in the Bills Calendar in the month they are due, once Include Transfers is ticked there.
Note: Use one-time transfers for planned large moves — like transferring money to cover an upcoming expense — so you do not forget and overdraft the destination account.
Paying a Credit Card Statement#
A transfer whose destination is a Credit Card or Line of Credit account offers an Amount type choice mirroring what card issuers offer:
| Amount type | What is paid |
|---|---|
| Fixed amount | The amount entered on the transfer, every time (the default). |
| Statement balance | What was owed on the card as of the due date — everything charged since the previous due date, plus any remainder a partial payment carried forward. Charges made after the due date are left for the next statement. |
| Current balance | Everything owed on the card at the moment of payment, including charges made after the due date. |
| Minimum payment | The Minimum Payment set on the card's account — capped at what is actually owed, so a nearly-cleared card is never overpaid. The card must have a minimum payment set: without one the transfer is refused, as it would pay nothing. |
With any type other than Fixed amount, the transfer has no fixed figure: the app works it out from the card's ledger each time the payment is made. For that reason, on a transfer someone has shared with you you can only choose one of these types when the card itself is visible to you, as otherwise the amount would show you the balance of a card that was never shared with you.
This makes the whole credit-card cycle hands-off:
- Open the credit card's account page and click Set up payment (the button appears when the card has no payment transfer yet). The transfer form opens pre-filled — pick the account the payment comes from and the day of the month it is due.
- When the payment is due, mark it paid — or enable auto-pay and let the app make it on the due date.
- Both sides are recorded: the paying account is debited and the card is credited, clearing what was owed at the due date.
Between payments, the amount shown on the transfer is the most recent figure it resolved (marked with a badge naming the amount type), and the pre-booked next occurrence uses it as the forecast estimate. Once a payment transfer exists, the card's account page shows when the next payment is due.
Note: The statement figure comes from the card's ledger in the app, so it is only as accurate as the card's recorded transactions — importing or bank-syncing the card account keeps it right. If nothing is owed at the due date, a zero-amount payment is recorded and the cycle simply moves on.
Auto-Pay#
Auto-pay automates the transfer on its due date, removing the need to mark it paid manually.
How to Enable#
- Edit the transfer and toggle Auto-Pay on.
- Ensure both a source and destination account are set.
How It Works#
- A background job runs daily and pays each auto-pay transfer that is due, by your own date rather than the server's.
- When triggered, it creates linked transactions in both accounts (a debit in the source, a credit in the destination).
- The due date advances to the next occurrence automatically.
- Transfers with auto-pay show an Auto-pay badge in the list.
Warning: If either the source or destination account is deleted, auto-pay will fail and be disabled. You will need to update the transfer and re-enable it.
Marking as Paid#
Click Mark Paid on any transfer to record the movement. This creates two linked transactions:
- A debit (withdrawal) in the source account for the transfer amount.
- A credit (deposit) in the destination account for the same amount.
Both transactions are linked together and reference the transfer name for easy identification. The transfer's due date then advances to the next occurrence based on its frequency.
When the two accounts use different currencies, the credit is converted at your exchange rate for the day (your own rate, if you set one), so 100 GBP out arrives as its value in euros rather than as 100 EUR. If there is no rate between the two currencies, the payment isn't booked.
If the money has already come in from a statement import or bank sync, Mark Paid offers the withdrawals already in the source account, as the Bills page does, so you can link one instead of booking a second pair. The destination's own matching credit is linked with it. An imported withdrawal that carries the transfer's Transaction Description Pattern, near its due date, pays the transfer by itself. Between two currencies the arrival is booked at your exchange rate in the same way, so with no rate between the two currencies the transfer cannot be paid from the bank's withdrawal either.
As on the Bills page, each click counts once, and when the transfer already holds a payment for the date it is due, Mark Paid asks first and offers Use that payment; see When the bill already has a payment.
Statements from the destination account#
The two accounts' statements often arrive at different times. When the destination account's statement is imported, or bank sync brings in its credit, the bank's credit takes the place of the deposit the app booked for the transfer, so the money only arrives once. This works whichever statement comes in first, however the transfer was paid (Mark Paid, auto-pay or the bank's own withdrawal), and even when the bank credits the money a few days after the withdrawal. The credit has to fall in the transfer's due window around the deposit. Within one currency it has to be the same amount, and between two currencies within 10% of the converted amount, as banks use their own rate and add fees. A credit that matches one of your recurring incomes, such as a salary of the same amount, or one already linked to another bill, transfer or pension payment, is never taken for it. Where more than one credit fits, one naming the transfer wins, then the one nearest the deposit's date. As with bills, a split, receipts, tags and notes you added to the booked deposit move across to the bank's credit.
A deposit you have reconciled against a statement is never replaced: it stays as the arrival, paired with the bank's withdrawal.
Tip: If you mark a transfer paid accidentally, click Undo in the notification that appears briefly after payment, or use Mark Unpaid later. This removes the transactions the app booked for the payment on both accounts. A transaction that came from your bank is kept and only unlinked from the transfer.
Skipping a Transfer#
Click Skip on a transfer to move its due date on to the next occurrence without moving any money. This is useful when a transfer is not going to happen this time, for example a savings sweep you are pausing for a month, or one you have already made outside the app. Any transactions pre-booked for the skipped date are removed, and the next occurrence is pre-booked in their place, so the transaction list and forecasts show the new date.
The Skip button is only shown on recurring transfers that have not yet been paid this month. A one-time transfer cannot be skipped, as it has no next occurrence.
Tip: If you skip a transfer by mistake, click Undo in the notification that appears briefly afterwards. This puts the previous due date back.
Monthly Equivalent#
Each transfer displays a Monthly Equivalent amount regardless of its actual frequency. This normalizes all transfers to a monthly figure so you can easily compare their impact on your cash flow.
| Frequency | Monthly Equivalent Calculation |
|---|---|
| Weekly | Amount x 52 / 12 |
| Biweekly | Amount x 26 / 12 |
| Monthly | Amount (unchanged) |
| Quarterly | Amount / 3 |
| Semi-Annually | Amount / 6 |
| Yearly | Amount / 12 |
Tip: The monthly equivalent is especially useful when comparing transfers of different frequencies side by side — it answers "how much does this cost me per month?"
Related Features#
- Bills — Transfers use the same underlying system as bills (frequencies, auto-pay, due dates). Bills track external payments while transfers track internal movements.
- Accounts — Transfers link two accounts and keep both balances synchronized.
- Transactions — Each paid transfer creates linked debit and credit transactions.
Settings#
Transfers do not have dedicated settings. They share the notification system with bills — reminders use the Nextcloud notification system and respect your Nextcloud notification preferences.