How Airbase works

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

For your 3-person AP team paying subcontractors, landlords and professional-services vendors out of two Sage Intacct entities, Airbase covers the intake end of 1099 work. It does not cover classification, threshold tracking or filing. In the vendor portal, vendors upload a tax form such as a W-9 and the system scans it and auto-fills legal name and tax ID. The help article also says the system validates the Tax ID with government records to support reporting requirements such as 1099. Airbase's AP page describes AI-powered W-9 collection and validation that make 1099 reporting more efficient. That covers the vendor-legitimacy and tax-data step before invoices are posted. …

Limitations: Airbase's documented 1099 support stops at W-9 collection and TIN validation. Classification, threshold tracking and e-filing across your two entities would still run in Sage Intacct or a separate filing service, so your team would not get a single in-tool 1099 workflow. …

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

For a $120M multi-location services company processing 1,800 invoices per month across two Sage Intacct entities, Airbase's Vendor Management module provides a vendor-level repository where your AP team can access payment history, spend data, compliance status, and preferred payment terms per vendor, filterable with advanced columns and custom views. The June 2024 launch of Airbase's Spend Analytics and enhanced Vendor Management capabilities added what the vendor describes as 'a comprehensive view of vendor performance and risk' with real-time insights across AP, expenses, and cards. Vendors can also self-serve payment status through the supplier portal, reducing inbound inquiries. …

Limitations: Airbase surfaces payment history and spend data at the vendor level, but third-party user reviews specifically flag limited custom reporting and analytics depth as a known gap, and no Airbase documentation describes a purpose-built on-time payment rate calculation, average days-to-pay metric, or dispute frequency trend …

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

Your AP team currently spends 6 hours per week on vendor status calls because suppliers have no visibility into where their invoices stand. Airbase addresses this primarily through a dedicated self-service vendor portal (vendors.airbase.io) where invited suppliers can log in to track payment status across all their invoices (paid and unpaid), submit invoices directly, update banking details, upload documents, and receive automated payment alerts. On the AP side, the bill payments module automatically attaches related email correspondence to each invoice record, giving your team a centralized record of vendor interactions per invoice. …

Limitations: The vendor portal gives suppliers self-service payment status and invoice submission, which will reduce a portion of inbound status calls; but Airbase does not document a structured per-invoice inquiry-and-response thread visible to both the vendor and AP team. …

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

For a $120M services company processing subcontractor and professional services payments across two Sage Intacct entities, Airbase covers the first two legs of 1099 compliance but stops before the finish line. During vendor setup, AP staff can flag a vendor as '1099 Vendor' on their profile; at year-end, the Vendors export can be filtered to include only vendors paid more than $600 via Bill Payments, and the resulting Excel or CSV file includes a '1099 Vendor' column marking eligible payees. …

Limitations: Electronic filing is not available within Airbase at any price point; the vendor's own documentation confirms Airbase will not file on the buyer's behalf, and completing the process requires exporting a CSV and engaging a separate filing vendor (e.g., Avalara/Track1099). …

Requirement evaluated: Batch approval capability for recurring invoices from the same vendor (e.g., monthly telecom bills across 6 locations)

For your scenario of approving monthly telecom bills across 6 locations, Airbase offers two relevant but incomplete mechanisms. First, the platform supports recurring bill creation: you can make recurring payments to a vendor on Airbase, and this option will create bills on a recurring basis for that vendor, which automates bill generation on a schedule so your 6 telecom invoices arrive without manual data entry each month. Second, bills are routed automatically to the right approvers and observers based on subsidiary, department, vendor, and amount, meaning approval policy rules can target a specific vendor and send all its bills to the same approver. …

Limitations: The buyer's AP team will still open and action each of the 6 location-level telecom bills one at a time at the approval stage; the recurring creation and vendor-based routing rules reduce setup friction but do not compress the approval touchpoints into a single action the way a documented bulk-approve-bills mechanism w …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

Requirement evaluated: Approval delegation with automatic expiration (e.g., delegate to backup for 5 business days while on PTO)

For a 3-person AP team at a 6-location services company, approval continuity during PTO is a real operational risk: a single absent approver can stall a bi-weekly check run or delay a subcontractor payment. Airbase does offer a 'delegated access' feature that lets a user grant a teammate restricted access to their Airbase account, and its Advanced Approvals module supports approval groups where any one member of the group can act, which partially addresses coverage during absences. …

