Bank fee
- Bank
- FEE-006 · −18.00 EUR
- Books
- 627 · −15.00 EUR
- Result
- Difference 3.00 EUR
The bank charged more than the books expected. Record the extra fee or ask the bank. The match waits until you decide.
! Needs a decision
Statement · Bank feeds & reconciliationExample period 01–06 Oct 2026
Bank statements, matched to the books
Your statement, reconciled line by line.
Import your statements, review the matches the desk proposes, each with its reason, and resolve what is left before it reaches the ledger.
Bank access runs through a regulated account information service provider (AISP), agreed per project. Setup starts with your statement files.
Operations · EURExample data
| Value date | Details | Reference | Amount (EUR) | Balance (EUR) | Proposed document | Reason |
|---|---|---|---|---|---|---|
| 01.10 | Opening balance | 8,000.00 | ||||
| 04.10 | Own-account transfer | TRF-0410 | −2,000.00 | 6,000.00 | Waiting for the USD statement | Set aside |
| 05.10 | Card settlement | CARD-0510 | +312.40 | 6,312.40 | Rule R-03 · Card settlements → 5125 Amounts in settlement · 312.40 | Rule |
| 05.10 | Customer receipt, partial | INV-1039 | +500.00 | 6,812.40 | INV-1039 · Invoice 1,200.00 · remaining 700.00 | Allocated in part |
| 06.10 | Customer receipt | INV-1042 | +1,240.00 | 8,052.40 | INV-1042 · Invoice, due 05.10 · 1,240.00 | Reference |
| 06.10 | Supplier payment | none | −426.50 | 7,625.90 | BILL-211 · Supplier bill, same amount, dated 04.10 · 426.50 | Amount + date |
| 06.10 | Account service fee | FEE-006 | −18.00 | 7,607.90 | 627 · Bank charges, Oct · ledger −15.00 · Difference 3.00 EUR | Needs review |
| 06.10 | Closing balance | 7,607.90 |
3 matched · 1 allocated in part · 1 to review · 1 set aside
- StatementsFiles your bank exports, assessed in scoping
- MatchingProposed, never silent
- HostingIn the EU
- TrailEvery decision logged with who, when and why
The matching desk
Matched by reference. Proposed by rule. Flagged for review.
Matching deskLocal session
Try the desk your accountant would use.
Select a statement line on the left and its accounting entry on the right. Exact matches can be accepted. A difference is set aside with a note. Nothing you do here leaves this browser.
Ready for review3
Accepted matches0
Unmatched net amount442.00 EUR
Bank statement
Select a transaction
Reference / descriptionAmount
Accounting ledger
Choose the corresponding entry
Document / descriptionAmount
Difference0.00 EUR
Select a line on each side. Accept exact matches; set differences aside for review.
Decisions stay in this browser session.Things to try
- Try the bank-fee line to see a difference.
- Switch to the USD account to see a second currency with its own queue.
- Keyboard: A accepts an exact match; R sets the selected line aside.
The browser desk changes no bank or ledger records. In the product, the same decisions are kept in the decision log.
How a match is proposedFour methods
Every match carries its reason.
The desk never matches silently. Each proposed pair names its method (reference, amount and date, rule or manual), so the person accepting it checks the logic in seconds and an auditor can check it a year later.
- ✓ Reference
The payment details carry the invoice number, and the amount agrees.
Example: INV-1042 · 1,240.00 = 1,240.00
- ✓ Amount + date
No reference, but one open document has the same amount and counterparty within the agreed date window.
Example: — · −426.50 → BILL-211 · ±3 days
- ✓ Rule
A recurring movement follows a rule you approved: card settlements, standing fees, salaries.
Example: R-03 · Card settlements
- ✓ Manual
A person paired it and wrote why. The note stays with the match.
Example: Note: “grouped payment, 3 invoices”
R-07Example rule
- When a statement line’s details contain INV- and the counterparty IBAN is known,
- if the amount equals the open invoice and the value date is within 3 days of the due date,
- then propose the match, and require a second review above 5,000.00 EUR.
ExceptionsOpen items
The lines that do not fit, in one queue.
Most of month-end goes on a handful of lines. Each one waits here with the amount that is missing and the decision someone has to make, so nothing is settled in a side spreadsheet.
Partial payment
- Bank
- INV-1039 · +500.00
- Books
- Invoice 1,200.00
- Result
- Remaining 700.00
A customer paid part of an invoice, or one transfer covers several invoices. Allocate it explicitly and keep the remaining balance visible.
◐ Allocated in partWhy a payment does not always match one invoice
Timing difference
- Bank
- TRF-0410 · −2,000.00 EUR · 04.10
- Books
- 581 Internal transfers · USD side not yet on statement
- Result
- Returns with the next statement
Money left one account and has not shown up in the other yet. Set it aside with a note; it returns to the queue when the next statement arrives.
○ Set aside
Duplicate import
- Bank
- Statement 06.10 · imported 09:02
- Books
- Imported again 11:47
- Result
- 6 lines already present · 0 added
The same statement loaded twice should not create twice the work. Lines already imported are recognised by their bank reference, so two genuine payments of the same amount stay separate.
In and outOpening · Closing
Statements in. Decisions out.
In · formats we assess during scoping
- MT940
- camt.053
- CSV
- XLSX
- Bank feed via a regulated provider · per project
Out · where accepted decisions go in RDCopilot
Banking proposes, your team reviews, the roles you name approve.
A format is confirmed only after we have tested a real export from your bank. If your accounting system is not an RDCopilot product, the handoff is an export file or an integration agreed in the scope.
Accounts in scopeConfirmed per project
Bring the banks you already use.
We do not publish a list of banks, because each one is confirmed for your accounts before go-live: the bank, the country, the account type and the fields its export carries. This is what a scope usually covers.
- Current accounts in your local currencyStatement format, IBAN, opening and closing balanceAssessed in scoping
- Foreign-currency accounts (EUR, USD and others)Currency per account, exchange details on the lineAssessed in scoping
- Card settlement accountsHow settlements are grouped and how fees are shownAssessed in scoping
- Several banks, one companyOne queue across banks, one set of rulesAssessed in scoping
- Several companiesSeparate books, separate rights, one place to reviewAssessed in scoping
For accounting firms: one desk, many client companies.
Each client company keeps its own books, its own banks and its own queue. Your team switches between clients from one place, and each client’s rules and rights stay separate. Read-only access for a client to its own decision log can be agreed in the scope.
Client separation, user rights and read-only access are agreed in the scope.
Client companiesExample data
- Client A! 4 to review
- Client B✓ up to date
- Client C○ 1 set aside
Handoff & trailPosted 06.10
Hand off to the books, with the trail attached.
Decision logExample data
| Time | Action | Line | Reason / note | Who |
|---|---|---|---|---|
| Accepted | INV-1042 | Reference + amount | AccountantWorks the queue every day: accepts proposed matches, allocates partial payments, sets aside what needs a document. | |
| Accepted | CARD-0510 | Rule R-03 · card settlement | Accountant | |
| Accepted | BILL-211 | Amount + date, no reference | Accountant | |
| Asked the bank | FEE-006 | Difference 3.00 EUR · still to review | Accountant | |
| Allocated | INV-1039 | 500.00 of 1,200.00 | Accountant | |
| Approved export | Batch 06.10 | 4 lines | Finance leadApproves the export before it reaches the ledger, signs off the month and owns the rules. | |
| Viewed | Batch 06.10 | Read only | AuditorReads, never edits: who accepted which line, on what reason, and when. |
Export to accounting · proposedExample data
| Date | Debit | Credit | Amount | Source |
|---|---|---|---|---|
| 06.10 | 5124 | 4111 | 1,240.00 EUR | INV-1042 |
| 05.10 | 5124 | 5125 | 312.40 EUR | CARD-0510 (rule R-03) |
| 06.10 | 401 | 5124 | 426.50 EUR | BILL-211 |
| 05.10 | 5124 | 4111 | 500.00 EUR | INV-1039 (partial) |
What reaches your books
- Only lines a person accepted, each with its reason.
- Only after the export is approved by the roles you name.
- Set-aside lines stay in the queue, with their note.
Access, consent, hostingAgreed in writing
Your accounts. An agreed route.
-
Bank access through a regulated provider
Automatic bank data goes through an account information service provider authorised or registered under PSD2, agreed with you per project. Until then, statement files do the same job.
-
Consent and renewal
Access needs your explicit consent and covers only the accounts you designate. Under EU rules your bank asks you to re-confirm it with strong authentication at least every 180 days. You can withdraw it at any time.
-
Hosted in the EU
Statement data, decisions and the log are kept in the EU. Retention, access and deletion at the end are set in a data processing agreement before the first import, in line with the accounting retention rules of your country.
-
Reads, never moves money
Banking reads statement and account information to reconcile it. Account information access is read-only by law: it cannot initiate payments or change anything at the bank.
R&D COPILOT provides the software and the integration. Transaction history and access periods differ from bank to bank, so each connection is confirmed in writing before go-live.
ImplementationDuration set in the quote
From your first statement to a signed-off month.
The duration depends on your accounts and banks, and is set in the quote.
- Step 1
Scope
We list your accounts, banks and currencies and test one real export from each bank.
- Step 2
Rules
We write the matching rules with your accountant and import a closed month as a test.
- Step 3
Parallel run
Your team reconciles a current month in Banking and the old way side by side.
- Step 4
Sign-off
We agree the export, roles and approvals, and the finance lead signs off the first month.
- Then monthly
Monthly licence
Updates, hosting and support. Rules are reviewed when your banks or accounts change.
Pricing modelSchedule of charges
One-off setup. Monthly licence.
One-off setup
Quoted per project
- Scoping
- Format tests on real exports
- Matching rules
- Provider route, where needed
- Test import
- Parallel run
- Training
Monthly licence
Quoted per project
- The matching desk
- Users and roles
- Decision log
- EU hosting
- Updates
- Support from the team that set it up
Both are quoted after scoping and depend on your accounts, banks and how decisions reach your accounting. Provider access for automatic bank data, if you choose that route, is quoted separately.
Request a quoteQuestionsEight questions
Before we connect your accounts.
Not here? Ask us directly
Which bank statement formats can Banking import?
We assess the exports your banks already produce, typically MT940, its ISO 20022 successor camt.053, CSV or XLSX. A format is confirmed only after we import a real file from your bank during scoping, because two banks can fill the same format differently.
Do you connect directly to my bank?
Automatic bank data goes through an account information service provider authorised or registered under PSD2, chosen and agreed per project. We confirm each bank, account and data field before go-live. If you prefer, Banking works entirely from statement files.
Will it post matches to the ledger on its own?
No. The desk proposes matches with a reason. A person accepts them, and the export to accounting is approved by the roles you name. Nothing reaches the ledger without that approval.
What happens with partial payments and payments covering several invoices?
The line is allocated explicitly: part to one invoice, or split across several. The remaining balance stays visible on the invoice, and the allocation is kept in the decision log.
Can I reconcile accounts in different currencies together?
Each account (for example EUR and USD) keeps its own currency and its own queue, so decisions never mix currencies. You review all accounts from one place, as you can try in the desk above.
We do not use RDCopilot Accounting. Does Banking still work?
Yes. Accepted decisions leave as an export file or through an integration agreed in the scope. Invoice numbers from your invoicing tool, including, for companies operating in Romania, those issued through RO e‑Factura, can serve as matching references.
Where is our bank data kept, and for how long?
In the EU. The retention period, who can see which accounts and how data is returned or deleted at the end are set in a data processing agreement before the first import.
How do we start, and what does it cost?
With a scoping call about your accounts, banks and accounting system. You then receive a quote for a one-off setup and a monthly licence. Support is available in English and Romanian.
From statement to accounted for.
Tell us which accounts and which accounting workflow you need to bring together. We will come back with the formats, the access route and a quote for setup and licence.
Access starts after scoping and a signed agreement.