Airbase vs Tipalti

Requirement evaluated: Our specific routing rules: under $2,500 manager, $2,500-$10K director, $10K-$50K VP, over $50K CFO

This $120M multi-location services company needs exactly four amount-driven approval tiers (manager, director, VP, CFO) applied at the bill stage, not just at the pre-purchase request stage. Airbase's Advanced Approval Policy module handles this directly: <cite index="18-1">bills are routed automatically to the right approvers based on subsidiary, department, vendor, amount, GL category, and organization structure.</cite> The configuration mechanism is a conditional rule builder: <cite index="14-6,14-7">an Advanced Approval Policy is comprised of Rules, and each Rule can be designed as one or more 'When... …

Limitations: The help center article at support.airbase.com (which returned a blocked preview) was not fully accessible to confirm granular configuration steps, such as whether each tier supports both named-user and role-based assignees simultaneously. …

Requirement evaluated: Our specific routing rules: under $2,500 manager, $2,500-$10K director, $10K-$50K VP, over $50K CFO

This $120M multi-location services company needs invoices auto-routed to manager, director, VP, or CFO based on four specific dollar bands. Tipalti's Bills module supports multi-level sequential approval chains with designated bill approvers per invoice: <cite index="43-21,43-31">the AP processor can select one or multiple approvers from the "Bill approver(s)" field during review, and once an approver acts, "the bill then goes to the next level for approval (if more than one approval is required)" or moves to pending payment.</cite> Beyond manual designation, <cite index="55-5,55-6">Tipalti provides AI-driven routing that "automatically directs invoices to the right approvers based on your o …

Limitations: The help center documentation retrieved does not surface a self-service UI that lets admins configure the four dollar-band thresholds as a pure rule engine without implementation assistance; the automatic threshold-to-role binding in the Bills module (as distinct from the Procurement/PR module) …

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 6-location services company fielding status calls from subcontractors, utilities vendors, and professional services firms, Airbase operates a dedicated vendor self-service portal at vendors.airbase.io. Vendors are invited by email and, once onboarded, can log in to track payment status across all invoices (paid and unpaid), submit new invoices, upload documents, add or update payment details, and receive automated payment notifications. …

Limitations: Airbase's vendor portal eliminates payment-status calls by giving vendors self-serve visibility, but it does not provide a structured communication log that captures every inquiry and response tied to a specific invoice. …

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

For a $120M services company whose AP team spends 6 hours per week fielding vendor status calls, Tipalti's primary mechanism is vendor self-service deflection rather than a structured communication log. The Supplier Hub (also surfaced as an iFrame) gives every registered vendor 24/7 access to their own invoice history and payment history without contacting AP: <cite index="54-3">the vendor can log into the Supplier Hub anytime to upload invoices and track payments.</cite> On top of self-service access, <cite index="13-1">automated payment status communications to suppliers with a 24/7 portal to view payment history</cite> push milestone notifications proactively. …

Limitations: The Supplier Hub reduces inbound status calls effectively through self-service visibility, but it does not provide a structured inquiry ticketing system where vendors can submit a question, AP responds, and the full exchange is logged as a persistent, searchable communication audit trail on the invoice record. …

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

This $120M services company runs 55% PO-based invoices across two Sage Intacct entities, making receipt-confirmed three-way matching a critical fraud and overpayment control for roughly 990 invoices per month. Airbase's dedicated AP automation module markets automated 2-way and 3-way PO matching, describing the mechanism as matching 'purchase orders, invoices, and receipts' to ensure 'every invoice is tied to the right PO and receipt with minimal manual effort.' However, the most specific technical documentation of the goods-receipt leg consistently ties it to NetSuite item receipts: a 2021 product announcement states '3-Way Purchase Order Matching: Match POs, invoices, and item receipts to …

Limitations: For this buyer on Sage Intacct, there is no documented evidence that Airbase's goods-receipt leg of the three-way match extends to Sage Intacct the way it does for NetSuite, creating a material gap in stage 4 receipt confirmation for their PO-based invoice volume. …

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

