Certify
Index

Common Issues

This page covers the problems most often encountered connecting to Certify and generating journals, with how to resolve them.

Connection Problems

"Could not contact..." error

The app could not reach the Certify API. Check:

  • Base URL is correct (default https://api.certify.com/v1/).
  • API Key and API Secret are correct and current.
  • Outbound HTTP access is allowed for the extension.

The error message includes the path, reason phrase, and HTTP status code to help pinpoint the cause.

Authorization / 403 responses

A 403 typically means the API key/secret are wrong or not authorized for the requested data. Re-check your credentials in Certify and re-enter them on the Setup card. Note that for some calls a 403 results in no data rather than a hard error, so an empty result can also indicate an authorization problem.

"Could not read..." error

The app reached Certify but received a response it could not parse as expected. Turn on Use Debug Mode to see the raw response, then verify your account and endpoint with your Certify administrator.

Missing required field

If you see a test-field error for Base URL, API Key, or API Secret, one of those is blank on the Setup card. Fill it in. See API Connection Setup.

Journal Generation Problems

"Journal Batch ... is missing a No. Series"

The general journal batch you selected has no number series, so the app cannot assign a document number. Open the batch and assign a number series. See Journal Template and Batch.

Lines post to the fallback account

Expense lines whose category has no valid G/L mapping go to the Fallback G/L Account. This is intentional so nothing is lost, but it signals a missing category mapping. Map the category and regenerate. See Expense Category to G/L Mapping.

A report won't process in multi-select

When generating for multiple reports, only those in Waiting status are processed. A report already Settled is skipped to avoid duplicates. If you really need to regenerate it, select it on its own and confirm the re-generation prompt.

Functionality is disabled in production

If actions are greyed out or you see an unregistered notification in production, the app is not licensed. Register it. See Registration.

Posting Problems

Because the app creates standard general journal lines, normal Business Central posting validation applies. Typical issues:

  • Closed posting period — adjust the posting date or open the period.
  • Blocked G/L account, dimension value, or mandatory dimension rules.
  • Tax setup mismatches when a default tax area is applied.

See Mapping Issues for mapping-related posting errors.