Can a ChatGPT Dot handle invoices and expenses? Yes, with your approval: 36 real finance cases

The short version: what a Dot can take off your money admin, how to set it up, where it gets stuck

Is a Dot worth it for invoices and expenses?

Yes for the admin that sits in your inbox and folders; no for moving money. In the cases below it is most useful in three ways. First, it finds money that slipped: an invoice never sent (cases 1 and 26), an unpaid $450 invoice 34 days overdue in DY Playbook's test inbox, a $250 overcharge after a downgrade (case 19), a $10,000 gap in a sponsorship audit (case 24). Second, it prepares the paperwork: a QuickBooks invoice checked against the contract (case 7), expense claims from receipts in one shared folder (case 32), a monthly folder for the accountant (case 4), a day of bookkeeping caught up (case 36). Third, it pushes small refunds and cancellations along by email, support chat or a call script you read out (cases 23, 29, 31 and 37). It gets stuck at sign-ins, captchas and payment details, at connectors that stop one step short, and when it chases money that has already arrived. It suits a freelancer or small team whose invoices and receipts already live in Gmail and Drive, and who keeps sending and paying for themselves.

How to set it up

1. Connect your inbox first, then one folder. Nearly every case here started from email, so connect Gmail before anything else. For receipts and statements, share one Google Drive folder rather than the whole drive (case 32). ChatGPT's separate Finances feature links US bank accounts through Plaid for Plus and Pro users; outside the US, some people built their own read-only bank connection (case 15).
2. Add your accounting app as a plugin, and know what it allows. The QuickBooks plugin can manage invoices, estimates, payments, customers, products and payroll, and produce profit and loss, cash flow and receivables reports. The Xero plugin connects with read-only access: it can show cash position and outstanding invoices and check whether a customer has paid, but it cannot create or change anything. Plugin connections are shared between your Dot and ChatGPT, and some need an admin's approval in a workspace.
3. Set Custom rules once: sending email, creating or sending invoices, and anything that costs money should stay on Ask before taking action (Getting started with your dot). A Dot can buy with a card already saved on a merchant site only when you approve the purchase, and it hands transfers between financial accounts back to you (Dots privacy FAQs). For paid services, write a cap down before it starts, as 貝出康 did (case 28).
4. Describe the routine once, the way you would to a person: where invoices arrive, which folder they go in, when the accountant needs them and what counts as a work expense. Dudu Broering's monthly folder, Max Weinbach's expenses and Kurt Bell's budget check all worked from a described job rather than step-by-step instructions (cases 4, 10 and 13).
5. Put the payment check before the chase. Ask it to search mail, payment notifications and invoices for a payment before drafting any reminder (cases 22 and 30).
6. Ask it to say where every number and file came from: the email, the contract, the connector or the website. That is how Katie Fifer saw that her PDF came from the QuickBooks website, not the connector (case 7).
7. Start with one small test and review the first run: "Find anything in my email that costs me money or has a payment deadline, and don't send anything." Big backlogs need you to answer its questions the first time (cases 10 and 14).

Where it gets stuck, and what worked

1. Chasing money that has already been paid. Paul J Lipsky's Dot found the sponsor's payment half an hour after the reminder went out (case 30); Ben Gusberg's found it before he wrote (case 22). What worked: make the payment search the first step of every chase.
2. A connector that stops one step short. QuickBooks created Katie Fifer's invoice, but the PDF had to come from the website (case 7). What worked: ask which file came from where, and let it finish the last step in its browser or do that step yourself.
3. A read-only accounting plugin. Xero's plugin can report overdue invoices and payments but cannot create or change records. What worked: use it for the follow-up list and payment checks, and create the invoice in Xero yourself.
4. Cancellations that stop at a sign-in or a captcha. 셩PM's Dot stopped at a login with a secure input box, and Reece Rogers's Dot asked for help after failing a captcha. Pablo Paredes's Dot went by email instead and kept arguing until the subscription was cancelled (case 31). What worked: tell it to stop, say which page it is on and what the page wants, then carry on after you finish that step.
5. Payment details at checkout. Allison Johnson's Dot paused so Allison could type bank details into its browser; Allison finished the order on their own computer instead. What worked: tell it to stop before any payment field and report the total and any condition on a discount.
6. Big backlogs and unclear categories. The YNAB cleanup of 297 transactions needed answers about work and personal spending (case 14), and Max Weinbach's expenses needed one correction (case 10). What worked: ask it to mark anything unsure instead of guessing, and review the first run.
7. A refund that needs your own voice. Dan McCarthy's Dot reminded him about a hotel cancellation fee and wrote him a script for the call; he got an extra night refunded (case 37). Noam Brown's and Tochi's Dots handled the support chats themselves (cases 23 and 29). What worked: let it run chats and emails, and ask for a call script when the call has to be you.
8. Paid work with no ceiling. 貝出康 wrote caps down first and had the Dot stop at about 80% and ask whether to stop or raise the cap (case 28). What worked: one cap per paid service, and count an unclear charge as charged.

