Outstanding
The Outstanding tab is where you manually match open bank transactions against open accounting documents when no automatic suggestion exists — or when you want to override the suggestion flow entirely. This page walks through everything you need to select items, understand the amounts shown, and confirm a match.
What the Outstanding Tab Shows
The Outstanding tab presents two panels side by side (or stacked, depending on your layout preference):
- Left panel — Bank transactions: all open transactions for the selected bank account that have not yet been fully reconciled.
- Right panel — Accounting documents: all open documents associated with the entity and currency in scope.
Selecting Items
Click the checkbox on any row to select a transaction or document. You can select multiple items on either side. The selection bar at the bottom of the screen updates as you select, showing a live count in the format:
X transactions ⇄ Y documents
where X is the number of selected transactions and Y is the number of selected documents.
The Three Manual Matching Scenarios
Once you have made your selections, the available action buttons change based on what you have selected. There are three distinct scenarios:
| Scenario | What you select | Button | What happens |
|---|---|---|---|
| Standard match | One or more transactions and one or more documents | Confirm | Opens the outgoing-document builder |
| Transaction only | One or more transactions, no documents | Create | Creates an outgoing document directly to record the transaction |
| Transfer | Two transactions in opposite directions (one debit, one credit), no documents | Create | Creates a Transfer match |
Scenario 1 — Standard Match (Transactions + Documents)
Select at least one transaction and at least one document, then click Confirm. A builder opens where you configure the outgoing document Atlar will post to your ERP as a result of the match.
For each outgoing document you choose a Document Type:
| Document Type | What Atlar posts | Who calculates the ledger entries |
|---|---|---|
Journal entry | A journal entry with explicit ledger lines | Atlar computes the ledger entries and posts them to your GL |
Payment | A payment document | Your ERP calculates and posts the ledger entries |
Credit memo | A credit memo document | Your ERP calculates and posts the ledger entries |
You also set a Trigger that controls when the outgoing document is generated:
| Trigger | When it fires |
|---|---|
Always | The document is always generated for the match. |
On positive residual | Only when a positive residual amount remains after application. |
On negative residual | Only when a negative residual amount remains after application. |
Defining ledger lines (Journal entry only). When the document type is Journal entry, you define the ledger lines that Atlar posts to the GL:
| Field | Description |
|---|---|
Bank Line | The line representing the bank side. The GL account is sourced automatically from the transaction's configured bank GL account; you can add optional GL classifications here. |
Balancing Line | The offsetting line. You select the GL account and, optionally, GL classifications (cost centre, project, etc.). |
| Additional Lines | Zero or more extra debit or credit lines. For each line you specify: GL account, Debit or Credit, amount, and optional GL classifications. Use these to split the entry across multiple accounts or to record tax, fees, or other components. |
For other document types, likePayment and Credit memo, you do not define ledger lines — Atlar sends the document to your ERP, and your ERP determines and posts the resulting ledger entries.
Scenario 2 — Transaction Only (No Document)
Select one or more transactions and leave the document panel empty, then click Create. This opens the same outgoing-document builder as Scenario 1, allowing you to record the transaction directly without linking an accounting document.
This is useful for bank charges, interest income, or any transaction that does not correspond to a pre-existing document in your system.
Scenario 3 — Transfer
Select exactly two transactions that move in opposite directions (one is a debit, the other is a credit) and no documents, then click Create. Atlar recognises this pattern as a transfer and opens the Transfer match flow instead of the standard builder.
Transfers come in two varieties depending on whether the transactions belong to the same legal entity or different entities.
Transfers — Intracompany vs. Intercompany
Intracompany Transfers (Same Legal Entity)
When both transactions belong to the same legal entity, the transfer requires a clearing account to balance the entry. Choose per-leg clearing accounts. Each leg then maps to a journal entry balancing the bank line against the chosen clearing account.
Intercompany Transfers (Different Legal Entities)
When the two transactions belong to different legal entities, no clearing account is needed. Each entity's leg is posted as its own journal entry, and the bank account lines are auto-balanced against intercompany receivable/payable (AR/AP) accounts at your ERP.
Understanding the Amounts Shown
The amount column displayed for each item depends on the document type:
| Item type | Amount shown |
|---|---|
| Source documents (e.g. invoices, credit notes) | The remaining (unapplied) amount — the portion that has not yet been matched |
| Instruction documents (e.g. payment instructions) | The full instructed amount |
| Bank transactions | The full transaction amount |
What Happens After a Manual Match
When you click Confirm or Create, Atlar immediately creates a manual match and places it in the Review & Post stage.
Posting the resulting outgoing documents to your ERP still happens on the Review & Post tab. See the Review & Post page for details on how to review and post matched documents.