# FAQ

### Capabilities & functionality&#x20;

**Q: What does the Supplier Invoicing Manager do?**&#x20;

A: The Supplier Invoicing Manager is a Digital Worker that automates supplier invoice intake, validation, and exception routing for accounts payable teams. It ingests invoices received by email, parses and extracts the invoice data, validates each invoice against the corresponding purchase order and goods receipt, and either auto-approves the invoice or routes it for human review based on the outcome of that validation. ERP records are updated automatically once an invoice is approved.&#x20;

**Q: What is three-way matching and how does the Digital Worker perform it?**&#x20;

A: Three-way matching is the process of comparing an invoice against both the originating purchase order and the goods receipt to confirm that what was invoiced matches what was ordered and received. The Supplier Invoicing Manager executes this comparison automatically for every invoice it processes. It applies configurable tolerance logic to determine whether any differences fall within acceptable thresholds or require escalation.&#x20;

**Q: How does the Digital Worker handle invoices that do not match the PO or receipt?**&#x20;

A: When the Digital Worker detects a discrepancy that falls outside the defined tolerance thresholds, it flags the mismatch and routes the invoice to an AP team member for review. The reviewer receives the relevant details and context needed to assess the situation. Once they provide a decision, the Digital Worker takes follow-up action, including emailing the supplier to request a correction if needed.&#x20;

**Q: What happens after a valid invoice is approved?**&#x20;

A: Valid invoices are auto-approved without requiring manual touchpoints. The ERP is updated immediately to reflect the approval, and a copy of the invoice is attached to the record. The entire process runs without human intervention for invoices that match within tolerance.&#x20;

**Q: Can the Digital Worker handle service charges and line-item variances?**&#x20;

A: Yes. Charge and variance interpretation is one of the Digital Worker's core capabilities. It classifies variances across line items and determines whether each can be resolved within configured thresholds or requires escalation for review. This prevents unclear charges from stalling the approval process or slipping through unchecked.&#x20;

### &#x20;Control & Collaboration&#x20;

**Q: Does a human review every invoice?**&#x20;

A: No. Invoices that match within configured tolerance thresholds are auto-approved without any manual review. Human involvement is reserved for genuine exceptions, specifically invoices where discrepancies, unclear charges, or variances cannot be resolved automatically. This keeps your AP team focused on decisions that require judgment rather than routine processing.&#x20;

**Q: How does the Digital Worker involve AP team members when an exception occurs?**&#x20;

A: When an invoice requires human review, the Digital Worker routes it to the appropriate team member with the relevant details surfaced so they can act quickly and with full context. The reviewer assesses the situation and provides their feedback, after which the Digital Worker handles any required follow-up.&#x20;

**Q: What information does the reviewer receive when an invoice is escalated?**&#x20;

A: Escalated invoices are accompanied by the details needed to understand the discrepancy, including the invoice data, the relevant purchase order and receipt records, and the nature of the mismatch or variance. Reviewers can make informed decisions without having to manually locate supporting documents.&#x20;

**Q: How does the Digital Worker communicate with suppliers?**&#x20;

A: After a reviewer assesses a discrepancy and provides feedback, the Digital Worker sends an email directly to the supplier to flag the issue and request a correction. This removes the need for manual inbox monitoring or back-and-forth coordination by the AP team. &#x20;

### Integration & Technology&#x20;

**Q: What systems does the Supplier Invoicing Manager integrate with?**&#x20;

A: The Supplier Invoicing Manager integrates with email platforms, enterprise applications including ERP and CRM systems, collaboration tools, and document platforms. This allows it to receive invoices from existing inbound channels and update records in the systems your team already uses.&#x20;

**Q: How does the Digital Worker receive invoices?**&#x20;

A: Invoices are captured from inbound email channels. The Digital Worker monitors these channels, ingests invoices as they arrive, and prepares them for processing automatically. No manual upload or intervention is required to initiate the process.&#x20;

**Q: How does it update the ERP after processing?**&#x20;

A: Once an invoice is approved, the Supplier Invoicing Manager updates the invoice status in the ERP directly. This keeps invoice progress and outcomes visible in your system of record without requiring manual data entry by the AP team.&#x20;

**Q: What collaboration and document platforms are supported?**&#x20;

A: The Digital Worker supports integration with collaboration platforms including Slack and Microsoft Teams, and document platforms including IFS and Google Drive. Refer to your implementation documentation for the full list of supported connectors available in your environment.&#x20;

### Security & Reliability&#x20;

**Q: How is audit traceability maintained?**&#x20;

A: Every decision the Digital Worker makes is traceable. Discrepancies, the context in which they were detected, and how they were resolved are all recorded with full traceability. This means AP teams and auditors can review the rationale behind any approval or escalation after the fact.&#x20;

**Q: What prevents duplicate payments or overpayment?**&#x20;

A: The Digital Worker enforces consistent matching rules and applies idempotency controls to prevent invoices from being processed more than once. Combined with three-way matching against PO and receipt records, this significantly reduces the risk of duplicate payments and overpayment.&#x20;

**Q: How are exceptions handled consistently?**&#x20;

A: Exception routing follows defined tolerance and matching rules configured for your environment. Every invoice is evaluated against the same criteria, regardless of volume or who is processing the queue. Consistent rules also make it easier to audit exception decisions and identify patterns over time.&#x20;

### Customization & Performance&#x20;

**Q: Can matching rules and tolerance thresholds be configured?**&#x20;

A: Yes. The Supplier Invoicing Manager uses configurable tolerance logic for three-way matching and auto-approval decisions. This allows organizations to define the thresholds that reflect their own procurement and finance policies, rather than applying fixed rules that may not suit their business.&#x20;

**Q: Can the Digital Worker be adjusted to route specific exception types differently?**&#x20;

A: Exception routing is governed by the rules configured in your environment. Invoices that fall outside tolerance thresholds are escalated with decision rationale, allowing your team to define how different types of discrepancies should be handled and by whom.&#x20;

**Q: What agentic skills does the Supplier Invoicing Manager use?**&#x20;

A: The Supplier Invoicing Manager is built on four agentic skills: Invoice Intake & Parsing, 3-Way Match, Charge & Variance Interpretation, and Exception Handling. Each skill handles a distinct part of the invoice processing lifecycle, and together they cover the full path from invoice receipt through to ERP update or supplier follow-up.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kb.theloops.io/digitalworkers/ifs-loops-digital-workers/digital-worker-guides/dispatcher-assistant/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
