Skip to content

QuickBooks, without opening QuickBooks.

Ask the books a question and get the number, with the report behind it.

  • Free to start
  • No card
  • Nothing irreversible without your yes
  • Your own account, not a shared login
Try asking Ray

Ask in your own words.

Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own QuickBooks details, and Ray takes it from there.

  • @Ray what is outstanding on receivables right now?

  • @Ray raise an invoice for Northwind for the September retainer.

  • @Ray how did profit and loss look last quarter against the one before?

  • @Ray which bills are due in the next two weeks?

What Ray can and cannot do in QuickBooks

Reading is free, because reading changes nothing. Everything that writes waits for your yes. The rest is not on Ray’s list.

38 reads wired, and 13 actions that wait for your yes.

Runs on its own

What Ray reads in QuickBooks

  • Invoices, bills, payments, estimates, and the chart of accounts
  • Profit and loss, balance sheet, cash flow, and aged receivables

Reading changes nothing, so Ray never stops to ask whether it may look something up.

Asks first, every time

Always waits for your yes

  • Create or update an invoice
  • Create an estimate, a credit memo, or a purchase order
  • Record a payment, an expense, a bill, or a sales receipt
  • Add a customer, a vendor, or an item
  • Email a credit memo to a customer

Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, and no setting turns that off.

Not on the list

Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

  • Run batch operations across entities
  • Read employee records
  • Pay bills or move money between accounts
Before it acts

Exactly what Ray will ask you to approve.

Not a category of permission. These are the QuickBooks actions that stop in the thread with the real content before they happen.

  • Record QuickBooks bill
  • Create QuickBooks credit memo
  • Add QuickBooks customer
  • Create QuickBooks estimate
  • Create QuickBooks invoice
  • Add QuickBooks item
  • Record QuickBooks customer payment
  • Record QuickBooks expense
  • Create QuickBooks purchase order
  • Record QuickBooks sales receipt
The card Ray posts

Record QuickBooks bill

Showing Doc number, Line, Vendor ref and Due date, each carrying the exact content that will land.

ApproveDecline

How Ray works with QuickBooks

No workflow to build, and nothing to maintain when the work changes.

  1. 01

    Connect QuickBooks

    One click, right where you asked. Ray posts a connect card, you authorise QuickBooks with your own account, and the work you asked for picks up where it left off.

  2. 02

    Ask in plain words

    In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.

  3. 03

    Approve, and it lands

    Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.

and the rest

Megan

@Ray the checkout bug is back. Take a look in QuickBooks, and tell Dana it is being looked at.

Record QuickBooks bill

Waiting on
your yes
ApproveDecline
Works with your stack

Ray uses QuickBooks together with the rest of your tools.

One ask can read QuickBooks, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.

What does connecting QuickBooks to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect QuickBooks and it can do the QuickBooks part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.

It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.

Every person on the team connects their own QuickBooks account, so Ray can only reach what that person can already reach, and the history in QuickBooks shows who actually asked.

Security and permissions

  • You authorise QuickBooks on its own login screen. Your password never passes through Ray.
  • What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
  • Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
  • Disconnect QuickBooks in a message, or uninstall Ray and every connection it held is revoked.

How Ray handles your data

QuickBooks and Ray, answered

The questions teams ask before they connect QuickBooks. Every answer is how this integration is built rather than a promise about it.

More finance, billing & signatures integrations

Ray uses them together in a single run when a request spans more than one.

Browse every integration

Put Ray to work in QuickBooks.

Free to start, no credit card, and nothing irreversible happens without your yes.

Add to Slack for free

By adding Ray, you accept the Terms and Privacy Policy.