What syncs
| Feature | Support |
|---|---|
| Connection | Keys you create in SQL Account, stored encrypted. Your SQL Accounting must be online (PC or server) for SQL's API to reach it |
| Daily journals | Sales per channel, marketplace fees and payouts, cost of goods sold, stock value and LHDN e-invoice references — previewed and approved by you each month |
| Draft journals | No — journals are posted |
Planned capabilities. Accounting integrations open with MyEasyMarket's public launch on the Pro and Scale plans; this table comes from the same source as our product code.
Journal entries only, through SQL's RESTful API, which needs your SQL Accounting online. Pro and Scale plans.
Before you start
- Accounting integrations are built and open with MyEasyMarket's public launch, on the Pro and Scale plans.
- SQL Accounting version 5.2025.1038.875 or later, on a Windows PC or server that stays online (SQL's public cloud or an on-premise server). A standalone PC that is often off does not work.
- SQL's RESTful API turned on for your company, with an access key and secret key. Ask SQL support (support@sql.com.my); SQL charges a setup fee for the API.
- The account codes you want to use: a clearing account per marketplace (or one for all), sales, shipping income, discounts, marketplace fees, your bank account, cost of goods sold and inventory.
- An owner or admin role in MyEasyMarket to connect. An accountant role can map accounts, preview, approve and retry.
Step by step
- Get your access key and secret key from SQL support and make sure SQL Accounting is running and online.
- In MyEasyMarket, open MyEasyBilling → Accounting and select Connect SQL Account. Paste both keys and select Connect. MyEasyMarket checks them by reading your accounts.
- Open Account mapping, select Suggest from account names, check every line and save.
- Open Sync & reconcile. Check the journals for this month, then select Approve. Nothing is sent before you approve a month.
- The owner or an admin opens Settings and turns sending on. Approved journals go to SQL Account straight away, then every day.
After you connect
- One GL journal entry per day and sales channel: order totals to the clearing account, sales, shipping charged and discounts, and cost of goods sold against inventory at the cost when each order was saved.
- One journal entry per day and marketplace for orders completed that day: commission, transaction and service fees, SST on fees, platform vouchers, and the payout to your bank.
- The document number is a readable reference such as MEM-261018-SSP.
- Sync & reconcile shows each day next to what MyEasyMarket sent. A cancellation after a day was sent becomes an adjustment entry; sent entries are never edited.
- Entries SQL Account refuses wait in the error queue with its message and a Retry button. If SQL Accounting was offline, MyEasyMarket retries on its own.
Limits and good to know
- Built on SQL's RESTful API (journal entries and accounts), signed with AWS Signature Version 4 as SQL documents. Before each entry MyEasyMarket looks for its document number, so a retry never posts twice.
- SQL Account has no draft journals through the API: entries are posted.
- Days are Malaysian business days; amounts are in ringgit. Only MYR orders are journalised.
- Your keys are stored encrypted and deleted when you disconnect.
- Prefer files? Sync & reconcile has a journal CSV download your accountant can key in or map in SQL's import tools.
Troubleshooting
| What you see | Why it happens | How to fix it |
|---|---|---|
| The connection shows Needs attentionauth_failed | SQL's API refused the keys (changed, revoked or typed wrongly). | Check the keys with SQL support, disconnect in MyEasyBilling → Accounting → Settings and connect again. |
| Sending is waitingprovider_unavailable | SQL Accounting or the PC it runs on is offline, or SQL's API is under maintenance. | Keep SQL Accounting running and online. MyEasyMarket retries on its own. |
| A line has no accountmapping_missing | The journal uses a line (for example commission) that is not mapped yet. | Map it in Account mapping, then select Retry in the error queue. |
| SQL Account refused an account codeinvalid_account | The account code does not exist or is inactive in SQL Account. | Choose another account in Account mapping, then Retry. |
| The period is closedperiod_locked | The journal date falls in a closed period in SQL Account. | Ask your accountant to reopen the period or post that day by hand, then Retry. |
Reconnect, disconnect and your data
- New keys? Disconnect in MyEasyBilling → Accounting → Settings and connect again with them. Mapping, approvals and history stay.
- To stop, turn sending off or disconnect. Entries already in SQL Account stay there.
Frequently asked questions
My SQL Account runs on one office PC. Will it work?
Only while that PC is on and online, because SQL's API reaches your data through it. Journals wait and retry while it is off.
Can I use a file import instead?
Yes. Download the journal CSV from Sync & reconcile; it lists every line with its account code, debit and credit.
Does it use AI credits?
No. Accounting sync uses no AI credits.
Ready when your channels are
Start a 30-day free trial, set up your catalogue now and connect each channel the day it opens.
Was this guide helpful?