One Login, Faster Close: How Expansive Streamlined AR Access Across 20+ Banks with Arpari
How Hempel Turned Scattered Bank Data Into One API-Powered Feed for RealPage Reconciliation
Expansive manages accounts across more than 20 banks, and before Arpari, getting a full view of cash meant logging into each bank portal separately. For a quick read on total cash position, that added up to real time lost for the property accounting team.
The bigger issue was access. Expansive relies on outside, overseas contractors for AR, and every new hire meant provisioning access across all 22 bank portals — one at a time, with each bank running its own process. Some banks didn’t even support self-service account setup; someone had to email the bank directly and follow up manually until access came through.
“Just adding a new login for one employee—it’s probably six hours to do that. And some are even longer.”
Once someone was in, keeping track of who had access to what across 20+ portals was its own ongoing job.
Bank feeds were another manual burden. Direct feed connections — building and maintaining BAI2 files across 22 banks — weren’t realistic to take on in-house. Expansive didn’t have the IT resources to build or maintain that kind of infrastructure themselves, so before Arpari, that level of automation was simply out of reach.
“We don’t have that big of an IT group, so we just knew we couldn’t do it ourselves.”
The Solution: One Login, Built to Scale With the Team
Arpari gave Expansive a single, API-connected access layer across all of its banks. Instead of provisioning a new AR consultant bank-by-bank, Expansive now provisions that person once in Arpari — and they have what they need everywhere.
“We can provision a user once in Arpari and everything works... we provision somebody once, and then it’s set. Keeping track of all of the bank access was a lot of work — Arpari has taken that off our plate.”
The same API connections that power Expansive’s dashboard also feed Yardi. Arpari transforms that API data into the BAI2 format banks require — something Expansive knew they didn’t have the resources to build or maintain on their own. Without Arpari, going live on auto-rec would have meant standing up and maintaining 22 separate BAI2 feeds in-house; with Arpari, that work simply isn’t theirs to do.
“Arpari is able to take the raw feeds that and then transform it into BAI2. We don’t have that ability. That to me was the secret sauce.”
Onboarding a new bank follows the same pattern: once Chris makes the introduction, Arpari takes it from there. And where API access isn’t available, Arpari’s connections tend to run more reliably than a raw feed — each bank’s feed has its own live window before it can time out, and Arpari manages around that, so uptime isn’t something Expansive has to think about.
The Impact: Minutes, Not Hours — and a Faster Close
What used to take about six hours per new AR hire across 22 individual bank portals is now a single step in Arpari — saving the team an estimated 10–15 hours per month now that setup and access management are handled.
That efficiency shows up directly in month-end. AR and bank reconciliations both finish sooner, and Expansive now closes its AR period two to three days faster.
“We’re probably able to close our AR period two to maybe even three days faster as a result.”
None of that would be possible without the underlying infrastructure Arpari runs for Expansive — turning API data into the BAI2 feeds their banks require, something Expansive knew it couldn't build or maintain in-house. That's the layer that makes faster provisioning and a faster close possible in the first place, without adding headcount or IT overhead on Expansive's side.