Questions, answered.
About the product, about Ledgestra as a company, and about treasury management as a discipline.
Product FAQ
What is Ledgestra?
A treasury management system (TMS): bank and system connectivity, payment approvals and transmission, bank statement reconciliation, cash and liquidity visibility, and cash flow forecasting, all sharing one data model.
What bank connectivity is supported?
SFTP and direct API connectivity, for both bank-side and internal system-side connections, with real connectivity testing built into the setup flow.
Can it handle more than one company?
Yes — Ledgestra supports multiple companies, and each one's data is kept completely separate from every other's, not just hidden behind navigation.
What statement and payment formats does it read?
MT940, MT942, BAI2, CAMT.052/053/054, and CSV for statements, matched automatically to the outgoing payment format each bank expects.
Is there an approval workflow for payments?
Yes — configurable, multi-level approval chains with per-approver amount limits, plus full status tracking from creation through bank acknowledgment.
Is there an audit trail?
Yes — changes to sensitive records are logged with who, what, and when, scoped to the company that owns them.
Company FAQ
Where is Ledgestra based?
Our office is in Lyon, France. See the Contact page for full details.
How do I get in touch?
Use the contact form, email hello@ledgestra.com, or call us — details are on the Contact page.
Can I get a demo?
Yes — request one from the Contact page and we'll walk through the platform on your own use case.
What size companies is this built for?
Organizations managing more than one bank relationship or legal entity, where treasury work has outgrown spreadsheets — from a single growing company to a multi-entity group.
Who handles support after onboarding?
Our customer support team, reachable at support@ledgestra.com.
Industry FAQ
What is treasury management software?
Software that gives a finance team visibility and control over cash, payments, and bank relationships — instead of managing them through bank portals, exports, and spreadsheets.
Why does multi-bank connectivity matter?
Most companies bank with more than one institution. Without a single connectivity layer, every additional bank relationship means another portal, another file format, and another blind spot in cash visibility.
How is a TMS different from an ERP's payments module?
An ERP payments module is usually built around one company's general ledger. A TMS is built around treasury's own concerns — multi-bank connectivity, liquidity across entities, and forecasting — often sitting alongside, not inside, the ERP.
What makes cash flow forecasts more accurate?
Forecasts that are reconciled against actuals as they happen, rather than rebuilt from scratch each cycle, so variance is tracked and the model improves over time.
What regulatory considerations apply?
Data residency, access control, and audit requirements vary by region and industry — treasury software should support real authentication, role-based access, and a genuine audit trail as a baseline, not an add-on.