QuickBooks Online
Link your accounting account to the right Gruv team. Check its connection status and sign in again when needed.
Connect from your Gruv dashboard
Integrations
Choose how your systems connect to Gruv
Keep using the tools your team knows. Bring payment data into Gruv by file or API, connect your accounting account, and send useful results back.
Start with a file. Connect more as the work grows.
Built around your existing tools
Your application. Your accounting. Connected.
Pick the simplest path that works
Start with CSV for a run your team reviews together. Add APIs and webhooks when your application needs to do the recurring work.
- APIs
- Create payment requests and retrieve records from your own application, with request identifiers to manage retries.
- Webhooks
- Receive the payment events enabled for your account at your own endpoint, so your system can react to status changes.
- File imports
- Upload a payout CSV and review line-level validation errors before processing the batch.
- Exports
- Download payout results with references, amounts, currencies and statuses for finance to match against the ledger.
Your tools. Connected to the payment.
Your payout file
CSV import
{ }
Your product
API requests
Gruv
Requests · Reviews · Payment results
Status updates
Webhooks to your system
Finance records
Exports for your ledger
Keep your original invoice and payee references
Connect your accounting account
A team owner or admin can authorise a QuickBooks Online or Xero connection from Gruv. Choose your team, sign in to your accounting account and check the connection status in the dashboard.
Xero
Sign in and choose the Xero organisation you want to connect. Check the selected organisation before completing setup.
Connect from your Gruv dashboard
Connecting the account is the first step. We help you agree which records to export, how fields map and how finance will check the first results before enabling the accounting sync.
Plan connections to your other systems
Accounting and ERP connections use Gruv-assisted setup. The other categories show systems your team may want to connect, not live Gruv connectors or partnerships. Tell us what records you need to exchange.
Earnings & partner networks(7)
Bring creator or affiliate earnings into the payment process, with the references needed to trace each payout back to an earnings statement.
Accounting & ERP(7)
Plan how invoice references, payment results and reconciliation records will reach your accounting system.
We help set up these accounting connections. Bring your credentials and required fields; we check the first results with your team before launch.
SSO & identity(4)
Discuss company sign-in, team access and how account changes will be handled when people join or leave.
HRIS & people systems(3)
Use existing contractor details as the starting point for onboarding, with clear ownership of updates and engagement dates.
Tax filing & paperwork(2)
Plan how payee details, tax documents and payment totals will reach the tools your team uses for filing.
Workplace tools(1)
Discuss sending actionable payment updates to the place your operations team already follows up on work.
Start simple, then add more
- 01
Map the data you need
Choose the source records and the results you want back. Match invoice, payee and payment references to the fields your team already uses.
- 02
Test a complete payment cycle
Check an accepted record, a rejected record and the results export. For webhooks, also test repeated events and a delivery that needs retrying.
- 03
Connect the recurring work
Use an API or webhook where your system needs to create payments or receive updates. Keep a named owner for failed deliveries and account reconnection.
Make the handoff easy to operate
A file has an invalid row
Use the reported line and field to fix the source. Keep invoice references intact, including leading zeros, and compare the new upload with the payments due.
An event arrives twice or late
Use the payment identifier to recognize repeats. Check the current status before an older event changes a completed payment in your system. Test this handling during setup.
The updates stop arriving
Check the last successful delivery and accounting connection status. Agree who handles reconnection and how to recover missing records before relying on the connection at close.
Integration questions, answered
Do we need an API integration to get started?+
No. You can start with CSV imports and results exports. Use an API when your application needs to create or retrieve records, and webhooks when it needs payment updates. Choose the connection around how often the work runs and who needs to review it.
Are all the listed systems connected to Gruv?+
Connect QuickBooks or Xero from the dashboard. The accounting and ERP systems marked “Gruv-assisted setup” need credentials, field mapping and a test run with your team. For tools marked “Discuss connection,” tell us which records need to move. We will confirm the connection method and availability.
Does Gruv connect to our ERP, HRIS, or identity provider?+
Tell us the system and what you want it to exchange with Gruv: payment results for NetSuite, contractor details from an HR system, or company sign-in through an identity service. We will confirm the connection method, fields and availability for that request.
What happens when a file or webhook fails?+
CSV validation reports the line, field and reason so you can correct the source and upload again. For a webhook connection, agree the retry and recovery path during setup, including repeated or missing events. Test those cases before your team relies on the updates.
What should we bring to an integration conversation?+
Bring a sample file, the names of your systems and the fields finance needs back. Include how often the data moves and one example of an error your team has had to fix. That helps us map the connection and the recovery steps together.
Connect the tools your team uses
Tell us which tools you use and what needs to move between them. We will help you choose a starting point and the records finance needs back.
Talk through your systems