TAC HRTAC HR
A man looking at a tablet on a glass desk beside stacked books, with the city skyline at night behind him
Oracle NetSuite
Accounting and ERPPayroll journal as an Excel file

Integration with Oracle NetSuite: Payroll Entries for Multi-Branch Companies

The integration with Oracle NetSuite in TAC HR suits a company that grows by branches and wants payroll entries to reach its accountants without manual gathering. The entry comes from the closed run, follows the company's chart of accounts and is exported as xlsx. A read API and signed webhooks sit alongside it.

01Overview

Requirements

What does your company get from the NetSuite integration?

  • One entry from one run, all branches: payroll is calculated in TAC HR by branch and department, and the journal is exported from the closed run.
  • No gap between teams: what the HR manager sees in the run is what the accountant receives.
  • Growth without redesign: a new branch joins the run, and its effect shows in the next entry.
  • Events for coordination: webhooks for payroll paid and for an employee who joins or leaves.

Operational example

A distribution company in Riyadh and Dammam closes the month. The accounts controller downloads the journal file and compares each branch's total against the payroll report. She spots a gap in the Dammam branch's payslip total, goes to the salary change log, finds a change recorded before closing, and then loads the file into the accounting system her way.

02What syncs

Where your data lands

What does the integration build on?

  • Accounting journal export (xlsx)a file on the company's chart of accounts.
  • Read-only APIscoped keys.
  • Webhookssigned events sent to an endpoint the company defines.

Loading the file into NetSuite follows a route the company decides.

How does it connect to the payroll run?

The run shows separate items and supports proration, closing and a salary change log. After closing, the total in the entry does not move, and the salary change log keeps pay changes on record.

When does the integration help most?

  • When a new branch opensits employees join the run and appear in the next entry.
  • When comparing branchesmanagement sees each branch's total in the payroll reports before the journal is loaded.
  • When you need an audit trailclosing the run and the salary change log show what changed and when.
  • When the accountant changesthe xlsx file stays readable to any new accountant.
03Setup steps

The setup, start to finish

Five steps from the system's own screens. What happens outside it, such as uploading a file or loading it into another system, is in your company's hands.

  1. 1Accounts and cost centresYou enter each account's code and name as in NetSuite, and turn on “Spread expenses over cost centres by department”.Then press “Save accounts” and the journal is built on them.
  2. 2Run payroll by scopeIn “Create payroll run” you pick “Locations and branches” and “Departments and groups”.Payroll computes the employees in the chosen scope.
  3. 3Approve the runSend it with “Send for approval”, then “Approve run”, along your company's approval chain.Once approved, the journal for the run opens.
  4. 4Review the journalThe page shows total debit and credit and the entry lines by account code and name.Cost centres show on the run page for comparison before download.
  5. 5Download the file and load it into NetSuitePress “Download Excel” (or CSV) and the entry comes out on your chart of accounts.Loading it into NetSuite is done in a way your company decides.
04FAQ

Asked before implementation

Is the entry calculated before the run closes?

The entry is built from the run after it is closed.

Does it support multiple branches?

The run covers branch employees with permissions that decide who sees them, and the journal comes from the closed run.

Do I need a developer?

Not to export the file. Receiving webhooks or reading through the API needs someone to set up the endpoint.

Ready to integrate?

Start with two branches

Request a demo to follow an entry from a two-branch run, or read about payroll and pricing.