How Expensify works

Requirement evaluated: Duplicate invoice detection across vendor, amount, date, and invoice number; must catch cross-entity duplicates

For a $120M services company processing vendor bills across 2 Sage Intacct entities, the buyer needs systematic duplicate detection that checks vendor identity, amount, date, and invoice number at bill ingestion, and that reaches across both entities to catch the same bill entered in Entity A and Entity B. Expensify does have a duplicate detection feature, but its documented scope is employee expense reports: it compares amount, currency, and date within a single member's account, and when receipts are scanned via SmartScan, it additionally checks merchant name, order or invoice number, card digits, and zip code. …

Limitations: The buyer's specific requirement, multi-field duplicate detection on vendor AP invoices spanning both Sage Intacct entities, is not addressed by any documented Expensify mechanism. …

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

For a multi-location services company processing 1,800 invoices/month through Sage Intacct, Expensify offers two mechanisms that partially address non-PO GL coding. First, Workspace Merchant Rules let an admin configure vendor-name-based coding rules that automatically apply category, tag, reimbursable status, and description fields when an incoming bill matches a configured merchant name pattern; these rules are designed to standardize how expenses from common merchants are coded across the workspace, running automatically in the background. …

Limitations: Workspace Merchant Rules require the AP team to manually configure a rule for every vendor upfront; the system does not learn from invoice history or adapt automatically, so new vendors and multi-line invoices with mixed expense types will receive no automatic coding suggestion until a rule is explicitly built. …

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

For a $120M services company routing 1,800 invoices per month through Sage Intacct and needing discrete exception categories (price variance, quantity variance, missing PO, missing receipt, duplicate, vendor mismatch), Expensify does not provide this mechanism in its AP bill-pay module. Expensify's bill workflow receives vendor invoices by email or forward to a domain billing address, codes them with GL categories from the connected accounting software, routes them through a workspace approval process, and exports them to Sage Intacct once approved. …

Limitations: Expensify's AP bill module provides no PO matching layer at all (2-way or 3-way), so none of the six exception categories (price variance, quantity variance, missing PO, missing receipt, duplicate, vendor mismatch) can be generated or routed automatically. …

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

For a $120M services company processing 1,800 invoices per month across two Sage Intacct entities, with 55% of invoices PO-based, Expensify's bill pay product covers three steps only: SmartScan capture of the vendor bill, routing through a workspace approval workflow, and export of GL-coded vendor bills to Sage Intacct. The help center documentation for Receive and Pay Bills describes this flow as: vendor emails a bill to a dedicated address, SmartScan creates the bill record, a primary contact reviews and approves it, and the bill is exported with GL codes from the connected accounting system. …

Limitations: All six exception categories the buyer specified require a PO matching and receipt confirmation layer that Expensify does not have: the product has no PO database integration, no goods receipt stage, and no structured exception taxonomy for invoice discrepancies. …

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

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, the buyer's requirement is a system-triggered, time-based escalation: if an approver has not acted within 48 hours, the pending item is automatically rerouted to their manager with a notification. Expensify's approval architecture does not contain this mechanism. The platform offers three approval modes: Submit and Close, Submit and Approve, and Advanced Approval. …

Limitations: For this buyer's 1,800-invoice-per-month operation, the absence of a time-based escalation engine is a material process gap: invoices awaiting approval simply sit in the queue with no system-enforced consequence for inaction beyond a manual nudge. …

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

For a multi-location services company processing roughly 1,800 invoices a month across 6 offices, Expensify's bill approval model routes each vendor bill individually through the workspace approval chain. When a vendor sends a bill to the company's Expensify billing address, Expensify SmartScans the document, creates a bill record, and submits it to the primary contact for review on the Reports page; from there it follows the configured workspace approval process one bill at a time. …

Limitations: There is no documented mechanism in Expensify for an approver to select a set of invoices from the same vendor (e.g., 6 location-level telecom bills) and approve them in one action; each bill moves through the approval chain individually, which replicates the sequential email-based review pattern this buyer is trying t …

Requirement evaluated: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

For a 3-person AP team at a $120M multi-location services company processing 1,800 invoices per month through Sage Intacct, Expensify offers role-based separation and workflow enforcement that partially addresses segregation of duties. On the submitter-vs-approver control: Expensify's Advanced Approval mode lets workspace admins configure per-person approval chains, and a 'Prevent Self-Approval' setting explicitly blocks an approver from approving their own report, enforcing the first SoD boundary (Expensify Help: Approve Expenses). …