This buyer processes roughly 990 PO-based invoices per month across facilities, supplies, and subcontractors: exactly the goods-and-services mix where 3-way matching is the control standard. Tipalti's PO Matching module covers all three stages of the pre-processing journey for PO invoices: PO match (stage 2), receipt confirmation (stage 4 via Goods Receipt Note capture inside Tipalti), and exception routing (stage 5 escalation). …

Limitations: One real-world note from third-party analysis is that Tipalti's procurement and AP modules can operate somewhat independently, meaning GRN logging discipline by receiving staff is critical: a GRN entered late creates a timing mismatch that generates false exceptions and erodes straight-through processing rates. …

Requirement evaluated: Native, bidirectional integration with Oracle NetSuite (not middleware-only)

For a company running NetSuite as its ERP and replacing an email/Slack approval process, Airbase connects to NetSuite through a native SuiteCloud/RESTlet integration that requires no third-party iPaaS or middleware. Setup involves enabling RESTlet integration within the buyer's NetSuite account and configuring Airbase's Settings > General Ledger panel, where an admin maps GL accounts, departments, classes, locations, and custom fields directly to NetSuite objects. …

Limitations: The Airbase help center confirms that some advanced features (such as NetSuite amortization template sync) require RESTlet integration to be enabled as a prerequisite in the buyer's NetSuite account, so implementation scope is broader than a simple OAuth credential exchange; the buyer should budget for a structured dep …

Requirement evaluated: Native, bidirectional integration with Oracle NetSuite (not middleware-only)

For a $250M tech company currently creating POs manually in NetSuite, Tipalti connects directly to NetSuite through Oracle's SuiteTalk Web Services API using Token-Based Authentication (TBA), with no third-party iPaaS or middleware layer involved. Setup happens entirely within Tipalti's Administration > Integrations > Apps panel, where an admin authenticates against NetSuite's Account ID, Consumer Key/Secret, and Token, then configures sync preferences object by object. …

Limitations: PO sync in the AP/PO Matching module flows one direction only (NetSuite to Tipalti), meaning POs this buyer creates in Tipalti Procurement require the separate Procurement-NetSuite integration path rather than the standard AP sync; the buyer should confirm that path is included in their Tipalti contract tier. …

Requirement evaluated: Vendor deduplication: identify and merge the 800+ vendor records into a clean master list

For a company needing to cut 800+ NetSuite vendor records down to a clean master list, Airbase addresses two different phases of this problem with unequal depth. On the forward-looking side, Airbase's vendor management module enforces an approval gate before any new vendor record is created, and it automatically validates Tax IDs against the IRS and 100+ international government agencies and verifies bank account details before payment — mechanisms that prevent future duplicates from accumulating once a clean list is established (Airbase Vendor Management page, airbase.com/features/vendor-management). …

Limitations: The buyer's most urgent need — consolidating 800+ existing NetSuite vendor records into fewer than 300 before or during migration — is not addressed by any documented Airbase mechanism; the migration path explicitly transfers the duplicate problem into Airbase rather than resolving it, meaning this cleanup work must ha …

Requirement evaluated: Vendor deduplication: identify and merge the 800+ vendor records into a clean master list

Your company's immediate need is to retrospectively clean up 800+ NetSuite vendor records that have accumulated without deduplication controls. Tipalti's payee management capabilities address the forward-looking side of this problem but not the retrospective cleanup. On the prevention side, Tipalti validates each new payee's TIN/EIN against IRS records during self-service onboarding through the Supplier Hub: <cite index="11-1,11-6,11-7">TIN validation verifies the number provided by payees against IRS records, and if it fails, the payee is marked "unpayable" until resolved; the TIN can be an SSN for individuals or an EIN for companies.</cite> This provides a forward-looking uniqueness signal …

Limitations: Tipalti has no documented mechanism for scanning an existing payee database for duplicate records using fuzzy name, address, or banking-detail matching, and no merge tool to consolidate fragmented transaction history under a master record. …

Requirement evaluated: Mandatory legal review routing for all software and professional services purchases over $25K

