Concur vs Vic.ai vs Spendesk for AP Automation

For a 3-person AP team processing 1,800 invoices per month across bi-weekly check runs and monthly ACH batches, SAP Concur handles automatic remittance through its Invoice Pay managed payment service. When the administrator enables the 'Send vendor payment email notifications for Check and ACH Concur Invoice Pay types' checkbox in Invoice Settings, vendors automatically receive an email when paid via ACH or check through Invoice Pay, containing full remittance information including when, how, and for what they are paid, covering both partial and full payments. The email contains the invoice date, invoice amount, invoice number, payment date, payment method, and any notes on the payment submission; for check payments, the check number is also included. For virtual card payments, upon a batch's closure and virtual card creation, vendors automatically receive remittance emails sent by Concur Invoice, which are critical to informing vendors about payment status and the date their virtual card was processed. The vendor contact email address must be populated in the vendor record to enable delivery; if the Contact Email field is empty, invoices are transferred to the Invoices Requiring Action queue and require manual handling. This capability sits at the payment execution stage of the pre-processing journey and is post-approval, not part of invoice capture or matching.

This $120M services company currently pays via ERP-native check and ACH runs with no outbound remittance communication; Vic.ai addresses this requirement through two connected mechanisms inside VicPay, its native payment module. First, the Vic.ai help center documents that the email address of the account used to onboard to VicPay will receive a copy of all remittances automatically; the remittance contains a detailed table of invoices and vendor credits in the first section, and a summary of remittance details on a second page. Second, the Vendor Portal layer adds proactive push notifications: automated notifications alert vendors when invoices are received, approved, or paid, with no emails or calls required from AP staff. For virtual card payments specifically, the vendor will receive a remittance containing card details one banking day after the payment is approved, so the vendor can then process the payment on their card terminal. The full mechanism requires vendor portal onboarding: vendors enter their remittance address preferences during setup, and once onboarded, they receive ongoing access to invoice and payment history with no additional outreach needed. This capability sits outside the pre-processing journey entirely; it is a post-approval, post-execution output triggered by VicPay payment batch completion, not by ERP GL posting. The critical dependency is that payment execution must flow through VicPay rather than Sage Intacct directly: bills paid outside of VicPay can be manually marked as paid in Vic.ai, but this path is for tracking only and does not trigger automatic remittance delivery to vendors.

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. To obtain a proof of payment for your supplier, the payment must have been done from the Spendesk wallet; the documented steps are: go to Invoices > History, check the batch from the date of payment, click on the paid invoice, click 'Get PDF proof of payment,' download the PDF file, and send it to the supplier. This is a reporting and retrieval feature, not an automated outbound push, and it directly replicates the buyer's current manual process. Compounding this, Spendesk does not provide notifications for when a request is reimbursed or paid; internal payment status is only visible by logging into the platform and checking the Payments tab. No trigger, no template, and no automated email push to external vendors upon payment execution is documented anywhere in Spendesk's help center.

For a $120M services company running 2 Sage Intacct entities and 1,800 invoices per month, Vic.ai operates as a certified Sage Intacct Marketplace integration that pulls master data continuously into the AP layer before any invoice is touched. The integration automatically syncs vendors, general ledger accounts, and dimensions from the organization's Sage Intacct account, giving the AI a live reference set to code against at the moment of invoice ingestion. On the PO side, once extracted, the AI reviews and classifies invoice data and matches all relevant invoice information, including vendor, dates, numbers, cost accounts, dimensions, assets, and purchase orders sourced from Sage Intacct. For the GL write-back, after approval, the invoice along with all the associated coding is pushed into Sage Intacct for payment, completing the loop back to both ERP entities. The integration is positioned for multi-entity Sage Intacct environments: Vic.ai unlocks always-on performance insights across invoice workflows, team productivity, and business entities, consistent with a 2-entity deployment. The primary gap in public documentation is the exact sync polling interval; the Marketplace language confirms automatic synchronization but does not specify whether it is event-driven, continuous API polling, or a short scheduled interval. Based on how Sage Intacct Marketplace-certified connectors operate using Sage Intacct Web Services, near-real-time or frequent scheduled polling is the standard mechanism, but the buyer should confirm the exact cadence (e.g., every 15 minutes vs. hourly) during vendor discovery.

