All articles
Use Case#Teams#Power Automate#SharePoint#Approvals#Digital Transformation

Invoice Approval in Microsoft Teams — From Physical Folder to Digital Collaboration Hub

15 June 20246 min read
Document folders and binders — digital invoice approval

Photo: Pixabay / Pexels

The Symbol of the Old Workflow: The Invoice Folder

An established trade company with 30 employees had a ritual that repeated daily. A physical folder — a gray plastic binder with a clamp mechanism — traveled each morning from the managing director's office to the project managers, then to the warehouse, then back to accounting. Each station was marked by handwriting, stamps, and dates. The folder was the visible symbol of organizational structure.

But this visibility was deceptive. Because the reality was chaotic:

  • Invoices were overlooked because the folder was "somewhere"
  • Early payment discounts (Skonto) were regularly missed because nobody tracked the deadlines
  • There was no control over how long an invoice spent in which phase
  • And at the end, all invoices were still printed — for digital archiving in... whatever

Management knew: this couldn't be the future. But what would a real digitalization project look like without disrupting daily operations?

Teams as the Nervous System

The insight was: invoice approval should go where people already are — in Microsoft Teams. Not a new specialized system, not a new "approval tool" that exists only for this one task. Instead, approval should be seamlessly integrated into the channel-based workflow employees already use daily.

The New Workflow in the Teams Channel:

A dedicated Teams channel "Invoice Approval" was created. All incoming invoices land here — not as printed copies, but as digital Adaptive Cards. These cards are key to usability.

The process:

  1. Invoice Receipt: An invoice arrives by email or scanner. Power Automate parses the email, extracts attachments, and immediately stores them in SharePoint with standardized metadata (vendor, amount, invoice date, category).

  2. Teams Notification: An Adaptive Card is sent to the "Invoice Approval" channel. This isn't just a link to a SharePoint file. It's an interactive card that shows all relevant information directly:

    INVOICE RECEIVED
    ───────────────────
    Vendor: ABC Electric GmbH
    Amount: €2,480.50
    Invoice Number: 2024-14782
    Due Date: 15.06.2024
    Early Payment: 2% if paid by 05.06.2024
    ───────────────────
    [View PDF] [Approve] [Reject] [Comment]
    
  3. Intelligent Assignment: The flow has already recognized that this invoice is for "Material Costs Outdoor Lights" — and automatically added the responsible person (project manager). This person sees the card with a special badge "You must approve".

  4. Approval in Teams: The project manager clicks "[Approve]" directly in Teams. That's it. No further steps needed.

  5. Automatic Orchestration: In the background, everything now happens automatically:

    • The invoice is marked as "approved" in SharePoint
    • A "print-ready" folder receives the PDF (if a physical copy is still needed for filing)
    • The invoice is made ready for DATEV export
    • A confirmation is sent to accounting

The Cockpit: Full Transparency

A major difference from the "invoice folder": the system has a built-in status board. In the same Teams channel, employees can click tabs and see:

  • Pending (Red): 7 invoices awaiting approval
  • Approved (Green): 42 invoices approved this week
  • Overdue (Orange): 2 invoices with due dates in 2 days — risk of Skonto loss
  • Archived (Gray): All completed invoices

A Power BI dashboard is also embedded, showing management in real time:

  • Average approval time per department
  • Which vendors have the longest payment terms
  • Savings through Skonto utilization (so far this year: €5,200)

This dashboard isn't hidden. It's publicly visible to everyone with Teams access.

The Workflow History: Audit Trail

A detail often overlooked: Teams Approvals automatically create a complete audit trail.

Every invoice has a "Workflow History" tab that shows:

14.05.2024 09:15 — Invoice received
14.05.2024 09:16 — Assigned to Max Müller (Project Manager)
14.05.2024 10:32 — Max Müller approved
  Comment: "Confirmed, ordered 3 spools."
14.05.2024 10:33 — Power Automate: exported to DATEV
14.05.2024 10:34 — Archived in SharePoint
14.05.2024 10:35 — Department notified (payment approved)

This is valuable not just for compliance. It creates clarity in daily work: if someone later asks "Did we pay this Müller invoice?", you can immediately check in Teams when and by whom it was approved.

The Differences from Traditional Solutions

One might think: this is the same as an approval tool or a SharePoint list with approval columns. But no. The difference is qualitative:

  1. Context: Teams is already open. Nobody has to load a new app. Messages, approvals, filing — all in one place.

  2. Passive vs. Active Notification: In an approval tool you have to "check again." In Teams, the notification pushes directly — not just text, but the complete card with action.

  3. Collegial Learning: When a project manager rejects an invoice with the comment "This vendor uses wrong account standards," everyone else sees it in the channel. Next time they know.

  4. Conversation Over Tickets: Teams doesn't feel like "working in a system" — it feels like communication.

The Numbers

After five months of operation:

  • Approval Time: Average reduced from 6 days to 1.5 days
  • Skonto Capture Rate: from 73 percent to 96 percent. That means: of ten invoices with 2% discount, nine are now paid early. Before, only seven were.
  • Error Clearance: If an invoice is "wrong" (e.g., invoice for a closed project), it's immediately spotted because the project manager sees it. Error rate dropped from 6 percent to 1.2 percent.
  • Paper Consumption: Invoices are only printed when necessary — consumption dropped 90 percent
  • Skonto Gain: In the first full year: €8,400 in additional savings compared to the old routine

An interesting side effect: average time to payment also decreased for invoices without early payment discounts. The reason: without physical barriers (folder must travel from A to B), throughput times are simply faster.

Future Expansions

What's nice about Teams-based automation: it's alive. The company is already planning:

  • Video Tutorials: A short video in the Teams channel shows new employees how approval works. Not in separate documentation, but directly in the workflow.

  • Vendor Master Data Validation: If an invoice comes from a new vendor, the system could automatically ask: "Is this a known company?" and warn the approver if not.

  • Invoice Prediction: A small ML model could learn: "Vendor XY always sends an invoice on the 5th, averaging €1,200." If then an invoice for €3,200 arrives, a flag can be set.

  • Integration with Payment Run: After approval, the invoice could automatically be added to the next day's payment run — if the company runs daily payment processing.

The Cultural Side

One last, important point: employees report less stress. The physical "invoice folder" wasn't just a workflow — it was also a psychological symbol. "Who has the folder?" — that was a sentence spoken daily. With deeper implications than just logistics: "Why haven't we heard back yet?"

With Teams-based approval, the question is implicitly answered. You see it. The red badge shows: 7 pending. The green dashboard shows: these were processed quickly. No hidden folder. No hidden anxieties.

For companies looking to go further, we've also built solutions with DATEV XML integration for planning offices and a scalable workflow handling 340+ invoices per month.


Book a free strategy call

Ready to automate your processes?

Book a free 30-minute intro call.

View projects

Free, no commitment, no sales pitch.