Limitations: The admin override clause ('Admins can still take control of reports') means the enter-cannot-approve SoD boundary is not a hard system control if the data-entry person holds Workspace Admin rights, which is common in a 3-person AP team where at least one member must be an admin to configure the workspace. …

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

For a multi-location services company needing four discrete authority tiers tied to invoice dollar amounts, Expensify offers its Advanced Approval mode, which supports multi-level, conditional approval chains. Within this mode, each workspace member can be configured with a 'Submits To' first-level approver and an 'If report total is over $X, then Approves To' escalation rule, allowing a chain to be built where a $75K invoice escalates from manager to director to VP to CFO in sequence. Vendor bills are confirmed to follow the same workspace approval process as expense reports. …

Limitations: The buyer's four-tier DOA requires that, for example, a $60K invoice routes directly to the CFO with no manager or director involvement. Expensify's documented mechanism routes every invoice to the submitter's designated first-level manager first, then escalates up through each successive threshold rule, so lower-autho …

Requirement evaluated: Payment approval workflow: all payment batches require CFO or Controller electronic approval before release; approval thresholds can be set per bank account

For your 1,800 invoices a month and bi-weekly check and monthly ACH runs in Sage Intacct, Expensify's Bill Pay creates a bill from each emailed vendor invoice, and the bill follows your workspace's approval process. That means bills go through the same workflow as expense reports. Each report must be approved by every person in its workflow before it can be paid, and you can add another approval level when a report exceeds a set amount. Payment is then made by connecting a business bank account and selecting an authorized payer, who must be a Workspace Admin with access to that account. This covers legitimacy review and coding (pre-processing stages 1 and 5) at the bill level. …

Limitations: Approval limits attach to workspace members, and the authorized payer and auto-pay threshold are set per workspace. I found no documented per-bank-account approval thresholds and no batch-level CFO or Controller release gate for check and ACH runs. …

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

Your company runs bi-weekly check runs through Bank of America and needs a positive pay file exported in Bank of America's required format after each run. Expensify's documented payment methods for vendor bills are ACH bank transfer, credit/debit card, and Venmo. Expensify's own help center documentation states explicitly that the platform does not issue checks: 'Expensify does not issue checks. Workspace Admins can select Pay elsewhere and issue a check outside Expensify.' Because Expensify has no check issuance capability, it has no check register from which to derive a positive pay file. …

Limitations: Expensify's payment infrastructure is built entirely around electronic rails (ACH, card, Venmo). Because it does not issue checks, the precondition for positive pay file generation, a system-of-record check register, does not exist within the platform. …

Requirement evaluated: Automatic remittance advice sent to vendors upon payment

For a $120M services company processing 1,800 invoices per month, the specific requirement is that vendors receive automatic, invoice-level remittance detail (invoice numbers, amounts, payment method) at the moment a bill is paid. Expensify's Bill Pay workflow covers the buyer side: vendors email invoices to a domain-specific Expensify address, the bill is SmartScanned and routed for approval, and payment is executed via ACH, card, or check. Once paid, the bill moves to a 'Paid' status and syncs to connected accounting software. However, across Expensify's entire bill pay documentation, no mechanism exists that sends an outbound remittance advice to the vendor upon payment completion. …

Limitations: There is no documented mechanism in Expensify Bill Pay for sending an outbound remittance advice to external vendor email addresses upon payment execution, meaning your AP team would still need to manually notify each vendor of payment details after every check run or ACH batch, exactly the manual burden this requireme …

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

For a $120M services company processing 1,800 vendor invoices per month through Sage Intacct, Expensify does offer an Auto Sync mechanism that writes payment data back to Intacct: when Auto Sync is enabled and reimbursement is processed via Expensify ACH, the system automatically creates Bill Payment records in Sage Intacct and marks the corresponding reports as Paid on the next sync. However, this writeback mechanism is architecturally tied to Expensify's employee expense reimbursement workflow. …

Limitations: The Auto Sync payment writeback to Sage Intacct covers employee reimbursements and Expensify Card activity only; it does not extend to vendor invoice payments executed via check runs or ACH batches to third-party vendors, which is the buyer's primary AP workload. …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a $120M services company processing 1,800 AP invoices per month across two Sage Intacct entities, Expensify offers an Insights module with three pre-built views that map directly to the buyer's stated analytics needs: Spend over time (total spending changes over a selected period), Top Spenders (members with highest spending), and Top Merchants (which vendors account for the most spending). Spend over time supports month-level grouping as the default, with quarter and year options as well. Top Categories shows which expense categories had the highest total spend, reporting all categories sorted by total spend and number of expenses. …