For a $250M technology company routing software and professional services purchases over $25K to legal, Airbase delivers this through two complementary modules: Advanced Approvals and Guided Procurement. In Advanced Approvals, admins build conditional 'When...then...' rules where the trigger conditions can combine spend type (e.g., software, professional services) and dollar amount, automatically routing to a named Legal approver or Legal approval group before the request advances. …

Limitations: Airbase's documentation describes the enforcement model as policy-configured rather than system-hardened: whether legal approval can be administratively overridden or delegated away by a super-admin is not explicitly addressed in the available documentation, so the buyer should confirm during a demo that the legal node …

Requirement evaluated: Mandatory legal review routing for all software and professional services purchases over $25K

For a $250M tech company needing mandatory legal sign-off on all software and professional services purchases over $25K, Tipalti Procurement (built on the acquired Approve.com engine) offers a rules-based approval routing module at the purchase-request stage, before a PO is ever generated. According to Tipalti's PO approval product page, administrators configure 'predefined workflows for various budget levels, departments, and locations' and the system can 'auto-route approvals to cross-functional teams like IT, security, and legal to ensure swift and thorough reviews.' Tipalti's intake management documentation confirms that 'approval flows are defined based on your organizational chart, bud …

Limitations: The buyer requires legal review to be mandatory and non-bypassable for the specific category-plus-threshold combination; Tipalti's documented language alternates between 'auto-route to legal' (system-enforced) …

Requirement evaluated: Real-time AP dashboard: invoice aging, approval queue depth, processing cycle time, spend by vendor/category/entity

For a 3-person AP team at a multi-location services company running 1,800 invoices per month across two Sage Intacct entities, Airbase's Spend Analytics module delivers real-time spend visibility across three of the four required dimensions. The reporting feature page explicitly states it surfaces <cite index="14-1">"up-to-the-minute spend by department, vendor, category, or subsidiary across all spend,"</cite> and the spend analytics ebook confirms the platform provides <cite index="24-6">"real-time visibility into your spend processes across a variety of metrics, from invoice processing cycle times"</cite> with a named set of productivity benchmarks. …

Limitations: Invoice aging is documented only as a manually triggered CSV/Excel export from the Bills module, not a live dashboard panel that auto-refreshes; a 3-person AP team monitoring aging daily would need to run and download the report each time rather than viewing it on-screen. …

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

For your 3-person AP team reporting to a Controller and CFO across two Sage Intacct entities, Tipalti provides a structured reporting layer with multiple pre-built report categories (payment reports, bill reports, payee reports, tax reports, and user reports) plus an AI Report Builder that generates custom reports from natural language prompts. The AI Report Builder, documented in Tipalti's official blog and product pages, lets a user type a plain-language query, refine columns and filters, save the report, and download it for deeper analysis; the Reporting Agent is also described as generating 'real-time spend or payment reports from natural language prompts.' A G2 reviewer who has used the …

Limitations: The confirmed export format from Tipalti's official help center documentation is CSV, not .xlsx; if the Controller's month-end close workbooks depend on native Excel formatting or formula-linked templates, CSV delivery may require an extra conversion step. …

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

For a 3-person AP team moving 1,800 invoices per month across two Sage Intacct entities, Airbase handles payment reconciliation through a documented bi-directional sync architecture. When a bill payment is executed in Airbase (ACH, check, or virtual card), Airbase writes the payment back to Sage Intacct as a paired Bill plus Payment record, automatically clearing the open payable in the AP subledger and posting the corresponding cash or clearing account entry without manual re-keying. …

Limitations: The full body of the 'Sync Bill Payments to Sage Intacct' help article was not rendered by search, so the precise field mapping (payment date, reference number, clearing account designation) …

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

For a 2-entity Sage Intacct environment processing 1,800 invoices per month, Tipalti's prebuilt API integration handles payment reconciliation as a configurable, automated writeback: once a payment is executed in Tipalti, the integration pushes a bill payment record directly to Sage Intacct in real time, closing the open bill in the AP subledger without any manual import or file upload. …

Limitations: Sync health depends on subsidiary and AP account alignment between both systems: Tipalti's troubleshooting documentation notes that mismatches between the entity's AP account on the bill and the payment will cause the payment sync to fail, so initial setup requires careful entity mapping across the buyer's 2 Intacct en …

