How MakePay works with Alegra
Alegra’s MakePay connection imports existing invoices and can record a confirmed crypto checkout as an accounting receipt. You choose the receiving account and payment method, plus an active non-electronic numbering series for that receipt.
This is a payment-reconciliation workflow, not electronic tax-document issuance. The connector explicitly requests an internal receipt without fiscal stamping. Your invoice and its original accounting exchange rate remain the source for collection.
Before you connect
- The API email and token from Alegra Settings → API – Integrations with other systems.
- An active receiving or clearing account, with its currency checked in Alegra if the API does not expose it.
- An existing payment method and active non-electronic receipt numbering series, with an open invoice whose amount fits the supported exact precision.
Set up Alegra with MakePay
- 01
Confirm your Alegra company
Enter the API email and token in Bookkeeping → Integrations → Alegra. Select Check API key and confirm the detected native company identity, currency and accounting precision.
- 02
Set up the receipt
Choose the receiving account, account currency, payment method and non-electronic receipt series. If the API omits account currency, inspect it in Alegra and explicitly confirm the value. Create or enable an internal series in Alegra if needed.
- 03
Share a supported invoice balance
Enable payment recording and sync. Open the imported invoice’s MakePay link. Foreign-currency invoices require a receiving account in the invoice currency; amounts must fit both Alegra precision and MakePay’s two-decimal checkout limit exactly.
- 04
Verify the accounting allocation
After settlement, MakePay records the receipt with fiscal stamping disabled and verifies its private reference, customer, account, series, date, method, exchange rate and exact invoice allocation.
What happens when a customer pays
A receipt series chosen by your bookkeeper
The selected non-electronic series determines internal payment numbering. The API request uses stamp.generateStamp=false. It does not issue an electronic tax receipt, bank transfer or card charge.
Recovery across customer history
Alegra has no documented payment-reference query filter for this flow. MakePay searches the customer’s payment history in bounded batches and continues long searches across worker runs. This can delay initial recording for a customer with extensive history.
Check these connection limits
- Unsupported precision, changed balances or missing receiving-account currency confirmation require review; amounts are never rounded.
- An uncertain receipt is searched by its original reference instead of being posted a second time.
- Wallet exports, receipt-file uploads, automatic invoice creation and existing-document link insertion are unavailable.
Setup resources
Follow the detailed connection guide and your software’s own account requirements. Configure merchant settlement before sharing a customer invoice.
