Quadient AP vs Concur vs AppZen for AP Automation

For a $120M multi-location services company running 2 Sage Intacct entities and 1,800 invoices per month, Quadient AP (powered by Beanworks) connects to Sage Intacct via API and uses its SmartSync feature to pull list items from Intacct into the AP platform, making them available for GL coding during the pre-processing journey (cost-allocation stage 5). The official connection guide documents that setup involves configuring a Web Services User in Intacct, authorizing API access, and running an initial SmartSync that pulls all list items from Sage Intacct into Beanworks; with scheduled or on-demand syncs thereafter to keep data current. The connection guide also documents a specific custom field step: a 'Beanworks' field is created in Intacct's Platform Services to create a back-link from each posted Intacct bill to its corresponding Quadient AP invoice, confirming the integration uses Intacct's Platform Services/custom fields layer. Quadient's marketing for the Sage Intacct integration states that once connected, users can 'customize it to your specifications,' and that the integration syncs vendors, accounts, departments, and other fields so data flows correctly between systems. However, the publicly available help documentation does not explicitly enumerate which Intacct custom dimensions or user-defined GL dimensions (beyond standard fields) are carried through the sync, and no documented field list or mapping UI is published that confirms the full breadth of Intacct custom segment support.

For a $120M multi-location services company on Sage Intacct with 2 ERP entities, SAP Concur offers a native 'Sage Intacct Integration' available through its App Center, expanded to cover Concur Invoice Professional edition as of February 2025. The connector operates as a bidirectional sync: it pulls GL accounts, vendor records, and Intacct dimensions (departments, locations, projects, cost centers) into Concur so invoices can be coded against those values during pre-processing, then posts approved invoices back to Intacct as vendor bills in near-real-time without requiring manual file exports. Standard Intacct dimensions are documented as selectable and mappable within Concur. However, community evidence reveals that multi-level or hierarchical custom fields encounter a hard limit in the current connector UI: users report that when configuring multi-level custom fields, the mapping interface constrains the top slot to the 'Entity' field only, blocking dependent custom dimension mapping (e.g., Project filtered by Department). A separate SAP help article titled 'Sage Intacct Custom Field Import for Cost Type' confirms that some custom field import functionality exists, but the scope is narrow and use-case-specific. The integration's underlying architecture includes a Financial Integration Service (FIS) API layer and a Standard Accounting Extract, which can theoretically carry additional field data, but doing so for arbitrary user-defined Intacct dimensions requires either connector-level configuration that is not fully self-service or engagement of a separate third-party connector (e.g., Wipfli InvoiceConnect, listed in the Sage Intacct Marketplace) to extend field coverage beyond what the native connector exposes.

For a $120M services company running 2 Sage Intacct entities and needing custom field mapping between an AP platform and Intacct, the critical question is whether AppZen has a documented Sage Intacct connector at all. AppZen's AP automation product markets pre-built integrations with over 100 ERP providers and specifically names SAP, Oracle Fusion, NetSuite, Microsoft, Workday, Coupa, and JD Edwards as integration targets. No AppZen-authored page, help article, or partner listing for Sage Intacct was found across three targeted searches, and AppZen does not appear in the Sage Intacct Marketplace. Without a confirmed Sage Intacct connector, the question of whether that connector carries custom Intacct dimensions and user-defined fields cannot be answered.

For a $120M multi-location services company with bi-weekly check runs and monthly ACH batches, Quadient AP's Payments module addresses this requirement through a dedicated payment-level Approval Channel that is separate from the invoice approval workflow. The Payments module allows approving invoice payments based on the approval matrix setup before export to the accounting system. The CFO or Controller is configured as a named required approver within that channel: payment Approval Channels can be based on dollar amount, Org Units, or a combination of both, and only System Administrators can create or edit those channels. Once a payment batch is assembled, it cannot be released until every required approver has acted: each approver's action is recorded in the payment's Approval History, and if multiple approvers are in the workflow, the payment stays in Pending Approval status showing who is still required to approve. The Quadient payments page explicitly frames this as a gate: once payments have completed the approval process they can be released, and the company retains control over which payments are exported to the accounting software and when. The product also uses the phrase 'signing authorities' to describe this role: automated payment batches are submitted to signing authorities for approval in seconds. Approval delegation is also documented so the CFO or Controller can reassign authority during absences without disrupting the batch release control: Approval Channel Delegation allows transfer of approval authority to another colleague, either temporarily to cover a vacation or leave, or permanently.

