How MineralTree works

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a multi-location services company processing recurring rent, utility, and subscription invoices that legitimately reuse invoice numbers month over month, MineralTree's duplicate detection operates as a global, company-wide control. The platform's support documentation confirms that MineralTree will not allow invoices with duplicate numbers to be created in the front end and also offers a 'duplicate detection' feature that highlights duplicate bills and emails Accounting Manager users when such duplicates occur. The matching logic checks invoice number and vendor name at the point of invoice creation. …

Limitations: No documentation in MineralTree's help center or product pages describes a per-vendor duplicate detection toggle, a vendor-level time-window threshold, a 'recurring billing' flag, or a whitelist that would exempt specific vendors such as your rent or utility payees from the global duplicate number check. …

Requirement evaluated: Clear exception categories: price variance, quantity variance, missing PO, missing receipt, duplicate, vendor mismatch

For a $120M multi-location services company running 1,800 invoices per month across two Sage Intacct entities, MineralTree's TotalAP platform operates at stages 2 and 4 of the pre-processing journey: PO matching and receipt confirmation. On the PO-based 55% of your invoice volume, <cite index="7-2,7-3">MineralTree's automated PO matching runs on every draft invoice, attempting to link each invoice line to a PO line from your ERP.</cite> <cite index="7-28,7-29">When comparing Cost Per on items or Total Amount on expenses, the system can require an exact match or allow up to a 10% variance; lines outside that tolerance are marked "Mismatch" and flagged for Accounting Manager review.</cite> <ci …

Limitations: The tolerance band is capped at 10% globally and cannot be set per vendor, per line category, or above 10% (lines with greater than 10% variance do not link at all), which limits precision for your subcontractor and facilities spend where contract-specific tolerances may differ. …

Requirement evaluated: Clear exception categories: price variance, quantity variance, missing PO, missing receipt, duplicate, vendor mismatch

For your 1,800-invoice operation spanning both PO-based and non-PO workflows, MineralTree surfaces exceptions at the pre-posting stage through its automated PO matching engine and duplicate detection feature. Price variance and quantity variance are covered through configurable match tolerances: <cite index="8-37,8-38">when comparing cost-per on items or total amount on expenses, administrators can require an exact match or allow up to a 10% variance; lines outside the allowed tolerance are marked as 'Mismatch,' requiring further scrutiny by an Accounting Manager.</cite> The system also supports receipt-based quantity matching: <cite index="8-40,8-41">a setting determines whether invoice qua …

Limitations: Three material gaps against your stated requirement: first, 'missing receipt' is not a distinct named exception category routed to a receiving team; it resolves as a quantity mismatch only if the ERP receipt record pre-exists before the invoice arrives, and there is no documented exception worklist that pushes the flag …

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

For a three-person AP team at your scale processing 1,800 invoices per month across two Sage Intacct entities, MineralTree provides several documented exception-signaling mechanisms, but they do not fully converge into a dedicated exception dashboard with aging and priority indicators as an organizing surface. At the invoice level, the PO Matching module highlights mismatched fields in red and surfaces an alert icon that users can click to learn why a mismatch occurred; a green check icon confirms clean line-level matches. …

Limitations: MineralTree's exception signals are distributed across individual invoice records and the general invoices list rather than consolidated into a dedicated exception dashboard with aging tiers and priority scoring. …

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

For your 2-entity Sage Intacct setup, MineralTree TotalAP connects via direct API-level integration. The Sage Intacct Marketplace listing confirms a bidirectional sync that carries 'vendors, bill details, coding fields and lists, payment/posting status and credits' between the two systems. At the invoice line (expense) level, MineralTree's own Intacct Integration Guide enumerates the specific fields that flow across: GL Account, Amount, Location, Class, Department, Item, Project, Employee, Customer, Form 1099, and Description. These seven coding dimensions (plus vendor as the eighth) cover the standard Intacct dimension set your AP team would code against during invoice processing. …

Limitations: If your Intacct environment uses renamed standard dimensions or has true user-defined dimensions (UDDs) beyond the seven standard ones, MineralTree's Intacct integration has no documented path to surface those labels or fields in its coding UI, which would require your AP team to map against generic or unlabeled field …

