The situation
Every bill went out by hand. Somebody had to know who owed what, put the bill together, send it, and then remember a week later that it still hadn't been paid.
It worked, because one person carried it. Which is another way of saying it stopped whenever that person was busy, away, or looking at something else. Replacing the accounting package was never on the table: the books live in QuickBooks Desktop and the bookkeeper knows it well.
What we built
- Syncs with QuickBooks Desktop automatically, with no re-typing.
- Sends invoices and statements by text message or email, each with a secure link to view and pay.
- Takes card payments online or by phone and posts them straight back into QuickBooks.
- Follows up on overdue balances on a schedule the office sets.
- Matches incoming payments to the right invoice, and leaves anything uncertain for a person to confirm.
The bill comes from a number their customers already know
An invoice reaches the customer as a text message from the organization's own number, with a link to see it and pay it. What has been billed and what has been paid is one list, not somebody's memory. It runs under their name, in their own account, and they own the code and the information outright.
Their staff report a problem; we don't wait to be emailed
There is a report button inside the system. Somebody says what's wrong in their own words and it reaches us with the context already attached. The report is read against the actual code, an engineer checks that answer before anyone acts on it, and the office sees the change running on their own information before it goes live. That loop is how most changes to this system now happen.
The demo runs on an invented company's invoices, so you can open anything without looking at a real customer's account.
Open the FlexAR demo ↗