Mekari Jurnal integration

Connect your company's Jurnal HMAC credentials from Bookkeeping → Integrations → Mekari Jurnal. Import existing sales invoices and optionally record confirmed MakePay payments. MakePay does not need to register an OAuth app.

Connect your company

1. Obtain a Client ID and Client Secret for your Jurnal company from the Mekari developer portal or your Mekari support contact. Choose Jurnal and the intended company. These are company-specific HMAC credentials; a different company or Mekari product needs its own pair. See Mekari's authentication guide.
2. Give the credential access to read the active company, accounting currency, accounts, payment methods, sales invoices and receive payments. Enable receive-payment creation only if you intend to record payments. Your Mekari subscription and assigned scopes must allow these APIs.
3. Select Connect, enter both credentials and choose Check API key. Confirm the detected company name, ID and accounting currency.
4. Optionally choose a receiving account and payment method. The account must be an unlocked, non-parent Cash & Bank account in the company's accounting currency, with a unique name among its active accounts. Select an existing payment method; MakePay does not create methods or accounts.
5. Enable only the workflows you want and save. Invoice import starts enabled. Payment recording and notifications start disabled. Both credentials are encrypted together with company-bound protection and are not returned after saving.

The API is Jurnal's hosted service at api.mekari.com. The connection signs each request, including its exact query string, with a fresh UTC date. Payment requests also include the SHA-256 body digest. No custom server address is needed.

Invoice payments

Enable Accept and record MakePay invoice payments to share MakePay payment links from imported open invoices. Links appear in the connection panel and the main Invoices list. Checkout verifies the current company, invoice customer, balance, currency, receiving account and selected payment method.

Payment recording currently supports approved, undeleted invoices in the company's accounting currency with a positive whole-unit balance. This follows the documented integer amount accepted by Jurnal's receive-payment creation endpoint. Foreign-currency and fractional-balance invoices are imported for review without an enabled checkout. Draft, void and fully paid invoices cannot accept new payments.

Each checkout keeps its receiving account, account name, payment method and invoice number. Changing the configured account or method pauses older unpaid links. Completed payments continue through reconciliation with their original mapping. A changed invoice number or account name prevents an unstarted receipt from being posted and requires review.

Only verified MakePay settlements can create a receipt. Sandbox/demo settlements, adjusted values, mismatched currency or customer, and multiple completed checkouts are held for review. Receipt creation can affect your Jurnal ledger. MakePay rereads the created receipt and verifies its custom reference, customer, account, payment method, date, currency, total, invoice allocation and zero withholding. Browser redirects do not mark invoices paid.

Sync and notifications

Sync runs in batches about every five minutes and repeats full scans to find edits. The list displays the most recent 100 imported invoices. Use Sync to request another batch. Pagination is validated; repeated or reordered pages stop with an error. An incomplete account list prevents setup instead of guessing which account a name refers to.

Recorded-payment and sync-problem notifications are optional, in-app and deduplicated. This connector does not enable wallet expense exports, supporting-file uploads, automatic invoice creation or existing-invoice edits. Share payment links from MakePay without replacing invoice documents in Jurnal.

Recovery and credentials

Before a receipt request is sent, MakePay stores its approved details and a stable custom ID. Jurnal documents receipt retrieval by ID or custom ID. If a response is lost, MakePay looks up that custom ID and verifies the receipt. If a previous request remains uncertain and no receipt is found, MakePay requires review; it does not automatically post another receipt. Check the displayed reference in Jurnal before taking manual action.

Use Replace API key to rotate the HMAC credentials for the same detected company. Disconnect before selecting another company. Disconnect pauses unpaid links and requires completed checkouts to be reviewed first. Reconnecting the original company preserves its imported invoices and history.

Local contract, recovery and UI tests use fixtures. A live Jurnal account round trip needs merchant credentials and is not implied by fixture results.