Requirement evaluated: Multi-entity support within the integration; we operate 2 entities in Intacct and plan to add a third

For a 3-person centralized AP team running 2 Intacct entities today with a third planned, MineralTree TotalAP offers a documented, production-tested multi-entity integration path via its direct API connection to Sage Intacct. At setup, the team chooses between two sync architectures: top-level sync (all entities are processed inside a single MineralTree environment, with invoices tagged to an entity using the Location field at the line level and intercompany transactions created automatically in Intacct) or entity-level sync (each Intacct entity maps to its own separate MineralTree company). …

Limitations: The sync architecture choice (top-level vs. entity-level) is locked at implementation and cannot be changed after go-live, so the buyer must select the top-level configuration from day one to preserve a unified AP queue across all three entities; selecting entity-level sync would create separate MineralTree company log …

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

For a $120M multi-location services company running 2 Sage Intacct entities and processing 1,800 invoices per month, MineralTree delivers a direct, API-level integration with Sage Intacct through its TotalAP product, with no middleware layer required. The connection is established directly via Sage Intacct Web Services: MineralTree pulls all objects from Intacct (bills, vendors, accounts, dimensions, credits) and posts approved invoices and payment data back to Intacct at the entity level, keeping both systems continuously in sync. …

Limitations: Payment voids executed in Intacct do not automatically sync to MineralTree and must be manually voided in both systems. Vendor credit application must also be completed in Intacct rather than in MineralTree, adding a small manual step for credit workflows. …

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

For your 2-entity Sage Intacct environment, MineralTree TotalAP connects via a direct, API-level integration using Intacct Web Service credentials, not a flat-file export. At the initial sync, all five object classes your team needs are pulled from Intacct into MineralTree: GL accounts (chart of accounts), named dimensions including Location, Department, Class, Project, and Employee at the expense-line level, the active vendor master (including 1099 designation), open purchase orders, and open bills. On an ongoing basis, the Intacct Integration Guide confirms that 'all objects (bills, vendors, accounts, dimensions, credits, etc) …

Limitations: The multi-entity sync architecture (top-level vs. entity-level) is a one-time configuration decision that cannot be changed after the initial sync, so your team must choose correctly upfront whether to run centralized or entity-segregated AP workflows. …

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

For a 3-person AP team at a $120M multi-location services company currently flying blind with no reporting whatsoever, MineralTree delivers a meaningful analytics layer via its MineralTree Analytics module, available to Invoice-to-Pay users. The module consolidates data from the invoice-to-pay workflow into real-time interactive dashboards covering vendors, purchase orders, invoices, and payments, with documented KPIs including invoice aging, discounts captured, rebates earned, and payment mix. The support center also lists invoice processing time and cost per invoice processed as KPIs tracked within the platform's AP metrics dashboard. …

Limitations: Three of the five KPIs the buyer requires (average days to approve, touchless rate, exception rate) are not confirmed in any MineralTree Analytics specification or help-center article; the documented dashboard metrics skew toward payment mix, invoice aging, rebates, and discount capture, meaning the buyer may need to d …

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

For a $120M multi-location services company running Sage Intacct, MineralTree's TotalAP platform includes MineralTree Analytics, a named analytics module bundled with the invoice-to-pay package. The support center lists 'Analytics Reporting' as a distinct capability, and the retail solutions page confirms that 'TotalAP from MineralTree includes MineralTree Analytics, giving you a single AP dashboard to easily see and manage what's happening at specific stores or across multiple locations and entities' (MineralTree Retail page). The documented dashboard metrics cover payment-centric KPIs: early pay discounts captured, rebates earned, payment mix, and invoice aging. …

Limitations: Four of the five buyer-required KPIs (average days to approve, touchless rate, cost per invoice, exception rate) have no documented evidence of being pre-built, labeled outputs in the MineralTree Analytics dashboard; the buyer would need to derive them from CSV exports or build custom views, which is a meaningful burde …

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For a 3-person AP team at a $120M services company processing 1,800 invoices/month across two Sage Intacct entities, MineralTree provides two adjacent mechanisms that partially address approval bottleneck visibility. First, the Invoice Details page includes an Approvals tab that shows all approvers assigned to a specific invoice and their current status, which the help documentation states 'makes it easier to understand approval routing and identify delays.' This is per-invoice inspection, not an aggregate view. …

