Fazeshift Answers
Straight answers about AI agents for AR
The questions finance teams ask us most on calls, answered directly: what Fazeshift is, how it works, how it compares, who it fits, how buying works, and the proof behind it.
Last reviewed
What Fazeshift is
Fazeshift is an AI-native platform for accounts receivable and B2B order-to-cash. Its AI agents apply cash, run collections, answer the AR inbox, run a customer payment portal, and turn signed contracts into invoices, working inside the ERP, bank, inbox, and portals a finance team already uses.
Your ERP stays the system of record. The agents do the work between invoice and cash and hand the cases that need judgment to your team.
It reads what arrives, decides what to do, and does it inside your systems. A payment comes in with remittance buried in an email: the agent finds it, works out which invoices it covers, and posts the application to your ERP. A customer emails asking for an invoice copy: the agent drafts the reply with the copy attached. An invoice is late because of a missing PO: the agent asks for the PO instead of sending another reminder.
When it isn’t confident, it escalates to a person with what it found and what it recommends.
No. It takes the repetitive work off the team so the same people can handle more volume and spend their time on the cases that need judgment: disputes, key accounts, and credit decisions.
PDQ grew through major acquisitions without adding finance headcount. AdVon’s AR capacity per person more than tripled.
No. Your ERP stays the system of record. Fazeshift reads open AR from it and writes its work back, so if you ever turn Fazeshift off, your records are exactly where they always were.
It does both, through the systems you already use. The customer portal takes ACH and card payments through Stripe, and Fazeshift never stores raw card numbers. For billing, the agent reads signed contracts and drafts invoices and subscriptions in the system you bill from, such as QuickBooks, NetSuite, or Stripe, for your team to approve.
Fazeshift is purpose-built for B2B organizations with complex accounts receivable operations.
We work best with businesses managing high invoice volumes, multiple entities, complex payment matching, customer disputes, and manual collections workflows.
Whether you’re scaling transaction volume, expanding into new markets, or looking to improve working capital, Fazeshift helps your finance team operate more efficiently without adding proportional headcount.
Fazeshift was founded in 2023 by Caitlin Leksana (CEO) and Timmy Galvin (CTO), and went through Y Combinator’s Summer 2024 batch. It has raised $27M from investors including F-Prime Capital, Gradient Ventures, Amex Ventures, and Y Combinator, and has offices in San Francisco and New York. The whole team, including the deployment team that implements Fazeshift with customers, is based in the U.S.
How it works
Through the connections you approve. Fazeshift connects to your ERP, your bank and lockbox feeds, your AR inbox, and your customers’ portals. Where a system has an API, it uses the API. Where it doesn’t, the agent works the screen the way a person would.
Email access is a token you approve in your email provider’s admin console, and you can revoke it at any time.
Fazeshift integrates with more than 20 ERPs and business systems. They include NetSuite, Sage Intacct, QuickBooks Online, Xero, Microsoft Dynamics 365, SAP, Oracle Fusion, Acumatica, Workday, Deltek Vantagepoint, Epicor Eclipse, and Epicor Prophet 21, plus industry systems like ServiceTitan, Bullhorn, and McLeod LoadMaster.
Fazeshift reads open AR from your ERP and writes its work back, so your ERP stays the system of record. Don’t see yours? We can build it: tell us what you run and what needs to flow back and forth, and adding it usually takes one to two months.
Its work: payments and their applications, journal entries, credit memos, deposits, invoices, and attachments. It writes only the entries you’ve authorized.
Collection notes, promise-to-pay dates, and dispute status stay in Fazeshift, so your ERP isn’t cluttered with collections activity.
Yes. Where a system or portal has no API, the agent signs in and works the screen the way your team does today, with credentials held per customer and isolated to your account. Adding an ERP we haven’t connected before usually takes one to two months.
From wherever they actually arrive: bank and lockbox files, email bodies and attachments, scanned checks, screenshots, and customers’ AP portals. The agent reads each one, works out which invoices a payment covers, and hands it to cash application.
Across customers, Fazeshift has detected and routed more than 170,000 email remittances into cash application.
The agent matches it from the amount, the customer’s payment history and the open invoices on the account, and applies it when it’s confident. When it isn’t, it sends the payment to a person with the candidate invoices and its best-fit recommendation, so the decision takes seconds instead of a search.
Yes. The agents submit invoices into portals such as Coupa, SAP Ariba and ServiceChannel with the PO and documents your customer requires, track approval, fix and resubmit rejections, and retrieve remittance and payment status. Where a portal has no API, the agent signs in the way your team does, with credentials held per customer and isolated to your account. Portal access is set up portal by portal, so tell us which ones your customers use and we’ll confirm what’s involved.
You decide, scenario by scenario. Cash applications and customer emails can wait for a person to approve, or run automatically for the cases you trust, and you set that per type of work rather than with one global switch.
Most teams start with review on and turn on automatic posting or sending for the cases they trust after they’ve seen the results. Payments customers make in the portal apply themselves, because the customer picked the invoices.
When it isn’t sure, it escalates: the person reviewing sees what the agent found, what it recommends, and why. When a person corrects it, that decision is recorded with their name and becomes the rule the next time the same case comes up. Every action and change is kept in the audit history, so a reviewer can reconstruct what happened to any invoice or payment.
From two places: setup, and your team’s decisions. In scoping sessions, we capture your dunning rules, posting conventions, and customer quirks, such as the parent company that pays for its subsidiaries or the customer who always short-pays freight. After go-live, every decision your team makes on an escalation becomes the rule for the next one like it.
By why each invoice is unpaid, not just how old it is. A dispute pauses the reminders, a missing PO gets a request for the PO, cash that’s already in and unmatched gets matched instead of chased, and a customer who’s simply slow gets a friendly, specific follow-up. High-value and high-risk invoices go to the top of your team’s list.
Yes. Collections emails go out from your own email domain, so customers see them coming from your team, and you set the tone the agent writes in.
It reads every message, works out what the customer needs, and drafts the reply with the real answer: the balance, the invoice copy, or the status of their payment. Remittance in an email goes straight to cash application. Angry or complicated messages go to the top of your team’s queue with a suggested reply, and nothing goes out on them until a person decides it should.
Across customers, the agents have read and triaged more than 1.4 million inbound AR emails.
By ACH or card, for one invoice or many in a single transaction, with autopay and saved payment methods they manage themselves. Each payment is tied to the invoices the customer picked, so it arrives already matched: about 99% of portal payments apply themselves to the correct invoice. More than 1,700 business customers have paid through it.
Yes. The agent reads the signed contract from your CRM, pulls the terms that drive billing, and drafts the invoice or subscription in the system you bill from, including QuickBooks, Stripe, Zuora, NetSuite, Sage Intacct, and Xero. A person approves each one before it’s issued, and anything ambiguous, like an escalator the contract doesn’t fully define, is held for review. It has read more than 1,175 signed contracts so far.
How it compares
Traditional AR automation focuses on automating individual tasks. Fazeshift goes further by using AI agents to understand context, make decisions within defined controls, and execute complex workflows across your finance operations.
From investigating payment discrepancies to resolving collections issues and processing remittances, Fazeshift doesn’t just identify what needs attention. It helps execute the work required to move it forward.
Fazeshift is AI-native and built for complex B2B order-to-cash: it connects context across your ERP, bank, inbox, and portals to find why cash is stuck, then executes the next step, with a U.S.-based deployment team that fits it to how you work.
We’ve written a comparison with each of these tools, including the questions worth putting to every vendor on your list.
RPA follows a fixed script: click here, copy this field, paste it there. It breaks when a screen changes or a case doesn’t fit the script. An agent understands what’s on the screen or in the document, makes a judgment call, and escalates when it isn’t sure, so it keeps working on the cases a script can’t handle.
ERP modules send the same reminder sequence to everyone and match payments one invoice at a time. That works until customers pay in lump sums, remittance arrives by email, or invoices are stuck for reasons a reminder won’t fix.
In one Fazeshift deployment at a B2B services company, replacing the ERP’s built-in dunning with cadence by account and matching built for multi-invoice lump sums took DSO from 120 days to 16 in five months, while AR grew about 25%.
Use cases and fit
Mid-market and enterprise B2B companies with complex receivables: high invoice volumes, multiple entities, payments that are hard to match, and customer disputes. Fazeshift also fits high-growth companies that want to scale AR without adding proportional headcount.
Industries where payments are hard to apply and invoices get stuck: construction, field services, logistics, technology, staffing, wholesale distribution, and manufacturing. Each has its own patterns, like retainage and pay apps, remittance by worker and week, or deductions on every payment, and the agents are set up for them.
Usually that’s where it pays off most. When there are more small invoices than a team can work by hand, the small ones wait, and past 60 days many quietly become write-offs. The agent follows up on every invoice the same way regardless of size, so the long tail gets worked instead of written off.
Yes, and most teams do. Cash application or collections is the usual first step, connected to your ERP, bank, and AR inbox. Once it’s running and the numbers have moved, you add the next agent on the same connections.
No. Each business keeps the system it runs on, and the agents work across them, posting back to whichever ledger each one rolls up into. Adding the next acquisition means connecting it, not migrating it.
Yes. Fazeshift supports multi-currency and multi-entity AR operations, helping finance teams manage complexity across business units, geographies, and financial systems.
Buying and evaluation
Most teams go live on their first workflows in one to three months. Timing depends on your ERP, bank, and portals, and most teams start with one workflow, such as cash application or collections. Our U.S.-based deployment team scopes it with you on the first call and runs the setup with you.
Mostly approvals and scoping sessions. IT approves the connections in your own admin consoles: ERP, bank feeds, and email. Your AR team joins scoping sessions where we rebuild your rules and posting conventions with you. Then the agents run against your own history, so you can review what they would have done before anything posts.
Fazeshift offers flexible, modular pricing based on the solutions you need, the complexity of your workflows, and the scope of your operations. Our pricing isn’t based on seats or AI token usage, so you can bring your entire team onto the platform with unlimited users.
For most teams, yes, because the agents scale with volume and a hire doesn’t. One person covers a fixed number of accounts. The agents work every invoice and payment, every day, and hand your team only what needs judgment.
AdVon got 80+ hours a month back and more than tripled AR capacity per person. PDQ cut manual cash application work by about 75%.
Yes. Our implementation team runs the switch with you. Your open invoices, customers and payment history load from your ERP, we rebuild your collections rules with you, and we plan the cutover of payment links and portals so your customers know where to pay. Many teams time go-live to the end of their current contract.
We believe successful AI adoption requires more than deploying software.
Fazeshift combines forward-deployed engineers, AI deployment strategists, and ongoing customer support to embed AI directly into your finance operations.
Proof and trust
Here are a few, all from production.
• PDQ cut manual cash application work by about 75%, moved AR meetings from weekly to monthly, and brought DSO to the lowest the company has seen.
• AdVon more than tripled AR capacity per person and collected 20% more AR on time.
• Adswerve manages more than 950 customer accounts with a lean accounting team.
• A growing software company took DSO from 94.6 days to 23.6.
• A commercial elevator and escalator service company took DSO from 114.9 days to 90.1 and posts 96% of payment runs the same day.
Customers typically see 90–95% of their cash application automated.
The agent applies a payment on its own only when you’ve allowed it to and it’s confident. Everything else goes to your team with its recommendation attached.
Across customers, the agents have read and triaged more than 1.4 million inbound AR emails, routed more than 170,000 email remittances into cash application, and read more than 1,175 signed contracts. More than 1,700 business customers have paid through the Fazeshift portal.
Yes. Fazeshift is SOC 2 Type II and SOC 1 Type II compliant, and GDPR compliant. We carry SOC 1 because Fazeshift touches your financial reporting. The auditor’s attestation letters are on our Trust Center, and the full reports are available on request.
No. Your AR data doesn’t train anyone’s model, ours or our providers’. Fazeshift runs on models from OpenAI and Anthropic under zero-data-retention agreements, which bar training on your data and bar the provider from storing the inputs and outputs of our calls.
In the United States, encrypted and kept separate for each customer. Your team signs in through enterprise SSO (SAML or OIDC, including Okta, Microsoft Entra ID, and Google Workspace) if you use it. Customers who pay through your portal get their own login and only ever see their own account.
Yes. Every action an agent takes is recorded with the evidence behind it, the remittance, email, or portal record, and when it happened. When someone on your team changes a decision, that’s recorded with their name. A reviewer can reconstruct what happened to any invoice or payment from the audit history.
Your records stay where they always were, because your ERP is the system of record. You switch off the connections from your own systems, and the data in your Fazeshift account is deleted under our retention policy, except where the law requires a record to be kept longer.
Have a question that isn’t here?
Bring it to a call, along with your hardest AR case. We’ll answer it, and add it here if other teams are asking too.
90–95% of cash application automated: the range customers typically see.