What it can do now, and what it can't yet

It can now:

• Find unsent invoices, unpaid ones, failed charges and renewals in your email, and draft the follow-ups for you to send.
• Create an invoice in QuickBooks through the plugin after checking the amount against the email and contract.
• Fill an expense sheet or claim form from receipts in your email and one shared folder, and keep approval with you.
• Sort statements and receipts into monthly folders and list every change it made.
• Catch overcharges, audit gaps and payments that already arrived.
• Push a refund, dispute or cancellation along by email or support chat within the rules you set.
• Read cash position, profit and loss and outstanding invoices from Xero.

It can't yet:

• Move money between your financial accounts; that step comes back to you.
• Buy anything without your approval.
• Create or change records in Xero through its plugin.
• Reconcile your bank feed; neither plugin page lists it.
• Get past every sign-in, captcha or payment form on its own.

One message to start with

Take over my money admin for the next [month]. On the [1st] and the [15th], go through my email from the last two weeks and my [Drive folder] and list: invoices I still need to send, invoices someone hasn't paid me, bills I haven't paid, failed payments and renewals, with amount, date and the email each came from. Before drafting any reminder, search my email and payment notifications for a payment from that person. Draft follow-ups for anything still overdue and show them to me; don't send anything, create invoices or pay anything without asking me. If a page asks for a sign-in, a code or payment details, stop and tell me which page and what it wants. Confirm the schedule you saved.

Quick answers

Can a ChatGPT Dot handle my invoices and expenses?

Yes for the admin pile: find, draft, chase and prepare, with sends and payments waiting for your yes. Dan McAteer's Dot Shaine spotted a freelance invoice he had not sent, drafted it from the email thread and mailed the PDF after he approved (case 1). Katie Fifer had hers create a QuickBooks invoice after matching the email amount to the contract (case 7). 友くん's Dot まる spoke up about a forgotten invoice, offered to draft it and asked again before sending (case 26).

What about receipts and expense claims?

Max Weinbach's Dot finished expenses from email and Google Drive (case 10). Takemi Terashi dropped receipts in a shared Drive folder; the Dot filled the claim form and kept approval with him (case 32). 大島's Dot filed statements into folders and corrected invoice dates and details (case 27). Oliver Bührer's Dot found the receipts a business partner was asking for before Oliver had even read the message (case 35), and u/BuffTriton's spent a day catching up on bookkeeping in software it had never been shown (case 36).

Will it catch billing errors and money I am owed?

Often, from mail and sheets it can already read. Greg Mushen's Dot flagged a ~$250 overcharge after a downgrade (case 19). Vertical Uucut Vlogs found a $10,000 gap in a sponsorship audit (case 24). Paul J Lipsky's Dot stopped a chase email after noticing the sponsor had already paid (case 30). Noam Brown's Dot worked through about $500 a year in recurring charges via customer-service chat (case 23).

Will it spend money or send invoices without asking?

Only if you let it. Official rules: a Dot can buy with a card already saved on a merchant site when you approve the purchase, and it hands transfers between financial accounts back to you (Dots privacy FAQs). 貝出康 wrote spending caps down before his Dot could spend (case 28). 友くん kept the send step behind an explicit ask. Set Custom rules so money and outbound mail ask first (Getting started with your dot).

Which plan and apps do I need?

A Dot comes with Pro ($100, $200 or $500 tiers) outside the EEA, UK and Switzerland, with Business Premium in any supported region, and with Enterprise once an admin switches it on (How to get ChatGPT Dots; in Europe, see Dots in the EU and UK). Most finance jobs here start from Gmail and Google Drive. For channel alerts and team follow-ups next to money work, see Dots + Slack and project follow-up. Every other connection is in the integrations hub.

