Connections

Banks: where charges come from

  • Wise — a read-only API token. Polls for new transactions; history reaches about a year back.
  • GoCardless open banking — most European banks, approved once through your bank's own login. Transactions sync automatically.
  • Statement upload — CSV or PDF exports from any bank, dropped onto Imports whenever you like.
  • Bank alert emails — if your bank emails you about purchases, forward those alerts to your inbound address and they become transactions.

You can connect more than one source — a Wise account plus a statement from another bank, for example. Duplicates are detected by amount, merchant and date, never silently merged.

Inboxes: where receipts live

  • Gmail and Outlook — OAuth connect, strictly read-only. Receipt Pair searches for attachments and downloads candidates; it cannot send, delete, or label your mail.
  • IMAP — any other mailbox with an app password.
  • Your inbound address — every workspace gets one. Forward receipts yourself or give it to vendors; PDFs, photos and e-invoice XML are all accepted.
  • Telegram — photograph a receipt and send it to the bot. See Agents and Telegram.

Accounting: where receipts end up

  • e-conomic — via your capture inbox address or the API integration.
  • Xero and QuickBooks — OAuth connect; receipts attach to the matching transaction, and remote deletions flag the local record for review.
  • Sage and Dinero — for Danish workflows.
  • Any capture email — most accounting systems accept receipts by email; if yours does, that address is all you need.

A test send at the end of setup confirms delivery before the integration goes live. Manage everything from the Integrations view in the app.

© 2026 Receipt Pair · receiptpair.com