How do you automate invoicing when the hours sit in a spreadsheet?
To automate invoicing without a new system, your AI brings together the hours, receipts and agreements from your spreadsheet and email, with what Bombos remembers, marks the differences from last month and gets draft invoices ready that go to QuickBooks after your approval.
Works with QuickBooks and your own project numbers.
First the invoicing round; the agreements behind it stay in one shared memory for every AI your team uses.
Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →
This is how it goes now, and how it goes with Bombos.
Hours, receipts or costs from a spreadsheet turn into draft invoices by hand every month, and again the month after that.
Today someone manually brings together hours, receipts and agreements from old emails into draft invoices. The hours and receipts are in a spreadsheet, while the agreement may be buried in an earlier email. Then comes the comparison with last month, but a difference does not explain why a line changed. QuickBooks Online can already create invoices. The manual work is the preparation when hours and receipts sit outside it.
The draft invoices sit ready, with the differences from last month marked.
The proposal for this round is ready with differences from last month marked and the reason attached when it can be found. Your AI reads the spreadsheet and email and finds the customer, project and agreement, with what Bombos remembers. If information about a project or agreement is missing, you get a question. You review the proposals, and if your AI has a connection to QuickBooks, it puts the draft invoices there after your approval.
After three months, the invoicing round no longer takes over a colleague's schedule. The drafts are ready, differences from last month are marked, so you see first what changed. Agreements that once lived only in your head have become rules. More customers can come in without making the round longer, and the colleague who used to shut everything else out has time for other work.
What's ready for you then
- Draft invoices ready without retyping the spreadsheet
- See first what changed since last month
- Duplicate and missing lines flagged before sending
- The round fits beside the week's regular work
Where do you see that?
You see the groundwork for your invoicing round on the list of proposals. Every proposal has a reason and a status. "Ready for you" means you can review it. "Waiting on your input" means information or a decision is missing. An unclear reference to a project, for instance, needs an explanation before you move on with the invoice.
You do not need QuickBooks open to see what is ready for the round; if your AI has a connection to it, the draft invoices land there once you approve them. You look at the groundwork and decide whether the data can be used for a draft invoice. You also check whether the marked differences fit this month's work. With every proposal you see where it came from. A ready proposal is not a sent invoice.
How does it start?
In the first week of the three-month pilot, we look together at how you prepare the invoicing round. In a setup conversation of about an hour, we go through the mailbox, the package and your rules. We look at where the hours and receipts sit and where the agreements behind that data can be found. We also agree who fills in missing information and who decides what belongs on the invoice.
Your AI then starts the first, clearly defined preparation task with proposals. You check the result and correct a wrong explanation or choice. Your correction becomes the rule for the next round; Bombos keeps that explanation; without it, the memory does not hold your invoicing agreements. You keep working with your existing bookkeeping. Adjustments happen by filling in settings together, no course required. Once a task type has gone well for a while, you decide how much autonomy you give your AI, with Bombos as the memory underneath. You keep deciding which draft invoices go to QuickBooks.
If only you know why the hours differ this month, your AI asks you once, and Bombos keeps the answer. You record the agreement, so a similar difference gets recognized on its own next month. In the next proposal you read that explanation back and judge whether the same agreement still applies.
The invoicing round is the start, not the whole offer. We take you along on the first task. After that, every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed, without you having to come back to us. After three months, the invoicing round no longer costs a day.
Every customer agreement in one shared memory.
An invoicing round grows with every customer you add, and every customer brings their own agreements.
Bombos is the memory layer under the AI your team already uses: Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor or your own agents. One plugin gives them all one shared memory: your team's knowledge, the rules it learns from your corrections, and what is already in your email, documents and business software.
You see where every answer came from. Bombos runs in the cloud or standalone on your own server, and one person can try the plugin with their own agents first.
The pilot runs three months for €2,000 instead of €3,000, then €1,000 per month, excl. VAT. Book your half hour to talk through your situation.
What Bombos does, in three steps
It reads what comes in
An email, a message, a photo or a PDF: your AI reads it, finds the client and the details through Bombos in the systems you already have, and sees what is missing.
It drafts the work, you approve it
The proposal sits on one list with the reasoning next to it. You read it, adjust it and approve. Only then is anything sent, booked or filed.
It remembers what you decide
Every correction becomes the rule for next time. Once it has gone well for a while, you give your AI more autonomy step by step, with Bombos as the memory underneath.
What does Bombos not do here?
Bombos does not act here itself: it gives your AI the memory. Without a connection between your AI and QuickBooks, it stays a proposal.
You approve before the draft invoices are posted; only after your check do they go to QuickBooks. Your AI marks differences from last month, but you judge whether that difference is justified. More hours might belong to different work. Without the agreement behind that work, the change is not yet explained. Matching last month is not enough to approve an invoice either: you look at the hours and receipts of this round. Which agreement explains a difference this month is not written down in the spreadsheet or the package. So your AI asks you once which agreement explains the difference, and Bombos keeps the answer, so a similar one is recognized next month with that same reason.
A proposal can be wrong or incomplete. The content needs checking before an invoice is made from it. A ready proposal does not mean the customer has received an invoice either. You approve outgoing messages to a third party, on any channel, before they go out. You set that in the AI or agent itself.
The invoicing round is about what was agreed this month, even when the spreadsheet looks like last month's.
What does your AI forget?
- 01You tell us which AI you use and where it keeps starting over.
- 02We show what a shared memory changes there, on your own examples.
- 03You keep the plan, with or without Bombos.
