Tabs Invoice Sync - Flexprice

What gets created in Tabs

When Flexprice syncs an invoice, it maps Flexprice entities to Tabs entities, creating each one only if it does not already exist.

Flexprice entity	Tabs entity	Behavior
Customer	Customer	If the Flexprice customer is not yet linked to a Tabs customer, Flexprice creates one and stores the link
Subscription	Contract	If the invoice’s subscription has no linked Tabs contract, Flexprice creates a contract on the customer
Invoice line items	Obligations	Flexprice raises obligations against the contract from the invoice’s line items
Invoice	Invoice (draft)	The invoice is generated in Tabs in draft state, open to modification

The sync is idempotent. Existing customers and contracts are reused, so re-syncing an invoice does not create duplicates.

When sync happens

Flexprice syncs an invoice to Tabs when both of these are true:

The Tabs connection is active

Invoice Sync is enabled on the connection

Sync is triggered at two points in the invoice lifecycle:

Invoice finalization - when an invoice transitions to finalized

Draft invoice computation - when a draft invoice is computed

Syncing draft invoices to Tabs is configurable. To change whether draft invoices are pushed, contact your Flexprice point of contact.

Invoices arrive in Tabs as drafts, so you can adjust them in Tabs before finalizing and collecting payment there.

Troubleshooting

Scenario	Behavior
No Tabs connection configured	Sync skipped
Invoice sync toggle off	Sync skipped
Customer not yet in Tabs	Flexprice creates the customer, then continues
Subscription has no Tabs contract	Flexprice creates a contract on the customer, then continues
Invoice already synced to Tabs	Reused; duplicate creation is prevented
API key is read-only	Sync fails - recreate the key in Tabs with Editor (full access)

​What gets created in Tabs