Quit digging through email for GitKraken invoices every month. belege.ai hunts them down, pins each one to the right bank transaction, and keeps the paper trail in one place.
Start freeThe workflow
Save your GitKraken login securely. The browser agent signs in on your behalf, and you approve 2FA over Telegram whenever it comes up.
The moment a GitKraken charge shows up in your bank account, the agent goes after the matching receipt — even if it only becomes available later.
The receipt lands on the right transaction, ready for the monthly package or your bookkeeper handover.
Vendor-specific collection
GitKraken receipts are behind a login—the browser agent signs in for you and downloads the relevant receipt; you confirm 2FA via Telegram.
belege.ai starts from the bank charge and goes looking for the one GitKraken receipt that matches it.
The charge comes first
Your open bank transactions are the to-do list. The agent knows which charge still needs a document — you never have to comb through portals and email folders yourself.
The agent hunts for the one receipt that fits a specific payment: its amount, date, counterparty, and context.
The PDF, receipt date, amount, and payment context travel together — ready for the monthly close and the handover to your bookkeeper.
When the original document can't be found, the transaction stays visible and traceable — nothing gets quietly filed away.
Common questions
belege.ai keeps an eye on your bank transactions for missing receipts and pulls the matching GitKraken invoice from the connected source. Depending on the vendor, that's email, forwarding, an API, or the browser agent.
The agent keeps the charge open, waits for the receipt, and retries. If the original truly can't be found, belege.ai can propose a documented substitute receipt as a fallback.
Yes. Each receipt is matched to its transaction and goes into the monthly package or a login-free link your bookkeeper can open — no account needed.
Two minutes to set up. Free to start — no credit card required.
Start free