Where the bills already are
If you run a business with no finance team, every bill you owe arrives in the same place. The PDF invoice from the electrician. The reminder written in plain words, with nothing attached. The direct debit that bounced. The insurance renewal that is not due for a month. Nobody decided the inbox would be the accounting system; it became one because it is where the bills land, and nothing else does.
I think this is the fact that most tools for paying bills get wrong, and I want to make the argument plainly.
The forwarding address
Nearly every product that helps a small business handle bills begins with an address. Forward your invoices to us. Send them to the receipts inbox. Upload the PDF. Some of those products are very good at what happens next — reading the invoice, routing the approval, landing it in the books. I have written about several of them, fairly I hope: ANNA Money turns a document you send it into a payment to confirm; Xero will take a forwarded bill into the ledger.
But an address presupposes a decision. Somebody has to notice the email, open it, decide that it is a bill, and send it on. For a business with a bookkeeper, that somebody is the bookkeeper, and the address is a fine design. For the owner doing it themselves at nine at night, that step is the job. It is the step that gets skipped, or done in a batch on the last day of the quarter, and the bill that arrived on a busy Tuesday never gets forwarded anywhere. The tools begin after it.
An inbox is built for reading, not for owing
An email has a sender, a subject and a date. A bill has a supplier, an amount, a due date and a state — unpaid, scheduled, paid, disputed. Those are different things, and the inbox only knows about the first.
The workarounds are the proof. A label marks that something arrived; it cannot hold an amount. A star cannot tell you what is due this week. Nothing unstars itself when you pay, and nothing warns you the day before. Search finds emails that contain the word “invoice”, and misses the reminder that says “following up on the amount owing” and the notice that says “your payment was unsuccessful” — two of the most important bill emails there are, and neither uses the word. The best manual system I know is a weekly search and a list kept elsewhere, and it works until the week it does not.
The tools that do read your inbox read it for something else
There are products that connect to Gmail and Outlook and read everything. They are not reading it for money.
The AI email assistants read it to sort and to draft replies: Fyxer’s categories are To Respond, FYI and Marketing, so a supplier invoice is an email you owe an answer to rather than money you owe. The receipt collectors read it for the accountant — what you bought, after you paid it, filed by month for the tax return — and to them a bill is a category to file under, not an obligation with a date. And Gmail itself now notices some bills and offers to add a due date to Google Tasks, one email at a time, with no list of what is owed and no sense of whether the sender has ever written to you before.
All of them have the access. None of them holds the question an owner actually asks, which is: what do I owe this week, and is any of it wrong?
What reading it would mean
It would mean noticing the emails that say money is owed, including the ones with nothing attached. Holding each one with its supplier, amount and due date, and keeping the original email beside it so you can see where it came from. Showing one list. Noticing when a supplier you have paid before writes with different bank details, and saying so. And never moving money without the owner, because the owner is the finance function, and the whole point is to give them the view they never had, not to take the decision off them.
That is the premise this company was started on, and I am aware it is a premise rather than a proof. If your inbox has its own version of this story — a bill that went missing, a system that works, a reason you think I have this wrong — write to me at hello@heydawn.ai. I read and answer these myself.
