Switching from Versapay
Leaving Versapay? We’ll move you over.
Our implementation team runs the switch. Your AR data loads from your ERP, saved payment methods can move with your customers, and we plan the portal cutover with you.
Why teams move from Versapay to Fazeshift
What teams on Versapay tell us they’re looking for.
Agents that work the exceptions
Short pays, lump-sum payments and remittance that arrives by email or through a portal go to the agents first, instead of back to your team’s queue.
Collections and cash application together
The same agents chase what’s owed, read the remittance and apply the cash, so a payment and the reminder that prompted it never live in different tools.
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.
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 Versapay
We carry over your email template wording and collections notes. Saved cards and bank details can move into Stripe when you own the processor account and it can export them, so most customers won’t re-enter them.
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 Versapay 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.