You track your money in Notion. You say so whenever someone asks. The Camera Roll has a month of coffee and gas receipts, each one a photo between a screenshot and a dog. Gmail holds the Amazon and Adobe PDFs. And there is a Notion page titled Expenses, which is paragraphs, pasted screenshots, and a few lines you typed in March.
It feels like a system. Then you try to see everything you spent at one vendor, or in one month, and the page can't answer. You scroll.
What does "receipt to Notion" actually mean?
Receipt to Notion means each receipt becomes one row with a date, vendor, total, tax, category, and source, and those rows are imported into a Notion database as properties. It does not mean pasting scanned text into a page, and it isn't a pipeline you build with automation tools. It's a file you review once and import.
Why isn't a page of paragraphs a ledger?
A page stores things you can read. A database stores things you can filter. The moment you want "Office, September" or "everything from Adobe," you need properties, and properties need rows.
The rule is one sentence: one receipt is one database row, and properties beat folders and dump pages.
What does a week of receipts look like as rows?
Here is one invented week. The sources are two phone photos, two email PDFs, and a paper slip from the truck.
| date | vendor | total | tax | category | source |
|---|---|---|---|---|---|
| 2026-09-08 | Blue Bottle | $6.45 | $0.58 | Meals | phone photo |
| 2026-09-09 | Amazon | $48.20 | $3.97 | Office | email PDF |
| 2026-09-11 | Adobe | $59.99 | $0.00 | Software | email PDF |
| 2026-09-14 | Shell | $52.10 | $4.29 | Travel | paper slip |
| 2026-09-18 | Staples | $27.64 | $2.28 | Office | phone photo |
| Week | 5 receipts | $194.38 | $11.12 |
The week comes to $194.38, with $11.12 of that tax. Adobe's tax is $0.00, and the row says so instead of leaving a blank. Once it's imported, filtering the category for Office gives you 2 rows totaling $75.84. Filtering source for paper slip shows what's still only on paper.
How do the columns map to Notion properties?
You map them once, when you import. A sensible first mapping:
- vendor becomes the Title property.
- date becomes a Date property.
- total and tax become Number properties. Notion's help center says Number properties can be formatted as currency.
- category becomes a Select property, which Notion describes as choosing one option from a list of tags.
- source becomes a Select or a Text property.
Notion's help center describes two routes. You can import a CSV to create a new database, where rows become pages and columns become properties, or open an existing database and choose Merge with CSV to match your columns to its properties. For a merge, it says your CSV headers should match the database's property names exactly. After the first import, every later week is the same move.
A few notes straight from Notion's help. Dates import in MM/DD/YYYY format, so check the date column after your first import. If a column with dollar amounts or negative values doesn't import correctly, map it to Text instead. Files on the Free plan are limited to 5 MB. And imports add rows but don't update existing ones, so import each file only once.
The categories stay yours. If your database already uses Meals or Software, use those words in the category column and they will match.
What does Slipsheet do in this, and what doesn't it do?
Slipsheet handles the middle. Photograph the paper slip, upload the PDF, or forward the email to receipts@slipsheet.app. Each one becomes a row you review, with date, vendor, total, tax, and the category you set. Then you export a CSV and import it into your Notion database.
Slipsheet has no live connection to your Notion workspace. There's no sync and nothing pushed. You review, export, and import. That's less magic than a pipeline and easier to check.
The review matters because reading a receipt isn't the same as getting it right. In a Q2 2026 test of 20 receipts with Tesseract OCR, vendor was right 95% of the time, date and total 100%, and tax 60%, and all four fields were correct on 11 of 20 (55%). Confirm the fields before the Notion import, not after.
Why isn't a card charge enough in Notion?
A card or bank charge proves money left. A Notion row with only a vendor and an amount, and no tax or receipt behind it, is incomplete when you hand the year to a bookkeeper. The longer argument is in a card statement is not a receipt. Keep the charge to reconcile against, and build the row from the receipt.
A few straight answers
Should receipts live on a Notion page or in a database?
In a database. A page holds paragraphs and screenshots you can read but not filter. A database holds one item per receipt, with properties like date, vendor, total, tax, category, and source, so you can filter by vendor or month and sort by amount.
Does Slipsheet sync with Notion?
No. There is no live Notion sync and nothing is pushed into your workspace. You review the rows in Slipsheet, export a CSV, and import that file into Notion yourself. You own the file and the database.
Which properties should I create first?
Start with six: vendor as the Title, date as a Date property, total and tax as Number properties, and category and source as Select properties. Add notes or a client property later if you need them. Keep the names the same as the CSV headers so merging next month is a single step.
Is importing a CSV better than typing receipts into Notion?
Usually, once you have more than a handful. Typing is one receipt at a time, and every field is a chance for a slip. An import adds the whole week in one go, and you check the properties once. Notion's help center says imports add rows and don't update existing ones, so import each file once.