Lynxbe
עברית
All guides
Import transactions, review the documents and understand exactly what you confirm.
A 6-minute video in 24 chapters. Jump directly to the step you need.
Bank reconciliation links an account transaction to the invoices or expenses it relates to.
The video is currently unavailable. You can continue with the written steps and demonstration below.
Every transaction. Its document. Bank reconciliation links an account transaction to the invoices or expenses it relates to. Real Lynxbe screens · Demonstration data
Open Bank Reconciliation Open the menu and go to Bank Reconciliation. Start with the account and its transactions. Real Lynxbe screens · Demonstration data
Add the right account Choose Add account. A bank account in Lynxbe groups transactions belonging to that account. Real Lynxbe screens · Demonstration data
Check the account details Choose the bank and branch, enter the account number and name, and check the currency before saving. Real Lynxbe screens · Demonstration data
Make sure the account is listed After saving, check the account name, number and currency in the account list. Demo data · No live financial changes
Import transactions from a file Open Import and choose the destination account. Use a CSV file containing the account transactions. Real Lynxbe screens · Demonstration data
Choose the file format Choose the bank format or Generic CSV, attach the file and check the selection before importing. Real Lynxbe screens · Demonstration data
Read the import result Check how many transactions were added, how many duplicates were skipped and how many rows could not be read. Demo data · No live financial changes
Get to know the transactions Open Transactions and check the date, description, amount and reconciliation status. Real Lynxbe screens · Demonstration data
Incoming or outgoing? Incoming money is matched to invoices; outgoing money is matched to expenses. Check the currency too. Real Lynxbe screens · Demonstration data
Narrow the search Choose the account, date range and status. Use search to find the relevant transaction. Real Lynxbe screens · Demonstration data
The system suggests. You review. Automatic reconciliation opens proposals for review. It does not approve them on your behalf. Real Lynxbe screens · Demonstration data
When there is no suitable proposal For 980 ILS against invoices of 600 and 400, this example has no suitable automatic proposal. Continue reviewing. Real Lynxbe screens · Demonstration data
Read the review reason Open the review queue and see why a transaction still needs attention. Compare it with your records. Real Lynxbe screens · Demonstration data
When a relevant document is missing The review queue shows transactions still missing a relevant document. Complete the review before confirming. Real Lynxbe screens · Demonstration data
Choose the documents yourself For manual matching, choose a transaction and document. Add another relevant document when the amount is insufficient. Real Lynxbe screens · Demonstration data
One transaction. Two documents. Add the 400 ILS invoice. The documents total 1,000 ILS, while the bank transaction is 980 ILS. Real Lynxbe screens · Demonstration data
A difference needs an explanation Check whether the difference is a partial payment or a fee. A preselected option does not prove the explanation. Real Lynxbe screens · Demonstration data
When the payment is partial Choose Partial payment: allocate 600 ILS to the first document and 380 to the second. The second retains 20 ILS. Demo data · No live financial changes
When the difference is a documented fee In the review draft, check allocations of 600 and 400 ILS with an explicit 20 ILS fee. Confirm that your records support it. Demo data · No live financial changes
Review again when information changes If the transaction or documents have changed, refresh and review a new proposal before confirming. Demo data · No live financial changes
Confirm the exact selection Select the proposal you reviewed and read the confirmation. Then confirm that selected match. Demo data · No live financial changes
Make sure the transaction is matched Return to Transactions and check that the status changed to Matched. This is an isolated demonstration result. Demo data · No live financial changes
Finish with what remains unresolved Check unmatched transactions and the review queue. Add the missing document or complete the review described there. Real Lynxbe screens · Demonstration data
Original Lynxbe screens use isolated demonstration data. The shown import, confirmation and result do not change an active bank account or financial records.
Before starting: access to the page and required actions, bank account details, a CSV transaction file and the relevant invoices or expenses. Saving and confirming require the appropriate permissions.
Use reconciliation to see which bank transactions have document links and which still need review. Our example is an incoming 980 ILS against two invoices for 600 and 400 ILS. All records are isolated demonstration data.
Open the menu, expand Accounting and choose Bank Reconciliation. The page contains accounts, transactions, reconciliation and imports. Available actions depend on your permissions. This lesson uses account setup and CSV import.
Select an existing account when it is already available. Otherwise, open the account creation page. Recording account details alone does not establish a live bank connection or retrieve transactions.
Enter the details shown in your records. Use the branch picker when needed and give the account a recognizable name. The currency should match the transactions you will import. Check these details before saving so you use the correct account.
Choose the new account and confirm that it is the destination for your bank file. This account is created only in isolated demo data. Its presence in the list shows that the details were saved; it does not prove a live bank connection.
Download your transaction file and select the correct destination account. Check that it covers the intended account and period. The demonstration uses an isolated sample; do not import demo records into an active account.
The page offers Hapoalim, Leumi, Discount and Mizrahi formats, plus Generic CSV. Choose the format that matches your file. Generic CSV uses a header row, followed by columns in this order: date, description, signed amount and optional balance. Dates and amounts must be readable. Our sample imports three transactions, skips one duplicate and identifies one unreadable row.
These counts describe different outcomes. A skipped duplicate is not a new transaction. An unreadable row needs review of the file and the reported reason. Check import history; a successful import message does not mean every row was accepted.
Identify the transaction using several details together. A matching amount alone does not establish which document it relates to. Our incoming 980 ILS transaction is initially unmatched. Next, review its possible documents.
In this workflow, the transaction direction determines the document type. Positive incoming transactions use invoices; negative outgoing transactions use expenses. Check direction and currency instead of relying only on a similar amount.
Filters narrow the displayed records. Start with the intended account and period, then unmatched transactions. If a transaction is missing, check the filters and import history before importing the file again.
Open reconciliation and choose the automatic action. It opens the proposal review page. Check the transaction and the suggested documents. Confirmation is a separate, explicit step after selecting a suitable proposal.
The system does not infer a fee from the difference or automatically propose a partial allocation across these two invoices. There is therefore no suitable proposal for this transaction. For other proposals, when available, check documents and allocations before selecting. Next, we will build and review a manual match.
Check the review reason and transaction details, including amount, date and description. Find the relevant invoices or expenses. Later, we will review the manual allocation details too. The on-screen explanation helps the review; it does not replace records establishing what the transaction belongs to.
Our example leaves transactions without a relevant document. Find the right invoice or expense. In other cases, if the displayed reason is multiple candidates or a suspected duplicate, investigate it separately. Leave the transaction unmatched until the review is complete.
Select the incoming 980 ILS and the first invoice for 600 ILS. That document alone does not explain the full transaction. Look for another document belonging to the same incoming payment instead of forcing an incorrect allocation.
Select both invoices and confirm that they belong to this incoming payment. There is now a 20 ILS difference. Before continuing, check what explains the difference and which option is selected on the page.
For this case the page offers different ways to explain the difference and may preselect Fee. Do not rely on the initial selection. Check the transaction records and choose the appropriate explanation. Next, compare both possibilities using the same example.
Here the full 980 ILS is allocated without a fee: 600 plus 380. The allocation does not cover the second document’s full outstanding amount. Check document order and each allocation, and retain the remaining balance for review or a later transaction.
This is an alternative to the partial-payment branch, not another action added to it. Use it only when your records support the fee. For this incoming transaction: 1,000 minus 20 equals 980. Review the draft details, both documents, allocations and explicit fee before selecting and confirming.
A proposal is based on the information available when it was reviewed. When changed information prevents confirmation, refresh the proposals and review again. Recheck the documents, allocations and fee. Do not confirm a refreshed proposal without reading it.
In the confirmation, recheck the transaction and selected documents. Confirm that the allocations and any fee agree with your review. Confirmation applies to the selected proposal; it does not approve other proposals together. This demonstration changes isolated data only.
Before confirming, we reviewed both documents, allocations of 600 and 400 ILS and the 20 ILS fee. After confirmation, check the transaction status. If a message appears after confirmation, check the status before trying again. This transaction view does not show links to both documents for this example. The action does not transfer money or itself change an invoice to Paid. The shown confirmed state belongs only to isolated demo data.
Review the transactions that remain open. Missing documents, amount differences, multiple candidates and suspected duplicates need different follow-up. Leave a transaction unmatched when information is insufficient. Complete the review, then return to check and confirm.
Check documents and allocations before confirming, then check the transaction status afterward. Transactions needing further review remain unmatched.
When amounts differ or information has changed, complete the review and recheck before confirming. An automatic selection does not replace your review.
Checked against Lynxbe screens and source behavior on 11 October 2026. This lesson uses account setup and CSV import; direct bank connection depends on the options available to your account.
A read-only walkthrough. Choose a step or use Next. It does not import into an active account or change financial records.
Use reconciliation to see which bank transactions have document links and which still need review. Our example is an incoming 980 ILS against two invoices for 600 and 400 ILS. All records are isolated demonstration data.
Open the menu, expand Accounting and choose Bank Reconciliation. The page contains accounts, transactions, reconciliation and imports. Available actions depend on your permissions. This lesson uses account setup and CSV import.
Select an existing account when it is already available. Otherwise, open the account creation page. Recording account details alone does not establish a live bank connection or retrieve transactions.
Enter the details shown in your records. Use the branch picker when needed and give the account a recognizable name. The currency should match the transactions you will import. Check these details before saving so you use the correct account.
Choose the new account and confirm that it is the destination for your bank file. This account is created only in isolated demo data. Its presence in the list shows that the details were saved; it does not prove a live bank connection.
Download your transaction file and select the correct destination account. Check that it covers the intended account and period. The demonstration uses an isolated sample; do not import demo records into an active account.
The page offers Hapoalim, Leumi, Discount and Mizrahi formats, plus Generic CSV. Choose the format that matches your file. Generic CSV uses a header row, followed by columns in this order: date, description, signed amount and optional balance. Dates and amounts must be readable. Our sample imports three transactions, skips one duplicate and identifies one unreadable row.
These counts describe different outcomes. A skipped duplicate is not a new transaction. An unreadable row needs review of the file and the reported reason. Check import history; a successful import message does not mean every row was accepted.
Identify the transaction using several details together. A matching amount alone does not establish which document it relates to. Our incoming 980 ILS transaction is initially unmatched. Next, review its possible documents.
In this workflow, the transaction direction determines the document type. Positive incoming transactions use invoices; negative outgoing transactions use expenses. Check direction and currency instead of relying only on a similar amount.
Filters narrow the displayed records. Start with the intended account and period, then unmatched transactions. If a transaction is missing, check the filters and import history before importing the file again.
Open reconciliation and choose the automatic action. It opens the proposal review page. Check the transaction and the suggested documents. Confirmation is a separate, explicit step after selecting a suitable proposal.
The system does not infer a fee from the difference or automatically propose a partial allocation across these two invoices. There is therefore no suitable proposal for this transaction. For other proposals, when available, check documents and allocations before selecting. Next, we will build and review a manual match.
Check the review reason and transaction details, including amount, date and description. Find the relevant invoices or expenses. Later, we will review the manual allocation details too. The on-screen explanation helps the review; it does not replace records establishing what the transaction belongs to.
Our example leaves transactions without a relevant document. Find the right invoice or expense. In other cases, if the displayed reason is multiple candidates or a suspected duplicate, investigate it separately. Leave the transaction unmatched until the review is complete.
Select the incoming 980 ILS and the first invoice for 600 ILS. That document alone does not explain the full transaction. Look for another document belonging to the same incoming payment instead of forcing an incorrect allocation.
Select both invoices and confirm that they belong to this incoming payment. There is now a 20 ILS difference. Before continuing, check what explains the difference and which option is selected on the page.
For this case the page offers different ways to explain the difference and may preselect Fee. Do not rely on the initial selection. Check the transaction records and choose the appropriate explanation. Next, compare both possibilities using the same example.
Here the full 980 ILS is allocated without a fee: 600 plus 380. The allocation does not cover the second document’s full outstanding amount. Check document order and each allocation, and retain the remaining balance for review or a later transaction.
This is an alternative to the partial-payment branch, not another action added to it. Use it only when your records support the fee. For this incoming transaction: 1,000 minus 20 equals 980. Review the draft details, both documents, allocations and explicit fee before selecting and confirming.
A proposal is based on the information available when it was reviewed. When changed information prevents confirmation, refresh the proposals and review again. Recheck the documents, allocations and fee. Do not confirm a refreshed proposal without reading it.
In the confirmation, recheck the transaction and selected documents. Confirm that the allocations and any fee agree with your review. Confirmation applies to the selected proposal; it does not approve other proposals together. This demonstration changes isolated data only.
Before confirming, we reviewed both documents, allocations of 600 and 400 ILS and the 20 ILS fee. After confirmation, check the transaction status. If a message appears after confirmation, check the status before trying again. This transaction view does not show links to both documents for this example. The action does not transfer money or itself change an invoice to Paid. The shown confirmed state belongs only to isolated demo data.
Review the transactions that remain open. Missing documents, amount differences, multiple candidates and suspected duplicates need different follow-up. Leave a transaction unmatched when information is insufficient. Complete the review, then return to check and confirm.
