Key Takeaways
- Payment gateway accounting is more complex than traditional accounting, involving high-volume transactions, API-based reconciliation, and stricter audit scrutiny.
- SST applies to most payment-related fees, including platform charges, MDR, and API access, once revenue exceeds RM500,000 annually.
- Incorrect classification of revenue is a major compliance risk, especially when mixing taxable fees with non-taxable transactions like wallet transfers.
- Audit readiness now requires system-level records, such as transaction logs, API triggers, and detailed SST filings, not just financial statements.
- Cloud accounting tools with API integration are essential, as manual or spreadsheet-based systems cannot handle transaction scale or SST requirements effectively.
Digital payment accounting isn’t just “ringgit in and out”. For e-wallet and payment gateway businesses, the hard part is separating gross flows vs fees, reconciling settlement batches, and documenting taxable service income clearly enough to stand up in an SST review.
In this guide, we’ll walk through how SST generally applies to payment services, what auditors typically ask for (beyond bank statements), and how to set up your accounting stack so reconciliation and reporting don’t become a monthly fire drill.
Payment Gateway Accounting vs Traditional Accounting
Why gateway accounting feels harder than typical SME bookkeeping
- Much higher transaction count (micro-fees + batch settlements)
- More reconciliation points (channels, settlement cycles, chargebacks, refunds)
- Clear separation needed between gross collections vs fee income
- Audit readiness depends on logs and traceability, not just bank statements
- Automation matters (API feeds, batching, rule-based tagging)
How Does SST Apply to E-Wallet & Gateway Providers
SST for payment providers covers both digital services and merchant charges.
Payment processing and gateway-related charges are commonly treated as taxable services under Malaysia’s SST framework. If the value of your taxable services exceeds RM500,000 within the relevant 12-month basis used by RMCD, SST registration is generally required.
Common taxable items:
- Platform / subscription fees
- Processing or gateway fees (including MDR-type charges where applicable)
- API / integration / access fees
- Chargeback or dispute handling fees (if charged)
Common non-fee flows to separate:
- Stored value movements (e.g., wallet balances) that are not a service fee
- P2P transfers where no service fee is charged
- Merchant settlements that are purely pass-through (supported by contracts and reporting)
Exemptions: Pure wallet transfers between users (P2P) or merchant cashbacks (if not fee-based).
“Always separate taxable and non-taxable revenue streams in your ledger for clearer reporting.”
Important: Be consistent about how you treat MDR/processing fees in your contracts and ledger. Auditors will look for clear documentation showing what is your taxable fee income versus amounts collected and passed through in merchant settlements.
What Are the Most Common Compliance Challenges?
Inaccurate classification and missed SST filing deadlines top the list and this is not surprising. The digital finance ecosystem moves quickly, but SST compliance doesn’t wait. Common pitfalls include:
- Lumping in top-up revenue with fee income, leading to over-declared SST.
- Delayed invoicing or incomplete tax invoice details for B2B clients, which creates mismatches between revenue recognition, collections, and SST reporting. SST is reported by taxable period and returns/payment are due by the last day of the following month.
- Omitting fees from cross-border transactions, mistakenly assumed to be exempt.
- Non-reconciled daily batch reports, especially if gateway splits by channel.
Case example: Payment providers commonly get flagged for non-itemised reporting (e.g., mixing taxable fees with pass-through settlement amounts), even when their profit-and-loss looks “clean.”
How Should You Prepare for a Payment Gateway Audit?
During an SST review or audit, auditors will ask for system logs, not just bank statements. Here’s what you’ll need to have ready when you approach an audit firm in Malaysia:
- Daily transaction summaries (timestamped, from server logs)
- Merchant settlement reports
- SST filing records (Form SST-02)
- Fee categorisation matrix (taxable vs exempt)
- API integration logs showing how fees are triggered and recorded
Tip: LHDN allows API-based SST audit trails but requires clear matching to declared revenue. Ensure your accounting team works closely with your IT integrators.
What Accounting Tools Are Best for E-Wallet Companies
You’re dealing with hundreds (if not thousands) of transactions per day across payment channels, QR pay, FPX, DuitNow, credit card tokens, and more. Without automated batching, SST-tagging, and real-time reconciliation, you’re either under-reporting tax or burning man-hours fixing exports manually.
Let’s look at the leading accounting tools suited for this fast-paced, compliance-sensitive environment.
Malaysia’s Best Accounting Software for E-Wallet & Gateway Services
Tool | Best For | SST Support | Key Feature |
Financio | Startups, solo wallet operators | Yes | Built-in SST codes, e-invoice ready |
SQL Cloud | Mid-sized payment processors | Partial | Customisable chart of accounts, limited SST automation |
Xero + API | Scaling platforms, retail gateways | Via plugin | Plugins for SST tagging, payment link integration |
AutoCount | SMEs with in-house finance team | Yes | Multi-location SST reporting, e-invoice support |
Custom Stack | Large-scale or cross-border players | Yes (custom) | Deep API integrations, end-to-end control |
Why These Tools Work for Payment Businesses (Real-World Use Cases)
Financio
A popular pick among early-stage wallet startups in Malaysia. Its built-in SST categorisation makes it easy for founders without a finance background to file service tax returns without external plugins. Plus, it syncs nicely with local banks like Maybank and CIMB for e-statement matching.
SQL Cloud
SQL is a solid mid-tier tool, often used by B2B payment resellers or closed-loop wallet systems (like those used in education or private food courts). While it doesn’t automate SST fully, it allows flexible categorisation for fee-based revenue.
Xero + API
This accounting software works well for payment aggregators or platforms with customer-facing dashboards. Its integration with tools like Stripe or local payment plugins (Paydibs, eGHL) allows tagging transaction types as taxable or exempt, which is essential for correct SST treatment.
AutoCount
AutoCount is increasingly favoured by Malaysian wallet operators with multiple outlet accounts or SST group registrations. Its multi-location SST reporting, support for custom fee mappings, and local plugin ecosystem make it a strong choice for mid-sized e-wallets that need both structure and flexibility. I
It’s also e-Invoice ready for LHDN’s phased implementation (with milestones across 2025 and 2026 depending on turnover).
Custom ERP stacks
SAP or Odoo Malaysian tax modules are often used by enterprise players like telco-backed wallets or regional gateways. They support high-frequency API log matching, merchant sub-accounting, and compliance trails that pass audit scrutiny with minimal effort.
Still Wondering Which Accounting Setup Fits Your Payment Model?
The best accounting software isn’t just about brand, it’s about fit.
If you choose a tool based purely on pricing or buzz, you’ll soon realise the system can’t handle your specific revenue structure (float revenue, MDR, top-up passthroughs).
Don’t let hours of spreadsheet exports and mismatched batch files slow down your business.
Use this quick-fit reference guide to help decide:
Business Type | Recommended Tools |
Fintech Startups | Financio, SQL Cloud |
Retail Payment Models | Xero with API Plugins |
Large E-Wallet Brands | Custom ERP with full audit trail |
Cross-Border Platforms | SQL Cloud + External Audit API |
“Always discuss your tech stack with your accountant before committing to any platform. You may be surprised how many “all-in-one” solutions fall short when SST or audit requirements change.”
Get Payment Machine Accounting Software from Us
At Accounting.my, we know that managing finances for e-wallet and payment gateway businesses isn’t just about bookkeeping, it’s about staying compliant, scalable, and audit-ready.
Relying on outdated systems simply won’t cut it. A hybrid approach using cloud-based tools, SST-ready workflows, and API integrations is now the industry standard.
Whether you’re looking for expert support or exploring accounting software tailored for payment platforms, we’re here to help you get it right from the start.
Frequently Asked Questions About Retirement Age
SST (Sales & Service Tax) applies to service fees from platforms and gateways earning over RM500,000 annually.
SST is filed bi-monthly via Form SST-02 through MySST, with deadlines on the last day of the following month.
Only if fees are charged on top-ups. The top-up value itself is not taxable, but service fees are.
Auditors request transaction logs, fee classifications, SST declarations, and matching ledgers.
You can, but it’s risky. High transaction volumes and SST complexity require better tools.
Yes, unless clearly documented as passthrough and not part of platform income.