Limitations: No Airbase help center article or product documentation found after exhaustive search confirms that approvers can self-initiate a time-bounded delegation window (e.g., 5 business days) that automatically restores routing to them upon return. …

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

For a 3-person AP team routing 1,800 invoices per month across two Sage Intacct entities, Airbase's Advanced Approvals module addresses the risk of a stalled workflow through availability-triggered contingency rerouting rather than a time-based inactivity timer. The Advanced Approvals product page documents the ability to 'build in contingencies for automatic re-routing — to next in line if one approver is not available — to keep teams moving,' and the product sheet confirms Airbase solves for situations where 'decision makers are out of the office.' However, this mechanism depends on an approver being declared unavailable (via an out-of-office setting or account deactivation), not on the sy …

Limitations: The buyer's specific requirement — escalate to the approver's manager automatically after 48 hours of no action — requires a time-triggered inactivity detector. Airbase's documented mechanism handles the declared-unavailability case (out-of-office, deactivated user) …

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: bills are routed automatically to the right approvers based on subsidiary, department, vendor, amount, GL category, and organization structure. The configuration mechanism is a conditional rule builder: an Advanced Approval Policy is comprised of Rules, and each Rule can be designed as one or more 'When... then...' statements called Conditions. This means the buyer's four thresholds ($2,500, $10K, $50K) …

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: Board-ready spend reports: quarterly spend summary by category with trend lines and vendor concentration metrics

For a $250M technology company currently flying blind with 35% maverick spend, Airbase's dedicated Spend Analytics module (launched June 2024) aggregates data across all three spend channels: accounts payable, corporate cards, and employee expenses, giving it the full spend footprint needed to reflect reality rather than just PO-backed transactions. The module surfaces spend broken down by department, vendor, subsidiary, and category with trend visualization across time periods, and users can filter by custom date ranges including quarterly windows. …

Limitations: For this buyer's CFO and board audience, the material gap is in the final presentation layer: Airbase does not appear to produce natively formatted, board-ready quarterly packages (PDF or slide-ready export with branded formatting and concentration metrics pre-calculated); finance staff will likely need to export raw d …

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: Tail spend analysis: identify high-transaction-count, low-dollar vendors for consolidation

For a $250M technology company with 800+ active vendors trying to identify candidates for rationalization, Airbase's Spend Analytics module (launched June 2024) surfaces vendor-level spend across AP, corporate cards, and expense reimbursements in real time. The reporting layer lets finance teams see spend by vendor, department, category, and subsidiary, and Airbase explicitly claims to help users 'visualize patterns and get control over maverick, zombie, duplicate, and inefficient spending.' Airbase's own tail spend glossary page confirms that its 'data analytics and reporting' tools help 'analyze spending patterns, identify trends, and make data-driven decisions' for managing high-volume, l …

Limitations: Airbase's spend-by-vendor reporting covers total dollar amounts and identifies maverick/inefficient spend broadly, but there is no documented Pareto, 80-20, or transaction-frequency-vs.-value segmentation view that would automatically surface a prioritized list of tail vendors for your rationalization effort from 800 d …

Requirement evaluated: Board-ready spend reports: quarterly spend summary by category with trend lines and vendor concentration metrics

For a $250M technology company replacing an email/Slack approval process, Airbase's Spend Analytics module (launched June 2024) aggregates data across AP, employee expenses, and corporate cards into a single reporting layer. The Reports section in the product includes a Summary Report, Categories Report, Departments Report, and a filterable All Transactions Report that covers virtual card, physical card, and bill payment transactions. …

Limitations: No documented evidence of native quarterly period-over-period trend line charts or vendor concentration metrics (e.g., top-N vendor spend share) formatted for board presentation; multiple independent user reviews confirm that board-presentation-ready reports require data export and assembly in Excel or a BI tool outsid …

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

For a services company processing 1,800 invoices per month across recurring vendor categories like rent and utilities, Airbase provides system-level duplicate invoice detection: the platform automatically flags potential duplicate invoices by comparing attributes including invoice number, vendor, and amount at the time of bill creation. This operates during the pre-processing legitimacy check (Stage 1 of the pre-processing journey) before a bill is posted to Sage Intacct. …

