Reconciliation
This section outlines the bank account reconciliation process in Atlar.
Overview & Concepts
Accounting Reconciliation in Atlar closes the gap between your bank activity and your books by matching bank transactions directly against accounting documents from your ERP. Instead of manually cross-referencing statements and ledgers, you work in a single workspace where matches are suggested automatically, confirmed by your team, and posted to your general ledger — giving you a continuous, auditable reconciliation process.
What Is Bank Account Reconciliation?
Bank Account Reconciliation is the process of verifying that the transactions recorded in your bank account agree with the entries in your accounting system. In Atlar, this means linking booked transactions — real, settled movements on your connected bank accounts — to accounting documents synced from your ERP, so that every bank movement is accounted for and your books stay in sync with reality.
When a match is confirmed and posted, Atlar can generate the corresponding journal entries and send them back to your ERP, completing the loop without manual data entry.
The Two Sides Being Reconciled
Every reconciliation match brings together items from two distinct sources.
Bank Transactions
A bank transaction is a booked (settled) movement on one of your connected bank accounts. Each transaction is tied to a specific bank account and its corresponding GL account. Atlar ingests these automatically from your connected banks; you do not need to import them manually.
Accounting Documents
An accounting document is a record synced from your ERP that represents either an obligation to receive or make a payment, or an instruction to execute one. Atlar uses a two-category model:
| Category | Description | Examples |
|---|---|---|
| Source | Documents that originate an obligation — they exist independently and drive expected cash flow. | Invoices, credit memos |
| Instruction | Documents that represent an instruction to move money — they are tied to an execution. | Payments, transfers |
For full field-level detail on accounting documents, see the Accounting Document reference page.
The Core Object: A Reconciliation Match
A Reconciliation Match is the central object in Atlar's reconciliation workflow. It represents the association between:
- One or more bank transactions, and
- Zero or more accounting documents
A match may also produce outgoing documents — journal entries that Atlar generates and posts back to your GL to record the reconciliation in your accounting system.
Matches move through a lifecycle: from suggested or created, through review, to posted.
How Matches Are Created
Matches can originate in three ways, shown in the Type column throughout the workspace:
| Type | How it is created | Confidence levels |
|---|---|---|
| Smart | Suggested by Atlar's AI-assisted matching engine | Low, Medium, or High |
| Rule-based | Matched automatically by reconciliation rules you have configured | Low, Medium, or High |
| Manual | Created by you — you select the bank transactions and documents yourself | None (not applicable) |
Smart and Rule-based matches are proposals — they are not applied to your books until you confirm them. Manual matches are created directly by your team and move straight to the review stage.
The End-to-End Happy Path
Here is the typical journey for a suggested match from creation to posting:
- Match suggested — The Reconciliation Assistant (Smart) or a configured rule (Rule-based) identifies a potential match between one or more bank transactions and one or more documents.
- Confirm — You review the suggested match in the
Matchestab and confirm it. Confirming signals that you agree the items belong together. Note, that matches with high confidence move directly to Reivew & Post. - Review & Post — The confirmed match moves to the
Review & Posttab, where you or a colleague performs a final review and initiates posting to your ERP. - Once Posted — Atlar generates the outgoing documents and posts them to your ERP. Either updating existing or creating documents in your ERP. The match moves to the
Postedtab and the reconciliation is complete.
For anything that does not match automatically, the Outstanding tab surfaces unmatched bank transactions and documents so nothing falls through the cracks.
Workspace at a Glance
The reconciliation workspace is organized into five tabs:
| Tab | Purpose |
|---|---|
Overview | Summary of reconciliation status and Reconciliation Assistant schedule |
Matches | Suggested and confirmed matches awaiting your review |
Outstanding | Unmatched bank transactions and documents |
Review & Post | Confirmed matches ready for final review and GL posting |
Posted | Historical record of completed, posted matches |
Each tab is documented in detail on the Reconciliation Workspace page.
Data Flow Diagram
Bank Transactions Accounting Documents
│ │
└──────────┬────────────────┘
│
▼
Reconciliation Match
(Smart / Rule-based / Manual)
│
▼
Confirm & Post
│
▼
Outgoing Accounting Documents
│
▼
Document Updated or Creatd in ERP
Prerequisites
Before you begin: Accounting Reconciliation requires your bank accounts and ERP to be connected and syncing. See the Getting Started with Accounting Reconciliation page for setup instructions, including how to connect your ERP, map GL accounts, and configure your first reconciliation rules.