Limitations: Expensify's Insights analytics are documented exclusively in terms of employee expense and card spend data; no help documentation confirms that AP vendor bills (the buyer's primary transaction volume at 1,800 invoices/month) …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a services company running 1,800 AP invoices per month across two Sage Intacct entities, Expensify's Insights module provides three pre-built reports that map to the buyer's stated analytics needs. The Top Merchants report groups all expense data by vendor and surfaces the highest-spend merchants for the prior calendar month; the Top Categories report groups expenses by expense category (which maps to GL accounts synced from the connected accounting system) and ranks by total spend; and the Spend Over Time report shows how total expenses change across a selected date range, with group-by:month, group-by:quarter, and group-by:year operators available for period-comparison trending. …

Limitations: For a buyer whose AP volume (55% PO-based, 45% non-PO, totaling 1,800 invoices per month across 2 Sage Intacct entities) is the primary analytics data source, Expensify's Insights module covers only the spend that flows through Expensify itself; any invoices processed or posted natively in Sage Intacct are invisible to …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a $120M services company processing 1,800 AP invoices per month in Sage Intacct, Expensify surfaces spending data through its Insights module, which provides pre-built reports including Top Merchants, Top Categories, and Spend Over Time. The Insights dashboard provides a real-time overview of company spending across categories, employees, projects, and departments. The new Expensify platform documents these as separate Insights views: Spend Over Time shows how total expenses change over a date range, Top Merchants shows which vendors received the most payments, and Top Categories shows the highest-spending expense types. …

Limitations: Expensify's Insights reports are built primarily around employee expense and corporate card data, not around AP invoice workflows: the buyer's 1,800 monthly vendor invoices (facilities, utilities, subcontractors) …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a $120M multi-location services company running 1,800 invoices/month through Sage Intacct, Expensify's Insights module provides three pre-built reports that address the three sub-requirements directly. The 'Top Merchants' report shows which vendors received the most payments; the 'Top Categories' report shows all expense categories sorted by total spend (these categories map to GL accounts imported from Sage Intacct, so the view is effectively spend by GL account); and the 'Spend over time' report displays how total expenses change across a selected date range, enabling month-over-month comparison with a Line chart view option. …

Limitations: Pre-built Insights reports default to the previous calendar month and surface the top 10 results per view; broader trending requires building custom saved searches. …

Requirement evaluated: Integration setup assistance included in implementation; not a separate SOW or additional cost

For your 2-entity Sage Intacct environment, Expensify's Sage Intacct connection is a documented self-service setup that the vendor does not price as a separate project. The admin creates a web services user, enables Customization Services (and Time & Expenses if exporting expense reports), downloads the Expensify package, uploads it to Intacct, and enters credentials in Workspaces > Accounting (Expensify Help: Connect to Sage Intacct). Expensify's Control workspace guidance says Control plan users get an Account Executive to assist with onboarding, reachable in the workspace's #admins room (Expensify Help: Playbook for Small to Medium-Sized Businesses). …

Limitations: The documented assistance is a general onboarding Account Executive plus self-serve checklists, not a scoped, hands-on Intacct implementation. The Sage-side prerequisites (web services user, Customization Services, and possibly a separately paid Time & Expenses subscription from Sage) …

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

For a $120M multi-location services company running 1,800 external supplier invoices per month through two Sage Intacct entities, Expensify's Sage Intacct integration does document support for all five standard dimensions the buyer named. The integration can import standard dimensions like Department, Class, Location, Customer, and Project/Job, as well as user-defined dimensions. Inside Expensify, dimensions are enabled in the Sage Intacct integration settings and can be assigned as Tags or Report Fields. For custom dimensions beyond Intacct's standard set, User-Defined Dimensions (UDD) …

Limitations: The buyer's core use case, routing and coding externally received supplier invoices (PO-based and non-PO) through a pre-processing workflow before posting to two Sage Intacct entities, sits outside the scope of what Expensify is built to handle; Expensify's Sage Intacct connector is designed for employee reimbursements …

Requirement evaluated: Integration setup assistance included in implementation; not a separate SOW or additional cost

For a $120M multi-location services company running 1,800 AP invoices/month across 2 Sage Intacct entities, the relevant question is whether Expensify's Sage Intacct integration setup requires a separately billed engagement. Expensify's Sage Intacct connector is self-serve: the buyer creates a web services user in Sage Intacct, enables Customization Services, downloads and uploads an Expensify integration package, adds web services authorization, and configures sync options, all following a documented step-by-step guide with no stated professional services fee for the connector itself. …