Limitations: For this buyer's 45% non-PO invoice mix, which includes utilities, subscriptions, and insurance policies that commonly reuse invoice numbers on a recurring cycle, Airbase's uniform duplicate detection will generate false-positive flags on legitimate invoices with no documented per-vendor override or sensitivity configu …

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

For your 45% non-PO invoice volume (utilities, subscriptions, professional services, insurance), Airbase's Bill Payments module applies auto-categorization at the point of bill creation: OCR extracts line-level invoice data from a dedicated invoice inbox, and the system then uses a combination of deterministic rules, OCR, and generative AI to populate fields and recommend GL coding without requiring a purchase order as an anchor. …

Limitations: The auto-categorization mechanism is most clearly documented for bill pay and card transactions; how quickly the ML model stabilizes on accuracy for a net-new vendor population (such as your subcontractors and insurance carriers where you have limited transaction history at go-live) …

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

For your 1,800-invoice-per-month operation with a 55% PO-based mix, Airbase's matching engine handles both 2-way and 3-way matching: invoices arriving via email or the vendor portal are compared against open POs and goods receipts, and the system routes non-matching bills to a review queue rather than passing them straight to payment. The 3-way match product page confirms the platform uses 'a combination of deterministic rules, OCR, and generative AI' to process invoices and explicitly states that 'finance teams spend less time keying in data and more time reviewing exceptions.' Fraud monitoring via ML models and real-time alerts covers some vendor-change scenarios (the security page confirm …

Limitations: No publicly available Airbase documentation confirms that exceptions are surfaced in a structured, categorized queue with distinct labels per mismatch type; the risk for your AP team of 3 is that discrepancies may arrive as undifferentiated 'needs review' holds, requiring manual root-cause investigation rather than tri …

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

For your 55% PO-based invoice volume, Airbase's bill payment module supports both 2-way and 3-way PO matching: the system compares invoices against purchase orders and, when receipts are attached, against receipt records as well. The PO detail page surfaces a 'Buffer Amount' field that allows a configurable tolerance for vendor overages, and matched payments are tracked directly on the PO record. When creating a bill, Airbase surfaces historical payment data for the same vendor, including prior invoice numbers, amounts, and dates, explicitly to help prevent duplicate payments. …

Limitations: For a 3-person AP team processing 1,800 invoices per month, the absence of confirmed named exception categories means your team may receive a generic 'needs review' hold rather than a pre-diagnosed category label, requiring manual investigation to determine whether each flagged invoice is a price variance, a quantity i …

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

For your 3-person AP team handling about 1,800 invoices a month across 2 Sage Intacct entities, Airbase's reporting sits on top of Bill Payments, after invoice capture and before the Intacct sync. Airbase says its unified platform delivers real-time visibility into spend. In Bill Payments, a Pending Bills report lists bills waiting for approval, and it names the pending approvers. The same help article lists Export Pending Bills, Export All Bills, Export Aging Reports and Export Unpaid Bills. …

Limitations: The documented AP aging, unpaid and pending views are export-based reports. The Pending Bills export is still labeled beta. I found no help-center documentation of a live AP dashboard with aging buckets, approval queue depth, or processing cycle time (receipt to approval to payment), so the buyer would need to confirm …

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 "up-to-the-minute spend by department, vendor, category, or subsidiary across all spend," and the spend analytics ebook confirms the platform provides "real-time visibility into your spend processes across a variety of metrics, from invoice processing cycle times" 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: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

Your AP team of 3 is currently flying blind on approval latency: no data on which of your approvers across 6 locations are sitting on invoices or which invoice categories (facilities POs vs. utilities vs. subcontractor invoices) cycle the slowest. Airbase addresses this through its Spend Analytics module, which the vendor describes as a tool to 'identify approval bottlenecks' across workflows, with dashboards that show where a hold-up exists, enable nudges for task completion, and surface invoice processing cycle times as a trackable metric. …

Limitations: For a 3-person AP team running 1,800 invoices per month, the material risk is that bottleneck visibility operates at the workflow-stage or invoice-category level rather than producing a self-serve, per-approver latency ranking your team can act on without support involvement. …

Requirement evaluated: Cash flow forecasting based on approved and pending payables with due date distribution

