If you run your books in QuickBooks and your marketing on Facebook, Meta now wants its AI agent sitting between the two. On September 29, Meta launched Muse for Small Business, a set of skills and connectors that plug its Muse agent into Intuit QuickBooks, Shopify, Stripe, Slack and other business tools such as Asana, Canva and Notion, plus your Facebook and Instagram business accounts (Meta). Intuit says the QuickBooks connector is live and that Muse can "create and send payment-enabled invoices directly to customers" (Intuit).
That last part is the one worth slowing down on. Asking an agent what you made last quarter is low risk. Letting it email a customer a bill is not. Our answer: yes for reading your numbers and drafting invoices, not yet for anything that goes out the door without you looking at it.
What Muse can actually do in QuickBooks
Intuit lists five workflows. Muse can review profit and loss and cash flow for any period, check your balance sheet against industry peers, show which customers and products drive the most revenue, create and send payment-enabled invoices, and track overdue invoices and send payment reminders (Intuit).
That is a deliberately narrow slice. Intuit says it "defines exactly which QuickBooks capabilities are available" in the connector, and that payroll, closing your books, filing taxes and complex cash flow planning stay in QuickBooks itself (Intuit). That tells you how Intuit ranks the risk.
Meta's own pitch leans toward the reading side. One of its suggested prompts is "How was my business's financial performance this month? Find any expenses that look off" (Meta). That's a good first job for an agent. If it gets a number wrong, you notice before anyone else does.
What it asks before it acts
Meta makes two kinds of promises here, and they are not the same strength.
The launch post is absolute: "nothing publishes, sends, or spends without your approval" (Meta). The product page FAQ is more careful. Muse "is designed to ask your permission before taking certain actions, like sending messages, making purchases, or sharing information with a connected app," and you can "allow an action once, always allow it, or deny it" (Meta Muse). The same page says you can review and approve actions before they happen and see "a complete audit trail" of what the agent has done and plans to do (Meta Muse).
Read those together and the real control is a setting, not a guarantee. "Always allow" on QuickBooks sends means the approval step is gone, by your own choice, for every invoice after that. Meta's AI chief Alexandr Wang made a related point to CNBC after some users complained on social media that the agent accessed personal messages without authorization: "there are certainly instances users have authorized various communications or whatnot earlier in a conversation, and then may have forgotten about that" (CNBC). Meta disputes the complaints. Either way, that's the failure mode to plan for.
What goes wrong when an agent touches money messages
Three risks matter for invoicing, and none of them are exotic.
Wrong amount. An agent building an invoice from "bill them for last week" has to infer hours, rates, materials and tax from whatever it can see. Intuit's own example is a plumber asking Muse "how to bill for last week's work" (Intuit). That's a convenient prompt and a vague spec. An overbill costs you trust. An underbill costs you money, and customers rarely flag it.
Wrong customer. Two clients named Garcia, a parent company and its subsidiary. Picking the wrong record in QuickBooks is a human mistake too, but a human usually knows who they did the work for. An agent is matching names.
Tone on reminders. A payment reminder is a relationship message. The same nudge reads fine to a new customer and insulting to one who has paid on time for six years and is a week late after a hospital stay. Meta says Muse knows "what your brand sounds like" (Meta). Knowing your brand voice is not the same as knowing that this client's spouse just had surgery.
An invoice is not a draft once it's sent. It's a claim on your customer's money with your name on it.
There's a fee angle too. A payment-enabled invoice paid by card or digital wallet runs 2.99% per transaction on QuickBooks Payments, per Intuit's rate page as of September 18, 2026 (QuickBooks). A wrong invoice that gets paid and then refunded is a mess to unwind.
A worked example
This is a fictional, illustrative scenario, not a real client. Every detail is invented.
A two-person HVAC company in Doral finishes a maintenance visit for a property manager who owns four buildings. The owner types into Muse: "Invoice Bayside for Tuesday's service, same as last time."
Muse finds two QuickBooks customers with "Bayside" in the name, picks the one with the most recent invoice, copies last month's line items, and drafts an invoice for $1,840. Last month included a $1,200 compressor part. This month didn't.
With approval on, the owner sees the draft, catches the part line and the wrong building, fixes both, and sends a $640 invoice ($1,840 minus the $1,200 part) to the right entity. With "always allow" on, the property manager gets a $1,840 bill for the wrong building, and the owner finds out when they call.
Two weeks later the owner asks Muse to "remind everyone who's overdue." The list includes a client who already mailed a check that hasn't been recorded yet. A reviewed reminder gets skipped. An unreviewed one gets an annoyed phone call.
Nothing in that scenario requires the agent to be bad. It requires the agent to be reasonable with incomplete information, which is what agents are.
What it costs
Meta says Muse is "free for most of what people need," with subscription plans for more (Meta). Meta's help page says the free tier has a usage limit that refreshes over time, and lists a Power plan at $20 a month and a Maximum plan at $100 a month, priced by weekly token allowance, and notes subscriptions are in limited testing and not available everywhere (Meta Help Center). Intuit doesn't publish a separate price for the QuickBooks connector on its announcement (Intuit). Your existing QuickBooks plan and payment processing fees still apply.
The rollout rule we'd use this week
Three stages, and don't skip one.
- Read and draft only. Connect QuickBooks. Use Muse for P&L questions, overdue lists and invoice drafts. Set send permissions to "allow once," never "always allow." Check every number it gives you against QuickBooks for the first two weeks.
- Approve every send. Let Muse send invoices and reminders, but approve each one. Look at three things every time: customer record, total, and the first sentence of any reminder. Keep a simple count of how many drafts you had to fix.
- Widen slowly. Only after a month of clean drafts, consider "always allow" for one narrow case, like recurring invoices with fixed amounts to long-standing customers. Keep first-time invoices and every reminder on manual approval.
If your fix count isn't near zero by the end of stage two, stay there. That number is your answer, not Meta's marketing or ours.
Where a custom agent still makes more sense
Muse is a general agent with a fixed QuickBooks menu that Intuit controls. That's fine for most shops. It stops being enough when your billing rules live outside QuickBooks: job tickets in a field service app, rates that change by contract, deposits held in escrow, or approvals that need a second person, not just the owner.
A custom agent can enforce rules Muse can't, such as "never invoice above the signed estimate," "no reminders to accounts flagged VIP," or "route anything over $5,000 to the office manager." It can also log decisions in your own system instead of an audit trail inside someone else's app. Before you buy one, read our notes on what vendors are and aren't allowed to claim, and run the numbers on what a wrong invoice costs you against what the build costs. Model costs are rarely the expensive part anymore, as we showed in what running an agent costs now.
If you want help setting up Muse permissions on your QuickBooks account, or deciding whether your billing rules need something custom, write to us: team@lirium.ai.