Point-of-sale integrations
Getting the receipt out of the point-of-sale system. Every merchant system has its own API, its own quirks and its own idea of what a line item is.

Careers
We're a small team in downtown Montréal. The problem is old, the systems we plug into are older, and most of what needs building hasn't been built yet.
Most of the job is getting data out of places that were never meant to share it.
A receipt starts in a point-of-sale system, lands on someone's phone, gets matched to a card charge and ends up in an accounting system. Every step has its own edge cases. If you enjoy the kind of problem where the answer is buried in a point-of-sale spec from 2009, you'll like it here.
The work
Four parts of one system. They all meet at the receipt.
Getting the receipt out of the point-of-sale system. Every merchant system has its own API, its own quirks and its own idea of what a line item is.
iOS and Android, in React Native. It's where people get their receipts, find them again a year later and send them to their accountant.
Where a business sets spending rules, approves expenses, pays suppliers and closes the month.
Writing clean, coded entries into QuickBooks, Xero, Sage and NetSuite, and keeping them right when someone edits on the other side.
.NET
C#
TypeScript
React NativeThe stack
The back end is .NET. The web platform and the apps are TypeScript, with React on the web and React Native on phones. Nobody expects you to know all of it on day one.
Working here

Nothing open right now.
We still like hearing from people who want to work on this. Send a few lines about what you'd want to build and a link to something you've made.
Email usinfo@smartbills.ca