ACUMATICA

LINARC ON THE JOB. ACUMATICA IN THE BACK OFFICE.

Map the connection once. Records from the field move into Acumatica on their own, and finance keeps working the way it already does.

One shared schedule across every trade
[01]// WHAT SYNCS

WHAT MOVES INTO ACUMATICA.

Seven record types. Each one is entered in one system and moves to the other. Employees can start on either side; you choose during mapping. Everything else is entered in Linarc because it is created on the project, then pushed to Acumatica.

RECORD
ENTERED IN
MOVES TO
Employees
Entered in Linarc or QuickBooks, your call
Moves to The other system
Vendors
Entered in Linarc
Moves to Acumatica
Cost Codes
Entered in Linarc
Moves to Acumatica
Projects
Entered in Linarc
Moves to Acumatica
Contractor Budgets
Entered in Linarc
Moves to Acumatica
Cost and Expenditures
Entered in Linarc
Moves to Acumatica
Payroll
Entered in Linarc
Moves to Acumatica
HOW DIRECTION WORKS

From the system where it's entered to the other one, one way. Not two-way. Payroll sends calculated wages, not timesheet hours or rates.

[02]// HOW IT RUNS

MAP IT ONCE. THEN LEAVE IT ALONE.

Background sync

Mapped records move to Acumatica without anyone pushing a button. New project in Linarc, new project in Acumatica. New cost code in Linarc, same cost code in the books.

Staged push

When finance wants to see a batch before it moves, select records across categories, stage them, and push them to Acumatica in one step. Sync status for the whole company shows in one view.

Employees move fast

Add an employee in the system you chose for employees and it appears in the other within moments. Only employee records move at that speed. The rest sync automatically or by a manual staged push, depending on their Auto-Create and Auto-Update settings.

[03]// SETUP

THREE STEPS TO CONNECTED.

01
REQUEST
Tell your Linarc account admin you run Acumatica.
02
PROVISION
A dedicated Acumatica space is set up inside your Linarc account.
03
CONNECT
Link your Acumatica instance to Linarc, map the records, and pick where employees get entered. You don't touch it again unless your setup changes.
[04]// WHAT YOUR TEAM STOPS DOING

DOUBLE ENTRY, RETIRED.

Every one of these used to be keyed in Linarc and then keyed again in Acumatica:

01
Employees, vendors, cost codes, projects
02
Contractor budgets
03
Cost and expenditures from the field
04
Payroll records
WHAT THIS MEANS
Now each is entered once by the people who create it. Finance keeps Acumatica. The field keeps Linarc. The job cost in both is the same number because it came from one entry.
See how Costs and Budgets work in Linarc →
[05]// QUESTIONS CONTROLLERS ASK

QUESTIONS CONTROLLERS ASK

Does data flow both ways?

No. Each record type moves one way, from the system where it's entered to the other. Vendors, cost codes, projects, budgets, costs and payroll are entered in Linarc. Employees can start in Linarc or in Acumatica. Vendors and cost codes already in Acumatica are not imported into Linarc.

What about invoices?

Invoices created in Linarc do not push to Acumatica. Invoice sync, with the paid status returning to Linarc, is available on QuickBooks Online and QuickBooks Desktop. The seven record types above all sync with Acumatica.

Is it real time?

Employee records come close: added where you enter employees, visible in the other system within moments. Every other record syncs automatically or by a manual staged push, depending on its Auto-Create and Auto-Update settings.

Do we have to accept everything the sync sends?

You decide which records are mapped when you connect. For more control, stage the records you want and push them yourself.

Can we connect Acumatica and another accounting system?

One per Linarc company at a time, and one Acumatica entity per Linarc company. Linarc also connects to Sage Intacct, QuickBooks Online and QuickBooks Desktop.

[06]// MAKE THE CALL

ACUMATICA STAYS.THE RETYPING GOES.

Bring your controller to the demo. We'll walk through what moves into Acumatica, which way, and what stays put.