For a $120M services company processing 1,800 invoices per month across two Sage Intacct entities, Airbase provides the underlying payables data that cash flow planning requires, but does not assemble it into a native forward-looking forecast. Specifically, the Bill Payments module surfaces three exportable reports relevant to this requirement: a Pending Bills report covering invoices still awaiting approval (including Payment Due Date, vendor, amount, and GL category fields), an All Bills report spanning every status including payments in progress and scheduled payments, and an AP Aging Report that groups unpaid bills into Current, 1-30 day, 31-60 day, 61-90 day, and 91-day-plus buckets. …

Limitations: The AP Aging Report is oriented around how long unpaid bills have been outstanding (past-due bucketing), not around forward-looking cash outflow timing by future due date period, which is the buyer's actual requirement. …

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M tech company replacing email-and-Slack approvals with a formal procurement system, Airbase offers genuine pre-approval spend controls through its Spend Controls module: finance administrators configure hard-block and soft-warning policies, spending limits by role and expense type, and card-level limits on virtual and physical cards, all of which fire at the point of requisition submission or card use. The NetSuite integration is deep and bi-directional for GL coding: Airbase pulls chart-of-accounts dimensions (departments, classes, custom segments) …

Limitations: The budget enforcement mechanism in Airbase is configured within Airbase, not pulled live from NetSuite's budget records, so the buyer cannot use NetSuite as the single source of truth for budget limits. …

Requirement evaluated: SSO via Okta (our identity provider)

For a 450-person technology company already standardized on Okta, Airbase has a published entry in the Okta Integration Network (OIN) that covers both SAML-based SSO and SCIM 2.0 user provisioning. An Okta admin configures the Airbase OIN app, retrieves a tenant-specific SCIM Base URL and API Token from the Airbase portal under Users > Sync with HRIS, and enables Create Users, Update User Attributes, and Deactivate Users in Okta's provisioning settings; from that point forward, Okta sends SCIM POST /Users to Airbase on assignment, keeping the Airbase user directory in sync without manual admin setup per employee. …

Limitations: After SCIM provisioning creates an Airbase account, new users default to the Employee/Requester role; budget and department scope cannot be set through SCIM and must be assigned manually inside the Airbase UI, which adds a post-provisioning step for each new hire. …

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: Matched invoices push to NetSuite AP for payment processing (or integrate with our AP automation tool)

For a $250M technology company looking to eliminate manual PO-to-payment re-entry in NetSuite, Airbase functions as a full AP automation layer rather than a feeder into NetSuite's native AP queue. The mechanism works as follows: vendor invoices are captured via AI-driven OCR and converted into bills in Airbase, then automatic 3-way matching is performed against POs and item receipts synced from NetSuite. Once matched and approved, Airbase automatically syncs approved transactions to the NetSuite GL and keeps an audit trail of all supporting documentation. …

Limitations: Airbase's model positions it as the system of record for AP and payment execution; it does not create pending vendor bills inside NetSuite's AP queue for NetSuite to independently process payment. …

Requirement evaluated: Contract repository: store agreements, track renewal dates, alert stakeholders 90/60/30 days before expiration

For a $250M technology company currently tracking zero contracts systematically, Airbase's Vendor Management module provides a meaningful starting point. Each vendor profile stores contracts, insurance certificates, and tax documentation centrally, and the platform's dedicated 'renewals' feature provides automated renewal planning with stakeholder notifications. A third-party review of the module documents that automated alerts fire at 30, 60, and 90 days before contract or document lapse, matching the buyer's required cadence. …

Limitations: The buyer's requirement for a true contract repository (searchable by metadata, with lifecycle status, expiration-date fields, and configurable multi-stakeholder alert rules) …

Requirement evaluated: Centralized supplier database with self-service onboarding portal: vendors enter their own info, upload W-9, insurance, banking

For a $250M technology company replacing email-and-Slack approvals with structured vendor management, Airbase provides a dedicated external-facing Vendor Portal (vendors.airbase.io) that covers exactly the self-service onboarding flow the buyer needs. When a buyer's AP team sets up a new vendor record in Airbase, the system sends the vendor an invitation email with a link to the portal. Once signed in, vendors are directed through an onboarding page where they enter bank details, contact information, and tax details; Airbase then initiates a Tax ID validation process against the legal name and Tax ID submitted. …

