Planned connections for your bank, accountant and customer channels.
These integrations are part of the product roadmap, not live connections. Book a demo to discuss the tools you use and what would need to connect.
Product preview. Helmar.AI is in development. The features shown are planned; accounts and integrations are not open yet.
- Read-only bank feedPlanned · not live
- Rivilė every nightPlanned · not live
- All sub-processors in the EUPlanned · not live
How it connects
How the planned connections fit together.
The proposed workflow links the estimate, accepted version, documents and payments. The diagram shows the intended connections; none are available to connect yet.
- Your bankread-only feed, bank links
- Rivilėdocuments every night
- Smart-ID · Mobile-IDqualified signatures
- Your email domainproposals, follow-ups, documents
- SMS · WhatsApp · Viberthe channel the customer reads
- Peppolpublic-sector e-invoices
Catalogue
Planned integrations, by what they would do.
Every integration below is planned and not live. Plan badges show the proposed launch packaging.
Planned controls
Connections would stay under your control.
The settings below describe the proposed behaviour. Connections cannot be activated yet.
Proposed data flow
What moves, and when.
An illustration of the intended workflow. Sync timings and providers will be confirmed before integrations launch.
Bank matches
Incoming payments matched to advance requests and invoices by purpose and amount. Reminders stop; the job moves on.
Documents to Rivilė
Advance requests, PVM sąskaitos faktūros and credit notes issued that day. On Business, payments the accountant recorded come back.
The accountant’s export
Documents and KPO cash receipts, and the i.SAF XML on Business.
Everything, any time
Every document as a PDF, photos, and every record as CSV, also for 90 days after you cancel.
What does not move
Card numbers, your customers’ money, or an edit to an issued document.
Developers
Webhooks for the three moments that matter.
API access and webhooks are planned for Business. No production endpoints or customer API keys are available yet.
proposal.acceptedThe customer accepted one exact versionpayment.matchedA bank payment was matched to a documentdocument.issuedAn advance request, invoice or credit note got its number
Illustrative payload for a planned API. Field names and delivery behaviour are not a production contract.
{
"event": "proposal.accepted",
"estimate": "EST-1042",
"version": 1,
"accepted_at": "2026-09-14T10:16:00+03:00",
"accepted_by": "Lukas Jankauskas",
"total": { "amount": 23178.76, "currency": "EUR" }
}Questions
Straight answers.
- Does it work with Rivilė?
- This integration is planned, not live. Invoices go to Rivilė every night and payments your accountant records there come back. The two-way sync is on Business.
- What about other accounting software?
- This integration is planned, not live. B1, Centas and Finvalda exports, and the i.SAF XML.
- How does the bank feed work?
- This integration is planned, not live. A read-only connection to your bank. Exact matches are counted within minutes, and the consent is renewed every 180 days. Team and Business.
- Do you see card numbers?
- This integration is planned, not live. No. Card numbers are handled by the payment partner and never reach Helmar.AI.
- Is there an API?
- This integration is planned, not live. API and webhooks are on Business.
- Where is my data stored?
- The marketing website is hosted by Hostinger in Germany. Product integrations are not live. The providers and data locations will be confirmed before they are enabled; see the privacy policy for the website services used today.

See the preview
Discuss the connections your team would need.
Explore the product preview in a 20-minute demo. Accounts are not open yet. No card, no obligation.