Question 1

Where do I find contract value and recognized revenue?

Accepted Answer

On obligations rather than on contracts, which surprises people. Contracts themselves carry the customer, status, dates, and source metadata but no amounts, ARR, or line items at all. Each obligation linked to a contract holds the financial terms: a billing schedule with dates, recurrence, payment terms and quantity, a pricing array with tier, amount and tier minimum, a revenue schedule containing recognized revenue by timeframe with a books closed flag, plus discount and seat configuration. So any revenue model starts by joining obligations back to contracts on the contract ID.

Question 2

What objects can Polytomic sync from Tabs?

Accepted Answer

Customers, contracts, obligations, invoices, payments, credit memos, renewals, items, events, event types, categories, classes, and custom fields. A few naming differences are worth knowing: there is no separate products object because products map to items, no separate usage object because usage is represented as events, and no standalone revenue schedules table because revenue schedules are nested inside obligations. Everything is there, just organized around Tabs' own model rather than the names you might expect.

Question 3

Which objects sync incrementally?

Accepted Answer

Four: customers, contracts, and invoices filter on last updated time, and events filter on their datetime. Everything else, including obligations, payments, items, renewals and credit memos, is read in full on each ETL run. Worth planning for since obligations are usually the largest object given they carry the revenue detail. The cursor is also date precision rather than a full timestamp and the filter is inclusive, so the boundary day is reread each time, which is deliberate insurance against missing late arriving records.

Question 4

How is currency handled on revenue amounts?

Accepted Answer

Carefully is the honest answer. The obligation pricing and recognized revenue amounts do not carry an explicit currency of their own; the only currency field in the catalog is the customer's default currency. If you operate in a single currency that is a non issue, but for a multi currency book you will want to join through to the customer and confirm the assumption holds for your data before building reporting on it. One other detail: the discount amount is typed as a string while other amounts are numeric, so cast it in your models.

Question 5

Why move Tabs data into a data warehouse?

Accepted Answer

Because revenue questions are rarely answerable inside a billing tool alone. Whether usage predicts expansion, which segments renew, how recognized revenue tracks against pipeline, and what a customer is worth against what they cost to serve all require joining Tabs to your CRM, product data, and support system. Running ETL into your data warehouse makes those joins possible on definitions your finance and analytics teams agree on. Reverse ETL then runs the other way on the same platform, so contract value or invoice status can be written onto a Salesforce account.

Tabs

Perfect pairings

Recognized revenue detail

Full billing object model

Incremental core objects

Example workflows

What you can sync

From Tabs

To your destinations

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Tabs in minutes

More integrations beyond Tabs