Tesorio
Blog

How Finance Teams Are Automating Cross-System Workflows Without Engineering Support

How Finance Teams Are Automating Cross-System Workflows Without Engineering Support

Every morning, finance teams open a handful of tabs and start piecing things together.

Which high-value accounts have gone quiet? Which invoices need reviewing? The information exists. It just lives in multiple places, and getting to it is a morning's work.

That's the problem Tesorio's new MCP server solves.

What MCP means for finance teams

MCP (Model Context Protocol) is an open standard from Anthropic, the company behind Claude. It lets AI assistants connect directly to the tools you already use, like your ERP, CRM, Slack, and Tesorio, then pull live data or take action across all of them from a single prompt.

Instead of spending time gathering information from different systems before work can begin, teams can ask a question, run a workflow, or trigger an action from one place. The AI can access the context it needs across systems and help move work forward.

At its simplest, you can ask one question that spans more than one system, like your Tesorio AR data alongside records in your ERP or CRM, and get the answer back in seconds, no exports or stitching required. From there, the same connection can act on what it finds: run the workflow, send the handoff, write the note back.

For finance teams, that means the morning triage problem has a better solution.

Five workflows finance teams can automate today

Most finance work falls into a few repeatable patterns. Here are five Tesorio customers are already running:

  1. Cross-system analysis: Pull AR data from Tesorio alongside records from your ERP or CRM, and analyze them together.
  2. Self-briefing: Start your day with a prompt that surfaces what needs your attention (flagged invoices, overdue accounts, recent payment activity) without logging into multiple systems to find out.
  3. Monitoring: Set up automated watches on specific invoices or account conditions. When something changes, like a payment coming in or a dispute being resolved, the right person gets notified.
  4. Handoffs: Route information to the right team automatically. When an account needs AE follow-up, a Slack message goes out with the right context attached. No manual handoff required.
  5. Write-back: Log notes back to an invoice or customer record, directly from a prompt. The AI can write back to your data, not only read it.

These aren't the only patterns, but they're the ones that show up most, and seeing them helps you spot where MCP fits your own workflows.

How Fin's Billing Ops team runs daily collections through a single prompt

Russell McBain is a Lead Billing Operations Specialist at Fin (previously Intercom), the Customer Agent company delivering perfect customer experiences, from support to sales to commerce. His team runs a high-volume collections process, and morning triage was eating up manual hours. The daily job: pull the list of high-value accounts, filter down to the ones with no recent note or promise-to-pay, and message the right rep on each.

Before Tesorio's MCP integration, that meant building the list, checking activity across systems, and reaching out to AEs by hand. Each step a separate task.

Now it's one prompt.

"Tesorio's MCP integration has changed how I work," Russell says. "What used to be a manual, multi-step process is now something I can initiate in a single prompt and have done in seconds. It's the kind of automation I didn't think was possible without engineering support."

Each morning, the Billing Ops team uses Tesorio's MCP to pull a filtered list of accounts, cross-check for recent activity, and send personalized Slack messages to the relevant AEs, all through a single conversational prompt. No ticket, no developer, no waiting.

What Russell describes is a combination of three MCP patterns working together: cross-system analysis, self-briefing, and handoffs.

The phrase is worth sitting with: "without engineering support." MCP doesn't require a developer to build a custom pipeline for every new workflow. When the process changes, the prompt changes. The team stays in control.

How Sitetracker automated invoice monitoring on flagged AR

Carey Van is the AR and Revenue Accounting Manager at Sitetracker, a platform that manages complex infrastructure projects. His team deals with the kind of AR that requires ongoing attention: disputed invoices, accounts with bad debt potential, situations that can go quiet for weeks before something changes.

The risk is already flagged, and those tags live in Tesorio. The problem was that the tags stopped there. When a "potential bad debt" invoice gets paid in their ERP, nothing carries the tag across, so no one would know to connect the two unless a person happened to remember. The same went for Sales asking whether a disputed invoice had been paid. Someone had to remember to check.

"Tesorio's MCP lets us connect AR data to the rest of our stack through Claude. We can pull invoices, tags, and customer details from Tesorio alongside ERP and CRM data in a single workflow," Carey explains.

That connection is what makes the monitoring possible. "I've automated invoice monitoring based on the AR tags and signals we already manage in Tesorio. When an invoice is flagged as disputed, bad debt potential, or otherwise needing attention, we can automatically watch for payment activity and alert my team in Slack when it's paid. Instead of manually checking Tesorio, our ERP, and internal notes, the workflow brings the right AR context together so we can act faster," he says.

The payoff is catching what used to slip by. When a flagged invoice gets paid, the right person hears about it in Slack, without anyone having to remember it was flagged. "It cuts out manual work, keeps the right people in the loop, and gives us visibility into payment activity on flagged invoices that would otherwise go unnoticed," Carey says.

Why this is different from previous automation tools

Finance teams have been promised "connected" software for years. What they usually got was a reporting layer on top of siloed systems.

The difference is what happens next. Older "connected" tools stopped at reporting. They showed you what happened. With MCP, an AI assistant can act on it: run the workflow, send the handoff, close the loop.

The teams using Tesorio's MCP integration are automating the manual steps: the checking, the cross-referencing, the follow-up. What remains is the judgment work, the decisions that require a person.

That's what good automation looks like.

Tesorio's MCP integration is available now. Chat with the team to learn more.

More from Blog