Banking

Banking & payment matching

Import transactions, match payments, keep liquidity in view.

Import bank transactions into Jupiter ERP and match them to open invoices. Payment matching stays in context with documents and contacts, without parallel Excel lists.

Start free trial All features

Bankumsätze und Zahlungsabgleich im Jupiter ERP Panel

At a glance

These are the points this module covers day to day.

Online banking on request
Statements as CSV, CAMT, or MT940
Automatic matching suggestions
SEPA direct debit as pain.008 file
Multiple accounts per tenant

In the product

The workflow in Jupiter ERP, on this page.

Views from the panel

Screenshots from Jupiter ERP for features in this module.

SEPA-Lastschrift-Export im Jupiter ERP Panel

SEPA direct debit (pain.008)

From the invoice list, download a bulk direct debit in pain.008.001.02 (CORE): mandate data on the contact, creditor fields in the export dialog. Import the file into your banking software; invoices are marked paid only after payment matching.

In depth

What the module means in practice, beyond the feature list, with concrete day-to-day value in the panel.

Payment matching in document context

Jupiter ERP does not replace your bank. It replaces the Excel reconciliation between statements and open invoices. Import transactions as CSV, CAMT XML, or MT940 (CSV uses column mapping) or record individual payments manually. Run multiple business accounts in parallel with balance overview. For collections, generate a SEPA pain.008 file from the invoice list and import it into your banking software.

Match open transactions to invoices, credit notes, and dunning, including partial payments and batch allocation. Jupiter ERP suggests matches from amount and payment reference; you review and post in bulk.

Liquidity without mandatory PSD2

An export from online banking is enough (CSV, CAMT, or MT940). You control import timing and data source.

Banking analytics show cash flow and matching status: a basis for short-term liquidity planning, right next to open items from the documents module.

What you do in the Banking module

Banking matches incoming payments to documents. A statement as CSV, CAMT, or MT940, or a manual entry, is enough.

Keep several business accounts and watch balances
Import statements as CSV, CAMT, or MT940; for CSV, map columns and check the preview
Enter single transactions manually and match them later
Link open transactions to invoices, credit notes, and dunning notices, including partial payments
Review suggestions from amount and document number, then post them together
Create a SEPA direct-debit pain.008 file from open invoices and import it into banking software
Match collected debits afterwards so the invoices become paid
Report cash flow and match status, and optionally include bank transactions in the DATEV export

Status on the invoice, not in a side list

As soon as you match a transaction, the payment status on the document changes. You only dun where an open amount remains.

The cash-basis statement reads the payment date from this set. Open items show what is still outstanding afterwards.

Rechnung bearbeiten im Jupiter ERP Panel — Positionen und Belegdetails

Direct debit is a file

Jupiter ERP creates pain.008.001.02 (CORE, recurring) and does not send it to the bank itself. Mandate data lives on the contact: IBAN, mandate reference, date.

Invoices become paid when the statement is matched in reconciliation.

Features in Banking

What you can do in this module, no fluff. Details for individual panel features are under Features.

Bank and payment accounts
Multiple accounts with balances and currencies. Payment methods and accounts are maintained centrally for the team.
Statement import & manual transactions
Import bank transactions as CSV, CAMT XML, or MT940, or capture individual transactions manually and edit them later. CSV still uses column mapping.
Payment matching
Link receipts to open invoices, credit notes, and dunning, including partial payments, bulk matching, and traceable history.
Automatic matching
Suggestions based on amount and document number in the payment reference. Review open transactions in bulk and assign with one click.
Online banking
Retrieve account transactions and assign them automatically. For Basic, Business, and Enterprise on request, with a setup fee. We verify your identity, then send an individual quote. Until it is set up, import transactions from a file (CSV, CAMT, or MT940).
Banking analytics
Cash flow, assignment status, and account overview at a glance: a basis for short-term liquidity planning.

Typical use cases

How teams use Banking day to day.

Several accounts

Business accounts are imported as transactions. Each account stays visible on its own, while matching still runs against the same open invoices.

Many incoming payments

A suggestion matches the payment to the right invoice. Anything that does not fit stays open for review. The status on the invoice follows the match.

No second tool

Open items and incoming payments are read in the panel. Direct debits export as a SEPA file for your banking software, without keeping the invoices in a spreadsheet beside it.

Works well with

These modules complement Banking in typical workflows.

Documents & invoicing

From quote to dunning: one continuous document flow.

Accounting & export

Recognize receipts with AI and prepare them for posting. Export for tax advisors and DATEV.

Your first invoice in minutes

Start for free: write invoices on the Free plan. Choose plan, term, and add-ons in the app afterwards. Custom adaptations or API integration? Get in touch.

Start free trial Custom solution

14-day trial
No credit card
Hosted in Germany
GDPR-compliant

Invoice overview in the Jupiter ERP panel