How Spendesk works

Requirement evaluated: International wire payments to 8 overseas vendors with multi-currency support

For your 8 overseas vendors, Spendesk has built a native international payment execution layer powered by an embedded Wise Platform integration. Once an international invoice clears the approval workflow, a controller or account owner can initiate payment directly from the Spendesk invoice queue using either local payment rails (routed through Wise's local banking networks, with 95% of transfers settling within one day) or SWIFT, covering up to 71 countries and 31 currencies at the mid-market exchange rate with no FX markup. …

Limitations: The international wire payment execution feature is documented as available to EEA (EUR wallet) customers only, with GBP in beta; a USD-entity US company cannot initiate cross-border wires from within Spendesk as of the current documented state, meaning the 8 overseas vendor payments would require manual bank execution …

Requirement evaluated: Automatic remittance advice sent to vendors upon payment

For your 6-location services company processing 1,800 invoices per month across bi-weekly check runs and monthly ACH batches, Spendesk does not provide automatic outbound remittance advice to suppliers upon payment. What the platform does offer is a manual, buyer-initiated proof-of-payment PDF: once a payment reaches 'Paid' status in Spendesk, an AP team member must navigate to Invoices > History, locate the paid invoice, click 'Get PDF proof of payment,' download the file, and then manually email it to the supplier who has asked for it. This workflow is reactive and manual on both ends; the supplier must request the document, and your AP team must retrieve and send it. …

Limitations: The manual proof-of-payment PDF is also restricted to payments executed through Spendesk's own wallet; payments initiated outside the Spendesk wallet (which is common for US ACH and check runs, particularly for a Sage Intacct-based company processing through bank payment files) …

Requirement evaluated: Automatic remittance advice sent to vendors upon payment

This $120M services company currently sends remittance manually via email chains, and Spendesk does not eliminate that step. The only documented mechanism for vendor payment notification in Spendesk's help center is a fully manual, AP-staff-initiated workflow: after a payment reaches 'Paid' status, an AP user must navigate to Invoices > History, locate the batch, click the invoice, click 'Get PDF proof of payment,' download the file, and then manually send it to the supplier. …

Limitations: For a buyer processing approximately 1,800 invoices per month across bi-weekly check runs and monthly ACH batches, the absence of automated outbound remittance means AP staff must manually generate and email a PDF proof of payment to each vendor upon request, which is functionally identical to the buyer's current email …

Requirement evaluated: Positive pay file generation formatted for Bank of America

This buyer runs bi-weekly check runs and needs to transmit a Bank of America-formatted positive pay file (an issued-check register containing check number, amount, date, and payee) to BoA's CashPro treasury system after each check run for fraud prevention. Spendesk's payment file infrastructure is built entirely on European payment rails: the platform generates SEPA XML files for wire-based reimbursements and generic CSV bank journal exports for accounting reconciliation. …

Limitations: Spendesk does not execute domestic US check runs and has no mechanism to produce a Bank of America-formatted positive pay file; this buyer would need to continue generating that file manually from Sage Intacct or via a standalone treasury utility, meaning Spendesk provides zero lift on this specific requirement.

Requirement evaluated: Vendor communication log: track every inquiry and response to eliminate the 6 hours/week our team spends on status calls

For a 3-person AP team fielding 6 hours per week of vendor status calls, the key question is whether Spendesk gives external vendors a self-service way to check invoice receipt, approval stage, or payment status without calling AP. The answer from Spendesk's own help center is no. Spendesk does have a Vendor Portal, but its documented scope is limited exclusively to onboarding new suppliers during a procurement request workflow: vendors receive a one-time link to fill out information forms and banking details, and the portal is 'only triggered from a purchase request.' It is not a persistent, ongoing communication channel. …

Limitations: Spendesk has no documented mechanism for external vendors to self-serve invoice or payment status, submit inquiries in a logged thread, or receive proactive status notifications at workflow milestones. …

Requirement evaluated: 1099 preparation: automated classification, threshold tracking, and electronic filing

For a $120M US services company that needs automated 1099-NEC/MISC classification, rolling IRS threshold tracking, W-9 collection, and electronic filing, Spendesk offers no documented mechanism for any of these steps. Spendesk is a France-based spend management platform whose compliance architecture centers on European regulatory requirements: VAT handling, PSD2, GDPR, and EU e-invoicing formats. Its own FAQ confirms that full payment services are available to companies in the European Economic Area, the UK, and the US, but no US-specific tax compliance features, including 1099 workflows, are documented anywhere in the vendor's help center, product pages, or fact sheet. …

Limitations: Spendesk has no documented 1099 classification, threshold tracking, or electronic filing capability for US buyers at any price point or in any module; the buyer would need to rely entirely on Sage Intacct's native 1099 module and a separate e-file service such as Tax1099 or Track1099, reintroducing the manual work this …

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For a $120M multi-location services company with a 3-person AP team processing 1,800 invoices per month, Spendesk provides a vendor portal that covers several but not all of the buyer's five stated sub-requirements. On new vendor registration and information collection: when a procurement request is created for a new vendor, Spendesk triggers a vendor onboarding step in the approval workflow and the primary vendor contact receives an email with a link to the vendor portal, where they fill out customizable forms to provide business information, tax information, payment details, and compliance documents. …

Limitations: Three of the five sub-requirements are materially incomplete for this buyer: external suppliers cannot independently log in to check payment status (no outward-facing supplier portal session), invoice submission through a true supplier-facing portal is absent (SMI is an employee-side feature), and W-9/W-8 collection is …

Requirement evaluated: Centralized vendor master synchronized bidirectionally with Sage Intacct

Your company runs two ERP entities in Sage Intacct, and the requirement is a centralized vendor master that stays in sync in both directions between your AP platform and Sage Intacct. Spendesk has no documented integration with Sage Intacct: its own help center contains zero articles referencing Sage Intacct, and its product blog explicitly lists its native accounting integrations as Xero, QuickBooks, and NetSuite, with no mention of Sage Intacct. …

Limitations: Spendesk has no Sage Intacct integration at any plan or price point, making the bidirectional vendor master sync requirement undeliverable. Additionally, at least one independent review notes that Spendesk does not serve businesses in the US, which compounds the fit gap for a US-based services company operating on Sage …

Requirement evaluated: Touchless processing target: 40%+ of PO invoices should require zero manual intervention from capture through posting

For a 3-person AP team processing 990 PO invoices per month in Sage Intacct, Spendesk's Supplier Invoices module covers several pre-processing stages: invoices arrive by email or file upload into a shared inbox, AI-powered OCR ('Marvin') extracts header and line-level data automatically, and the system links each invoice to its corresponding PO using automatic matching. When the 'Skip budget owner approval for linked invoices' setting is enabled, <cite index="1-3,1-4,11-13">invoices linked to approved Purchase Orders skip the approval stage and are sent straight to the 'Invoices > Review' stage</cite>, removing the budget-owner touchpoint. …

Limitations: The buyer's 40% touchless target requires zero human intervention from capture through posting: Spendesk's workflow architecture does not permit this because the Controller Review stage is mandatory for all invoices and requires a human Validate action before any invoice can move to payment or be exported for bookkeepi …

Requirement evaluated: Confidence scoring on extracted data so AP clerks know which fields to verify vs. which are high-confidence

For your team of three processing 1,800 invoices a month, Spendesk's OCR engine (called Marvin) extracts header fields (vendor, amount, date, due date) and pre-fills the invoice submission form. A separate ML-powered feature called AutoCatML then predicts expense account, VAT account, and analytical field values in the Bookkeep > Prepare stage by learning from your organization's historical bookkeeping patterns. Critically, AutoCatML uses an internal confidence threshold to decide whether to surface a suggestion at all: the help center states it 'only proposes values when the confidence of a correct value is high' and withholds the suggestion if that threshold is not met. …

Limitations: The buyer's requirement is for AP clerks to know field-by-field which extractions to trust and which to double-check. Spendesk's internal confidence gate suppresses low-confidence bookkeeping suggestions rather than surfacing the uncertainty to the reviewer, so clerks must treat every pre-filled field as equally unveri …

Requirement evaluated: Automatic ingestion from our shared AP email inbox; no manual downloading or sorting

For a multi-location services company currently receiving invoices by email into a shared AP inbox, Spendesk provides capture through a vendor-hosted forwarding address (beginning with 'bills+...') assigned to each Spendesk entity. Suppliers can send invoices directly to this address, or the buyer can configure a one-time auto-forwarding rule at the email provider level so that all inbound messages to the existing shared AP inbox are automatically relayed to Spendesk, where each attachment is parsed by Spendesk's AI assistant ('Marvin') …

Limitations: Spendesk does not natively poll or monitor the buyer's existing shared mailbox via IMAP or OAuth; the mechanism requires the buyer to configure an auto-forward rule at their email provider (Gmail, Microsoft 365, etc.) …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For your 3-person AP team at a $120M services company, Spendesk's OCR tool 'Marvin' triggers automatically when an invoice is uploaded as a PDF, JPG, or PNG, or forwarded to your company's dedicated Spendesk inbox email address. <cite index="7-18,7-19,7-20">Suppliers and Spendesk users can forward invoices via email, and the feature allows invoices to be automatically created in Spendesk's shared inbox when forwarded to your company's dedicated invoice email address.</cite> Once received, <cite index="41-7,41-8">a draft invoice request is created with pre-filled information from Marvin, Spendesk's AI assistant.</cite> The fields Spendesk's help center explicitly documents as extracted are: s …

Limitations: Two fields in the buyer's required set, payment terms and line-item detail from standard PDF or scanned invoices, are not confirmed in Spendesk's documented OCR output for routine supplier invoice capture; users would need to manually enter payment terms (losing early-pay discount visibility) …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For your 6-location, 2-entity services company, Spendesk delivers spend analytics through its native Spend Trends dashboard, which your Controller or Account Owner can access directly from the homepage. The dashboard provides adjustable date ranges covering spend history by weeks or months, enabling month-over-month comparisons, and it surfaces a ranked 'Top 30 invoice suppliers' view alongside card, subscription, and expense supplier rankings. Spend by cost center is also available within the same dashboard. …

Limitations: The two material ceilings for your scenario are: (1) analytics are siloed per Spendesk subsidiary, so your 2 Sage Intacct entities would require separate dashboard views with no documented consolidated roll-up, forcing manual reconciliation across entities for any enterprise-wide trending; and (2) …

Requirement evaluated: Export to Excel and scheduled report delivery to Controller and CFO

For your 3-person AP team producing reports for the Controller and CFO, Spendesk provides on-demand CSV download from two main surfaces: the 'All Payables' tab (Bookkeep > All Payables), where users filter by payment status, period, payable type, or cost center and click 'Download selection' to export a CSV of all matching payable data that can be opened in Excel, and the Spend Trends and Control dashboards, which each have a download button that exports data in CSV or PDF format. Spendesk also provides a custom export template builder (Settings > Accounting Setup > Exports) …

Limitations: The absence of scheduled report delivery means your Controller and CFO will not receive automated AP reports in their inboxes; someone on the AP team must manually pull, filter, and distribute the CSV each reporting cycle, which partially defeats the oversight goal for executives who are not daily Spendesk users. …

Requirement evaluated: KPI tracking: average days to approve, touchless rate, cost per invoice, exception rate, discount capture rate

For your 3-person AP team processing 1,800 invoices monthly across 2 Sage Intacct entities, Spendesk offers two native reporting surfaces: a Spend Trends dashboard and a Control dashboard. The Spend Trends dashboard provides spend history by team and cost center, unused card budgets, and duplicate subscription detection. The Control dashboard covers wallet financial status, card restriction data, and rejected transactions. Invoice workflow status is visible per transaction ("To Approve / Approved / Rejected"), so AP controllers can see where a given invoice sits in the queue. …

Limitations: Days to approve, touchless rate, cost per invoice, exception rate, and discount capture rate are not documented as native, pre-built dashboard outputs in Spendesk's reporting layer; cost per invoice in particular requires labor cost inputs that Spendesk does not instrument, and discount capture rate requires capturing …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a 3-person AP team processing 1,800 invoices/month across 2 Sage Intacct entities, Spendesk's Spend Trends dashboard (accessible via Homepage > Dashboards > Spend Trends tab) provides named widgets for top-vendor analysis and time-period trending. The dashboard explicitly surfaces a 'Top 30 invoice suppliers' widget alongside spend history for 'past weeks or months' with an editable date range, and a spend-by-cost-center breakdown that spans multiple entities by default. …

Limitations: GL-account-level spend trending is not documented as a native analytics dashboard dimension; it is available through cost center and expense category filters and the bookkeeping export layer, which means this buyer would need to build GL-category views manually in a spreadsheet from exports rather than accessing them a …

Requirement evaluated: Real-time or near-real-time sync of: chart of accounts, dimensions, vendor master, PO data, and GL postings

Your team runs 1,800 invoices per month across 2 Sage Intacct entities and needs a live sync of chart of accounts, Intacct dimensions (location, department, project, custom), vendor master, PO data, and GL postings. Spendesk does not offer a native Sage Intacct connector at any tier. Its documented accounting integrations collection covers Sage 100 (on-premise and cloud SPC), NetSuite, Xero, DATEV, Pennylane, and ACD — Sage Intacct does not appear anywhere in Spendesk's help center. …

Limitations: There is no Spendesk-native mechanism — at any price point — to sync Sage Intacct's chart of accounts, dimensions, vendor master, PO balances, or GL postings in real time or near-real time. …

Requirement evaluated: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

Your team runs on Sage Intacct across two entities, and your requirement is a native, pre-built, bidirectional connector maintained by the AP vendor itself. Spendesk's documented native accounting integrations are NetSuite, Microsoft Business Central, Xero, QuickBooks Online, Odoo, Exact Online, DATEV, and Sage 100. Sage Intacct does not appear in that list. Spendesk's own accounts payable product page states that outside of its named native partners, the connection method is a file-based data export and upload, not a live bidirectional sync. …

Limitations: There is no Spendesk-to-Sage Intacct native connector available at any price point. Reaching Sage Intacct from Spendesk would require either a third-party iPaaS the buyer sources and maintains independently, or a custom API build, both of which conflict directly with the buyer's stated requirement.

Requirement evaluated: Real-time or near-real-time sync of: chart of accounts, dimensions, vendor master, PO data, and GL postings

This buyer runs 1,800 invoices per month across 2 Sage Intacct entities and needs real-time sync of chart of accounts, dimensions, vendor master, PO data, and GL postings between their AP automation layer and Sage Intacct. Spendesk's documented native ERP integrations cover Sage 100 (a separate French/European accounting product), NetSuite, Xero, and DATEV. A thorough search of Spendesk's help center and the Sage Intacct Marketplace returned no Spendesk connector for Sage Intacct; the product does not appear in the Sage Intacct partner ecosystem at all. …

Limitations: There is no Spendesk connector for Sage Intacct: not a native one, not a certified marketplace integration, and not a documented API-based path. This is a hard stop, not a depth or fidelity gap; the entire requirement is undeliverable with this vendor on this ERP.

Requirement evaluated: Custom field mapping between the AP platform and Intacct

This buyer runs 1,800 invoices per month across 2 Sage Intacct entities and needs custom field mapping between an AP platform and Intacct's dimensions, user-defined fields, and chart of accounts. Spendesk does not offer a native Sage Intacct integration. <cite index="38-1">Spendesk's help center integration index lists its native accounting connectors as NetSuite, Microsoft Business Central, Xero, DATEV, Sage 100 (on-premise and cloud SPC), and ACD.</cite> Sage Intacct does not appear. <cite index="10-1">Credit note functionality, for example, is explicitly scoped to "accounts using file-based accounting exports (single-entry, double-entry, SAGE or CEGID) …

Limitations: Spendesk has no native Sage Intacct connector at all; the buyer would be operating entirely on flat-file exports with no live dimension sync, no custom field mapping, and no loop-back posting to Intacct's AP module. This is a fundamental architectural mismatch for a Sage Intacct shop.

Requirement evaluated: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

For a $120M services company processing 1,800 invoices/month across two Sage Intacct entities, Spendesk's anomaly coverage operates in two documented places. First, <cite index="1-1,1-7,1-8">the 'Anomaly and Fraud Detection' feature in the Bookkeep > Prepare section uses AI to check every submitted receipt against its attached payable, verifying that the supplier name, date, and amount on the receipt align with the payable record.</cite> Second, <cite index="27-2,27-6,27-7">duplicate invoices are flagged in the Inbox: when an invoice is identified as a duplicate, a 'duplicate' flag appears in the right side of the screen.</cite> On the vendor master side, <cite index="21-1,21-12">Account Own …

Limitations: The three anomaly scenarios in the buyer's requirement map only partially to what is documented: duplicate detection is confirmed, but vendor behavioral baselines (amount spikes vs. historical averages) …

Requirement evaluated: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

For a $120M multi-location services company running 1,800 invoices per month, the buyer needs AI that watches supplier invoice data for behavioral red flags: amount spikes relative to a vendor's history, newly introduced bank account details, and unusual vendor patterns. Spendesk does have a documented 'Anomaly and Fraud Detection' feature, but its scope is narrower than this requirement. According to the Spendesk Help Center, the feature 'automatically checks all receipts that are submitted and uses AI to automate receipt verification for accountants,' confirming that a receipt's supplier name, date, and amount align with the attached payable. …

Limitations: The documented anomaly detection operates at the receipt-to-payable matching level (supplier name, date, and amount match) and the card-transaction monitoring layer; the buyer's three specific signals, namely invoice amount spikes versus a vendor's historical baseline, new bank account numbers appearing on a supplier i …

Requirement evaluated: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

For a 3-person AP team processing 1,800 invoices/month across two Sage Intacct entities, Spendesk provides three overlapping but narrow fraud controls. First, its documented 'Anomaly and Fraud Detection' feature uses an AI model to verify that every submitted receipt matches its payable on supplier name, date, and amount in the Bookkeep > Prepare section; when a receipt fails, the payable is flagged for controller review before it moves to bookkeeping. Second, <cite index='24-4'>the AI detects duplicates</cite> at the invoice stage, catching same-vendor/same-amount resubmissions. …

Limitations: The buyer's three specific sub-requirements — invoice amount spike detection, new bank account proactive alerting, and unusual vendor behavioral monitoring — are only partially addressed: duplicate detection and receipt-to-payable verification cover document-level consistency checks, and the bank info change history is …

Requirement evaluated: Complete audit trail: every action timestamped with user ID, viewable by invoice or by user

For a $120M multi-location services company replacing email-based AP with structured workflows, Spendesk offers audit trail capabilities that differ in depth depending on which module processes the invoice. In the Procurement module, a per-request audit trail is explicitly documented: every field value change, task status update, and assignee change is logged and accessible directly from the request page via a three-dot menu, meaning a controller can open any procurement request and see a chronological change history. For the supplier invoice (AP) …

Limitations: The per-invoice audit trail at field-edit granularity is explicitly documented only for Procurement requests, not for the standalone AP supplier invoice flow; for this buyer's 1,800 invoice/month AP process, it is unclear whether every field-level edit on an invoice carries the same before/after log depth. …

Requirement evaluated: Non-PO invoice routing: automatic GL coding suggestions based on vendor history and invoice description

For a 3-person AP team processing 810 non-PO invoices per month, Spendesk addresses GL coding suggestions through two overlapping mechanisms that activate in its Bookkeep > Prepare stage (pre-ERP-export, after invoice approval). First, AutoCat provides rules-based coding: <cite index="5-16">the supplier rule links a supplier to a specific expense account so that each time a payable is created with that supplier, the expense account is pre-filled</cite>, and <cite index="5-20">the expense category rule links an expense category to a specific expense account so that each time a payable is created with that expense category, the expense account is pre-filled.</cite> Beyond simple supplier-to-GL …

Limitations: Without a documented native Sage Intacct integration, Spendesk cannot pull the buyer's Intacct dimension set dynamically for coding suggestions -- the AP team would need to manually mirror Intacct's chart of accounts and custom dimensions inside Spendesk, and GL data flows to Intacct via flat-file export rather than a …

Requirement evaluated: Automated three-way matching: invoice to PO to goods receipt, with configurable tolerance (2% price, 5% quantity)

For a $120M multi-location services company with 55% PO-based invoices covering facilities, supplies, and subcontractors, Spendesk provides three-way matching through its Supplier Invoices module. During the Review stage, <cite index="5-1,5-16">details from purchase orders, delivery notes, and invoices are automatically compared, matched, and pre-filled.</cite> <cite index="11-5,11-6">Spendesk's AP automation links each invoice to its corresponding purchase order and delivery notes, runs three-way matching automatically, and routes an immediate alert to the relevant controller if a discrepancy is found.</cite> The goods receipt leg is handled through Spendesk's delivery notes feature: <cite …

Limitations: The buyer's specific requirement for two separately configurable tolerance bands (2% price, 5% quantity) is not documented as a supported configuration in Spendesk's help center or product pages; the platform references tolerance thresholds in general terms without evidence of per-dimension percentage controls. …

Requirement evaluated: Exception dashboard showing all unmatched/flagged items with aging and priority indicators

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, Spendesk surfaces invoice problems through several distinct mechanisms rather than a single dedicated exception dashboard. Duplicate invoices are automatically detected and flagged in the shared Inbox, where controllers can see the duplicate flag on the offending item. When an employee cannot match or reconcile an assigned invoice, they can return it to finance, and it then appears with a 'disputed' status in the controllers' inbox. At the PO level, billing status is tracked as 'Partially billed,' 'Billed,' or 'Overbilled,' so over-invoicing against an approved PO is visible. …

Limitations: The buyer specifically needs aging indicators (how many days an invoice has been stuck in an exception state) and priority signals (urgency based on due date, amount, or vendor terms): neither is documented as a feature of Spendesk's inbox or Review queue. …

Requirement evaluated: Exception dashboard showing all unmatched/flagged items with aging and priority indicators

For a 3-person AP team processing 1,800 invoices monthly across a multi-location services business, Spendesk provides a controller-facing 'Invoices > Review' queue where flagged and approved invoices surface for human attention. <cite index="23-1,23-2,23-3">Only Controllers and Account Owners can access this view: they navigate to the Invoices tab, click the 'Review' sub-tab, and see a list of invoices awaiting their attention.</cite> On the matching side, <cite index="1-4,1-5,1-6">Spendesk's AP automation links each invoice to its corresponding purchase order and delivery notes and runs three-way matching automatically; if there is a discrepancy, the relevant controller receives an immediat …

Limitations: The buyer's core ask — a persistent, purpose-built exception dashboard showing unmatched and flagged items with aging and priority indicators — is not evidenced in Spendesk's documented product. …

Requirement evaluated: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

For a 3-person AP team at a multi-location services company, Spendesk structures invoice processing across three distinct role types: Requesters submit invoices, Approvers review and approve them, and Controllers review validated invoices and schedule payment. The invoice lifecycle documentation confirms this staged handoff: 'Once your invoices are submitted (by Requesters) and approved (by Approvers), Controllers can review them before paying them,' with only Controllers and Account Owners permitted to access the payment step. …

Limitations: For this buyer's audit and control purposes, the most material gap is that role assignments are additive and not mutually exclusive: an administrator can give any Controller the Requester role, collapsing the entry-to-payment separation that formal SOD requires, and the Account Owner superuser bypasses all three lifecy …

Requirement evaluated: Mobile approval with full invoice image view; approvers must be able to act from their phone in under 30 seconds

For a 3-person AP team processing 1,800 invoices per month across 6 locations, Spendesk does offer a native iOS and Android mobile app where approvers can act on pending requests. <cite index="11-6,11-9,11-10,11-11">Account owners and team approvers can approve requests directly from the Spendesk mobile app on the go: pending requests appear under a 'To Approve' tab on the home screen, and tapping a request surfaces details and approve/reject buttons.</cite> <cite index="18-2">Spendesk also supports multi-level approval workflows with mobile and web approvals and customizable approval thresholds.</cite> However, two structural shortfalls prevent this from meeting the buyer's sub-30-second st …

Limitations: The notification channel for supplier invoices is a weekly Monday email digest to controllers, not an immediate push notification with deep-link to the invoice, which structurally prevents the sub-30-second action the buyer requires. …