The Complete ChatGPT AI Receipt Book
Turn Gmail receipts and order confirmations into a visual AI receipt book that helps you track purchases, surface returns, and recover value from old purchases.
What this lesson gives you
A polished visual receipt-book system built from accessible Gmail purchase records, plus copyable prompts for returns, spending analysis, warranties, refunds, and a daily refresh task.
Best for
Anyone who already receives receipts and order confirmations by email and wants to turn that scattered purchase history into something visual, searchable, and useful.
Inside this lesson
- Use Gmail as the evidence layer, not as a complete bank ledger.
- Make Potentially Recoverable the economic scoreboard without treating it as guaranteed cash.
- Keep one canonical receipt-book artifact and refresh it daily instead of creating disconnected copies.
The full lesson
Most people already have a purchase database. They just call it Gmail.
Every emailed receipt, order confirmation, shipping notice, return message, warranty email, and refund notice is a small financial record. The problem is that those records are scattered across an inbox, so most people only use them when they already know what they are looking for.
This system turns those emails into a visual receipt book you can actually use.
The goal is not “better receipt organization.” The goal is simpler:
Keep more of the money you already spent.
By the end of this guide, you will have a visual receipt book that can help you:
- find a purchase without remembering where you bought it;
- see recent spending in one place;
- surface purchases that may still be returnable;
- find warranty, replacement, refund, credit, or protection opportunities;
- spot repeat spending and merchant patterns;
- refresh the book automatically every 24 hours.
The receipt book is intentionally visual. The default design is a black, horizontal panorama with large numbers, readable cards, charts, and clear sections. You should be able to open it and understand your purchase history without reading a wall of text.
1. What you are building
The finished system has six sections:
- Overview — spending captured from accessible receipt emails, purchase count, average purchase, largest purchase, and potentially recoverable value.
- Recent Purchases — clean cards with merchant, item, date, amount, category, and status.
- Spending Breakdown — category and merchant summaries with simple charts.
- Returns — purchases with evidence that suggests a return may still be possible.
- Refunds + Warranties — purchases with evidence of a refund, replacement, warranty, credit, guarantee, or protection opportunity.
- Purchase History — a searchable/filterable ledger.
The artifact should never fabricate missing information.
If no money appears recoverable, show $0 Potentially Recoverable.
If a specific field cannot be determined, do not show an ugly “Not found” placeholder. Either omit the field or explain what was checked.
Example:
Return status: No return deadline was located in the accessible receipt or order-confirmation emails. Check the merchant’s current policy before relying on this item.
That is more useful than “Not found,” and it tells the user what the system actually did.
2. Before you start
You need:
- a ChatGPT account with access to connected apps/plugins;
- the Gmail account that receives your receipts and order confirmations;
- permission to let ChatGPT read the relevant Gmail messages;
- a conversation you are willing to keep as the canonical home for this receipt book.
For the cleanest setup, create a fresh chat named something obvious like:
AI Receipt Book
Keep the system in that conversation so every future refresh knows what it is updating.
Do not expose private receipt details while filming or sharing screenshots. Receipts can contain names, addresses, order numbers, payment fragments, travel details, and other personal information.
3. Step 1: connect Gmail
Open ChatGPT.
Open Settings.
Open Plugins or Connected Apps.
Choose Gmail.
Connect the Gmail account that receives your purchase emails.
Approve only the permissions you are comfortable granting.
Product labels can change over time. If your interface says Apps, Plugins, or Connected Apps, use the Gmail connection available in your current ChatGPT interface.
After connecting, test it with one narrow request before building anything larger:
Search my connected Gmail for one recent purchase receipt or order confirmation.
Return only:
- merchant;
- item or service;
- purchase date;
- total paid;
- source email.
Do not guess any missing value.If ChatGPT cannot retrieve a real message, stop here and fix the connection first.
4. Step 2: build the visual receipt book
Paste the prompt below into the same conversation.
Search my connected Gmail for receipts, order confirmations, invoices, purchase confirmations, shipping confirmations, refund messages, warranty/protection messages, and other emails that reliably document something I purchased.
For every purchase you can reliably identify, extract only information supported by the accessible emails:
- merchant
- item or service
- purchase date
- total paid
- subtotal if available
- tax if available
- order number
- payment method only when explicitly shown
- category
- return information when present
- warranty or protection information when present
- refund, replacement, credit, price-adjustment, or guarantee information when present
- source email
Do not guess missing values.
Then create a polished interactive HTML artifact that functions as my personal AI receipt book.
DESIGN
- black background
- premium editorial / luxury-finance aesthetic
- large, elegant, highly legible typography
- generous spacing
- visually sparse rather than dashboard-cluttered
- restrained accent colors used only to communicate status
- smooth horizontal left-to-right scrolling instead of a traditional vertical page
- one continuous panoramic experience with no conventional page breaks
- responsive behavior on desktop and mobile
- subtle transitions only; no gimmicky motion
LAYOUT FROM LEFT TO RIGHT
1. OVERVIEW
Show:
- total spending represented by the available receipt data
- number of purchases
- average purchase
- largest purchase
- a large “Potentially Recoverable” amount
If no supported recovery opportunity is found, show:
$0 Potentially Recoverable
Do not display “Not found.”
2. RECENT PURCHASES
Create visual purchase cards showing, when available:
- merchant
- item
- date
- amount
- category
- status
If a secondary field is unavailable, omit it instead of showing a placeholder.
3. SPENDING BREAKDOWN
Show:
- spending by category
- spending by merchant
- a clean donut or pie chart
- largest categories
- most frequent merchants
- repeat purchases when supported by the data
Make it explicit that this represents purchases found in accessible Gmail records and may not equal all spending across my financial accounts.
4. RETURNS
Show purchases for which the accessible emails contain evidence relevant to a return.
For each supported item, show:
- product
- merchant
- amount
- purchase date
- known return deadline or policy evidence
- urgency based only on a known deadline
- source email
If no supported return opportunity is found, show:
“$0 currently identified for returns”
and underneath:
“No supported return opportunity was located in the accessible receipt and order-confirmation emails checked during the latest refresh. Merchant policies may exist outside these emails.”
Do not invent return windows.
5. REFUNDS + WARRANTIES
Show purchases with accessible evidence of:
- warranty
- replacement
- refund
- store credit
- price adjustment
- protection plan
- guarantee
- another purchase-linked recovery benefit
For each one, show what evidence exists and link it back to the source email.
If nothing is found, explain what categories were checked rather than displaying “Not found.”
6. PURCHASE HISTORY
Create a searchable and filterable ledger.
Include filters for:
- merchant
- category
- month
- amount
- status
SYSTEM RULES
- include a clear last-updated timestamp
- every financial claim must be traceable to a source email
- distinguish confirmed information from something that still requires merchant verification
- never invent return, refund, or warranty eligibility
- never display “Not found”
- omit unavailable minor fields
- for an important unavailable field, state what evidence was checked and why the value could not be verified
- treat “Potentially Recoverable” as an evidence-based opportunity total, not guaranteed cash
Build the complete artifact now.5. What a good first output looks like
Do not judge the artifact by whether it looks busy.
A good first version should answer five questions almost instantly:
- How much purchase activity did the system actually capture?
- What did I buy recently?
- Where is most of the captured spending going?
- What might I still be able to return?
- Is there any money or value sitting inside warranties, refunds, replacements, credits, or guarantees?
The big number is Potentially Recoverable.
That is the economic scoreboard for the system.
It should include only opportunities with enough evidence to justify surfacing them. It should not imply the money is guaranteed.
6. Step 3: find purchases you may still be able to return
Once the receipt book exists, paste this:
Refresh my receipt book using my currently accessible Gmail purchase records.
Identify purchases for which the accessible email evidence supports a possible current return opportunity.
For each supported purchase, show:
- product
- merchant
- amount paid
- purchase date
- known return deadline or return-policy evidence
- source email
Update the Returns section of the receipt-book artifact.
Put the most time-sensitive known opportunities first.
Calculate “Potentially Recoverable” using only purchases where:
1. the amount paid is supported by the email evidence; and
2. there is supported evidence of a current return or other recovery opportunity.
If no supported return opportunity is identified, show:
“$0 currently identified for returns”
Then explain in one short sentence which accessible receipt/order-confirmation evidence was checked and that no current return opportunity could be verified from those emails.
Do not invent store policies or eligibility.Useful follow-up
Show me only return opportunities with a known deadline inside the next 14 days.
Sort them by deadline.
For each one, show the amount, item, merchant, deadline evidence, and source email.7. Step 4: see where your money went
This is not a replacement for connected bank-account data. It is a purchase-history view built from the receipts and confirmations available in Gmail.
Paste:
Using the purchases currently represented in my receipt book, analyze the most recent complete month of available receipt data.
Update the Spending Breakdown section with:
- total spending captured by these receipt records
- spending by category
- spending by merchant
- largest purchases
- repeat purchases
- most frequent merchants
- largest spending categories
- comparison with the previous complete month if enough comparable receipt data exists
- three concise observations supported directly by the data
Use clean charts and large readable numbers.
Label the total clearly as:
“Captured receipt spending”
Do not present it as total bank-account spending.
If the previous month does not contain enough comparable receipt evidence, omit the comparison and explain that there was not enough comparable receipt coverage.Ask better spending questions
Once the data is structured, you can ask things like:
Which three merchants account for the most captured receipt spending this month, and what percentage of the captured total does each represent?Show me repeat purchases that occurred at least twice in the last 60 days.
Group them by item or service when the emails make that reliable.Show me purchases above $100 from the last 90 days, sorted from largest to smallest.8. Step 5: recover value from old purchases
Returns are only one form of recovery.
Paste:
Search my accessible purchase emails for evidence of:
- warranties
- extended protection
- refund eligibility
- replacement eligibility
- credits
- price adjustments
- guarantees
- unused benefits tied to a purchase
For every supported opportunity, extract:
- purchase
- merchant
- amount originally paid
- type of recovery opportunity
- relevant deadline if explicitly available
- evidence found
- source email
Update the Refunds + Warranties section of my receipt-book artifact.
Do not claim I am eligible unless the accessible email evidence supports it.
Clearly separate:
- supported opportunity;
- requires merchant verification.
If no supported opportunities are found, show:
“$0 currently identified from refunds, warranties, replacements, or credits”
Then add one concise explanation of which categories of purchase emails were checked and that no supported recovery opportunity was identified in the accessible evidence.
Never display “Not found.”9. Make the receipt book refresh itself every 24 hours
The cleanest setup is to keep one canonical AI Receipt Book conversation and create one daily Scheduled Task that refreshes the artifact.
Create a new Scheduled Task and use a daily cadence.
Then paste this task instruction:
Refresh my canonical AI Receipt Book using my connected Gmail once per day.
Use the existing receipt-book artifact and its current structure as the source of truth.
Search for new or changed purchase evidence since the previous refresh, including:
- receipts
- order confirmations
- shipping confirmations
- refunds
- cancellations
- return messages
- warranty or protection messages
- replacement messages
- store credits
- price adjustments
- guarantees
Update the existing purchase dataset and receipt-book artifact rather than creating a disconnected duplicate.
Recalculate:
- captured receipt spending
- purchase count
- average purchase
- largest purchase
- spending by category
- spending by merchant
- Potentially Recoverable
- current supported return opportunities
- current supported refund, warranty, replacement, credit, protection, price-adjustment, or guarantee opportunities
Preserve source-email traceability for every financial claim.
Never invent missing policy information or eligibility.
Never display “Not found.”
If a minor field is unavailable, omit it.
If an important field cannot be verified, explain briefly what evidence was checked and why it could not be verified.
If no supported recovery opportunity exists, display $0 for the relevant total and explain what was checked.
Update the last-refreshed timestamp.
Notify me only when:
- a new time-sensitive return deadline is identified;
- a new supported recovery opportunity is identified;
- the artifact cannot be refreshed because Gmail access or another required dependency is unavailable.
Otherwise refresh silently.Important limitation
A Scheduled Task can refresh what ChatGPT can access in its own connected environment.
Do not assume it can overwrite a random file on your local Desktop every day unless your current ChatGPT setup explicitly has permission to write to that location.
The dependable setup is:
one canonical chat + one canonical artifact + one daily refresh task.
If your ChatGPT environment supports exporting or writing files to a connected folder, you can additionally ask it to keep an exported copy there.
10. Make the book easy to open
Use one of these access patterns.
Simplest
Rename the conversation “AI Receipt Book.”
Keep it pinned or saved so the canonical artifact is always one click away.
Desktop shortcut
After the artifact is created, export/download the standalone HTML file if your ChatGPT interface offers that option.
Save it as:
AI-Receipt-Book.html
Put it on your Desktop or in a dedicated folder.
The exported file is useful as a visual snapshot. The canonical ChatGPT artifact remains the safer source for daily refreshes unless your environment can directly overwrite the exported file.
Connected-folder version
If your setup supports writing to a connected Drive or other persistent folder, use:
Keep an exported copy of my current AI Receipt Book in the connected folder [FOLDER NAME].
Use the stable filename:
AI-Receipt-Book.html
Whenever the canonical artifact is refreshed, update that file only if this environment has explicit write access.
If write access is unavailable, do not claim the file was updated. Tell me which permission or capability is missing.11. Add a one-tap “refresh now” command
Scheduled refreshes are useful, but sometimes you want the latest state immediately.
Save this:
Refresh my AI Receipt Book now.
Check my connected Gmail for purchase-related changes since the last refresh.
Update the existing artifact in place.
Recalculate every summary and recovery total.
Preserve source evidence.
Never invent eligibility.
Show me only:
1. what changed;
2. the updated Potentially Recoverable amount;
3. any deadline that needs my attention.12. Add an “I am holding this item” lookup
This is useful when you have the product in front of you but do not remember where it came from.
I am trying to identify a purchase from my receipt history.
Use the item description I give you to search my accessible Gmail purchase records.
Find the strongest matching purchase and return:
- item
- merchant
- purchase date
- amount paid
- order number if available
- return information if supported
- warranty/protection information if supported
- source email
If multiple purchases could match, show the best candidates and explain the distinguishing evidence instead of guessing.13. Add a return-deadline watch
If you frequently buy things online, add a focused task:
Check my AI Receipt Book for supported return deadlines occurring in the next 7 days.
Notify me only when at least one deadline is supported by accessible evidence.
For each alert, show:
- item
- merchant
- amount
- deadline
- source evidence
- the next action I need to take
Do not infer a return deadline from a generic merchant policy unless the policy and its applicability to this purchase are both supported.14. Privacy rules worth keeping
Receipt data is financial-adjacent personal data.
Keep these rules:
- do not publish screenshots with addresses, order numbers, account details, or payment fragments visible;
- do not ask the system to infer sensitive information that is not necessary for the receipt-book job;
- do not treat Gmail receipt totals as a complete accounting ledger;
- do not let “Potentially Recoverable” become a promise of guaranteed money;
- verify any merchant policy that matters before acting;
- keep the system grounded in evidence from the accessible emails.
15. Troubleshooting
Gmail is connected but ChatGPT finds almost nothing
Try a narrow test:
Search my connected Gmail for messages from the last 30 days containing common purchase evidence such as:
receipt
order confirmation
invoice
your order
payment received
shipped
refund
return
warranty
Show me only the message subjects, senders, and dates first.
Do not build the receipt book yet.If that still produces nothing, check whether the correct Gmail account is connected and whether the current ChatGPT surface has permission to use the connector.
The artifact looks like a generic dashboard
Paste:
Redesign the receipt book without changing the underlying data.
Make it feel like a premium editorial panorama, not a SaaS admin dashboard.
Use:
- black background
- oversized typography
- strong whitespace
- one dominant number per section
- horizontal left-to-right progression
- simple charts
- restrained borders
- minimal labels
- no dense tables except in Purchase History
- no gradients unless they materially improve legibility
- no decorative widgets that do not answer a financial questionThe artifact contains too many empty values
Paste:
Clean the receipt-book presentation.
Never display “Not found,” “N/A,” “Unknown,” or empty placeholder cards.
For optional fields, omit the field.
For an important unavailable field, show one plain-language explanation of:
1. what evidence was checked;
2. what could not be verified;
3. what I would need to check next.
If an amount is zero, display $0.The system overstates returns or warranties
Paste:
Audit every recovery opportunity in the artifact.
For each one, classify it as:
- supported by accessible evidence;
- requires merchant verification;
- unsupported.
Remove unsupported opportunities from Potentially Recoverable.
Do not treat a generic policy as purchase-specific eligibility unless the evidence supports that connection.16. The five-step version
If you want the entire build compressed:
- Connect Gmail.
- Build the visual receipt-book artifact.
- Surface supported return opportunities.
- Analyze captured receipt spending.
- Surface refunds, warranties, replacements, credits, and other recovery opportunities.
Then create the daily refresh task.
That is the complete loop:
Capture → organize → inspect → recover → refresh.
Your Gmail was already storing much of your purchase history.
The useful upgrade is turning that history into something you can see, search, analyze, and revisit before value disappears.
Your next step
Connect Gmail, run the one-receipt access test, then build the visual artifact before adding the daily refresh task.
Copy the build prompt