Procountor setup

Connect Procountor for read-only company reporting.

Omadata uses Procountor's API Key login so a signed-in Procountor user can choose the company and authorize reporting access. Omadata stores the resulting user/company API key encrypted and uses short-lived access tokens for backend sync.

How connection works

  1. 1Sign in to Omadata and verify your email.
  2. 2Accept the integration data access terms and complete MFA step-up before connecting financial data.
  3. 3Open Flows and choose the Procountor company feed.
  4. 4Omadata redirects you to Procountor's API Key login. Sign in there and choose the company you want to connect.
  5. 5Procountor returns to Omadata with a short-lived code. Omadata exchanges it for a company-bound API key and then for short-lived access tokens.
  6. 6You can disconnect Procountor from Omadata, which stops new syncs and clears stored provider credentials.

Connection facts

PurposeRead-only company finance dashboards and monitoring.
Initial dataCompany income, spending, invoices, cash position, and ledger visibility.
Never used forPayments, invoice approvals, bookkeeping mutations, or bank-account control.
CredentialsProvider API keys and tokens are encrypted at rest.
Open Flows →

Recommended Procountor permissions

Use a Procountor user or technical user with the minimum rights needed for reporting. Omadata's first Procountor scope should be read-oriented: invoices, ledger and company reporting data needed to show dashboards.

Do not grant rights for payment initiation, approvals, bookkeeping edits, or administration unless a future feature explicitly requires and documents those rights.

Before production use

  • Confirm the registered redirect URI matches Omadata exactly.
  • Validate the integration in Procountor's test environment.
  • Confirm production access approval and customer support contact details.
  • Review Procountor release notes and API terms before rollout.