Limitations: Insurance certificate upload is covered only as a general document upload (described alongside contracts and tax documents); there is no documented structured COI tracking module with expiration alerts or renewal prompts within the Airbase Vendor Portal, which may require a manual process or external tracking for buyer …

Requirement evaluated: Automated vendor onboarding workflow: request → IT security check (for software) → finance approval → vendor master creation in NetSuite

For a $250M tech company with 800+ vendors and no procurement system, Airbase addresses this requirement through two connected modules. First, the Guided Procurement module (Workflow Builder) handles the intake and multi-stakeholder approval chain: an employee submits a vendor request, and no-code configurable workflows route it sequentially or in parallel to IT security (including capture of SOC attestations and integration with ticketing systems like Jira), then to finance for approval, with each step tracked in a full audit trail. …

Limitations: The evidence confirms multi-stakeholder approval routing through IT security and finance, and vendor portal data collection, but does not explicitly document that Airbase pushes a fully formed new vendor master record into NetSuite upon workflow completion as a discrete, automated step. …

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: 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 $120M multi-entity services company running two Sage Intacct entities, Airbase closes the payment reconciliation loop through its dedicated 'Sync Bill Payments to Sage Intacct' capability, part of what Airbase calls Accounting Automation. When a bill payment is executed in Airbase (via ACH, check, or virtual card), the transaction is pushed back into Sage Intacct using the native Bill and Payment object structure rather than a generic journal entry, so the AP subledger bill is marked paid and the corresponding GL debit and credit entries are generated automatically. …

Limitations: The specific behavior of the payment sync across this buyer's two distinct Sage Intacct entities (e.g., whether each entity's bills and payments are written back to that entity's subledger separately, or whether the integration operates at the top-level parent) …

Requirement evaluated: Automatic remittance advice sent to vendors upon payment

For a 6-location services company processing 1,800 invoices per month across two Sage Intacct entities, Airbase addresses vendor payment notification primarily through its Vendor Portal. The portal's feature list explicitly includes the ability for vendors to 'track payment status' and 'receive notices of new invoice payments,' meaning vendors enrolled in the portal get alerted when a bill is paid. Airbase also maintains a dedicated knowledge base article titled 'Vendor Payment Notifications' in its Paylocity support center, confirming this is a named, documented capability rather than an incidental feature. …

Limitations: The payment notice mechanism requires vendors to onboard into the Airbase Vendor Portal; vendors who do not enroll may not receive automated payment notifications at all, leaving the AP team to manually communicate remittance details to non-enrolled suppliers (a significant share of a 1,800-invoice-per-month operation) …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

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

For a $120M multi-location services company running bi-weekly check runs through Bank of America, positive pay file generation is a post-payment control step: after each check run, the AP system exports a structured file in Bank of America's exact format (check number, payee, amount, date) and transmits it to the bank so the bank can validate presented checks before clearing. Airbase documents check as a supported payment method alongside ACH, virtual card, and wire, and its security page describes internal fraud controls such as vendor bank account change alerts and two-factor authentication on the vendor portal. …

Limitations: No documentation of positive pay file generation exists in Airbase's product or help content; the buyer would need to confirm directly with Airbase whether this capability exists, whether it supports Bank of America's specific file format, or whether it requires a workaround such as manually exporting a check register …

Requirement evaluated: Configurable retention policies aligned with our 7-year record retention requirement

For a $250M technology company that currently has no system-enforced record preservation, Airbase does automatically capture and store a comprehensive audit trail for every spend event: purchase requests, PO approvals, invoice activity, card transactions, and reimbursements. According to Airbase's own audit trail feature page, the platform captures transaction details as they happen and records them to 'an easily retrievable audit trail,' covering all purchase transaction elements regardless of payment method. The audit trail also syncs bidirectionally to the connected ERP (NetSuite in this buyer's case), so the general ledger receives a complete, audit-ready record of each event. …

Limitations: The buyer's requirement is not just record creation but enforced, configurable retention: a guarantee that POs, invoices, and approval logs cannot be deleted or become unavailable before 7 years have elapsed. …

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: SOC 2 Type II certification for the platform

For a $250M technology company whose CFO requires audit-ready compliance documentation, Airbase (now operating as part of Paylocity) publishes a dedicated security policy page at airbase.com/legal/security-policy that confirms both annual SOC 2 Type II attestations and ISO 27001:2022 certification. The SOC 2 Type II attestation is performed by reputable, independent audit firms on an annual cadence and covers controls related to security, confidentiality, and availability — the three trust service criteria most relevant to a procurement platform handling vendor and spend data. …