Requirement evaluated: Support for Sage Intacct dimensions: Location, Department, Class, Project, Customer, and custom dimensions

For your two-entity Sage Intacct environment, Airbase codes invoices (bills) using a system of Line Level Tags and Transaction Level Tags that map to Sage Intacct's dimension fields. The bill export documentation explicitly lists Department and Location as Sage Intacct-specific dimension fields carried on bill transactions, and a separate help article confirms that Sage Intacct users can set Project as a GL line-level tag, meaning Project coding can be applied per invoice line to support split allocations across your 6 locations and subcontractor projects. …

Limitations: Airbase's documented Sage Intacct dimension coverage is limited to Department, Location, and Project; Class, Customer, and any user-defined/custom dimensions the buyer has configured in Sage Intacct are not documented as supported in the bill coding or sync workflow, meaning those dimensions would require manual coding …

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

For a $120M services company running two Sage Intacct entities, Tipalti's native Sage Intacct connector handles all five data objects the buyer requires through a single API-based integration configured inside the Tipalti Hub. On the master data side, GL accounts (chart of accounts) flow from Intacct into Tipalti incrementally: <cite index="2-8">all GL accounts in Intacct that were added, updated, or deleted since the last sync are collected and synced to Tipalti</cite>, and <cite index="2-24">GL accounts linked to multiple entities sync from Intacct to Tipalti</cite>, covering the buyer's two-entity structure. …

Limitations: <cite index="2-17">Syncing bills before approval is not available for payers using the PO Matching feature</cite>, which means the 55% of this buyer's invoices that go through PO matching will only write back to Intacct after approval rather than on receipt. …

Requirement evaluated: Spend dashboards: real-time spend by vendor, category, department, location, and period

For a $250M technology company currently flying blind on 35% maverick spend, Airbase's native Spend Analytics module addresses this requirement directly. Finance and procurement users access pre-built and custom dashboards that aggregate spend across all payment types captured in the platform: AP invoices, guided procurement purchase requests, corporate cards, and employee expense reimbursements. The documented dashboard dimensions include vendor, department, category, and subsidiary (Airbase's term for location-level or entity-level segmentation), with period-based filtering for trend and projection views. …

Limitations: The 'location' dimension is documented primarily as subsidiary-level segmentation; if the buyer requires office-level spend breakdowns below the entity level (e.g., distinguishing the four US offices independently within a single legal entity), they should confirm during demo whether office/cost-center tagging on trans …

Requirement evaluated: Real-time budget tracking: available budget = annual budget minus actuals minus committed (approved POs not yet invoiced)

Your company's scenario, a $250M tech firm running all purchasing through email with no live budget visibility, maps directly to the problem Tipalti Procurement (built on the acquired Approve.com platform) addresses. Within the Tipalti Procurement module, admins load budgets via an 'Upload budget' function, and the system then tracks spend against those budgets as purchase requests flow through approval workflows. Approvers see real-time budget consumption status during the PO approval stage, giving them a live view of how much of a budget has been consumed before they approve additional spend. …

Limitations: Two material gaps remain for this buyer: first, the 'Upload budget' mechanism implies budgets are manually loaded rather than pulled live from a GL, so the annual budget baseline is only as fresh as the last upload; second, the three-part waterfall balance (budget minus actuals minus open PO commitments) …

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

For your 3-person AP team processing 1,800 invoices per month, the relevant question is whether Airbase surfaces per-field confidence scores so clerks know exactly which extracted values to verify rather than checking every field on every invoice. Airbase's bill capture module uses AI-powered OCR and machine learning to auto-fill key invoice fields such as vendor name, invoice date, amount, and line items, and applies ML-based predictive GL coding that learns from past coding corrections. …

Limitations: No evidence was found in Airbase's help center, product documentation, or any third-party review that Airbase presents per-field confidence percentages or visual confidence indicators to AP clerks during invoice review; clerks would need to rely on their own judgment to determine which auto-extracted fields require ver …

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

