fintech
uCollect
Invoice collection · Xero / QuickBooks · teQmavens
uCollect: automated invoice collection into Xero/QuickBooks through a multi-country gateway catalog.
teQmavens
Context
At teQmavens I worked on uCollect — not a generic “Xero plugin.” uCollect reads invoices from Xero or QuickBooks Online, collects via the merchant’s own gateway, and posts payments back to the ledger. Public docs list processors such as Stripe (cards and ACH), Forte, Windcave, Authorize.net, NMI, EziDebit, Ezypay, NAB Transact, Netcash, Mint, Australian ABA files, NZ bank direct debit, and SEPA — plus regional bank-file variants.
Problem
Businesses needed one collection pipeline across direct API gateways and old bank-file uploads, assigned per contact, with payments landing correctly in Xero/QBO.
- —Direct API gateways versus upload/batch bank files
- —One gateway per contact; cards vs debit often need split contacts
- —Financial posting accuracy back to the ledger
What I worked on
- →Built collection flows and Xero API integration
- →Designed transaction schemas for reconciliation
- →Implemented REST/MVC services around gateway adapters
Architecture & approach
Laravel backend with a gateway abstraction: API collectors where the processor allows it, file generation for upload banks, contact-to-gateway assignment, Pay Now where supported, and payment records written back to Xero/QBO.
Outcome
- ✓One collection path across API and file-based processors
- ✓Automated ledger posting that cut manual reconciliation
- ✓Stable production collection for teQmavens’ uCollect work