Solutions Invoices

Invoice capture

Documents read on arrival, matched against the order, filed and queued for payment.

01 / What it looks like running

Start to finish, and where a person still comes in.

  1. 01 / TriggerInvoice arrives
  2. 02 / AutomatedRead and keyed
  3. 03 / AutomatedMatched to the order
  4. 04 / AutomatedFiled
  5. 05 / AutomatedQueued for payment
  6. 06 / Needs a personMismatches and disputes

Automated Needs a person 4 of 6 run without anyone

02 / What stops happening

7 steps become 1.

The struck lines are the ones nobody performs after this is live.

  1. Invoice arrives in a shared mailbox
  2. Someone opens it and downloads the attachment
  3. They key the values into the finance system
  4. They match it against the purchase order
  5. They file the document
  6. They email the approver
  7. Mismatches and disputes, resolved by a person

03 / Built on

In your tenant, under your licences.

  • Power Automate
  • Power Automate Desktop
  • SharePoint

Yours may differ. What a process runs on is decided by what it touches, not by what we prefer building with.

Does yours run like this?

It probably runs nearly like this, with two steps that are entirely your own. Those two are the interesting part.

Book a call Next: Statement reconciliation