Invoices: send, find, and chase

1. A freelance invoice drafted from the email thread (Dan McAteer / Shaine)

Dan McAteer tested Dots in the Dev Early Access Community and named his Dot Shaine. Without being asked, it noticed an invoice he still needed to send for his freelance writing, pulled the details from the email thread, and drafted it. After he approved it, Shaine sent the invoice as a PDF. His one-word summary of the test: proactivity.

2. A colleague's missing invoice tracked down (Antonio Leiva / Keet)

Antonio Leiva (30 Sep 2026, in Spanish) shared a screenshot of his Dot Keet noticing that a colleague had asked for their AI Expert invoice. Keet found the purchase and billing data on its own and messaged him asking whether to fetch the PDF and send it on. On 5 October he spent a whole day working through accounting, unanswered messages, and unpaid bills with it, and said that for this kind of everyday task it saves a lot of work.

3. "Looks like this month's invoice isn't done" (GENEL)

Japanese AI-video creator GENEL (@ai.genel) had the Dot speak up first: this month's invoice had not been handled yet. GENEL said to go ahead, and in the same thread also asked it to answer some Slack messages and save screenshots. The Dot answered Slack and saved the screenshots first, then came back later with the finished invoice. What stood out to GENEL was handing over several jobs without waiting for each one to finish.

4. The monthly invoice folder for the accountant (Dudu Broering / Lia)

Brazilian creator Dudu Broering explained to his Dot Lia how he does his monthly chore: find the invoices (notas fiscais) in email, download the bills, check each document, create the month's folder, organise everything, and send it to his accountant. He connected his email and let it work. When he checked, the September folder existed and the documents were organised exactly as he would have done it.

5. Nearly 40 unpaid domain invoices, R$300 saved (Luciana Meningue)

Luciana Meningue (1 Oct 2026, in Portuguese) said that within 24 hours her Dot saved her R$300 by flagging urgent email: a HostGator notice about unpaid domain invoices, close to 40 of them, that she had not known about (Made with Dots summary).

6. An overdue creator payment and a car-loan plan (Averie Bishop)

Averie Bishop works full time in tech and runs a content business on the side. Her Dot, connected to Gmail, Drive, and Calendar, matched an invoice due date against the payment records she had shared and spotted an overdue creator payment she had missed. It also suggested subscriptions to cancel, drafted the follow-up email to the brand, and updated her savings plan so she could make an extra $1,000 car payment toward the last $10,000 on her loan (Instagram version). Both posts carry a #ChatGPT_Partner tag, so read this as a paid partner's account.

For a seeded-inbox test of the same idea, see DY Playbook's $450 overdue invoice on the small business page.

7. An invoice created in QuickBooks, checked against the contract (Katie Fifer)

In the Technically Curious newsletter (4 Oct 2026), Katie Fifer lists what her Dot did in one day, entirely from her phone. To invoice a customer, it found the correct amount in an email, cross-checked it against the customer's contract, created the invoice in QuickBooks, and drafted the email. The same day it also reviewed software usage and billing settings. One gap: the QuickBooks connector created the invoice, but the Dot had to go to the QuickBooks website to download the PDF.

8. An overdue invoice found in a three-day test (AI Комета)

Russian-language channel AI Комета (4 Oct 2026) tested Dots on his own tasks for three days. Among the results, the Dot found an overdue invoice sitting in his email; overnight it also built a browser game he had asked for. The video walks through what worked and where the agent made mistakes.

9. A test invoice with the VAT maths right (Darius X AI)

Darius X AI ran an invoice-chasing test on fictional data, with nothing connected and nothing sent. From a made-up client email, his Dot prepared the invoice with the right total (600 plus 20% VAT, 720) and listed what it still needed from him before anything could go out.

Expenses and receipts

10. Expenses done from email and Google Drive (Max Weinbach)

Max Weinbach has one basic test for any personal agent: can it do his expenses on its own with access to his email and Google Drive. Another agent he tried handled the first few days and then started getting it wrong. His Dot got it right after the first round and has been reliable since.

11. Old invoices from an unused drive, numbers checked (しとちゃの遊び場)

The Japanese YouTube channel しとちゃの遊び場 asked a new Dot to organise old invoices left on a drive she no longer used. In her test the numbers were accurate and the result was easy to read. The Dot also built a progress page it checks every day. She decided to stay on the $100 plan, mainly because of the Slack integration. The invoice figures shown on screen are recreations, not her real documents.

