Special Labels Guide
Protect the accuracy of your totals. These labels keep transfers from looking like income, card payments from counting twice, and messy rows from quietly distorting your reports.
What this does: Tells the system how to treat unusual rows — not just what to call them
Key risk: Skipping these turns transfers into fake income and payments into double expenses
Success: CC payments, transfers, and duplicates stop inflating your totals
Remember: Special labels instruct the system. Normal categories describe a transaction.
What This Tutorial Is For
Most transactions can be categorized normally. Groceries are groceries. Payroll is payroll. But some rows are not ordinary categories at all — they are system situations.
That means the most important thing about them is not just what they were, but how they should behave in your totals. This is where special labels come in. They tell Money Mastery:
- This is not new income
- This is not a normal expense
- This money is just moving
- This row should not distort the picture
- This transaction needs a system workflow, not a standard category
If you skip these labels and force these rows into ordinary categories, your reports may still look tidy — but they will quietly stop telling the truth.
These labels apply to both Personal and Business systems. CC Payment, Transfer, Refund, and Ignore are not limited to users who have a Business account. If you only use the Personal system, you will still encounter situations where these labels are the correct choice. They live in the Business / Special Label column, but that column is not business-only — it is where all special treatment happens, regardless of which system you are in.
The Big Idea
Normal Category
Describes a transaction
Food — Groceries. Rent. Payroll. Marketing. These tell you what the money was for. They describe purpose and meaning.
Special Label
Instructs the system how to treat it
Transfer. CC Payment. Ignore. These don't just describe — they control whether a row counts as real income or real spending in your reports.
That distinction matters. A transfer between your own accounts is not "income." A credit card payment is not a new expense if the charge was already counted when you swiped the card. Special labels exist so the system can recognize those differences and keep your totals clean.
Each Special Label Explained
Select any label to see when to use it, how it works, and what happens if you skip it.
Credit card payoff is one of the most common places people accidentally double-count money. These two labels work together and should always be applied as a matched pair.
Label 1
Credit Card Payment Received
Use on the credit card account — the account where the payment arrives
Label 2
Debt Payment Sent to Credit Card
Use on the checking account or source account that sent the payment
What goes wrong without them:
❌ Without special labels — money gets counted twice
Expense
Amazon.com — original purchase
−$84.00
Expense
Amex Payment — counted again as expense
−$84.00
Reported total expense−$168.00
✓ With correct labels — payoff stays as payoff
Expense
Amazon.com — original purchase
−$84.00
CC Payment
Amex Payment — labeled, not counted
—
Reported total expense−$84.00
Use transfer labels when money moves between two accounts you own inside the same money map. The money is changing location, but not changing ownership.
Receiving account
Transfer Deposit Personal to Personal
Use on the account receiving the money
Sending account
Transfer Withdrawal Personal to Personal
Use on the account sending the money
Example: moving $500 from Chase Checking to your Savings account
Chase Checking
Transfer Withdrawal ↑
Savings Account
Transfer Deposit ↓
Without transfer labels: The $500 deposit into Savings looks like income. The $500 withdrawal from Checking looks like a new expense. Your net worth calculation stays the same — but your income and spending totals each grow by $500 for no real reason.
Use Ignored when a row would distort your financial picture and should not count in normal totals. Not because it's inconvenient — because it's genuinely misleading.
When to use it:
- A duplicate charge that appeared twice
- A row imported by mistake
- A test transaction or system artifact
- A pass-through item that should not affect normal totals
Date
Description
Amount
Status
Jan 8
Shell Gas Station
−$58.40
Transportation
Jan 8
Shell Gas Station (duplicate)
−$58.40
Ignored
Ignore with intention, not avoidance. This tool exists to protect accuracy — not to sweep hard-to-categorize rows under the rug. If a row is just confusing or annoying, that's not the same as being a distortion.
Split Transaction is not a normal category you pick manually. It is a system-support label that belongs to the split workflow — and it only belongs there.
Do not select "Split" as a casual label
If you type or select the split placeholder like an ordinary category, you can create the appearance of a split without actually completing the workflow the system expects. This leaves the row in an unresolved state that is harder to clean up later.
The right approach:
- When a transaction genuinely belongs in two or more categories, open the split transaction workflow
- The workflow handles the structural change — not just the label
- A split changes how the transaction is represented, not just what it's called
This is the distinction users most need to hear clearly: moving money between Personal and Business is not the same as a standard same-system transfer.
Two separate maps — each with its own story
crossing them needs a different workflow
Personal Map
Chase Checking
Savings Account
Personal Credit Card
Cross-map
movement
movement
Business Map
Business Checking
Business Savings
Business Credit Card
Same-system transfer labels are for movement within one map. Crossing maps needs the cross-system workflow.
Why this matters:
- Personal and business reporting should stay clean and separate
- Owner contributions, reimbursements, and cross-system movement each need their own logic
- Using a simple transfer label flattens an important boundary the system is trying to protect
- Blurring the line creates confusion later about what was truly personal, truly business, or moved between the two
A Simple Way to Decide
When you're unsure whether a row needs a special label, ask these three questions in order:
The special-label check — run these when something feels off
1
Is this real new income?
If no — do not force it into an income category. A deposit that is really a transfer or a refund is not new income.
2
Is this real ordinary spending?
If no — do not force it into an expense category. A card payment is not a new expense if the underlying purchase was already counted.
3
Is the money moving, offsetting, duplicating, or needing system treatment?
If yes — you are probably looking at a special-label situation. That one pause can save you a surprising amount of cleanup later.
What to Check When You're Done
Special labels are working when…
- Credit card payments are not inflating spending or income
- Transfers between your own accounts don't appear as real financial gain or loss
- Duplicate or distortion rows are not muddying your reports
- Split transactions are being handled through the split workflow, not improvised manually
- Personal ↔ Business movement is treated differently from same-system transfers
- Your totals feel clean, not busy
Common Mistake
Treating special-case rows like normal categories — a transaction can look ordinary on the surface and still need special treatment underneath. If you label everything as if it were normal spending or normal income, your system may stay filled in, but your totals will stop being trustworthy. The point of special labels is not complexity for its own sake. It is precision where precision actually matters.
"Special labels are quiet — but they do some of the most important work in the system. They protect the difference between a sheet that is merely full and a system that is actually true."
These labels keep movement from pretending to be income. They keep payoff from pretending to be spending twice. They keep messy rows from becoming misleading reports. In other words, they protect the difference between a sheet that is merely full and a system that is actually true. And that protection is worth getting right.