Stop hunting for HTML Signature invoices every month. belege.ai collects them, matches them to the correct bank transaction, and keeps the evidence together.
Start freeHow it works
Store your HTML Signature login securely. The browser agent signs in for you; you confirm 2FA through Telegram when needed.
When a payment to HTML Signature appears in your bank account, the agent looks for the matching receipt, including when it becomes available later.
The receipt is linked to the right transaction and is ready for your monthly package, DATEV export, or accountant link.
Provider-specific collection
HTML Signature receipts are behind a login—the browser agent logs in for you and downloads the relevant receipt, while you confirm 2FA via Telegram.
belege.ai starts with the bank payment, then searches specifically for the matching HTML Signature receipt.
Payment first
Open bank transactions form the work queue. The agent sees which payment still needs evidence instead of making you search portals and email folders.
The system looks for the receipt that fits the amount, date, counterparty, and context of a concrete payment.
The PDF, receipt date, amount, and payment context stay together for the monthly close and accountant handover.
If the original document cannot be found, the transaction remains traceable instead of being silently filed away.
Frequently asked questions
belege.ai watches for missing receipts on bank transactions and retrieves the matching HTML Signature invoice from the connected source. Depending on the provider, that can be email, forwarding, an API, or the browser agent.
The agent keeps the payment open, waits for the receipt, and tries again. If the original receipt cannot be found, belege.ai can propose a documented self-receipt as a fallback.
Yes. The receipt is matched to the relevant transaction and can be included in the monthly package, DATEV export, or a login-free accountant link.
Set up in 2 minutes. Free to start, no credit card.
Start free