Limitations: The material shortfall is product fit, not cost: Expensify's Sage Intacct integration is oriented toward expense management and corporate card reconciliation, not toward AP invoice automation. The integration setup assistance (Account Executive, self-serve wizard) …

Requirement evaluated: Integration setup assistance included in implementation; not a separate SOW or additional cost

For a $120M multi-location services company needing AP automation, this requirement has two layers: the commercial packaging question and the scope of what actually connects to Sage Intacct. On packaging: setup specialists are included in both Collect and Control plans at no additional cost, and no published implementation fees exist. The Sage Intacct integration itself is gated to the Control plan, and Expensify's help documentation directs customers to schedule a free onboarding session with an Account Executive rather than purchase a separate professional services SOW. …

Limitations: The absence of a separate SOW reflects the fact that the Sage Intacct connection is self-serve and documentation-driven, with an Account Executive session available but no dedicated integration engineer configuring the connection on the buyer's behalf. …

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

For a $120M services company processing 990 PO-based invoices per month and targeting 40%+ zero-touch throughput, Expensify does not provide the mechanism this requires. Expensify's vendor bill workflow works as follows: a supplier emails a bill to a domain-specific address, SmartScan OCR captures header-level data (amount, date, merchant), and the bill is then submitted to a primary contact who reviews it on the Reports page before it follows the workspace approval process and is exported to Sage Intacct. …

Limitations: Expensify has no PO matching engine of any kind: no 2-way match, no 3-way match, no configurable tolerance thresholds, and no auto-posting for invoices that clear a match. …

Requirement evaluated: AI/OCR-powered extraction from PDF, image, and email-embedded invoices with 95%+ accuracy on header and line-item data

For a services company processing 1,800 invoices per month, Expensify's SmartScan technology provides the capture layer. Vendors can email bills directly to a company-specific address (domain.com@expensify.cash), and Expensify automatically SmartScans the document and creates a bill record ready for the approval workflow. PDFs can also be uploaded via drag-and-drop on the web, and the receipts@expensify.com forwarding address handles email-attached documents. However, every documented source -- including Expensify's own help center -- describes SmartScan's extraction output as header-level fields only: merchant name, date, total amount, and currency. …

Limitations: SmartScan's documented extraction covers header fields (merchant, date, total, currency) only; no line-item extraction capability is documented at any plan level, which directly blocks the buyer's requirement for 95%+ accuracy on both header and line-item data and prevents automated PO-line matching for the 55% of invo …

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

For a services company receiving invoices across four formats, Expensify's SmartScan OCR engine handles two of the four channels this buyer requires. Standard digital PDFs and scanned image files (JPG, PNG) can be submitted by dragging and dropping files into the app, photographing them via the mobile camera, or by having vendors email their PDF invoices directly to a domain-specific capture address (yourcompany.com@expensify.cash), which SmartScan automatically converts into a bill ready for review and payment. …

Limitations: EDI invoice ingestion (ANSI X12 810) is entirely absent from Expensify's documented capabilities, meaning the buyer's 3 large subcontractor invoices would require manual re-keying or a separate, independently contracted EDI middleware solution outside Expensify. …

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

For a multi-location services company processing 1,800 vendor invoices per month in Sage Intacct, Expensify's SmartScan technology is the capture mechanism. A vendor bill is uploaded (photo, drag-and-drop PDF, or forwarded email to receipts@expensify.com), and SmartScan uses OCR to automatically extract the merchant name, date, and total amount, then creates a bill record that follows the workspace approval workflow before being coded with GL codes from the connected accounting system and exported to Sage Intacct. …

Limitations: SmartScan's documented extraction covers header-level fields (vendor name, date, total amount, currency) for the buyer's AP scenario; invoice number, PO number, individual line-item extraction, tax line separation, and payment terms are not documented as auto-extracted fields from vendor bills, meaning AP staff would n …

Requirement evaluated: Multi-factor verification for banking change requests; we need systematic fraud prevention, not email-based trust

For a $120M multi-location services company running 1,800 invoices per month through Sage Intacct, the specific requirement is a systematic gate on vendor banking detail changes: an MFA challenge, dual-control approval, verified supplier portal, or out-of-band callback that prevents a fraudulent bank change from reaching a payment run without human-verified authorization. Expensify offers TOTP-based 2FA for platform login — requiring a code from an authenticator app each time a user signs in — but this is a session-entry control, not a per-event challenge scoped to banking changes. …

