# A long tail of vendor invoices, kept in order.

A SaaS company pays for dozens of tools and cloud services. Invoices and receipts arrive by email from all of them, and someone has to keep the spend tracker and the budget owners up to date.

> Example scenario: an illustration of how Mission Control could be used, not a customer story.

## Where the time goes

- Vendor invoices and renewal notices arrive at different inboxes, often addressed to whoever signed up for the tool.
- The spend tracker falls behind, so budget owners find out about renewals after they've been charged.
- Receipts needed for the accountant are scattered across mailboxes at quarter end.

## Relevant workflows

- **Vendor invoice intake** — File each vendor invoice to the right Drive folder and append vendor, amount, period and owner to the spend tracker in Sheets.
- **Budget owner notifications** — Post a Slack message to the owning team's channel when an invoice or renewal notice for their tool arrives.
- **Receipt collection for the accountant** — Draft an email forwarding the month's receipts to the external accountant once they are filed.

## Example scenario: a lean finance function

This is an illustration of how the workflows could run, not a customer story.

Imagine a SaaS company with a one- or two-person finance function. Engineering, sales and marketing each sign up for their own tools, and the invoices go wherever the account was created.

Each team connects the mailbox that receives those invoices. When one arrives, Mission Control drafts the follow-up: upload the PDF to the vendor's folder in Drive, add a row to the spend tracker with the vendor, amount and billing period, and post a short note to the owning team's Slack channel.

The finance lead reviews each case and approves. Actions run with their own access, so the spend tracker stays under the permissions finance already controls. At month end, a drafted email collects the filed receipts for the external accountant — sent only once approved.

[Book a demo](/contact)