Limitations: Post-acquisition, the SOC 2 Type II report is issued under the Paylocity entity umbrella; the buyer should confirm during procurement that the audit scope explicitly includes the Airbase spend management module and is not limited to Paylocity's core HCM/payroll systems. …

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

For a $250M technology company moving off email/Slack approvals, Airbase enforces role separation across three of the four required SoD touchpoints through its combination of named User Roles and Permissions and configurable Approval Policies. The platform recognizes distinct roles including Admin, Accountant, Manager, and Spend Owner, and its Advanced Approvals engine routes requests to designated approvers who are separate from requesters: with Advanced Approvals, custom workflows automatically route requests to the right approvers, with approval groups that define whether requesters need sign-off from one individual or all members, sequentially or concurrently. …

Limitations: The material ceiling for this buyer is the receiver stage: Airbase does not surface a distinct, system-enforced role for goods or services receipt confirmation that is blocked from the original requester, which is the third leg of the required four-way SoD chain. …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

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: AI/OCR-powered extraction from PDF, image, and email-embedded invoices with 95%+ accuracy on header and line-item data

This buyer's AP team of 3 processes 1,800 invoices per month arriving by email and mail, currently keyed manually into Sage Intacct. Airbase's Bill Payments module addresses Stage 1 (legitimacy) and the data capture pre-processing step through a combination of deterministic rules, OCR, and generative AI: invoices submitted via email forwarding, drag-and-drop upload, or vendor portal are scanned and key fields auto-populated, including invoice date, bill description, line items, vendor details, amounts, and due dates. …

Limitations: No Airbase-published accuracy benchmark for line-item extraction exists in any available documentation; the buyer's 95%+ requirement on both header and line-item data cannot be confirmed against a disclosed metric, and one independent reviewer notes that OCR accuracy improves materially with a clean vendor master file, …

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

This $120M services company receives invoices across four distinct formats, and Airbase handles three of them with varying depth, while the fourth represents a hard gap. For standard digital PDFs and scanned images, Airbase operates a dedicated invoice inbox product backed by an OCR and generative AI engine: its intelligence uses a combination of rules, OCR, and generative AI to accurately populate invoice, bill, and PO details, and the invoice inbox and AI-powered OCR are included as named product features. …

Limitations: The EDI 810 gap is the material ceiling for this buyer: the 3 large subcontractors that transmit structured EDI invoices cannot be onboarded into Airbase's capture pipeline without manual re-entry or a separate middleware layer, which defeats the touchless processing objective for roughly their highest-volume, highest- …

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

For a $120M multi-location services company processing 1,800 invoices per month through a three-person AP team, this requirement asks whether Airbase surfaces per-field extraction reliability indicators so clerks know which fields to spot-check versus trust automatically. Airbase's documented extraction model operates on an auto-population basis: its intelligence uses a combination of rules, OCR, and generative AI to accurately populate invoice, bill, and PO details, with invoice fields automatically read, coded, and categorized. …

Limitations: Airbase's AP clerks receive no documented per-field confidence signal distinguishing high-confidence from low-confidence extractions; the model is auto-populate-and-route, which means clerks either trust all auto-filled fields or revert to verifying every field, exactly the manual burden this requirement was designed t …

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

For a finance team that wants PO amendments to go back for approval only when they grow more than 10% or $5,000 over the original, Airbase has approval rules but nothing documented that works on the size of the change. Airbase Approval Policy rules combine conditions (for example, department and a spend amount such as 'greater than or equal to USD 500') with an ordered list of approvers. POs created in Airbase can go through the approval cycle if the Approval Policy dictates it, and requests go to approvers in the order listed in the rule. Policies for purchase orders can be specific to a department, spend threshold, or expense category. Airbase works at the PO request and approval stage, then bill matching and receipts. Receipts are created against POs, and PO and receipt details sync to NetSuite every 6 hours. I found no public help article describing a change-order or amendment flow that compares the amended total to the original PO and re-triggers approval on a percentage or dollar variance.

