Productive.io: COGS, revenue and cashflow planning

Connect Productive.io so Cortena can sync cost centers from your Productive workspace into reference data used for matching, booking, and planning-related workflows (COGS / revenue and cashflow planning streams).

Related: Cost centers on invoice line items and Connecting your accounting system.

1. Connect Productive

1. Open Settings → Integrations.
2. Select Productive.io.
3. Enter your Productive organization ID and Productive API token from Productive (generate a token with access to the organization you use for planning).
4. Click Connect Productive (or Update connection when rotating the token).

If the connection fails, the banner explains whether the token is invalid or revoked · generate a new token in Productive and update the connection.

2. Map cost center custom fields

Before syncing, configure Cost center mapping:

1. Choose which Productive custom field supplies the cost center value (number used in matching and export · for example a cost center code).
2. Choose a second custom field for the label (shown next to the number · for example project slug or name).
3. Both fields must belong to the same entity type in Productive (for example projects).
4. Click Refresh custom fields if you added fields in Productive recently.
5. Click Save mapping.

Cortena shows a reminder until value and label fields are saved.

3. Sync reference data

Under Reference data sync:

• Sync cost centers · incremental sync of planning cost centers into Cortena reference data.
• Full refresh cost centers · rebuilds the full list when mapping changed or data drifted.

Last sync time and row counts appear on the integration page. Synced cost centers are available in invoice comboboxes and matching like other reference data.

4. How teams use this

Typical flow:

1. Productive holds project / dimension custom fields used in COGS and revenue planning.
2. Cortena maps those fields to KOST-style reference rows.
3. AP books payables with the same codes Productive uses for cashflow and margin views.

Pair with Cost centers on invoice line items when invoices need different cost centers per line.

Tips and limitations

• You need a valid Productive API token and organization ID · Cortena does not OAuth Productive today.
• Mapping must be saved before the first sync; changing entity type clears the opposite field pickers.
• Disconnect removes the stored token from Cortena; re-connect to resume sync.
• Productive sync supplies cost center reference data · it does not replace your accounting system export.

Quick reference