This setup connects Cortena to Twinfield for payable export (provisional and final), lets you choose which purchase transaction type (journal) Cortena uses, and ensures users can open the related Cortena invoice directly from Twinfield transactions.
Who this is for: Finance admins connecting Twinfield and configuring Document Imaging for purchase invoices.
Where to configure in Twinfield
Go to Twinfield Company settings → Transaction Types.
Configure the same purchase transaction type Cortena uses for export. The default is Inkoopfactuur (ledger code INK). If your administration uses another purchase journal, select it in Cortena first, then apply the Document Imaging steps to that transaction type in Twinfield.
Step 0: Choose the purchase transaction type in Cortena
Settings → Integrations → Twinfield (after Twinfield is connected and an office is selected).
- Open Purchase transaction type.
- Click Load transaction types to fetch journals from Twinfield.
- Select the journal Cortena should use when exporting payables (default INK · Inkoopfactuur).
Provisional and final export both use the selected type. Sub-entities with an inherited Twinfield connection can set their own purchase transaction type per tenant.
Step 1: Save your current Link value
Before changing anything, copy the current Document Imaging Link value from your selected purchase transaction type and store it in Cortena (backward-compatible field).
Why: existing bookmarks and older Twinfield links can still resolve correctly after switching.
Step 2: Replace the Document Imaging Link with the Cortena URL
Copy the Cortena URL from the Cortena settings page and paste it as the Document Imaging Link value on the same purchase transaction type you selected in Step 0.
Step 3: Check required transaction type settings
Verify on your selected purchase transaction type:
- Quantities are allowed on line items.
- Free text field 1 is set to Allowed (not Mandatory).
Free text field 1 carries the link reference so Twinfield can open the correct Cortena invoice from provisional and final transactions.
Validation checklist
- Purchase transaction type is selected in Settings → Integrations → Twinfield
- Document Imaging Link on that transaction type is replaced with the Cortena URL
- Previous Document Imaging Link value is stored in Cortena for backward compatibility
- Quantities are enabled for line items
- Free text field 1 is Allowed
- A test invoice exported from Cortena opens correctly from Twinfield
- Reference data sync (creditors, VAT, cost centres) completed after connecting
Common mistakes
- Configuring Document Imaging on INK in Twinfield while Cortena exports to a different purchase transaction type
- Changing the Document Imaging link without saving the old link in Cortena first
- Setting Free text field 1 to Mandatory instead of Allowed