Built to solve reconciliation headaches
We started Smartfocusrer in 2018 because we kept seeing the same problem: businesses outgrew their accounting tools but couldn't get transaction data flowing properly between systems. Manual exports, spreadsheet gymnastics, and monthly reconciliation marathons became the norm. We decided to fix that with purpose-built integration frameworks.
Who actually builds this
Liam Kowalski
Technical Architect
Started building API integrations for payment processors in 2015. Spent three years watching businesses struggle with data sync issues before deciding there had to be a better approach.
What we actually do
We write custom integration code that connects your accounting software with payment gateways, banking APIs, and transaction processors. The goal is simple: get all your financial data flowing into one place without manual intervention.
Most of our clients need automatic reconciliation between their point-of-sale systems and accounting platforms. We build the middleware that handles transaction matching, currency conversion tracking, and fee allocation. It's not glamorous work, but it saves hours every week.
How we work with clients
Initial consultation covers what systems you're using and where data gets stuck. We map out transaction flows and identify reconciliation bottlenecks. Then we build a custom integration layer that sits between your systems and handles data transformation.
Implementation typically takes 4-8 weeks depending on API complexity and data volume. We test everything in a sandbox environment before touching production data. You get documentation explaining exactly what the integration does and how to monitor it.
Why Malaysia specifically
We're based in Penang and work primarily with Malaysian businesses because regional payment processors have specific data formats. Touch 'n Go eWallet, Boost, and local bank APIs all have their quirks. We've spent years working with these systems and understand how to handle ringgit transactions, SST calculations, and multi-currency scenarios common here.
Being local means we can meet in person when you need to walk through complex reconciliation issues. Remote work is fine for most things, but sometimes you need to sit down with transaction records and figure out why numbers don't match.
2018
Founded in Penang, first integration built for retail client
2021
Added support for major Malaysian e-wallet platforms
2024
Automated reconciliation framework deployed for 40+ clients
Technical team
Astrid Voss
Integration Engineer
Handles API authentication flows and webhook implementations. Previously worked on banking infrastructure for three years. Specializes in debugging rate limit issues and handling transaction retry logic.
Development approach
Technical methodology
We test integrations against sandbox environments first, then gradually roll out with real transaction data. Every integration includes logging for audit trails and error tracking. Documentation covers API endpoints used and transformation logic applied to data fields.
Visual examples of our work
These screenshots show actual integration dashboards we've built. Top row: reconciliation matching interface and configuration panels. Bottom row: sync status monitoring and system connection diagrams. Most clients check these daily to verify data flows are running correctly.