Limitations: Expensify's banking verification architecture is oriented toward the company's own reimbursement bank account and employee deposit accounts, not toward a supplier banking master data workflow. …

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 fielding vendor status calls at 6 hours per week, the critical mechanism needed is one that gives vendors direct, self-service visibility into invoice status, so they never need to call AP in the first place. Expensify documents two communication touchpoints, neither of which addresses this. On the bill-pay side (the buyer's AP workflow), the help documentation states that approvers can communicate with the bill sender via a comment thread linked to the bill record; however, this is an internal approver-to-submitter mechanism, not a vendor-facing status channel. …

Limitations: Expensify has no vendor-facing self-service portal or communication log for the AP direction; vendors cannot check invoice or payment status without contacting the buyer's AP team, meaning the 6-hours-per-week problem remains entirely unaddressed. …

Requirement evaluated: Centralized vendor master synchronized bidirectionally with Sage Intacct

For a $120M multi-location services company running 1,800 AP invoices per month across two Sage Intacct entities, the requirement is a centralized supplier vendor master that stays in sync with Intacct in both directions: new vendors created in Expensify push to Intacct, and vendor record changes made in Intacct pull back to Expensify. Expensify's Sage Intacct integration does not operate in this space. The integration is purpose-built for employee expense management: it imports chart-of-accounts categories, dimensions (departments, locations, projects), and employee records from Intacct into Expensify, then exports approved expense reports or reimbursable vendor bills back to Intacct. …

Limitations: Expensify has no AP vendor master module at all: its Intacct integration pulls coding dimensions and employees from Intacct and pushes expense transactions outward, but supplier record creation and management for AP payables remains entirely outside its scope. …

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For a $120M services company with a 3-person AP team processing 1,800 invoices/month, the vendor self-service portal requirement covers five discrete sub-capabilities: new vendor registration, W-9/W-8 collection, banking detail entry, vendor-initiated invoice submission, and payment status inquiry. Expensify's documented mechanism for vendor invoice intake is an email-inbox model: the buyer shares a dedicated billing address (domain.com@expensify.cash) with vendors, vendors email their invoices to that address, and SmartScan automatically creates a bill inside Expensify for internal AP review. …

Limitations: Expensify has no external supplier self-service portal; all five sub-capabilities in this requirement (registration, W-9/W-8, banking entry, invoice submission, and payment status inquiry) remain manual workflows handled by the buyer's AP team, which defeats the purpose of vendor self-service for this team. …

Requirement evaluated: Data encryption at rest and in transit

For a multi-location services company moving invoice and financial data through Expensify, encryption is applied at both layers the buyer requires. For data in transit, Expensify enforces HTTPS+TLS across all web connections, covering browser-to-server traffic and inter-server communication within its network. For data at rest, Expensify uses a dual-control encryption key architecture: the key is split into two parts, each stored in a separate secure location and managed by different Expensify employees, so stored financial data cannot be accessed outside the vendor's secured servers. …

Limitations: Expensify's published documentation does not specify the exact cipher standard (e.g., AES-256) used for data at rest, nor does it document whether customer-managed encryption keys are available, which may matter to buyers with specific key-management requirements in their security policy. …

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

For a $120M services company with 2 Sage Intacct entities, Expensify's entity-level separation works through a workspace-per-entity model: if your Sage Intacct account supports multiple entities, you can connect each Workspace in Expensify to a specific entity or to the Top Level. Users are then added to one or more workspaces with a role assigned per workspace, so a user added only to the workspace connected to Entity 1 cannot see data in the workspace connected to Entity 2. Within each workspace, roles include Member (can submit and/or approve expenses), Admin (can manage members, roles, workflows, and settings), and Auditor (can view and comment on reports but cannot make changes). …

Limitations: For this buyer's AP automation use case, the role set (Member/Admin/Auditor) is built around expense submission and approval, not the distinct AP staff roles (coder, approver, payment releaser) …

Requirement evaluated: SSO integration with Microsoft Azure AD

For a 200-employee, multi-location services company standardized on Microsoft Azure AD, Expensify supports SAML 2.0 federation with Azure AD (Microsoft Entra ID) as the identity provider. Expensify is listed as a pre-built enterprise application in the Microsoft Entra gallery: an IT administrator adds the Expensify app, downloads the Entra Federation Metadata XML, and pastes it into the Identity Provider Metadata field under Expensify's Domain Control settings, where SAML Login is toggled enabled and 'Required for login' can be enforced to block all non-SSO access for domain members. …

Limitations: Two material gaps apply for this buyer: first, automated deprovisioning (the offboarding loop that prevents a terminated employee from retaining Expensify access) …