Finance playbook · AI Employee: Fin

PO & Invoice Status Lookup

Vendors + team get status in seconds

Install this playbookBack to marketplace
The problem

"Has PO-4211 been approved yet?" "Did we pay Acme's invoice?" "When's the next payment run?" Every finance person spends an hour a day answering variants of these questions in Slack. Requesters ask the finance team because they can't find it themselves; finance has to look it up in NetSuite / Coupa / Bill.com anyway; the answer is public information gated on someone else's tooling knowledge.

At a glance
Trigger
Chat
Approvals
None
What it does
Read-only
Systems
NetSuite · Coupa · Bill
How it feels in production

An hour-by-hour walkthrough.

Priya asks in Slack: "@Fin what's the status on PO-4211 for Acme Cloud?" Fin recognises the reference, pulls PO-4211 from Coupa, and replies in-thread: "PO-4211 · Acme Cloud · $24,500 · Approved 2026-09-04 by CFO Diane · Invoice INV-9812 received 2026-09-06 · Scheduled for payment run on 2026-09-14 · Payment method ACH." Priya replies: "can we speed that up, they're threatening to pause the service?" Fin responds: "To move to today's off-cycle run: I need CFO approval (over $10K). Draft request attached — approve to send." Priya reviews, hits approve. Fin routes to Diane in Slack with the context. Diane approves in 4 minutes. Fin schedules the off-cycle payment and replies in the original thread: "Payment scheduled for today's run at 14:00. Confirmation will follow." Same pattern for any lookup: invoice status, payment date, PO balance remaining, vendor payment history, approval-chain progress. Every answer is grounded in the finance system, every action requires the same approval it would have required through the finance system's UI, and finance sees the volume drop from 40 lookup DMs per day to 4.
How it works

Step by step.

  1. 01

    Parse the question + identify the reference

    Recognise PO / invoice / vendor / payment references from context — "PO-4211", "Acme Cloud invoice", "last payment to Stripe". Ambiguity triggers a follow-up clarification ("which Acme — Cloud or Analytics?").

    Reasoning · Reference resolver · Vendor directory
  2. 02

    Fetch from the finance system with the right scope

    Query NetSuite / Coupa / Bill.com / SAP / Concur. Respect access control — Fin only surfaces what the asker is authorised to see. AP clerks see everything; CSMs see only their accounts' invoices.

    NetSuite · Coupa · Bill.com · SAP · Access control
  3. 03

    Present the answer with actionable context

    Not just "approved on X" — include the full state: amount, approver, next milestone, payment date, method. In a form the asker can act on directly (link to Coupa, next-step buttons).

    Slack · Teams · Web UI
  4. 04

    Handle follow-up actions with proper approvals

    Follow-ups like "can we speed that up" become approval requests routed through the correct authority chain (over-$10K needs CFO). Fin never bypasses the approval matrix; it just makes the routing invisible.

    Approval matrix · Slack · Teams
  5. 05

    Log the lookup + auto-improve

    Every lookup logged with question, answer, satisfaction (implicit from follow-up patterns). Common lookups become saved views + Slack shortcuts. Fin surfaces top-asked patterns in a monthly digest for process improvement.

    Analytics · Query log · Digest
Systems and wiring

What you connect to make this run.

NetSuite · SAP · Sage · QuickBooks

read

Master financial data: PO, invoice, payment, vendor. Read-only for lookups. Writes (payment scheduling, PO edits) go through the accounting system's own approval flows, not around them.

Coupa · Bill.com · Ramp · Airbase

read+write

Procurement + payables platforms. Read status; write approvals + payment scheduling actions when the caller has authority. Every write is logged with the caller's identity.

Slack · Teams

read+write

Primary surface. Ask in DM or channel; answers threaded with full context; follow-up actions inline. Reduces the AP inbox by an order of magnitude.

Approval matrix · Access control

read

Who can approve what threshold, who can see which vendors' invoices. Fin enforces both — never surfaces data the asker can't see, never actions requests the asker can't authorise.

What changes

Before and after, honestly.

Time from lookup question to answer
Before
45 minutes to 4 hours
After
Under 30 seconds
Finance team hours per week on lookup requests
Before
20-40 hours across the AP team
After
3-6 hours (only complex exceptions)
% of PO / invoice questions self-served
Before
5-15%
After
80-90%
Vendor complaints about payment status confusion
Before
20-40 per month
After
Under 5 per month
Related

Playbooks that pair with this one.

Finance

Bill Payment Approval

Lookups often lead to speed-up requests; the approval flow is shared.

Finance

Vendor Intake & Onboarding

Vendor directory used here to disambiguate references.

Finance

Expense Submission & Approval

Same lookup + action pattern applied to employee expenses.

Frequently asked

Answers about this playbook.

Can requesters just look this up in Coupa themselves?

Most requesters don't have Coupa licenses (they're expensive per-seat) or don't know the UI. Fin democratises the read-access without giving everyone a license they don't need for daily work.

How does it handle sensitive vendor info (rates, contract terms)?

Respects the same access control the finance system enforces. A CSM asking about "vendor X" sees invoice status and payment date but not contract rates unless they have vendor-management access.

What if the finance system is down?

Fin returns the last-known cache with a timestamp and "cached — live system unreachable" note. Writes queue for retry when the system comes back; failed writes escalate to the AP team.

Can we use it in email as well as Slack?

Yes — same engine reachable from email (vendor asks about payment status, forwarded to a finance-alias mailbox, Fin replies with the status + payment date). Vendor sees a finance team member's signature, not a bot.

How does it handle multi-entity companies?

Each entity's finance system queried separately. Cross-entity lookups ("has Acme paid us across all entities?") aggregated by Fin with per-entity breakdown. Access control respected per entity.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore Finance playbooks