Alegra integration

Connect from Bookkeeping → Integrations → Alegra using the email and API token shown in your merchant account. Confirm the detected company before saving. Invoice import starts enabled. Payment recording and MakePay notifications start disabled.

Connect your company

In Alegra, open Settings → API – Integrations with other systems. Copy the API email and generate or copy a dedicated token. Enter them in MakePay and select Check API key. See Alegra's authentication guide.

The connection reads the native company UUID, name, currency and accounting precision. Confirm the displayed business. A different company requires a separate connection. Replacing credentials for the same native company preserves its invoice links and history. Credentials are encrypted with your MakePay company and connection context; neither the token nor API email is returned in connection summaries.

Read permission is needed for company information, invoices, bank accounts and payment numbering. Payment reads are needed for reference recovery; payment writes are required only if you enable recording. The connection uses Alegra's core accounting API at https://api.alegra.com/api/v1. Alegra MCP and Payroll use different APIs and authentication.

Configure invoice payments

To enable Accept and record MakePay invoice payments, choose:

• The receiving or clearing account from Alegra's active bank/cash accounts.
• That account's actual currency. If the API omits the currency, inspect the account in Alegra and explicitly confirm the value. A returned native currency must agree with your selection.
• The payment method to use in Alegra: Transfer, Cash, Deposit, Check, Credit card or Debit card. This classifies the ledger receipt; it does not charge a payment source.
• An active non-electronic receipt numbering series. If none appears, create or enable an appropriate internal payment series in Alegra, then check the key again or reopen Settings. MakePay explicitly selects that series and sends stamp.generateStamp=false.

MakePay rereads the invoice, company, receiving account and receipt series before checkout and before first dispatch. Only open invoices with a positive native balance can accept checkout. Amounts must fit the native accounting precision exactly and MakePay checkout's two-decimal limit; no value is rounded. Foreign-currency invoices retain their native exchange rate and require a receiving account in the invoice currency. A changed balance, customer, currency or unavailable mapping requires review.

After a confirmed checkout, MakePay records the exact received amount against the original invoice. The original payment method, receipt series, account currency, exchange rate and UTC settlement date are retained for reconciliation, even if you later change settings. The payment is an accounting receipt. This connection does not initiate a bank transfer, card charge or payout, and does not issue an electronic tax receipt. Alegra's independently configured notifications and automations still apply.

Sync, recovery and notifications

Full invoice scans run in batches of 20 about every five minutes. Larger accounts take several runs. Scans repeat to refresh balances and voids. The panel shows the most recent 100 imported invoices. Sync requests another batch. Voided invoices pause unpaid MakePay links.

Before dispatch, MakePay stores the exact request and a stable reference in the payment's private observations. Alegra has no documented payment-reference query filter, so recovery scans the customer's payment history in bounded batches. Long histories continue across worker runs. New receipts are caught up; changed or deleted pagination boundaries restart the search safely. Recording waits until the relevant complete search succeeds. This can delay the first recording for customers with long histories.

A receipt is accepted only when its reference, customer, currency, amount, receiving account, method, date and exact native invoice allocation agree. A final invoice balance alone is insufficient. Duplicate references, partial allocations, other document allocations, fiscal stamping or inconsistent proof require review.

There is no assumed API idempotency guarantee. After an uncertain dispatch, MakePay keeps checking the original reference and never automatically posts a replacement. If a payment is delayed in Alegra's API, a later worker run can recover it. Use the displayed reference and Alegra's payment records when reviewing an uncertain result.

Payment-recorded and sync-problem notifications are optional, in-app and deduplicated. Turning recording off or changing receipt mappings pauses unpaid links; confirmed checkouts retain their original context. Disconnecting preserves local history.

The connection currently supports invoice import and optional confirmed checkout recording. Wallet expenses, receipt uploads, invoice creation and automatic payment-link insertion into Alegra documents are unavailable through this connection. No live vendor ledger round trip is claimed without merchant credentials.