---
title: "Contact Ledgeriano support, sales and security"
description: "Contact Ledgeriano support, sales or security by email. See what to include in a support request, such as the entry number and error reference code."
canonical: https://ledgeriano.com/contact
language: en
publisher: "Ledgeriano"
updated: 2026-11-05
---

# Contact Ledgeriano support, sales and security

> Contact Ledgeriano support, sales or security by email. See what to include in a support request, such as the entry number and error reference code.

Email is the fastest way to reach us. Choose the address that fits your question and a person on our team will reply.

Choose the right inbox

## Customer support

Help with your account, businesses, entries, reports, credits and the API.

## Sales

Questions about the trial, or planning a rollout for a group or an accounting firm.

## Security

Report a vulnerability or a suspected unauthorized access to your account.

## What to include so we can help in one reply

A clear request saves a round of questions. Where they apply, please include:

- **The business** the question is about: its name, and its ID if you have it.
- **The entry number**, for example entry #1024, or the report and date range you were viewing.
- **The error reference code.** When something fails on our side, the message ends with a short code, such as `7KD2QX9M`. That code lets us find the exact event in our logs.
- **What you did and what you expected**, step by step, plus a screenshot if it helps.
- **For API calls:** the method and path, the response status and body, the time with your time zone, and the name or last four characters of the API key.

Example

- Business: Northwind Trading (ID 12)
- Entry #1024, posted 2026-09-18
- Error reference: 7KD2QX9M
- Steps: opened the entry, clicked Reverse, chose 2026-09-20

Never send your password, a two-factor code or a full API key. We will never ask for them. If a key may have leaked, revoke or rotate it first in the business settings, then tell us.

## When you will hear back

- Every message is read by a person. We reply as soon as we can, and security reports and payment problems go to the front of the queue.
- Requests with the details above are often solved in a single reply. If we need more information, we ask for the specific item instead of starting over.
- We do not publish guaranteed response times. If an issue blocks your closing or payroll deadline, say so in the subject line and we will prioritize it.

## Answers you can find right now

Many questions already have a written answer.

### Frequently asked questions

Short answers about accounts, credits, standards and the API.

### Accounting guides

Step-by-step guides with worked examples, from journal entries to year-end closing.

### Credits

How credits work and what each action costs.

### Security

How we protect accounts, API keys and your ledgers.

## API reference

Endpoints, request examples and error codes for the REST API.