One backend, several external workflows.
Invoice management needed to connect four business systems with a regulatory service, while account access, subscriptions, administration, and support ticketing remained part of the same product. Each integration had its own boundary and purpose.
Own the product backend and its integration boundaries.
- Implemented the backend supporting account access, subscriptions, administrative operations, and invoice-management workflows.
- Built invoice-management integrations with Odoo, QuickBooks, ERPNext, and Microsoft Dynamics.
- Integrated the Nigerian NRS service into Tranero’s compliance workflow.
- Connected the self-hosted Frappe Helpdesk ticketing system to support the product’s support workflow.
A complete backend ownership scope.
My contribution covered Tranero’s backend and the named invoice, NRS, and ticketing integrations. The public site gives reviewers a product to inspect; the contribution map shows my implementation scope without publishing private source or client records.
The central engineering responsibility was owning the backend across invoice systems, regulatory integration, administration, and support, rather than delivering a single isolated connector.
Scope and evidence
This study describes the backend I owned and the integrations I implemented. The public product pages provide context for invoice management, ERP connections, and compliance workflows. Backend ownership and the named implementation scope are confirmed by me; the application source remains private. The public website is presented as product context rather than evidence of marketing-interface authorship.
- Backend ownership: I wrote Tranero’s backend at Zweidevs.
- Invoice-management scope: Odoo, QuickBooks, ERPNext, and Microsoft Dynamics integrations.
- Compliance and support scope: Nigerian NRS integration and self-hosted Frappe Helpdesk ticketing.
- Public product context: the invoicing page describes invoice creation, tracking, PDF/XML generation, and ERP integration.
- Public product context: the API and compliance pages show ERP-to-tax-authority workflows; the site currently uses FIRS terminology, while my implementation scope uses the NRS name I confirmed.
Public product context: Tranero: invoicing, compliance, and API integration, Tranero, Public product pages, Inspected October 2026. The invoicing, API-integration, and compliance pages describe invoice creation and tracking, ERP connections, digital invoice formats, and tax-authority submission workflows. Their marketing performance and certification claims are not used as portfolio results.
Visit the product site