For a multi-location services company running bi-weekly check and monthly ACH batches through Sage Intacct, Concur Invoice Pay provides a dedicated batch release gate that directly addresses the CFO/Controller sign-off requirement. Within the Invoice Payment Manager module, administrators enable the 'Require Batches to be Released' checkbox in the check configuration and ACH funding account settings. Once enabled, every closed payment batch enters a 'Pending Release' status and is held from transmission to the payment provider until a user holding the 'Payment Release Manager' role takes explicit action. As SAP's Invoice Pay training documentation states, batches with this status 'must be manually released for payment by a user assigned to the Payment Release Manager role' and are released 'by selecting Release Payment from the Actions button.' The CFO or Controller is assigned the Payment Release Manager role, creating a hard electronic gate: no check run or ACH batch reaches the bank until that named individual acts. This separates payment creation (handled by AP staff with the Invoice Payment Manager role) from payment authorization (restricted to the Payment Release Manager), enforcing segregation of duties at the batch execution stage.

For a $120M multi-location services company requiring CFO or Controller electronic sign-off before any payment batch is released, AppZen does not provide this control at the payment execution stage. AppZen's documented scope covers invoice capture, AI-powered GL coding, PO matching, and invoice-level approval routing. Its own published documentation states that 'any further approvals and GL posting happen within your P2P and ERP systems,' explicitly placing payment-stage authorization outside AppZen's native perimeter. The platform's configurable Low-Code Workflow builder and Smart Routing can enforce role-based approval chains on individual invoices before they are posted, but no evidence exists of a native payment batch queue, a payment run hold/release control, or a mandatory designated-role gate (CFO or Controller) that blocks payment execution until electronic authorization is received. Payment batch release controls for the buyer's bi-weekly check runs and monthly ACH batches would need to be configured within Sage Intacct itself, not within AppZen.

For a multi-location services company evaluating AP automation vendors against a security compliance baseline, SAP Concur holds a completed, issued SOC 2 Type II report covering the audit period April 1, 2024 through March 31, 2025, prepared by an independent third-party accountant. The report is published on SAP's public Trust Center and covers the trust principles Security, Availability, and Confidentiality under AT-C Section 205 and ISAE 3000 standards. Critically for this buyer's use case, the audit scope explicitly includes the Invoice module: 'Concur Standard/Professional/Premium Editions, including Travel, Expense, and Invoice' are named in-scope solutions. The report is not in-progress; it is a completed Type II attestation with operating effectiveness tested over a full 12-month period. SAP also publishes quarterly bridge letters to cover the gap between the end date of the most recent report and the current date, and a Remediation Update document addressing any auditor findings. The report is available to customers and prospects under a non-disclosure agreement via the SAP Trust Center or the SAP for Me customer portal.

For a $120M services company running Sage Intacct and evaluating AP automation vendors on security posture, AppZen's published Compliance and Security Guide confirms that the platform undergoes SOC 1 Type 2 and SOC 2 Type 2 assessments conducted by a Certified Public Accountant designated by the AICPA, and that AppZen has maintained SOC compliance continuously since 2017. The same guide documents annual ISO/IEC 27001 certification audits, indicating an active, recurring third-party audit program rather than a one-time point-in-time assessment. The SOC 2 Type 2 report is not publicly downloadable, which is standard practice: buyers typically request it through AppZen's sales or security team, often under NDA, as part of vendor due diligence.

For a $120M multi-location services company evaluating AP automation vendors against a security compliance requirement, the relevant question is whether Quadient AP holds a completed, independently audited SOC 2 Type II report, not just a generic SOC 2 reference. Quadient's Digital Trust Center, which explicitly lists Quadient AP (by Beanworks) as a covered product, states that Quadient Digital complies with certifications and frameworks including 'ISO27001:2022, ISO9001:2015, HITRUST, PCI DSS, SOC 2, NIST, GDPR, HIPAA, or CCPA,' and that compliance levels are 'regularly reviewed by internal auditors and independent external auditors.' However, every retrieved page from quadient.com lists 'SOC 2' without specifying Type I or Type II, and no audit period, issuing CPA firm, or report availability statement was found across three targeted searches of the vendor's public documentation.