Switching from Billtrust
Leaving Billtrust? We’ll move you over.
Our implementation team runs the switch. Your AR data loads from your ERP, we rebuild your collections rules with you, and we plan the cutover so your customers know where to pay.
Why teams move from Billtrust to Fazeshift
What teams on Billtrust tell us they’re looking for.
Every payment, not just portal payments
Checks, ACH, wires and virtual cards are applied too, with remittance read from check images, stubs and email, so your automation doesn’t depend on how customers choose to pay.
An AR inbox that answers itself
Requests for invoice copies, statements and W-9s are answered with the document attached, and what the emails reveal reaches collections.
Built for complex B2B receivables
High invoice volumes, multiple entities, hard-to-match payments, disputes and customer-specific rules: Fazeshift is built for the AR work that doesn’t fit a simple rule.
What comes over, and where it comes from
Most of your AR data already lives in your ERP, so that’s where we start.
From your ERP
Open invoices, customers, contacts and payment history load from your ERP, the system of record. Your old AR tool usually copied them from there anyway.
From Billtrust
We only need what your ERP doesn’t hold, such as your email template wording, collections notes, and the format your ERP expects when payments post.
Rebuilt with you
Dunning rules and workflows don’t import from another tool. We rebuild them with your team in scoping sessions, which is a good moment to fix the ones that never worked.
How the switch works
Five steps from kickoff to go-live
Most teams go live on their first workflows in one to three months, depending on your ERP, bank and portals. We set the date with you at kickoff, often around the end of your current contract.
We connect to your ERP or billing system and load open invoices, customers, contacts and payment history. The integrations page lists the systems we connect to.
What takes the most planning
The AR data is the easy part. These are the pieces we plan around early.
Payment links your customers already have
Old invoices and welcome letters point at the old portal. We plan the notice and the customer email so payments keep reaching you.
Saved cards and bank details
Stored cards and bank details can move into Stripe, so customers don’t re-enter them, when you own the processor account and it can export them. Autopay consent and ACH mandates are set up again.
Check lockbox files
Every bank formats its lockbox file a little differently. We map yours before cutover, so checks are read the same way on the first day as on the last.
How payments post to your ERP
Your old tool posted payments, fees and short pays in its own way. We match that format, so reconciliation works the way your team expects.
Frequently asked questions
Switching from Billtrust to Fazeshift, from first call to go-live.
Plan your switch with us
Bring your ERP, your bank and your current tool to a call, and we’ll walk through what moving looks like for your team.