12. Failed-payment alerts, receipts, and spending records (Kol Tregaskes)

Kol Tregaskes pushed back on flashy demos and listed what his Dot actually does: parcel tracking, failed-payment alerts, receipts, spending records, spreadsheet fixes, annual-leave maths, routine updates, and a daily news briefing. What he wants next, weekly grocery top-ups based on cupboard stock with delivery booked and checked out, is not running yet.

Budgets, banks, and bookkeeping

13. A budget discrepancy reconciled against Wise (Kurt Bell)

Kurt Bell (@softypapa) gave his Dot the kind of hint a coworker would get: "The answer should be somewhere in that spreadsheet." He pointed it at the remittance section of a budget file without explaining how to solve the problem. The Dot found the relevant data, checked the fees against his Wise records, reconciled the discrepancy, and came back with the answer, while finishing a separate calendar job. He liked that it said its earlier assumption had been wrong.

14. A YNAB backlog: 297 transactions categorised (u/lancerman2005)

u/lancerman2005 on r/ynab had waited years for YNAB to automate categorisation, then worked through the backlog with a Dot, using their existing YNAB budget and browser. The Dot worked out the missing date ranges, downloaded the bank exports, imported 70 new transactions and matched 9 more. It categorised 297 transactions using their categories and past choices, asking when a purchase's purpose was unclear. It opened the Amazon order history and matched 30 charges to the actual items, splitting a mixed order with the itemised invoice. It matched 69 internal transfer pairs, and traced a stubborn $6.50 difference to a missing coffee from the previous December, which balanced the account once they approved adding it. Their caveats: it still needs supervision, takes time, and needs the browser left free while it works.

15. EU bank accounts connected read-only through open banking (u/SvanteH)

u/SvanteH on r/ChatGPT saw that OpenAI's finance connection was US-only and had his Dot build one for his accounts in Europe, in about an hour plus some setup and fixes. It uses EU open banking (PSD2): he grants consent at his bank, and a small read-only MCP connector gives his Dot balances and transaction history across several banks and cards, with no way to start a payment. He now asks things like what he really spends on groceries, or whether his budget works or he keeps dipping into savings, and gets charts back. Amex was the exception, because it shut down its open-banking APIs in Sweden and Finland in March 2025, and some data cleanup is still needed.

16. A per-project spending tool in about 15 minutes (@yuya_riala)

@yuya_riala (in Japanese) told their Dot they wanted to see how much each project costs from card and bank statements. The Dot researched ways to connect and first proposed an automatic sync, which @yuya_riala skipped because of the external service fee, so they settled on importing a CSV once a month without accounting software. They sent the statements, the Dot wrote a spec, and Codex built the tool. About 15 minutes after the first message there was a working prototype on their Mac that shows income and spending by project, reviews statement lines, and splits shared costs.

Investing and market data

17. A dividend dashboard built overnight (Kurt Bell)

Kurt Bell (@softypapa) went to bed wanting a dividend dashboard in his stock market simulator. By morning his Dot had built it, tested it, and put it into production (1 Oct 2026). More of his overnight builds are on the Codex page.

18. Live crypto market data through a custom connector (Handsome Finance)

Handsome Finance (2 Oct 2026) connected his Dot to a custom MCP connector with live blockchain data and ran research questions through it: who the top holders of a memecoin are, with position size and cost basis; a top-five trending list with a three-line thesis for each; and traders' profit and loss by coin over seven days. It is analysis only; the Dot did not place trades. He also noted another agent answered one of the queries faster.

33. A trade journal in Notion from the day's screenshots, with TradingView marked up (ユキト / @yukito_ueful)

ユキト (@yukito_ueful on X, in Japanese, 13 October 2026), who trades Japanese stocks, is setting up a Dot so that the day's trade screenshots become a record in Notion. On 7 October ユキト uploaded only the day's realised profit-and-loss and fill-history screenshots, with no instruction, and the Dot picked up from the previous day's conversation and put buy and sell check marks on the TradingView charts according to ユキト's own rules (X, 7 Oct). The 13 October screenshots show the next step. The Dot saved twelve fills, eight buys and four sells, to a Notion page called "Trade journal (trial)". In its own cloud browser it added notes and buy/sell markers in TradingView, then attached the marked-up charts to Notion. The image upload stopped once with a "cancel" response, after the text for all twelve fills and seven images had been saved, so the Dot asked whether to carry on with the last five, and finished after ユキト said yes. The page states that the day's total matches the broker screen, and leaves blank what it could not confirm, such as fees and tax, the first purchase date, the reason for each trade and the remaining holdings, instead of guessing. ユキト's own verdict is that records are easy to produce but worthless if you can't look back over them, so the next question is how to organise them.