For your 1,800-invoice-per-month operation on Sage Intacct, Tipalti's touchless path works as follows. Invoices arrive via email or portal and are captured by AI Smart Scan, which applies OCR and machine learning to extract header and line-level data without manual keying. For your PO-based invoices (facilities, supplies, subcontractors), Tipalti pulls POs and goods receipt notes (PO receivers/GRNs) directly from Sage Intacct via its named integration, so receipt confirmation (pre-processing stage 4) is handled through a live sync rather than a manual step. …

Limitations: Tipalti's Sage Intacct integration does not support syncing bills to Intacct before the matching/approval step is complete, so mid-process ERP visibility is not available for PO-matched bills. …

Requirement evaluated: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

For your company's need to gate PO amendments above a 10% or $5,000 threshold, Airbase does offer a formal 'Request Change of Amount for Purchase Orders' pathway: spend owners submit an amount-change request, and that request routes through the approval chain configured in Airbase's Advanced Approval Policy engine. The Advanced Approval Policy uses configurable 'When...then...' conditional rules that can be based on spend amount, department, GL category, spend type, and other dimensions, and these rules apply to Purchase Order requests. …

Limitations: The critical gap for this buyer is the absence of documented delta-based re-approval logic: Airbase's approval rules appear to route based on the total request amount or spend category, not on the percentage or dollar increase over an already-approved PO amount. …

Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed

For a $250M technology company replacing email/Slack approvals and manual NetSuite PO entry, Tipalti's Procurement module covers the full PO status lifecycle the buyer requires. Tipalti's help center documents discrete, named stages across the lifecycle: 'Create and track purchase requests,' 'Approve purchase requests,' 'Mark goods and services as received,' PO Matching, Bill approval for PO-backed bills, and PO updates, all surfaced in the Tipalti Hub (Tipalti Help Center navigation, help.tipalti.com). …

Limitations: The buyer's Canada development center introduces no documented gap, as Tipalti's Procurement module supports multi-entity configurations. However, the Procurement module is a separately licensed product from Tipalti's core AP/payments suite, so the buyer should confirm during scoping that both modules are included in t …

Requirement evaluated: SOC 2 Type II certification for the platform

For a $250M technology company routing financial data through a spend management platform, Airbase's SOC 2 Type II attestation directly addresses the compliance audit-readiness requirement. Airbase has held SOC 2 Type II attestation since at least 2021, covering the platform's security controls over a defined audit period; the report is issued by an independent CPA firm and is available to customers and prospects upon request following execution of an NDA (Airbase Security Policy and Compliance page, archived at dryobalanops.com). …

Limitations: The archived Airbase security page dates to 2021; buyers should confirm that a current, post-acquisition SOC 2 Type II report has been issued for the combined Airbase-by-Paylocity platform and that the audit scope explicitly covers the spend management module rather than only Paylocity's core HCM infrastructure. …

Requirement evaluated: Segregation of duties enforcement: requester ≠ approver ≠ receiver ≠ payment processor

For a $250M tech company replacing ad-hoc email approvals, Tipalti enforces role separation across the full transaction lifecycle through its named, admin-assigned role system. On the procurement side, the Enhanced Procurement module surfaces three distinct role-gated actions in separate documented workflows: creating and tracking purchase requests (requester), approving purchase requests (approver), and marking goods and services as received (receiver). Each of these is a separately accessible function in the Tipalti Hub, and a user must hold the specific role to perform each action. …

Limitations: The documented separation is enforced through administrator-configured role assignments rather than a transaction-level hard block that explicitly prevents a requester from being named as their own approver on a specific bill; your admin team will need to configure role assignments deliberately to realize full four-way …

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

For a $120M multi-location services company evaluating security posture before committing to an AP automation platform, Airbase (now operating under Paylocity following acquisition) maintains an annually renewed SOC 2 Type II attestation conducted by independent, reputable CPA firms. The official Airbase security policy page states that audits cover controls related to financial reporting, security, confidentiality, and availability, with each control tested for both design appropriateness and operating effectiveness. …

Limitations: Because Airbase was acquired by Paylocity relatively recently, buyers should confirm during the sales process that the SOC 2 Type II report scope explicitly covers the Airbase spend management modules (AP automation, bill pay, guided procurement) …

