Question 1

We’ve acquired a dozen brands and they’re all on different systems. Do we have to consolidate first?

Accepted Answer

No. Each brand keeps the platform it runs on, and the agent works across all of them into one AR process, posting back to whichever ledger they roll up into. Adding the next acquisition means connecting it, not migrating it.

Question 2

Most of our invoices go through our customers’ AP portals. What can you actually do there?

Accepted Answer

Plenty of AP portals have no API, so the agent signs in the way your team does today, with credentials held per customer and isolated to your tenant. For customers whose remittance is locked inside a portal, it logs in and retrieves it, and a portal rejection reaches your queue as a reason to act on instead of a surprise weeks later.

Portal access is built per portal, so tell us which ones your customers put you in and we’ll confirm what’s involved.

Question 3

Our invoices are small — a few hundred dollars, thousands of them. Is that even worth automating?

Accepted Answer

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 sixty days many of them quietly become write-offs: real cash, never collected. The agent follows up on every invoice the same way regardless of size, so the long tail gets worked instead of written off.

Question 4

Does the agent act on its own, or does someone approve first?

Accepted Answer

You decide. Autonomy is a setting, not a default: replies can wait for a person to read and send, or go out automatically, and you set that per scenario rather than with one global switch. A person stays in front of anything you’re not ready to hand over.

Question 5

What happens when the agent isn’t sure what to do?

Accepted Answer

It escalates. When the agent hands something to your team, it hands over what it found, what it recommends, and why, so the person approving sees the decision in full. Every action and change is tracked, so a reviewer can reconstruct what happened to an invoice and who touched it.

Question 6

Do we have to replace our ERP or change how the team works?

Accepted Answer

No. Fazeshift isn’t another system of record. The agents work in the systems you already run: your ERP, bank, inbox, and customer portals. Your ERP stays the record, the agent writes back only the entries you’ve authorized, and if you turn Fazeshift off your records are exactly where they always were.

Question 7

Are you SOC 2 compliant?

Accepted Answer

Yes — SOC 2 Type II and SOC 1 Type II, and we’re GDPR compliant. Our auditor’s SOC 2 attestation letter is viewable on our Trust Center without a request, and the full reports are available on request, with the observation period stated on each.

Question 8

Do you train AI models on our data?

Accepted Answer

No. Your AR data doesn’t train anyone’s model: not ours and not 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 API calls.

Question 9

What access do you need to our email?

Accepted Answer

You approve the connection in your email provider’s own admin console. We hold a token, never a password, and you can revoke it from your side at any time without involving us. Every connection is one you grant, and one you can take back.

Question 10

How do you handle logins for our customers’ portals?

Accepted Answer

Where a portal offers an API, we use it. Many don’t, so the agent signs in the way your team does today. Those credentials are held per customer and isolated to your tenant.

Question 11

Do you support single sign-on?

Accepted Answer

Yes. Fazeshift supports enterprise SSO via SAML and OIDC, including Okta, Microsoft Entra ID, and Google Workspace, so your identity provider stays the front door.

Question 12

How are card payments handled?

Accepted Answer

Card payments in the Payment Portal run through Stripe, which is certified to PCI Service Provider Level 1. Fazeshift never stores raw card numbers.

Question 13

What happens to our data if we stop using Fazeshift?

Accepted Answer

Your ledger never moves: the agent reads what it needs and writes back only the entries you authorized, so turning Fazeshift off leaves your records exactly where they always were. Data held in Fazeshift is retained and deleted under policy, and the Trust Center covers the details for your security review.

Question 14

Which ERPs does Fazeshift work with?

Accepted Answer

We connect to NetSuite, Sage Intacct, QuickBooks Online, Dynamics 365 Business Central, and Xero, plus banks and customer portals, and customers also run Fazeshift on ERPs such as Epicor Eclipse and Trimble Viewpoint Vista.

Where a system offers an API, we use it; where it doesn’t, the agent works the screen the way a person would. A new ERP usually takes one to two months to add.

Question 15

How long does implementation take?

Accepted Answer

Most teams go live in 1–3 months, depending on scope, integrations, and complexity. We implement it with you, not at you, and your team decides which steps need a person’s approval before anything goes out.

Question 16

How is this different from rules-based AR automation?

Accepted Answer

Rules handle the payments that were always going to apply cleanly. Fazeshift is built for the rest: the short pays, the mismatched remittance, the lump-sum check covering several customers, the real judgment calls. The agent works off intent, so it adapts when a remittance format changes or a portal layout shifts, instead of sending the exception back to a queue.

Question 17

Can the agent apply payments that arrive without remittance?

Accepted Answer

Yes. The agent looks for the remittance wherever it actually arrived, in an email body, an attachment, or a customer’s portal, works out which invoices a payment covers, and posts the application to your ERP. When a payment is short, it applies what it can and flags the difference with the invoice detail and its reasoning attached.

Question 18

How does the agent decide how to follow up on an unpaid invoice?

Accepted Answer

By why it’s unpaid, not just how old it is. A deduction waiting on a credit memo, a short pay, a portal rejection, and a customer who’s simply slow each get a different next step, so outreach matches the reason instead of a blanket reminder.

Question 19

Can our customers pay us directly?

Accepted Answer

Yes. The Customer Portal is a hosted page where your customers see open invoices, pay by ACH or card, and pull their own statements, with each payment applying itself to the right invoice on the way in.

How the agents work

Security & data

Accounts receivable

See it run in your system