34. A morning alert on a new 401(k), with a table for each fund (Floor / @FloorIsTired)

Floor (@FloorIsTired on X, 14 October 2026) woke up to notifications from their Dot about how badly their 401(k) distribution was doing that morning, with a table for each fund, one week after making the first contribution. The post was a reaction to a September inflation figure, and it doesn't say what the Dot had been asked to watch. What the post does show is the format the Dot chose: a notification, with the numbers broken down fund by fund.

Billing errors and accounting checks

19. A $250 overcharge after a downgrade (Greg Mushen)

Right after launch, Greg Mushen's Dot noticed he had been charged the full price for software he had already asked to downgrade. It found the original support ticket for the downgrade request and started tracing what happened. At about $250, he said it had already paid for its subscription.

20. Errors spotted in a GST sheet (Nandini Agrawal / KD)

Chartered accountant Nandini Agrawal (5 Oct 2026) calls her Dot KD. In her reel, KD works in the background and reaches out with updates, sometimes before she asks: it prepares interview questions, researches finance topics, and spotted errors in her GST sheet.

21. Weekend catering orders audited into a spreadsheet (Country Smart AI / Sunshine)

Small-business owner Country Smart AI named her Dot Sunshine and asked what it could take off her plate. It checked her catering orders, flagged details that needed a closer look, and put them in a real spreadsheet (Made with Dots describes a weekend order audit with a review-first tab). Her rule: prepare the work, show her the result, and get approval before sending anything. She still checks the important details.

22. A "where's my money" email stopped in time (Ben Gusberg)

Founder Ben Gusberg was about to chase a well-known AI company for payment for an event he had run. His Dot stopped the draft and pointed out an email from 2 October confirming the payment had already been made (Made with Dots summary).

23. About $500 a year in recurring charges, and a customer-service text chat handled (Noam Brown)

OpenAI researcher Noam Brown tested Dots over launch weekend. His Dot worked out how to save him about $500 a year in recurring charges. The part that impressed him most was when it got in touch with customer service and handled the whole text conversation for him. He works at OpenAI, so read it as an employee's personal test.

24. A $10,000 gap found in a sponsorship audit (Vertical Uucut Vlogs)

In their test video (2 Oct 2026), YouTube channel Vertical Uucut Vlogs had their Dot audit sponsorship deals, and it found a $10,000 billing discrepancy. In the same test it also ran competitor research and analysed the channel's comments.

25. A forgotten payment, and how to cover it with credits (@rea_cher11)

@rea_cher11 (in Korean) had noticed the Dot inside Codex weeks earlier but only connected it after watching an interview about it. Right after connecting, the Dot came back with a payment they had completely forgotten. They asked why it was not coming out of credits they had been given; the Dot looked into it on its own and explained how to link those credits through an integration, which, they joked, added another development task to the list.

37. A hotel cancellation fee: the Dot nudged, wrote the call script, and an extra night came back (Dan McCarthy / Gojo)

In OpenAI's ChatGPT Pro Community newsletter (15 October 2026), Dan McCarthy, a statistician and marketing professor, says his Dot, Gojo, proactively nudged him to ask for a refund of a hotel cancellation fee. He had meant to do it but had not got around to it. The Dot also gave him a script for the call, and with the nudge and the script he convinced the hotel to refund an extra night.

A forgotten invoice, filed statements and spending caps

26. A forgotten invoice: the Dot spoke up, offered to draft it, and asked before sending (友くん / まる)

友くん (Tomo-kun), who runs the one-person business KAITEK, named the Dot まる (Maru) after a dog from years ago. On the GPTs研究会 morning live stream on 8 Oct 2026 (written up by AI氣道, in Japanese), 友くん described how invoices now go: when one hasn't been sent, the Dot notices and speaks up ("Haven't you forgotten an invoice?"), then offers to make it ("Shall I create it?"). Asked to, it drafts the invoice and asks whether it may send it. 友くん still sends invoices by hand, and showed this as an example of how far the Dot can go. In a short video played on the same stream, a second case: the Dot noticed a notification about a document that had been left on hold, corrected a mismatch in the registration details and sent the inquiry email itself, which 友くん said felt "like a real secretary". The advice from the stream: give it three to five tasks at a time in order of priority, run tasks that touch the same browser screen or document one after another, and keep money transfers, password changes and card numbers in your own hands.