Limitations: Approval thresholds are set on a spend amount. The public documentation does not show a condition for 'amended total exceeds original by more than 10% or $5,000', so the buyer would likely need a workaround. That could be a threshold on the new total, or a manual re-request or Workflow Builder process. The documentation also does not say what happens to approval status when an already-approved PO is edited.

Requirement evaluated: Automatic PO closure when fully received and invoiced, with alerts for POs open longer than 90 days

For a $250M technology company moving off manual NetSuite PO creation, Airbase offers two relevant primitives but neither fully automates the buyer's requirement. First, PO-to-invoice matching: Airbase supports automated 2-way and 3-way PO matching, ensuring every invoice is tied to the correct PO and receipt with no manual effort required. However, completing a match does not automatically close the PO: the help center documents a manual 'Close' action on the PO record, with no mention of a system-triggered status transition. …

Limitations: The buyer specifically needs two automated behaviors: a status-driven closure trigger fired when receipt and invoice are both fully matched, and a proactive alert when any PO exceeds 90 days open. …

Requirement evaluated: Automatic PO generation from approved requisitions; no manual PO creation

For a $250M technology company currently creating POs manually in NetSuite after Slack/email approvals, Airbase's Guided Procurement module replaces that entirely. An employee submits a purchase request through Airbase's structured intake form, supplying vendor details, amount, GL category, and supporting documents. The system then automatically routes that request through configured approval milestones covering finance, legal, IT security, and other required stakeholders, with approvals completable inside Airbase or integrated tools like Jira or DocuSign. …

Limitations: PO-to-invoice matching is an add-on feature available for an additional charge, so the buyer should confirm that 3-way matching is included in their tier if they intend to close the full PO lifecycle in Airbase rather than in NetSuite. …

Requirement evaluated: Blanket PO support for contract-based spending with release tracking against the total commitment

For a $250M technology company managing contract-based recurring spend across IT, facilities, and professional services, Airbase offers a single-PO-per-contract model rather than a true blanket PO with child release order architecture. A user creates a PO tied to a vendor engagement and sets a total approved amount; the platform then tracks an 'Available Balance' showing how much of that approved amount has been paid, what remains, and the amount in pending transactions, alongside configurable service start and end dates for the contract period. …

Limitations: Airbase's single-PO-with-available-balance model means this buyer cannot issue discrete release orders against a master contract commitment or track each release as a distinct procurement event with its own approval workflow; teams managing professional services contracts with monthly draw-downs or IT vendor SOWs with …

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: SSO integration with Microsoft Azure AD

For a $120M multi-location services company running Sage Intacct with an Azure AD identity infrastructure, Airbase delivers SAML 2.0 federation with Microsoft Entra ID (Azure AD) as the identity provider. Airbase supports both SP and IDP initiated single sign-on, meaning users can launch the login flow directly from the Airbase sign-on URL or be pushed from the Microsoft Entra My Apps portal. The configuration path runs through Entra ID > Enterprise Apps > Airbase > Single sign-on, where the admin selects SAML as the authentication method. …

Limitations: Airbase supports SCIM provisioning, but only on Enterprise plans starting around $8,500/year; while SCIM works with Okta, Entra ID, and Google Workspace, the Enterprise requirement creates a barrier for teams that need automated provisioning but cannot justify that price tier. …

Requirement evaluated: Role-based access control with entity-level restrictions

This buyer operates two separate Sage Intacct entities and needs to ensure that a user credentialed for Entity 1 cannot view or action invoices belonging to Entity 2. Airbase has a documented role-based permission model built around six predefined roles: Super Admin, Admin, Accountant/Finance, Manager/Budget Owner, Employee/Requester, and Auditor/Read-Only. The platform uses a fixed set of six predefined roles with no support for fully custom roles; granular access is achieved by combining a role with explicit budget and department scope assignments, not by toggling individual permissions. …

Limitations: The scoping dimensions documented for Airbase user permissions are budget and department, not ERP legal entity; no source confirms that invoice-level data visibility can be hard-restricted to one of the buyer's two Sage Intacct entities, which is the specific isolation this buyer requires. …

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 processing 1,800 invoices per month across two Sage Intacct entities, Airbase's fraud controls operate at two distinct layers with uneven depth. The first and most concretely documented layer is bank account change protection: Airbase's security feature page specifies that workflows can be configured to require approval of any vendor bank account change, and two-factor authentication is enforced for changes submitted through the vendor portal, with notifications sent to the finance team whenever account details are updated. …

