Weeks Cut From Customer Payments: Elevex Automates Its Receivables Follow-Up

At Elevex, receivables follow-up was entirely manual. To find out which invoices were overdue, the team had to look them up in Acomba, compile the balances, then contact each customer one by one.

‍

Without a reliable overview of its receivables, the team couldn't quickly see which customers needed a reminder. Many accounts stayed outstanding longer than they should have.

‍

The real issue was cash flow. Every late reminder pushed back incoming cash, and the business felt it directly. Acomba is built to work in a silo, so the follow-up couldn't be automated without a bridge.

Phase 1, Mapping the Collections Process: We documented how the team tracked its receivables, from pulling balances in Acomba to contacting the customer. This work defined the follow-up rules based on invoice age.

‍

Phase 2, Connecting Acomba: Acomba's classic edition has no public API. We implemented ExoConnect, a bridge that reads Acomba's accounting data and makes it available to other tools. To learn how it works, read our guide: How to Connect Acomba to Your Business Systems.

‍

Phase 3, Automating Follow-Up in Make: We built the logic in Make. Overdue invoices are pulled from Acomba and sorted by age in an Excel tracking file. Every customer now receives their account statement automatically. Reminders on outstanding invoices go out on their own and are logged in the file, where the team adds its collection notes. When an invoice reaches 90 days overdue, the person in charge of receivables is alerted to decide whether the account should go to collections.

‍

Phase 4, Ongoing Adjustments: After go-live, we refined the scenarios with the Elevex team. We added note columns and a dedicated account statements tab. Invoices moving from 60 to 90 days are now transferred automatically, with their full note history.

‍

Stack: Acomba + ExoConnect + Make + Excel