Skip to main content
Use quickbooks in twins and put this configuration under seed_config.quickbooks. QuickBooks Online Accounting company with customers, vendors, employees, accounts, products and services, invoices, estimates, sales receipts, payments, bills, purchases, journal entries, budgets, attachments, reports, queries, CDC changes, OAuth credentials, and accounting webhooks.

Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

Parameters

The following fields belong directly inside seed_config.quickbooks. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Seeding behavior

Use native QuickBooks entity fields, directly or inside values, with an optional alias. Relationship shortcuts such as customer_alias, vendor_alias, and item_alias resolve previously created records. Token grants must include the selected realm_id.

Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

accounts[]

customers[]

vendors[]

items[]

invoices[]

invoices[].Line[]

bills[]

bills[].Line[]

attachments[]

Typed configuration objects

Named object types in the parameter table use these fields.

QuickBooksCompany

QuickBooksOAuthClient

QuickBooksToken

See Scenario seeding for saving, provisioning, and resetting fixtures.