BILL (Bill.com) vs Expensify

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

For your 6-location services company with a 3-person AP team, BILL's approval workflow does support multi-level routing and the use of approval groups, where any member of a designated group can act on a pending bill. As documented in BILL's help center, approval groups let you assign a pool of approvers to a policy, and once any one member approves, the bill moves to the next stage. This provides coverage continuity when a named approver is unavailable. …

Limitations: For this buyer's audit and separation-of-duties needs across 2 Sage Intacct entities, the approval group workaround removes named-delegate accountability: the audit trail shows which group member acted, but not that they were acting as a bounded substitute for a specific absent approver, and there is no automatic rever …

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: 1099 preparation: automated classification, threshold tracking, and electronic filing

For a $120M services company processing roughly 1,800 invoices per month through BILL and syncing to Sage Intacct, the full 1099 workflow lives natively inside BILL's AP platform as of its December 2024 product launch. AP staff flag vendors as 1099-eligible directly in BILL, and an automated W-9 Agent can collect and AI-validate W-9s from vendors via email without leaving the platform. …

Limitations: For this buyer's 2-entity Intacct setup, 1099 vendor type selection is limited to NEC/Box 1 by default when a vendor originates in BILL; if the buyer has vendors requiring MISC classifications or non-standard boxes, those vendors should be created in Intacct first so the correct form type carries over. …

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: Export to Excel and scheduled report delivery to Controller and CFO

For a 3-person AP team processing 1,800 invoices monthly across two Sage Intacct entities, BILL covers one of the two sub-requirements here clearly and the other not at all. On ad-hoc export: BILL documents 'Export .CSV' and 'Export to Excel' options directly on the Bills page, the Payments Out page, and individual vendor-level bills and payments tabs, with pre-export filter and column-header selection so the AP team can shape the output before downloading. BILL also offers an Insights dashboard presenting AP financial data in eight charts, which can be exported, available to users with Admin or Accountant roles on Essentials, Teams, Corporate, and Enterprise plans. …

Limitations: BILL does not appear to offer scheduled, recurring report delivery as email attachments to named recipients (Controller, CFO); this buyer's stated need for automated push distribution is not met by any documented BILL mechanism, and recipients must log in and export manually each time. …

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. <cite index="1-1">The Insights dashboard provides a real-time overview of company spending across categories, employees, projects, and departments.</cite> The new Expensify platform documents these as separate Insights views: <cite index="2-1,2-2,2-3">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.</cite> Categorie …

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: Automatic combination of multiple approved invoices to the same vendor into a single payment, with the matching criteria used for combination clearly stated

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, BILL's payment consolidation works as follows: administrators enable the feature globally under Payables Preferences, then activate it per vendor by checking 'Combine payments' under Payment Processing on each vendor record. Once enabled, BILL automatically combines multiple approved bills to the same vendor into a single check or ACH (ePayment) disbursement. …

Limitations: BILL can combine a maximum of 35 bills per single consolidated payment; vendors with more than 35 open approved invoices in a payment run will require a second payment. Card payments (virtual card, BILL Divvy Card) …

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: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a multi-location services company processing ~1,800 invoices per month where rent, utility, and subscription vendors routinely reuse the same invoice number each billing cycle, BILL's duplicate detection operates as a global exact-match check on vendor + invoice number combination. When a bill is entered and the system detects a matching vendor and invoice number, it surfaces a duplicate warning; an approver can then deny the bill with the reason 'Duplicate bill' or the entry can be overridden manually at the point of creation. …

Limitations: No evidence was found of a per-vendor duplicate sensitivity setting, vendor-level exception list, or configurable duplicate check window in BILL's vendor profile or org settings; the recurring bill workaround only applies to bills BILL generates internally, not to externally-arriving invoices from rent or utility vendo …

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; <cite index="17-3,17-4">these rules are designed to standardize how expenses from common merchants are coded across the workspace, running automatically in the background.</cite> Second, Expensify's Concierge engine applies pattern-based learning: <cite index="23-1,23-2,23-3,23-4">categories repres …

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: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a company currently keying invoices manually from email and mail into Sage Intacct, BILL offers two stacked AI extraction layers. The first is the Intelligent Virtual Assistant (IVA): <cite index="10-1">a feature that uses machine learning to extract invoice information from documents in the Inbox.</cite> IVA attempts to pre-populate header-level fields including vendor name, invoice number, invoice date, due date, total amount, and payment terms. …

Limitations: <cite index="10-14">IVA will only make predictions for a bill from the first page of a document</cite>, requiring manual Click and Capture for multi-page invoices, which is a real friction point for subcontractor and facilities invoices that frequently run to multiple pages. …

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: SOC 2 Type II certification (current, not in-progress)

For a $120M multi-location services company evaluating BILL as its first AP automation layer, SOC 2 Type II is a completed, annually renewed audit rather than a point-in-time snapshot or an in-progress effort. BILL's dedicated security pages confirm that the company undergoes an annual SOC 1 and SOC 2 Type II audit by a leading national CPA firm, covering BILL Accounts Payable, BILL Accounts Receivable, and BILL Spend and Expense. The completed report is available to account administrators and accountants upon request, delivered under a non-disclosure agreement (NDA). …

Limitations: BILL does not publicly name the specific CPA firm conducting the audit (the security page references 'a leading national CPA firm'), and the full report is restricted-use under NDA rather than publicly downloadable. …

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: Integration setup assistance included in implementation; not a separate SOW or additional cost

For a $120M company running 2 Sage Intacct entities, BILL provides a pre-built, native Sage Intacct connector with a documented self-service setup process: the buyer creates a Web Services sync user in Intacct at the top/root level, assigns full module permissions, and configures the two-way sync for vendors, chart of accounts, departments, locations, and bills. …

Limitations: For this buyer's specific scenario, a 2-entity Sage Intacct environment, the evidence consistently indicates that hands-on integration setup assistance beyond self-service documentation is separately scoped and priced rather than bundled into the standard implementation fee; the buyer should require explicit written co …

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. <cite index="10-2">The integration can import standard dimensions like Department, Class, Location, Customer, and Project/Job, as well as user-defined dimensions.</cite> Inside Expensify, <cite index="1-1,1-2">dimensions are enabled in the Sage Intacct integration settings and can be assigned as Tags or Report Fields.</cite> For custom dimensions beyond Intacct's standard set, <cite index="19-46,19-47,19-48,19-49,19-50,19-51,19-52">User-Defined Dimensions ( …

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 …