Limitations: MineralTree's documented Analytics module tracks invoice aging, payment mix, and spend metrics but does not include a purpose-built approver-performance report showing cycle time by individual approver or average approval duration segmented by invoice type. A third-party review aggregator (research.com, April 2026) …

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

For your 3-person AP team running 1,800 invoices/month across two Sage Intacct entities, MineralTree provides on-demand CSV export from its Search page, covering invoices, payments, vendors, and documents. An Accounting Manager logs into the Search tab, applies filters using the Advanced Search function, and clicks 'Download Report' to generate a CSV file that opens directly in Excel; the export covers data categories including invoices, payments, and vendor records, with a documented cap of 10,000 records per export. …

Limitations: The scheduled push delivery half of the buyer's requirement (automated email of Excel/CSV reports to the Controller and CFO on a defined cadence) has no documented mechanism in MineralTree's help center or product documentation; the only supported path is on-demand, login-required export. …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For your 2-entity Sage Intacct environment, MineralTree holds a current SOC 2 Type II attestation, completed by an independent third-party auditor against AICPA's five Trust Service Criteria: Security, Availability, Processing Integrity, Confidentiality, and Privacy. <cite index="22-1">MineralTree's TotalAP product page states that "security policies and platform are regularly audited to ensure compliance with some of the strictest standards, including Sarbanes-Oxley (SOX), SOC 1 Type 2, SOC 2 Type 2, and SOC2+/HIPAA."</cite> Post-acquisition, the parent company GTreasury has codified this commitment contractually: <cite index="10-1,10-2,10-3">GTreasury's Security Addendum commits to causing …

Limitations: The SOC 2 Type II report is not publicly downloadable; your team will need to formally request it during vendor evaluation or contracting, at which point you will be required to sign a confidentiality agreement before receiving the report. …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M multi-location services company with AP data flowing through Sage Intacct, this requirement asks whether MineralTree holds a completed, third-party-audited SOC 2 Type II report covering its application environment. MineralTree's own published content confirms it does: <cite index="10-3,10-4">MineralTree implements security at the platform level and states that its security policies and platform are regularly audited to ensure compliance with SOC 1 Type 2, SOC 2 Type 2, and SOC2+/HIPAA, among other standards.</cite> This is corroborated by the Sage Intacct Marketplace listing, which notes <cite index="12-8">two-factor authentication, payment limits, and the production of Positive …

Limitations: MineralTree does not publish the current report's specific audit period, coverage dates, or auditor name on its public pages. The buyer should request the full SOC 2 Type II report under NDA and confirm: (1) the report issuance date is within the last 12 months, (2) …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M multi-location services company evaluating a payment processing vendor against a security baseline, MineralTree publicly documents SOC 2 Type II compliance on its own AP compliance page. <cite index="12-7,12-8,12-9,12-10">MineralTree's Type 2 report is completed every six months; the SOC 2 standard sets requirements for organizations that store and transmit customer data, and a third-party auditor verifies that MineralTree's security controls meet AICPA's five trust service principles for managing and protecting customer data.</cite> <cite index="12-20">For its TotalAP solution, MineralTree performs regular audits to maintain SOC 1 Type 2, SOC 2 Type 2, SOC2+, and PCI DSS Level 1 …

Limitations: MineralTree does not publish a publicly accessible trust page with explicit audit period start/end dates, so the buyer cannot self-serve confirm the most recent report date without contacting the vendor. …

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 with an AP team of 3 handling 1,800 invoices per month, MineralTree addresses invoice fraud risk through a set of documented process controls rather than a purpose-built AI anomaly detection engine. The product page enumerates the specific security mechanisms in the platform: <cite index="7-1">role-based access, dual approvals, duplicate detection, invoice flags, two-factor authentication, and Positive Pay help reduce the risk of fraud.</cite> On the bank account change risk specifically, <cite index="18-6,18-7,18-8">a Notification of Change (NOC) …

