What it does
Embat connects banks, payment processors and business accounting systems for consolidated cash positions, transaction matching and accounting entries. Its two-way connections bring in invoices and send reconciled results back to the ledger. Finance teams choose the required modules and receive a tailored subscription proposal.
Embat's two-way connection brings payable and receivable information into the treasury workflow, then sends reconciliation results and journals back to the accounting system. Bank and payment-processor feeds provide the cash side, including fees, chargebacks and settlements.
Follow a bank movement through the ledger
Rules handle recurring items such as payroll and bank charges. TellMe then proposes matches against open invoices or suggests ledger accounts using the transaction details. It can match several invoices to one movement or deal with a partial payment.
Entries created through Embat are reconciled with the returning ledger entry. For entries posted elsewhere, matching movements appear as suggestions. The history records the method, user and time, and entries can be undone when needed.
Choose a date range in the reconciliation dashboard to compare the bank and accounting opening and closing balances. Export the comparison to Excel or PDF.
Practical review controls
The Reconciliation origin column shows whether a result came from an automatic rule, manual work or TellMe. Notes can be left on a transaction while a missing invoice or accounting query is resolved.
For repeated postings, select transactions in the accounting table and post them together to the same ledger account or contact. Each keeps its own description unless you apply common text to the batch.
Payment-file approvals need deliberate setup: configure an approval flow in Automation to insert a check before bank submission. Without that flow, the uploaded payment file is sent automatically.
Scope and price
The pricing selector lets you identify modules for bank and accounting-system connectivity, forecasting, reconciliation and payments. Embat uses that selection to prepare a proposal. The order specifies fees, users and the permitted scope, including relevant bank accounts.
Implementation includes connection setup and testing. The ERP Console exposes synchronization status, logs and errors, so the team can investigate a failed connection instead of treating every missing entry as a reconciliation issue.
Strengths
- Sends reconciliation results and journal entries back to the accounting system
- Includes processor fees, chargebacks and settlement matching
- Records how each reconciliation was created and supports transaction notes
Watch out for
- Payment-file approval flows must be configured to prevent immediate submission
- Users and connected-account scope are limited by the agreed order
Best for
- Finance teams reconciling multibank and processor activity with their ledger
- Groups needing cash visibility and payment controls across entities
Sources
- Embat treasury platform and integrations (Oct 27, 2026)
- Embat modular pricing (Oct 27, 2026)
- Embat bank reconciliation and ledger posting (Oct 27, 2026)
- Embat accounting and payment controls (Oct 27, 2026)
- Embat subscription terms (Oct 27, 2026)
