Bills, collected and approved
Supplier invoices come in by email, by upload, or straight from the supplier's portal, where an agent signs in and downloads them on each billing cycle. Your customers review, approve and keep the due dates in view.
Embedded
Embedded expenses, bills and invoicing for your platform
Your customers already run their business in your product. Give them their receipts, expense reports, bills and invoices there too, under your brand, instead of sending them to another app.
What you can embed
The money workflows your customers keep asking for
Use one, or all four. They share the same receipts, the same people and the same records, so nothing has to be reconciled between them.
Itemized receipts, straight from the POS
Receipts from stores on the Smartbills network arrive line by line, with tax per line. Emailed receipts are pulled from the mailbox and paper ones come in as photos. Each one is matched to the card or bank transaction it belongs to.
- Line items and tax, not just a total
- Matched to the card or bank line
- Tagged to your own objects, like a job or a project
Expense reports with approvals
Your customers' employees submit reports, policy rules flag what needs a second look, and managers approve or send it back without leaving your product.
- Policy checks on every line
- Mileage and per diem
- Approve or request changes in one step
Invoices your customers get paid on
Your customers build an invoice from the job, with GST, QST, HST or PST worked out line by line, and send it by email with the PDF attached. Their client pays online by card or pre-authorized debit, and the invoice updates itself.
How you launch
Build it, drop it in, or have it hosted
Pick the path that fits your roadmap. You can start with one and move to another later; the data underneath is the same.
Full control over the experience. A REST API, events and SDKs, with a sandbox to build against. Your interface, our data and workflows.
Prebuilt receipt, expense, bill and invoice views you render inside your own app. Pass your colors, radius, font and locale and they match the rest of your product.
A complete expenses experience on your own domain and under your brand, with no front-end work. Link to it from your product and your customers find it where they already work.
Who it's for
Built for platforms that small businesses run on
The pattern is the same everywhere: your customers' spending happens in your product, and the paperwork happens somewhere else.
Vertical SaaS for trades, clinics, restaurants or agencies
Your customers schedule, invoice and get paid in your app, then leave it to deal with receipts and supplier bills. Bring that work inside, tied to the jobs and clients they already track with you.
Small-business banks, neobanks and card programs
Every card transaction can show the itemized receipt behind it, and expense reports and bills sit next to the account they're paid from.
Commerce and POS platforms
Your merchants buy from suppliers as well as sell. Give them their own purchases, bills and receipts in the same back office they use for sales.
Prefer the data on its own?
If you only need part of it, each piece is also available as its own API.
Embedded receipts
Itemized receipts from the merchant's point of sale, shown inside your own app under the transaction they belong to. For banks, fintechs, retailers and any app built on the API.
Transaction enrichment
Resolve a card descriptor into a business your customer recognizes, with logo, location and category, plus the itemized receipt when the merchant sent us one.
Insurance claims
Proof of purchase that comes from the merchant instead of the claimant: the line item, price, tax, date and serial as data an adjudicator can use.
Dispute defence
Chargeback prevention that explains a charge right on the transaction screen, with the merchant's evidence ready for the disputes that open anyway.
FAQ
Questions platform teams ask
Embedded finance means offering financial features, like payments, cards or accounting, inside a product whose main job is something else. Smartbills covers the back-office side: receipts, expense management and bills, delivered inside your product rather than in a separate app.
Yes. The hosted app runs on your domain under your brand, and the drop-in components take your colors, radius, font and locale. Your customers see your product, not ours.
Bills are part of the platform: capture from email, uploads and supplier portals, plus approvals and due dates. You can reach them through the API, render them with the components, or use them in the hosted app.
Yes. Your customers' invoices, with taxes calculated per line, online payment by card or pre-authorized debit, recurring schedules and reminders, are available through the API, the components and the hosted app.
Yes. The API returns receipts itemized line by line, with tax per line, whether they came from a store on the Smartbills network, an email or a photo. The JavaScript SDK wraps it, for example with receipts.listAsync.
Choose the API when you want to design every screen yourself, the components when you want to ship inside your app quickly with your own styling, and the hosted app when you want the whole experience without front-end work. Many teams start hosted and move to components later.
Platform access isn't self-serve yet. Talk to our team, and we'll confirm the workflows and regions you need and set you up with sandbox keys. The reference documentation is public at docs.smartbills.io.
Get started
Put expenses, bills and invoicing inside your product
Tell us what your customers do in your app today and we'll show you where these workflows fit.