Merge Accounting API vs Pennylane

Merge Accounting API

12 accounting platforms behind one set of common models, with writes. Launch jumps from free to $650 a month at the fourth linked account.

Pennylane

The v2 API has per-resource read and write scopes, an OpenAPI definition on every reference page, llms.txt and a breaking-change process that ran over 24 weeks. Access needs a paid Essentiel plan or partner approval, creation endpoints are not idempotent, and the API agreement lets Pennylane change or revoke the API without notice.

Merge Accounting API

1. Call GET /invoices/meta/post for the linked account first. Required fields differ by platform
2. Bills and sales invoices are one model. Set type to ACCOUNTS_PAYABLE or ACCOUNTS_RECEIVABLE
3. Append .md to any docs URL for the Markdown twin
4. Check sync_status before reading a freshly linked account. Common models fill in over the first sync
5. Look the record up before retrying a POST that timed out. There's no idempotency key

Pennylane

1. Call GET https://app.pennylane.com/api/external/v2/me first to confirm the token, user and company context
2. Stay under 25 requests per 5 seconds per token and wait for the retry-after value on a 429
3. Do not retry a create after a timeout without checking first. Only supplier invoice imports are deduplicated
4. Send filter and sort again with every cursor. The cursor stores position only
5. Send amounts as strings such as "120.00", and ask for :readonly scopes when the task only reads
6. Use the MCP server for reads only. It cannot create, edit or delete, and firm connections need company_id