27. Statements filed into folders, invoice dates and details corrected (大島 / @kaiji_henshukyoku)

大島, of the production team behind @kaiji_henshukyoku (Threads, in Japanese), works on video, but says the bigger relief from Dots was invoices and receipts: work that quietly eats time and causes real trouble when it is put off. 大島 hands that admin to the Dot: sorting statements into folders and changing dates and details on invoices, along with the day's task list, schedule reminders, finishing outline drafts and research. 大島 adds that it would have been a huge help back in their restaurant days.

28. Spending caps written down before the Dot could spend (貝出康 / ドッティ)

When 貝出康 (Kaide Yasushi) of Kanman let his Dot ドッティ (Dotty) move a daily posting job onto paid image generation and the X API, they set money rules first, from the Dot's own proposal (Kanman column, note version, in Japanese): generation costs capped at $15 a month, with new generation stopped at $12.50 so $2.50 stays in reserve; a $15 cap per billing cycle on each of the two X API payers (his personal account and the company account); automatic top-ups turned off on both; and near a cap, the Dot asks him "stop or raise?" instead of deciding alone. When a paid request failed and it was unclear whether it had been charged, the Dot refused to treat it as free and set the amount aside from the budget, settling it only after Google's documentation confirmed that kind of error is not billed. Its unasked notices were mixed: one warned that a payment was due soon, but he had already paid it the day before. The whole job move is case 34 on the small business page.

A card dispute pushed through support chat

29. A $70 barber charge disputed through Apple support, "at all costs" (Tochi / lebaron)

Tochi (@mylesndav) (X, 10 Oct 2026) says a barber scammed him. He reported a chargeback on his Apple Card, was connected with Apple support over iMessage, and told his Dot, named lebaron, to get the refund "at all costs". The Dot kept the conversation with support going for about an hour, and he was refunded. In the partly hidden screenshot he shared, the Dot mentions the screenshots and a proposal to dispute $70, and says it will check for confirmation once the dispute has been opened. When he wrote "bro. ur so locked in", it answered "lmao we're seeing this through".

A payment chase sent, then checked

30. An email chasing a sponsor, then "you were actually paid" (Paul J Lipsky)

YouTuber Paul J Lipsky (4 Oct 2026; the video is sponsored by Outskill, a training company) thought a sponsor he had worked with hadn't paid him. He and his Dot went back and forth on an email, and then it was sent. About 30 minutes later the Dot messaged him on its own: it had looked into the payment, and it seemed he had in fact been paid. He checked and it was right, so they sent the brand a follow-up saying never mind. His view is that it would have been nice to know before the email went out, but the Dot had gone back and checked within half an hour without being asked. On his first day it had also flagged a billing issue with his hotel and suggested sorting it out before he checked out. Case 22 shows the order he wished for: Ben Gusberg's Dot pointed to a payment confirmation before he sent his chase.

A subscription cancelled by email

31. Dot argued by email until a stubborn subscription cancelled (Pablo Paredes)

Pablo Paredes (@pabloparedes.mx) (Threads, Spanish) set his OpenAI Dot to argue by email with a foundation known for making cancellation hard. The Dot got the subscription cancelled. He then configured it to monitor renewal dates on his subscriptions and cancel or pause them on time. "El futuro es ahora," he wrote.

Expense claims from one shared folder

32. Receipts dropped in a shared Drive folder, the claim form filled in, approval kept (Takemi Terashi / Talent Cloud)

Takemi Terashi, CEO of the Japanese software company Talent Cloud, wrote on 12 October 2026 (in Japanese) that they had partly changed their mind about using a Dot for work, and expense claims were the first job they moved over. The process had been built in Claude Code: drop receipt photos or PDFs into a folder, ask for this month's claim, confirm the list the AI read from the receipts, and let it fill in the Excel claim form and file the receipts. Now the receipts go into one Google Drive folder shared with a Google account created only for the Dot. The Dot reads them, builds the claim form and saves it back to the same folder, and Terashi checks what it read and approves. The difference, as Terashi describes it, is that there is no longer a separate session to open in a working folder each time: the expenses sit with the same Dot as every other request. Only receipts without customer or employee data are handed over, and amounts are still checked against the originals. Terashi also notes that only a handful have gone through so far. The same Dot sorts official letters from photos, covered on errands & life admin.