Limitations: The documented fraud controls (duplicate detection, invoice flags, dual approvals, Positive Pay, 2FA, and NOC-based bank account change alerts) address meaningful fraud vectors but fall short of the buyer's requirement for AI-powered anomaly detection covering amount spikes, new bank account flags, and unusual vendor b …

Requirement evaluated: Vendor performance visibility: on-time payment rate, average payment cycle, dispute frequency

For your 3-person AP team processing 1,800 invoices monthly across two Sage Intacct entities, MineralTree's Analytics module (available in TotalAP packages) provides visual dashboards that can be filtered by vendor, business unit, or time period. Documented KPIs include invoice aging, payment mix, days payable outstanding, average invoice processing time, and vendor spend totals. …

Limitations: Two of the three requested metrics — on-time payment rate per vendor and dispute frequency per vendor — are not documented as pre-built, natively computed KPIs in MineralTree's Analytics module; they would require the buyer to export raw payment data via Search Page Reports and calculate them offline. …

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 at a $120M services company currently losing 6 hours per week to vendor status calls, MineralTree addresses the vendor communication problem through two mechanisms rather than a single structured communication log. First, the platform centralizes all invoice and payment history in one place so that Accounting Managers can quickly pull up payment status to answer an inbound call without digging through email chains: the help documentation explicitly notes that 'Accounting Managers access payment history to research questions from vendors or review invoice and check documentation' (MineralTree Review & Edit Invoice Details, support.mineraltree.com). …

Limitations: No evidence exists of a dedicated, timestamped vendor communication log (inquiry in, response out, attached to the vendor or invoice record) within the MineralTree platform itself. …

Requirement evaluated: Vendor performance visibility: on-time payment rate, average payment cycle, dispute frequency

