Automate first the handoff that repeats most and follows the clearest rules: an email or spreadsheet in Microsoft 365 that someone retypes into QuickBooks or NetSuite, or a decision made in Teams that someone copies into the ERP. Four good candidates are emailed vendor bills, Excel price lists, approvals in Teams or Outlook and customer emails asking where an order is. Each needs a clean source, a matching rule and a person for the exceptions.
Emailed vendor bills into QuickBooks or NetSuite
The handoff: vendor invoices land in a shared Outlook inbox as PDFs, and someone keys each one into the accounting system.
What already exists: both systems can take bills by email. QuickBooks Online lets you email receipts and bills to a forwarding address you set up in QuickBooks, then extracts details such as dates and amounts for you to review. NetSuite’s Bill Capture turns emailed or uploaded bills (PDF, JPEG or PNG) into vendor bills after a person reviews what was scanned. Its email option runs through the Transaction Email Capture SuiteApp, and the sender’s address must belong to an active employee or vendor record.
The Microsoft 365 catch: an Outlook rule that forwards bills to either address is automatic forwarding to an outside domain. Microsoft 365 controls that in its outbound spam policy, and since 2021 the default has blocked it for new organizations, with blocked messages bounced back to the sender. Ask your admin how to allow it for that one mailbox and address before you build anything on it.
What it needs: one inbox for bills, vendor email addresses on file, a person who reviews each draft bill and a rule for statements, reminders and duplicates, which aren’t new bills.
Excel price lists into the ERP
The handoff: a vendor emails a new price list in Excel. A buyer updates costs line by line, and someone else updates your selling prices.
What already exists: NetSuite can import a vendor price list from a CSV file on the vendor record if you use the Multiple Vendors feature, but the items must already exist and their names must match exactly. Selling prices can be updated with a CSV import of item pricing. QuickBooks Online can import products and services from Excel, CSV or Google Sheets, up to 1,000 rows at a time, with an option to overwrite existing items, though Intuit warns that an import can’t be undone.
What it needs: a cross-reference from the vendor’s item codes to yours, a step that reshapes the vendor’s layout into your import layout, a check that flags large changes and a person who approves them.
For example, with illustrative numbers: a vendor sends 1,800 rows. If 45 rows change by more than 10%, those 45 go to the buyer and the other 1,755 load as is. With the 1,000-row limit above, the 1,755 go into QuickBooks Online in two files.
Approvals in Teams or Outlook
The handoff: someone approves a purchase over a limit, a credit memo or a new customer’s terms in a Teams chat or an email thread. Then someone else records the decision in the ERP, or forgets to.
What already exists: with Power Automate approvals, approvers can respond from an Outlook email, a Teams card or the Power Automate action center, and Teams has a built-in Approvals app. NetSuite has approvals of its own: a sales order can wait in Pending Approval until someone with the right permissions approves it.
The catch: the decision has to get back into the ERP. As of October 2026, Microsoft’s connector reference lists a connector for QuickBooks Time but none for QuickBooks Online or NetSuite. A flow would need a custom connector, and custom connectors aren’t included in Microsoft 365 plans, so you’d also need a Power Automate Premium or Process license.
What it needs: one place for each kind of approval, the thresholds written down, a decision about which system holds the approval of record and a way to write the result back, whether that’s a person, a connector or another tool.
Customer emails asking about order status
The handoff: “where’s my order?” emails arrive in a shared inbox. Someone looks up the order and its tracking, then writes back.
What already exists: in NetSuite, every sales order carries a status, such as Pending Approval, Pending Fulfillment, Partially Fulfilled or Billed. It also has a PO Number field for the customer’s reference. The NetSuite Connector for Outlook can sync a received email and its attachments to a customer, contact or opportunity record, which files the email but doesn’t answer it. NetSuite’s Email Case Capture turns messages sent to a support address into cases, but it works by forwarding your support email to a NetSuite address, so the forwarding policy above applies.
What it needs: a match from the sender to a customer and from the PO number to an order, read-only access to status and tracking, a reply template and a person for complaints, changes and cancellations. If your order status lives outside the accounting system, in a spreadsheet or a shipping tool, the automation needs read access there instead.
Other handoffs to keep on your list
- Purchase orders by email. Customers’ POs retyped into the ERP; see order entry automation.
- Overdue invoices. Follow-up that runs from the accounting system back to Outlook; see invoice follow-up without the chasing.
- New customers. A deal closes in the CRM and the customer gets typed into the ERP again; see new customer setup across four tools.
How to compare handoffs
For two weeks, log each handoff: how often it happens, the minutes per item and how many need a judgment call. Then compare them on the same scale. For example, with illustrative numbers: 60 emailed bills a week at 4 minutes each is 240 minutes a week. Three vendor price lists a month at 90 minutes each is 270 minutes a month, a little over an hour a week. If the bills also follow clearer rules, start there.
Pick your first handoff
| Handoff | Start here if | Set up first |
|---|---|---|
| Emailed vendor bills | Bills arrive as PDFs in one inbox | Allowed forwarding, vendor emails on file |
| Excel price lists | The same vendors’ lists get retyped | An item code cross-reference |
| Teams or Outlook approvals | Decisions get lost in chats | One place to approve, a way to write back |
| Order-status emails | The same question arrives daily | PO numbers on orders, read-only access |
| Emailed purchase orders | Orders arrive in many layouts | Matching rules and an approval step |
Pick the one with the most volume and the clearest rules, and automate it with a person on the exceptions.
Kestrel is an AI-native consulting firm in St. Louis. The agent we deploy is designed to connect only to the inboxes, spreadsheets and systems you authorize, find which of these handoffs repeat most in your own records and draft the automation, with exceptions sent to a person and nothing running until your team switches it on. It’s in development; see order entry automation for one example, or request early access.