NetSuite approvals

How to approve NetSuite transactions from Microsoft Teams

The options for approving NetSuite records in Teams, and the checklist that separates a notification from a controlled approval.

7 min read · Updated 1 November 2026

On this page

Why approve in Teams

If your managers spend the day in Microsoft Teams, that is where approval requests get seen. Moving the request to Teams shortens the time a bill or purchase order waits, without moving the approval process out of NetSuite.

Three ways to do it

1. Notifications only. A saved search or workflow e-mails a Teams channel, or a simple connector posts a message with a link. The approver still has to open NetSuite to decide. It helps visibility, not speed.

2. A general integration platform. iPaaS tools can post an Adaptive Card to Teams and call NetSuite when someone clicks. It works, but you build and maintain the identity mapping, the security checks, multi-level routing and the audit trail yourself, and the logs live in the integration platform.

3. A NetSuite-native Teams approval app. A purpose-built app sends an Adaptive Card to the right person when NetSuite assigns them as approver, verifies who clicked, and executes the same approve or reject action NetSuite's own button would — then routing continues.

What a controlled Teams approval needs

Use this checklist whichever route you take:

  • Right person only. The card goes to the person NetSuite assigned, matched to their Teams account by work e-mail, not to a shared channel anyone can click.
  • Verified click. The request from Teams is signature-checked, and the decision token is single-use and bound to that person and that record.
  • Your routing decides. The click performs NetSuite's own approve or reject, so levels, limits and segregation of duties still apply.
  • Stale cards refused. If the record was changed, re-routed or decided elsewhere, a late click does nothing.
  • Limits for big amounts. Above an amount you set, the card has no buttons and the decision is made in NetSuite.
  • Audit trail on the record. Approver, time, channel and comment recorded on the NetSuite record.
  • Context on the card. Vendor, amount, due date, budget, attached document and warnings, so the approver doesn't approve blind.

What it takes to set up in Teams

A Teams app package is uploaded by your Microsoft 365 administrator, and a bot registration connects Teams to the service that talks to NetSuite. With Axiera Approvals, that gateway runs in a tenant you own, so approval data never passes through a vendor platform, and there are no Power Automate flows to build or maintain.

Teams-only features worth having

  • Ask a question from the card — the approval stays open, the answer arrives in the same chat, and both are saved to the record as notes.
  • Approve routine items together — small, clean items decided in one go, each re-checked on its own; anything with a warning is left for a closer look.

See Axiera Approvals on your own NetSuite records