For a $120M services company running 1,800 invoices per month across two Sage Intacct entities, MineralTree's named Analytics module and Search Page reporting layer provide payment visibility at the vendor level, but cover the buyer's three target KPIs unevenly. On average payment cycle: the platform tracks DPO and 'typical payment times or budget spent for individual vendors,' and a customer (Simple Mills' Controller) …

Limitations: MineralTree's analytics are oriented toward payment mix optimization, DPO, and cash flow forecasting rather than vendor-facing scorecards: on-time payment rate as a calculated per-vendor percentage and dispute frequency as a structured per-vendor metric are not documented as native dashboard outputs, meaning the buyer' …

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

For your 1,800-invoice/month operation running on Sage Intacct, MineralTree's documented role in the 1099 lifecycle is limited to flag propagation and field carry-through. The Intacct Integration Guide confirms that MineralTree syncs the vendor-level 1099-enabled condition from Intacct: if a vendor is marked 1099-eligible in Intacct, invoices created in MineralTree will have the 1099 checkbox checked by default and that status syncs back to Intacct on posting. The Form 1099 Description field also appears at the invoice expense-line level in MineralTree's Intacct data model, so line-level 1099 coding is carried through to the ERP. …

Limitations: Two of the three components the buyer requires — automated threshold tracking across cumulative vendor payments and electronic IRS filing — are not documented as MineralTree capabilities; they would need to be handled in Sage Intacct directly or via a separate filing service connected to Intacct. …

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

For a 3-person AP team currently keying invoices by hand into Sage Intacct, MineralTree's Invoice Capture feature sits at pre-processing Stage 1 (legitimacy and data ingestion) and partially Stage 2 (PO matching). When an invoice arrives by email or scanned mail, your team forwards or uploads it to a dedicated MineralTree inbox. The system then applies OCR combined with human-in-the-loop validation to extract both header and line-level fields: <cite index="27-2,27-3">returned data includes header-level information such as vendor name, invoice number, and invoice amount, and line-level data is also available.</cite> Payment terms receive specific treatment: <cite index="17-1,17-2">the terms p …

Limitations: Line-item extraction (required for your 55% PO-based volume and for coding non-PO line detail) is configurable rather than on by default: <cite index="15-2,15-3">invoices can be captured at either the header-summary level or by line and header, and line-level capture must be enabled to take advantage of line-level PO m …

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

For a 3-person AP team currently sorting invoices manually out of a shared email inbox, MineralTree TotalAP addresses this at the very first stage of the pre-processing journey: document ingestion. MineralTree provisions each customer with a dedicated capture email address. When a vendor or any sender emails an invoice attachment to that address, the document automatically lands in the MineralTree Document Inbox without any manual downloading, sorting, or re-uploading by AP staff. As MineralTree's own support documentation states, 'when someone (e.g., a vendor or Accounting Manager) …

Limitations: MineralTree's ingestion model uses a vendor-provisioned capture email address rather than a native IMAP or OAuth connection that continuously monitors the buyer's existing shared inbox directly. …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, MineralTree's TotalAP delivers invoice capture accuracy through a combination of OCR and a human-in-the-loop (HITL) review step, achieving a documented ~99.5% accuracy rate on every invoice submitted. The mechanism works as follows: invoices arrive at a dedicated company email inbox, OCR extracts header and line-level data, MineralTree's own human reviewers validate and correct the extraction output before it is returned to the AP team, and the resulting invoice is then checked against that vendor's stored 'Invoice Preferences' profile to auto-populate default GL coding fields. …

Limitations: The buyer's requirement asks for extraction accuracy that improves over time on their specific vendor invoice formats, which implies autonomous model refinement from their own correction data. …

Requirement evaluated: Support for all invoice formats we receive: standard PDF, scanned images, email body invoices, and EDI (from 3 large subcontractors)

For your $120M services company currently receiving invoices by email and mail, MineralTree handles two of your four required formats well: standard PDFs and scanned image files sent as email attachments are captured via a dedicated company-specific inbox address (ap-docs.com), processed through OCR combined with human-in-the-loop validation, and extracted at the header and line level (up to 100 lines per invoice) with a documented 99–99.5% accuracy rate. …

Limitations: Two of your four required formats have documented gaps: email body invoices are explicitly excluded from automated capture per MineralTree's support documentation, and EDI 810 ingestion is absent from all MineralTree product documentation, meaning your 3 large subcontractors using EDI would require a manual workaround …

Requirement evaluated: Automatic combination of multiple approved invoices to the same vendor into a single payment, with the matching criteria used for combination clearly stated

For a multi-location services company running 1,800 invoices per month through Sage Intacct, MineralTree's payment grouping feature directly addresses this requirement. <cite index="5-1,5-13">When paying multiple invoices to the same vendor, the default setting in MineralTree is to group them into one payment amount, with the individual invoices itemized on the remittance sent to the vendor.</cite> This behavior is on by default across all payment methods and is controlled at the vendor profile level: <cite index="20-1">if a specific vendor requires one payment per invoice, the AP team edits that vendor's profile and checks the 'disable payment grouping' checkbox.</cite> For Sage Intacct spe …

Limitations: The published documentation confirms that the primary grouping criterion is same vendor (payee), with the vendor-profile toggle as the override mechanism; however, the documentation does not explicitly enumerate secondary matching criteria such as same payment method, same Intacct entity, or same currency, which the bu …

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

For a $120M services company paying 8 overseas vendors through Sage Intacct, MineralTree TotalAP handles international wire payments natively within the same platform used for domestic AP. MineralTree explicitly announced multi-currency invoice processing and international payments for Sage Intacct users, covering the full invoice-to-pay cycle: automated capture and approval of foreign-currency invoices through to payment execution. The payment mechanism uses an 'FX Payments' payment type: the AP team queues international invoices alongside domestic ones, a payment authorizer locks in a real-time exchange rate (rates refresh every minute) …

Limitations: International payments are capped at 20 per payment batch (versus approximately 500 for domestic payments), which at 8 overseas vendors is not a binding constraint for this buyer but worth noting if the overseas vendor count grows. …

Requirement evaluated: Payment reconciliation with automatic journal entries back to Sage Intacct

For a $120M services company currently reconciling payments manually after bi-weekly check runs and monthly ACH batches, MineralTree closes that loop automatically. When an authorized payment leaves MineralTree, the payment data syncs back to Sage Intacct through a direct API connection: the bill is marked paid, the disbursement posts against the correct bank account, and Intacct's AP sub-ledger and GL are updated without any manual journal entry by the AP team. …

Limitations: Void and delete actions do not sync bidirectionally; if a payment is voided in MineralTree it must also be voided separately in Sage Intacct to maintain reconciliation. …

Requirement evaluated: Early payment discount detection: auto-flag invoices with discount terms (2/10 net 30) and alert AP when deadline approaches

For a $120M multi-location services company processing 1,800 invoices/month in Sage Intacct, MineralTree's Invoice Capture uses OCR to extract payment terms from the invoice document, and the system calculates the discount date and amount automatically from those terms. <cite index="31-7,31-8">MineralTree calculates discount information (date and amount) …

Limitations: MineralTree flags discount terms and calculates discount expiry dates visually on the Invoices tab, but there is no documented proactive deadline-approaching alert pushed to AP staff before the window closes. …

Requirement evaluated: Dual approval requirement for all capital expenditures regardless of amount

For a multi-location services company needing dual approval on every CapEx invoice regardless of dollar amount, MineralTree's approach involves two layered mechanisms. First, invoice approval rules can be built on GL account coding: <cite index="6-2">invoices can be routed for approval automatically based on class, vendor, or GL account coding</cite>, so your team would create a rule tied to each CapEx GL account code and assign the two required approvers to that rule. …

Limitations: The 'approval by all' enforcement is a company-wide global setting per <cite index="21-3,21-4">the configuration that applies to all invoices within your organization and cannot be changed for specific vendors</cite>: activating it to enforce dual CapEx approval forces the same requirement onto every invoice across the …

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

For a multi-location services company whose approvers are distributed across 6 offices and rarely log into a finance system, MineralTree offers two mobile-accessible approval paths. The first is an email-link flow: when an invoice is routed for approval, the approver receives an email notification containing a link that opens a read-only view without requiring a login. On that page the approver can tap Approve, Reject, or Add a Note. This path eliminates authentication friction and is well-suited to the sub-30-second interaction requirement. However, MineralTree's own help documentation states that this no-login view shows only 'high-level invoice summary details' (vendor and amount) …

Limitations: The no-login email-link path, which best supports the sub-30-second requirement, displays only vendor name and amount rather than the full invoice image; approvers who need to view the invoice document before acting must log into the web application, adding an authentication step that is likely to push the interaction …

Requirement evaluated: Automatic escalation: if approver has not acted within 48 hours, escalate to their manager with notification

For a 3-person AP team at a multi-location services company processing 1,800 invoices monthly across two Sage Intacct entities, MineralTree's TotalAP platform addresses the approval-bottleneck problem primarily through automated reminder notifications. The platform's documented mechanism sends follow-up reminders to the originally assigned approver at a steady cadence until they act: as one MineralTree differentiation blog describes, 'MineralTree's automated follow-up system will trigger reminders to approvers at a steady cadence until they are ready for review,' and the invoice approval workflow blog confirms that MineralTree 'automate[s] approval reminders so you don't have to.' The servic …

Limitations: MineralTree's documented approval follow-up mechanism is a reminder cadence to the original approver, not a time-triggered reroute to that approver's manager with approval authority. …

Requirement evaluated: Configurable multi-step approval routing by: dollar threshold, department, GL account, vendor, entity, expense type, and project

This $120M, 6-location services company running 2 Sage Intacct entities needs approval chains that respond to seven distinct attributes: dollar threshold, department, GL account, vendor, entity, expense type, and project. MineralTree's Invoice Approval Rule engine, configured by an Accounting Manager via the Invoice Approval Rule tab, does support attribute-based routing: <cite index="11-1,11-2">after global rules are set in the Customer Administration Application, users assign default approvers to different routing attributes within the Company Profile on the Invoice Approval Rule tab, defining how many tiers of approval are required, the dollar thresholds for each tier, and the names of ap …

Limitations: The routing attribute set confirmed in help-center documentation covers vendor, dollar threshold, and location/department for Intacct, but GL account, expense type, and project as independent approval-routing triggers are not verified. The precedence-based rule engine (one winning attribute per invoice) …