Accounts Payable Automation

Method: jurisdiction and activity comparison. FinCEN distinguishes data-processing software from money transmission, supporting the proposed federal operating boundary but not establishing overall launch lawfulness. Conditions to verify include maintaining no payment execution or custody, authorized invoice-data processing, applicable privacy and security requirements, business registration, tax obligations and provider terms. No state is selected, so applicable state requirements remain unresolved. BILL's contractual permissions and licences are not ours.

The supplied ruling is fact-specific and does not resolve all applicable federal or state launch requirements.

Method: workflow comparison. The source describes email or upload invoice capture, digital approval routing, and manual CSV import and export. Our proposed intake, duplicate checks and approval exports can therefore be delivered and supported online. This judgment assumes digital invoice submission and remote support; bank or provider payment operations remain outside our service.

The documented digital workflows directly match the narrow proposed service without requiring our own physical operations.

Method: regulatory role comparison. FinCEN states that the described software business provides 'data processing hardware and software and product networking services - not money transmitting services'. This supports distinguishing our software-only role from BILL's licensed transmission and custody activities. However, the supplied historical, fact-specific ruling does not establish that our exact role needs no special licence before the first client. State applicability and external-provider arrangements remain unverified.

Federal supporting guidance exists, but complete licensing applicability and a selected state are missing.

Method: revenue-mechanism comparison. BILL documents subscription fees and recurring billing; the comparison also documents invoice-based usage pricing. Our proposed prepaid subscription plus invoice-processing usage fees applies these mechanisms to repeated invoice intake and approvals, without requiring payment-transaction fees. This establishes a recurring mechanism, not validated demand or profitability.

Documented recurring charging structures directly support the proposed subscription and invoice-usage design.

Method: money-flow and obligation comparison. Our proposed prepaid software service neither advances vendor funds nor guarantees payment; execution stays with the client's bank or provider. BILL's funding, return and expedited-payment obligations concern its broader payment services and are not transferred to us. Pass assumes we do not contractually assume client payment defaults or provide advances; ordinary subscription refunds or disputes are distinct from lending.

The proposed boundaries exclude credit exposure, but our final customer and provider contracts are not supplied.

Method: product-role comparison. The documented invoice capture, duplicate flagging and approval functions are software controls, not insurance. Our proposal sells these functions and expressly excludes insurance. Pass assumes duplicate checks are not accompanied by promises to reimburse fraud or other insured losses.

The operating design excludes risk underwriting, although final contractual promises are unverified.

Method: custody-flow comparison. Our design receives payment for its own prepaid software service, not vendor-payment funds; client payments settle directly through an external operator. BILL's terms instead describe holding payment funds in its own custodial master account. That comparable-company custody is outside our proposed role. Pass assumes exports do not introduce collection, pooled balances or control over client funds.

The proposed flow clearly excludes custody, but implementation and provider contracts have not been verified.

Method: activity classification. The source documents invoice capture, matching and approval workflows, which match our proposed administrative software. Our revenue comes from software subscriptions and invoice processing, not trading. This judgment assumes the stated feature boundary remains unchanged.

The proposed core activity is clearly invoice administration rather than asset trading.

Method: buyer and function comparison. The source describes business finance workflows, consistent with our proposed small-business finance-team buyer. Our baseline provides private invoice-administration software, performs no government function and does not depend on government procurement. This is an assessment of the proposed buyer and service, not evidence of acquired customers.

The specified baseline clearly identifies a private-business function and customer segment.

Method: valuation-evidence check. BILL is a relevant functional comparable, and the source reports substantial business and payment scale. Neither supplied BILL document establishes a company valuation of at least $300 million. Payment volume, customer counts and published pricing are not company valuation; the other examples likewise lack qualifying valuation evidence.

No supplied evidence documents the required valuation threshold.