prompts.chatprompts.chat
Login
All classifiers
Decision chainDocuments & email4 steps · 9 endpoints

Finance mailbox intake

Sort a shared finance inbox, identify documents, match invoices to orders, and hold duplicates before approval.

Scenario paths

Pick a predefined path to highlight it through the chain. No model is called; outcomes are illustrative.

Steps
  1. Finance inbox email intent
  2. Business document type
  3. Invoice and purchase order match
  4. Duplicate invoice signal
Endpoints
  • Reply with payment status
  • Archive
  • Route to team
  • Ask supplier for the right PO
  • Payment approval
  • Call-back verification
  • Restricted handling
  • AP specialist
What each endpoint means

  • Reply with payment status · Automated

    Code looks up the invoice and replies with its status.

  • Archive · Automated

    Archived without action.

  • Route to team · Automated

    Credit notes to AP, receipts to expenses, purchase orders to procurement.

  • Ask supplier for the right PO · Automated

    Asks the supplier to confirm the purchase order number.

  • Payment approval · Human review

    The budget owner approves payment; nothing is paid without a person.

  • Call-back verification · Human review

    A person calls the supplier on a number already on file before any change.

  • Legal team · Human review

    Forwarded to legal without interpretation.

  • Restricted handling · Human review

    Moved to restricted storage and passed to the responsible team.

  • AP specialist · Human review

    An accounts payable specialist handles disputes, mismatches and duplicates.

Steps

  1. Finance inbox email intentChoiceEntry

    Work out what the sender wants.

    Question, inputs and notes

    Asks:What is the sender asking the finance team to do?

    Receives

    • Inputemail
  2. Business document typeChoice

    Identify the document.

    Question, inputs and notes

    Asks:What type of document is this?

    Receives

  3. Invoice and purchase order matchChoice

    Compare the invoice with its purchase order.

    Question, inputs and notes

    Asks:Do the items on the invoice correspond to the items on the purchase order?

    Receives

    • Inputextracted_text as invoice lines
    • Inputpo_lines
  4. Duplicate invoice signalNoul

    Hold anything already received.

    Question, inputs and notes

    Asks:Is this the same invoice as one of the candidates already received?

    Receives

About this chain

Goal and input

Every email ends answered from the system, archived, with the right team, verified by phone, with legal or restricted handling, or in front of a person who approves payment.

The email, extracted document text, and ERP data looked up in code.

email
Sender (with known-contact check), subject, body and attachments.
extracted_text
Text extracted from the attachment.
po_lines
Purchase order lines from your ERP, with code checks.
candidates
Possible duplicate invoices found in code.
How it runs
  • Every payment is approved by a person, and bank details are never changed from an email.
  • Contracts and personal records are identified and handed off only; nothing in this chain interprets them.
  • Totals, tax and duplicate candidates come from code and your ERP; the classifiers compare descriptions.
Sources (3)

Primary documentation this chain builds on.