Requirement evaluated: Data encryption at rest and in transit

For a multi-location services company moving invoice and payment data through an AP platform, Tipalti protects financial information at two layers. For data at rest, Tipalti's published security documentation explicitly states it uses AES-256 encryption to safeguard stored data, covering personal information, payment details, and banking records held on its AWS-hosted infrastructure. For data in transit, Tipalti's official Data Processing Addendum (a contractual document, not marketing copy) …

Limitations: Tipalti's published documentation names AES-256 and TLS as the encryption standards in use but does not publicly disclose whether customer-managed encryption keys (CMEK) …

Requirement evaluated: Automatic match-and-pass for invoices within tolerance, reducing AP workload to exceptions-only review

For a technology company coming from a fully manual, email-and-Slack approval environment, Airbase's AP Automation module covers the full matching journey your AP team needs. Invoices arrive via email, bulk upload, or the vendor portal; OCR and AI extract line-level data automatically. The platform then runs automated 2-way matching (PO vs. invoice) for service purchases where no goods receipt exists, and automated 3-way matching (PO, goods receipt, and invoice) for direct materials spend, comparing price and quantity against tolerance thresholds and flagging duplicates and partial receipts. …

Limitations: Public documentation from Airbase describes tolerance thresholds as part of the matching logic, but granular configuration options (e.g., whether tolerance rules can be set by percentage vs. dollar amount at the line-item vs. header level, or per-vendor or per-category) …

Requirement evaluated: Simple receipt confirmation workflow: designated receiver confirms delivery with quantity, condition, and date

For this $250M technology company coming from a manual email/Slack approval environment, Tipalti Procurement does include a goods receipt confirmation step that feeds a true 3-way match (PO + GR + invoice). The mechanism works as follows: once a PO is issued, <cite index="9-1,9-2,9-3">Tipalti captures item receipts 'on auto-pilot' by prompting users to log Goods Received directly in the platform or via email at the right moment, with item statuses automatically updated to facilitate the 3-way PO match.</cite> However, the critical limitation for this buyer is who receives that prompt: <cite index="21-1,21-2">Tipalti prompts *requesters* at the right time to confirm goods or services were rec …

Limitations: The receipt confirmation step is tied to the requester role, not a separately designated physical receiver, which collapses the separation of duties the buyer needs (requestor vs. receiver) and reduces the control value for verifying actual delivery condition. …

Requirement evaluated: Link request to existing contract when applicable (e.g., ordering under a blanket PO or master agreement)

For your $250M technology company trying to eliminate maverick spend and ensure purchases reference existing agreements, Airbase's Guided Procurement module operates at the intake stage but does not offer a native contract repository that auto-surfaces existing blanket POs or master agreements when a requester selects a known vendor. What Airbase does provide is a configurable, no-code intake form that can collect and route contract documents: the Guided Procurement overview sheet states that 'requirements for each business group, like SOC attestations, tax information, or contracts flow automatically to stakeholder systems,' meaning an admin can build a custom intake field prompting the req …

Limitations: Airbase has no native contract repository, so there is no mechanism to automatically surface an existing blanket PO or master agreement when a requester picks a vendor during intake: a requester must manually know an agreement exists and attach it themselves, which does not reliably prevent off-contract ordering. …

Requirement evaluated: Mobile submission capability; our field team needs to submit requests from job sites

For this $250M technology company whose field team needs to originate purchase requests from job sites, Tipalti's procurement intake sits in the web-based Tipalti Hub. Employees fill out customizable intake forms in the Hub to submit purchase requests, and the system routes them through automated approval workflows. Tipalti does publish a native mobile app, but that app is scoped specifically to expense management (the 'Tipalti Expenses' app on iOS and Android, documented in help.tipalti.com): it handles post-purchase receipt capture and expense reimbursement, not pre-purchase requisition creation. …

Limitations: The Tipalti Expenses mobile app covers post-purchase reimbursement workflows, not pre-purchase procurement requests; using it as the 'mobile' solution for field requisition intake would perpetuate the maverick spend problem the buyer is trying to solve. …