Limitations: The bank account change workflow and 2FA control are clearly documented, but the buyer's requirement also covers amount spikes and unusual vendor behavioral patterns on AP invoices; Airbase's public documentation does not specify the mechanism, signal library, or quarantine workflow for those patterns, and the Inscribe …

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: Service receipt: time-based or milestone-based confirmation for professional services engagements

For a $250M technology company processing significant professional services spend, Airbase approaches service receipt confirmation through two layered mechanisms rather than a dedicated service receipt document type. First, the Guided Procurement module allows admins to configure milestone-based approval checkpoints across the procurement lifecycle: admins set milestones per spend category, and milestone completion triggers stakeholder notifications and sign-off requirements before the process advances. …

Limitations: The milestone system in Guided Procurement is primarily an intake and pre-purchase approval control; Airbase does not document a purpose-built service receipt document type that natively slots into the receipt leg of 3-way match for professional services, nor a time-based (e.g., monthly period attestation) …

Requirement evaluated: Exception routing when matches fail; price exceptions to procurement, quantity exceptions to receiving manager

For a $250M technology company moving off email-and-Slack approvals, Airbase provides automated 2-way and 3-way PO matching within its AP Automation module: invoices are captured via OCR, matched against synced NetSuite POs and receipts, and bills that fail the match are held from payment. Airbase "easily match[es] purchase orders, invoices, and receipts with automated 2-way and 3-way PO matching," designed to "strengthen internal controls, prevent overpayments, and speed up approvals by ensuring every invoice is tied to the correct PO and receipt." When a match fails, the bill enters Airbase's Advanced Approvals engine, which uses conditional "When...then..." rules to route to designated ap …

Limitations: The buyer's core requirement is a bifurcated exception queue: price mismatches route to procurement, quantity mismatches route to the receiving manager. Airbase's documented routing conditions (amount, department, vendor, GL, subsidiary) …

Requirement evaluated: Service receipt: time-based or milestone-based confirmation for professional services engagements

For a $250M technology company whose indirect spend is dominated by IT and professional services engagements, Airbase supports three-way matching through an invoice-PO-receipt workflow, but the receipt leg for services relies on human attestation rather than a dedicated time-period or milestone-tracking mechanism. When goods or services are received, a goods receipt note is created confirming arrival and quantity; for services specifically, the person who ordered the services verifies that what was received was in accordance with contract deliverables. …

Limitations: The receipt step for services appears to be a general human attestation routed through Airbase's Workflow Builder rather than a structured milestone or time-period confirmation module; buyers with professional services POs spanning multiple phases or recurring retainers will have no native mechanism to enforce delivery …

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

Your field team would use Airbase's native mobile app, available on iOS (15.1+) and Android, which Airbase describes as supporting 'an active on-the-go request and approval flow.' The app allows employees to create expense reports, capture receipts with the camera, manage card transactions, and track approval status from a smartphone. However, the upstream purchase request intake workflow — Airbase's Guided Procurement module, which is the mechanism for submitting a pre-purchase request before a PO is issued — is documented as a multi-step, multi-stakeholder web form ('Go to Request > Purchase, complete the Spend Intake form') with no documented equivalent in the native mobile app. …

Limitations: For a field team at a job site needing to initiate a new procurement request (not just capture a receipt or track an existing PO), Airbase's mobile app does not appear to support the full Guided Procurement intake form; the buyer should verify with Airbase whether the Spend Intake form is accessible and fully functiona …

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

For a $250M technology company whose field team needs to originate purchase requests from job sites, Airbase offers a native iOS and Android mobile app ("Airbase: Procure, Pay, Close") that covers expense submission and receipt capture from mobile devices. Airbase markets itself as a procure-to-pay solution with intake, AP automation, expenses, and corporate cards accessible on mobile. The Guided Procurement module is the relevant intake mechanism: it is a no-code, customizable workflow that directs any employee who wants to make a purchase to capture all necessary information and documentation, then routes purchase details to appropriate stakeholders for approvals. …

Limitations: The documented mobile-native capability skews toward approvals and expense/receipt capture rather than origination of new Guided Procurement intake requests from a job site; field employees at this technology company may need to fall back to a browser-based web interface to submit a full purchase request, and there is …