Skip to main content
Use xero in twins and put this configuration under seed_config.xero. Xero Accounting organisation with contacts, chart of accounts, tax rates, inventory items, invoices, payments, bank transactions, credit notes, purchase orders, quotes, manual journals, tracking, attachments, reports, OAuth connections, tenant isolation, 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.xero. 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 Xero-native field names and aliases for relationships. Tokens must authorize the selected tenant. Resource collections accept their canonical provider names and the supported snake_case aliases; explicit dates are preserved.

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[]

tax_rates[]

tax_rates[].TaxComponents[]

contacts[]

items[]

invoices[]

invoices[].LineItems[]

payments[]

attachments[]

Typed configuration objects

Named object types in the parameter table use these fields.

XeroOAuthClient

XeroTenant

XeroToken

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