Native integrations

Stop fixing exports after the week is already closed.

Arcova connects directly to QuickBooks Online and ADP Workforce Now so approved shifts, payments, credits, payroll checks, and journal entries move from verified work instead of hand-cleaned spreadsheets.

Included in every plan No third-party connectors No additional fees Pre-export readiness checks

QuickBooks Online

Native two-way sync via OAuth2

One-click authorization. Customers, invoices, payments, credits, and payroll journal entries sync from Arcova as the operational record is approved. Changes made directly in QuickBooks are detected through Change Data Capture polling, so finance can see what moved and what needs attention.

1

Connect

One-click OAuth2 authorization from Billing Settings. No API keys to manage.

2

Map accounts

Map 12 QuickBooks account types to your chart of accounts. Five minutes of setup.

3

Sync

Everything syncs automatically as it happens. Monitor from the real-time dashboard.

Stale sync token detection prevents duplicates
Rate limit handling with automatic retry
Full audit trail for every synced transaction
Failed syncs retryable from the dashboard

What syncs

Customers

Two-way

Customer created or updated

Billing customers push to QuickBooks. Changes in QuickBooks detected via CDC polling.

Invoices

Outbound

Invoice sent, paid, or voided

Invoices sync with correct line items, rates, and client references. Status stays in lockstep.

Payments

Outbound

Payment received

Client payments through Stripe or payment portal record in QuickBooks automatically.

Credits

Outbound

Credit applied

Applied credits sync as credit memos, keeping your AR accurate.

Payroll journal entries

Outbound

Payroll period exported

Payroll runs export as journal entries with full account mapping across 12 account types.

ADP

ADP Workforce Now

Purpose-built EPI file export

One-click EPI file generation with pre-export readiness checks. Configure your company code, batch ID, and hours codes once. Every export after that is a single click with validation that catches missing file numbers and invalid settings before the file is generated.

1

Configure

Enter your ADP company code, file ID, batch ID, and hours codes. Five minutes of one-time setup.

2

Validate

Readiness check verifies every employee has a file number and settings are valid before export.

3

Export

One click generates a perfectly formatted EPI CSV. Upload to ADP and run payroll.

Missing file numbers flagged by name
Department codes auto-truncated to 6 chars
Zero hours suppressed (empty, not 0.00)
Export history with downloadable files

EPI file columns

Co Code

Your ADP company code (3 chars)

Batch ID

Import batch identifier

File #

Employee ADP file number

Reg Hours

Regular hours worked

O/T Hours

Overtime hours

Holiday Hours

Configurable hours code (default: H)

PTO Hours

Configurable hours code (default: V)

Double Time

Configurable hours code (default: D)

Temp Dept

Optional department allocation (6 chars max)

Temp Rate

Optional pay rate override

How we compare

The question is not whether data exports. It is whether finance trusts it.

Most integration pain shows up after the damage is done: bad mappings, missing employee file numbers, duplicate syncs, and invoices that do not match approved work. Arcova surfaces those problems before export or sync.

QuickBooks sync type

Native OAuth2, real-time

Third-party connector (Amaka), daily batch

QuickBooks data direction

Two-way with CDC polling

One-way outbound only

Entities synced to QB

Customers, invoices, payments, credits, journal entries

Invoices and wage expenses

Account mapping

12 QB account types, user-configured

Limited or none

ADP export format

Purpose-built EPI file with validation

Generic CSV export

Pre-export validation

Readiness checks before every export

Export and hope

Sync monitoring

Real-time dashboard with retry

Limited visibility

Additional cost

Included

Connector subscription fees

Common questions

Straight answers about how the integrations work.

Bring one payroll week and one invoice cycle.

We will show what syncs, what gets validated, what fails safely, and how finance traces numbers back to approved shifts.