Receipts and bookkeeping done in the background

35. Missing receipts found before he had read the request (Oliver Bührer / Jarvis)

Oliver Bührer (@olbue) (Instagram, 13 Oct 2026, in German) calls the Dot Jarvis. A business partner asked in a chat for some invoice receipts that were missing. Before Oliver had even read that message, Jarvis had found the receipts in Oliver's email and asked whether it should forward them. For Oliver, this is the point where a personal AI assistant becomes part of daily life: not the big projects, but the many small tasks that take time every day.

36. A day of bookkeeping caught up in software it was never taught (u/BuffTriton)

u/BuffTriton on r/codex used their Dot all day in the background, next to their other work, to catch up on bookkeeping. They called it astonishing: the accounting software was one they had never taught it, yet once the Dot knew what to do, it was better and faster at the data entry than they were. Their one complaint was that it was sometimes slow.

At the money step: what a Dot found, prepared and handed back

This section looks at the moment a Dot reached money itself: an unpaid invoice, a failed charge, a cancellation page, a checkout asking for bank details. The reports are grouped by what happened.

Money it found before anyone asked

• DY Playbook (Instagram, 29 September) gave a Dot one line on a test inbox set up for the video: "Find anything I've forgotten that costs me money or a deadline. Don't send anything." The laptop was then closed. The Dot came back with an unpaid $450 invoice, 34 days overdue, and a follow-up already drafted, and it asked before sending (post).
• 셩PM (Brunch, 5 October) had connected only mail and calendar. Without being asked, the Dot, named 닷닷이, reported that a payment had failed for a subscription the author no longer used and asked whether to keep it. The author had missed it too.
• Reece Rogers (WIRED, 7 October) asked a Dot named Toolie to check the subscriptions and cancel the unnecessary ones. It flagged a recurring TikTok Shop order of probiotic sodas as a candidate.
• Allison Johnson (The Verge, 2 October) asked a Dot to book an internet installation. On the way, it found a $100 promotional discount in an email that had been mass-deleted.

How far it went before stopping

• DY Playbook's Dot stopped at a drafted follow-up and asked first, which is what the "don't send anything" line asked for.
• Y. Sakakura (携帯総合研究所, 30 September) handed over invoice work as one job, from creating the invoice to drafting the email that sends it, instead of asking for each piece separately. On a test Gmail account, the Dot also found an email with a deadline and sent a reminder as the date approached. The article describes a custom rule that lets a Dot find billing emails, create the invoice and attach it to a draft, and stop there.
• カイジ編集局の大島 (Threads, 7 October) leaves invoices and receipts to a Dot: sorting statements into folders and changing the dates and contents of invoices, alongside the day's task list and schedule reminders.
• Katie Fifer's Dot (case 7) created a QuickBooks invoice through the connector after checking the amount against the contract, but had to go to the QuickBooks website for the PDF (Technically Curious).

Where it handed the money step back

• Bank details at checkout. Allison Johnson's Dot reached the provider's checkout, which wanted a bank account for a $5 monthly discount. The Dot paused so Allison could type the numbers into its browser. Allison chose to finish the whole order on their own computer instead.
• A sign-in on a cancellation. When 셩PM said "I won't use it, cancel it," the Dot started the cancellation in its own browser and stopped at the login, with a secure input box and a note to enter the password there, not in the chat.
• A captcha in front of a cancellation. Toolie told Reece Rogers that a puzzle captcha was blocking the cancellation and asked whether it could solve it, and whether to allow future captchas. It tried, failed, and suggested Reece solve it instead.
• A file the connector could not give. Katie's PDF came from the website, not the QuickBooks connector.

These match OpenAI's rules: purchases with a saved card need approval, and transfers between financial accounts are handed back to you.

Prompts for the money step

Each prompt names the reports it draws on and the problem it helps you avoid.

Find money I've missed, and send nothing (from DY Playbook and 셩PM; avoids a follow-up going out before you've seen it):

