Accounting software integration
When a payroll run is committed, MooPayroll turns it into one balanced journal and sends it to your accounting software — so nobody retypes payroll totals into the ledger at month end.
| Accounting software | How it connects |
|---|---|
| AutoCount Accounting | Desktop 2.x: a journal import file, or the AutoCount On The Go (AOTG) API. AutoCount Cloud Accounting: its Integration API, with a key pair from your Cloud settings. |
| SQL Account | The SQL Account REST API, using an access key you generate for a dedicated API user. |
| QuickBooks Online | Click Connect and sign in with your Intuit login. No keys to copy. |
| Xero | Click Connect and sign in with your Xero login. Departments map to a Xero tracking category. |
| Financio | Click Connect and sign in with your Financio login. |
One journal per payroll run
Salaries, allowances, overtime, employer EPF, SOCSO and EIS, and the amounts payable to each statutory body — one entry, dated the end of the pay period.
Your chart of accounts
Pull your accounts from the accounting software and map each payroll category to one of them once. The mapping is reused every month.
Split by department
Expense lines follow each employee's department, mapped to the department, project or tracking category your books use.
Nothing posts unbalanced
If a category is unmapped or a run does not balance, the journal is refused and the screen names exactly what is missing.
Each company sets up its own connection under Setting → Accounting; keys and sign-in tokens are encrypted at rest. AutoCount, SQL Account, QuickBooks, Xero and Financio are trademarks of their respective owners.
MooPayroll Open API
For system integrators and in-house developers: connect an ERP, finance, BI or HR system to MooPayroll with an API key your company creates and controls. Any system can integrate — it does not need a connector written by us.
Keys your company controls
Create keys under Settings → API Access. Each has its own scopes, an optional department or branch limit, an optional IP allow-list and an expiry. Rotate or revoke at any time.
HR and payroll data
Company and organisation structure, employees, committed payroll runs with per-employee lines, statutory totals and the accounting journal, leave balances and applications, and attendance days.
Webhooks
Be told the moment a payroll run is committed or an employee is created or updated. Deliveries are signed, retried on failure and listed in a delivery log.
Audited and scoped
Every call is recorded in the audit trail against the key that made it. IC, passport and bank details sit behind a separate scope that is off by default.
A request looks like this
GET /api/open/v1/payroll-runs?year=2026
Authorization: Bearer moo_live_…
200 OK
{
"items": [{
"id": "01J9ZQ3M…",
"year": 2026,
"month": 9,
"status": "paid",
"totals": { "net": "45210.50" }
}],
"next_cursor": null
}Read-only today, writes on the roadmap
Version 1 of the Open API reads data and pushes webhooks. Write operations — posting HR data into MooPayroll and performing HR operations from your own system — are planned. Tell us what your integration needs.
The API is versioned, paginated and rate-limited per key, and money is always returned as a decimal string. The developer reference is linked from Settings → API Access.
Timesheet & attendance
Employees clock in and out from the MooPayroll mobile app or the web. Hours, overtime and exceptions are worked out from the punches, reviewed by HR, and the approved overtime flows into payroll.
Clock in and out on mobile
One button in the MooPayroll employee app, or on the web. The time is stamped by the server, not the phone, so changing the device clock changes nothing.
Location and photo, if you want them
Optionally check a mobile punch against your work sites and ask for a photo. Both stay off until the company switches them on.
Shifts and rosters
Define shifts, assign them to people and sites, and let rest days and public holidays classify each day.
Missed punches, handled
An employee can claim a forgotten punch from the app; it counts only once an approver accepts it. HR adjustments are kept in the audit trail.
Clocking machine import
Already have a clocking machine? Import its CSV with a saved column mapping, preview the rows, and revert the batch if it was wrong.
Overtime into payroll
Overtime hours by day type — normal day, rest day, public holiday — feed the payroll run once the month has been reviewed and closed.
Timesheet is optional per company, with three settings: off, record only, or feeding payroll. Employees get clock-in and clock-out reminders on their phone, and approvers see their own team's day at a glance. Get the mobile app.
System guide and helpdesk
Help is built into the system: full documentation that shows where to click, and a support ticket when the guide is not enough.
Full system documentation
Every feature of MooPayroll is listed in a searchable guide under Helpdesk → System guide, grouped by module. Each entry plays a short animated walkthrough of where to click, with numbered steps beside it and a button that opens the screen itself.
Available in English, Bahasa Malaysia and 中文.
Helpdesk ticketing
Your HR team raises a ticket from inside MooPayroll — subject, category, priority, screenshots or PDFs attached — and follows the conversation there until it is solved.
A ticket goes to your agency first. Anything they cannot resolve is escalated to MooPayroll's technical team as the same ticket, history included, so you never explain the problem twice.