This $120M, 2-entity Sage Intacct organization needs bidirectional, near-real-time sync covering all five data objects: chart of accounts, dimensions, vendor master, PO data, and GL postings. SAP Concur's native Financial Integration connector, available for Concur Invoice and Expense Professional editions, delivers confirmed near-real-time sync for four of those five objects. The Sage Intacct Marketplace listing documents that 'SAP Concur automatically collects all Account Codes, dimension lists, and vendors directly from Sage Intacct' and that bills post back to Sage Intacct's AP Module in near real-time, with no manual extract downloads required. A February 2025 SAP Concur community announcement confirmed expansion of this integration to Professional editions, adding 'automatic syncing of master accounting data, such as accounts, users, vendors, and cost objects.' The integration is bidirectional: Intacct master data flows into Concur for coding, and approved invoices write back as AP bills to Intacct automatically after processor approval, with feedback on posting success or failure visible in the audit trail. Multi-entity sync is supported up to 10 entities, which accommodates this buyer's 2-entity configuration. However, no official SAP Concur or Sage Intacct source confirms that PO data (open POs, PO line items, receipt status) is pulled from Sage Intacct into Concur in near real-time for invoice-to-PO matching, which is the critical gap for the buyer's 55% PO-based invoice volume. An implementation partner (RSM) also noted that the invoice payment write-back to Intacct was not fully part of the native integration at time of documentation, though this is a separate payment loop-back concern.

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. Spendesk's integration library, as documented in its help center, covers Sage 100, DATEV, Xero, NetSuite, and ACD as its named native accounting integrations, with no Sage Intacct connector present. Spendesk markets an 'API and integrations' capability to 'link all of your existing accounting and business tools,' but no Sage Intacct mechanism is documented anywhere in the product. Without a connector, none of the five data objects the buyer requires (chart of accounts, dimensions, vendor master, PO data, GL postings) can sync; the buyer would be stranded on manual export workflows.

For a multi-location services company whose approvers are often in the field or across six office locations, Vic.ai delivers mobile approval through a purpose-built native app available for both iOS and Android. Once an invoice clears AP staff review (pre-processing stage 5: cost allocation and coding), the system fires a per-invoice push notification directly to the assigned approver's phone when it is their turn in the workflow. Inside the app, the approver taps 'Approvals' to see a queue showing vendor, amount, due date, GL account, and applicable dimensions; then taps 'View' to render the full invoice PDF inline alongside editable dimension fields, and approves or rejects from that same screen. Out-of-office redirection to an alternate approver is built into the mobile app, so the 30-second window is not silently bypassed when the primary approver is unavailable. Vic.ai also reports customers achieving approvals up to 88% faster after adoption. The inline document viewer article in the help center describes keyboard shortcuts and external monitor options that are desktop-only features, but the mobile approval flow has its own dedicated help section confirming PDF view and action capability within the app itself.

For a 3-person AP team at a multi-location services company routing invoices to managers on mobile, SAP Concur provides a native iOS and Android app (the SAP Concur mobile app) through which approvers can review pending invoices. The app allows approvers to open Concur Invoice from any location; at a glance they see a summary, an image of the invoice, and line-item details, and with one click the invoice can be approved or sent back with a comment. The desktop-side workflow is well-documented: the approver navigates to the Approvals interface as a starting point, then selects Approvals > Invoices to reach their pending queue. However, the path to that one-click action on mobile is gated by two friction points that work against the buyer's 30-second requirement. First, Two-Factor Authentication was introduced by SAP Concur in 2023, requiring approvers to authenticate via an authenticator app on sign-in, adding steps before the invoice is reachable unless a persistent session is already open. Second, and more critically for the notification-to-action speed test, push notifications on the mobile app have not yet been developed for the Invoice solution; for Expense they work, but not for Invoice. The primary notification mechanism for invoice approvals is email: after submission the approving manager receives a notification email; if they do not act, they receive a reminder after three calendar days, then daily reminders. That email links back to the web session rather than deep-linking into the native app's approval screen, meaning the approver must open the app independently, authenticate, and navigate to the invoice queue before acting. The capability to view the invoice image and tap approve is real, but the trigger mechanism (email notification, no push deep-link to invoice) and the 2FA re-authentication layer make sub-30-second completion unreliable as a design guarantee rather than a best-case outcome.

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. 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. Spendesk also supports multi-level approval workflows with mobile and web approvals and customizable approval thresholds. However, two structural shortfalls prevent this from meeting the buyer's sub-30-second standard for AP invoice approvals specifically. First, the notification path for supplier invoices is email-based, not immediate push: supplier invoice submission and purchase order requests are sent by email, and controllers receive only a Monday recap of invoices to approve. A weekly digest email does not give approvers the immediate, tap-to-open-and-act path the 30-second requirement demands. Second, the formal invoice review step sits in a desktop-centric controller queue: only controllers and account owners can review invoices, navigating to the Invoices tab and the Review sub-tab to check invoice information. No help center article documents this controller review step as available or optimized on mobile. The mobile app's approval capability is well-documented for card spend and expense claims, but supplier invoice approval on mobile lacks immediate push notification and a confirmed full invoice image rendering path.