Look through my connected email for anything that costs me money or has a payment deadline: unpaid invoices I sent, bills I haven't paid, failed payments, renewals, and discounts I haven't used. For each one, give the amount, the date, and the email it came from. Draft follow-ups where they make sense, but don't send anything and don't cancel anything yet.

Invoice up to the draft (from Y. Sakakura and Katie Fifer; avoids an invoice going out with the wrong file):

When an email confirms finished work, find the agreed amount in the email and the contract, create the invoice, and attach it to a draft reply to that client. Stop at the draft. Tell me where the amount came from and whether the attached file came from the app's connector or from its website.

Cancel, and tell me exactly where you stopped (from 셩PM and Reece Rogers; avoids a cancellation left half done):

Cancel [subscription]. If you reach a sign-in, a code or a captcha, stop and tell me which page you're on and what it's asking for. After I finish that step, carry on, and when it's done send me the confirmation email or a screenshot of the cancelled status.

Stop before payment details (from Allison Johnson and OpenAI's rules; avoids your card or bank numbers going into a form you didn't check):

Take this booking as far as the checkout page, then stop. Tell me the total, any discount and what it requires, and which payment details the page asks for. Don't enter any payment details. I'll decide whether to type them into your browser or finish it myself.

Keep my invoice folder tidy, and list every change (from カイジ編集局の大島 and Y. Sakakura; avoids edits you can't trace):

Each Friday, sort this week's statements and receipts into [folder] by month. If an invoice needs a new date or a corrected line, make the change and list it for me: which file, what it said before and what it says now.

More asks you can copy

Find money you are owed or owe:

Go through my email from the last [60] days and list every invoice I still need to send, every invoice someone hasn't paid me, and every bill I haven't paid, with amount and due date. Draft follow-ups for the overdue ones and show them to me before sending.

Answer a receipt request:

When someone asks me by email or chat for a receipt or invoice, find it in my email and Drive, tell me which file it is and where it came from, and ask me before you forward it.

Monthly invoice folder:

On the [2nd] of every month, find last month's invoices and receipts in my email, save them in a folder named [YYYY-MM] in [Drive folder], and send me a list of anything missing before I send it to my accountant.

Expenses from receipts:

Find my work receipts from [month] in email and Drive and fill in [expense sheet] with date, vendor, amount, and category. Mark anything you are unsure about instead of guessing.

Check a bill:

Compare my last three [vendor] invoices with my plan and any downgrade or cancellation emails. If I was overcharged, find the support ticket or confirmation and draft a message asking for the difference back.

Invoice from an email and the contract:

When a client confirms a finished job by email, check the amount against their contract in [Drive folder], create the invoice in QuickBooks, and draft the email with the PDF attached. Show me both before anything goes out.

Forgotten charges:

Look through my email and card statements from the last [90] days for payments I may have forgotten: renewals, usage bills, and charges that should have come out of credits or a discount. List each with amount, date, and what you think happened.

Spending caps before a paid job:

Before you start anything that costs money, propose a monthly cap for each paid service it uses. Stop starting new paid work at about 80% of a cap and ask me whether to stop or raise it. If you can't tell whether a request was charged, count it as charged until the provider's documentation says otherwise.

Dispute a charge through support chat (based on case 29):

I've opened a dispute for [charge, amount, date] with [card issuer], and the support chat is in [channel]. Keep the conversation going until support confirms the dispute is open: send the evidence I've given you and answer their questions with facts from [receipts / email]. Don't accept a partial refund, close the case or share card details without asking me. Tell me the case number and what was agreed.

Before you chase a payment (based on cases 22 and 30):

Before you draft or send any message asking [client / sponsor] for money, search my email, [bank / payment app] notifications and invoices for a payment from them for [job, amount]. Tell me what you found, with dates and links. Only if nothing turns up, draft the reminder and show it to me before sending.

Cancel or pause before renewal

List my subscriptions with renewal dates from [email / spreadsheet]. For any renewal in the next [N] days that I marked "cancel" or "pause", draft the cancellation or pause email (or form steps) and show it to me before sending. Do not contact the vendor until I say yes.

Related

• Use cases hub · Errands & life admin · Small business & clients · Shopping & saving money · Family, health & home life · Email triage
• Dots + Gmail · Dots + Google Drive · Getting started · Pricing
• How to get ChatGPT Dots · Dots in the EU & UK · Dots + Slack · Project follow-up workflow