Payment matching without a direct bank connection

Open invoices only become cash when money arrives and someone links the payment to the document. Spreadsheets break when partial payments, collective transfers, and several business accounts pile up. A direct bank connection (PSD2-style retrieval) can help, but it is not mandatory for orderly matching.

Many SMEs already download statements from online banking. Reusing that file avoids waiting for bank API onboarding, identity checks, or vendor setup fees. You keep control of when data enters the ERP.

Jupiter ERP’s banking module is built around import and matching first. Online banking retrieval is available on request for Basic, Business, and Enterprise, with setup and an individual quote. Until that is active, a statement file is enough.

Supported statement formats are CSV, CAMT XML, and MT940. For CSV you map columns, preview rows, and then import transactions into the chosen business account. CAMT and MT940 follow their structured fields with less mapping.

You can also capture individual payments manually and assign them later. Multiple business accounts run in parallel: each keeps its own balance view while matching still targets the same open documents in the tenant.

That workflow fits teams that already reconcile in banking software and only need the ERP to close open items and feed DATEV or internal reports. You are not forced into a permanent API link to get matching suggestions.

Jupiter ERP suggests documents for open transactions based on amount and document number in the payment reference, including partial payments. You review suggestions before posting. Nothing is silently marked paid without that step.

Bulk matching helps when many similar remittances arrive. Items that do not fit stay open for manual assignment. Matching history stays traceable, which matters for internal questions and for GoBD-style audit trails alongside period lock.

After you export a pain.008 file, match the collection when it appears on the statement. That keeps invoice payment status aligned with the bank.

Open items, matching status, and cash flow appear in the banking dashboard. That is a base for short-term liquidity planning without a second spreadsheet of “really paid” invoices.

Matched payments support clean hand-off to accounting: DATEV export from Business can include bank transactions as CSV when you choose. Unmatched noise in the bank feed becomes noise in the advisor package, so a weekly matching habit pays off.

Roles matter: not every user should match bank lines or export. Combine tenant separation with permissions so finance owns matching while service users stay on orders. Activity logging keeps who assigned what visible inside the tenant.

A practical rhythm is enough for most teams: import after each statement cut, clear obvious matches the same day, park unclear lines with a note, and lock the period only when open bank rows for that window are reviewed. That keeps EÜR payment dates and open-item lists aligned with reality.

High daily payment volume, many accounts, or a policy that forbids manual downloads can justify online banking retrieval. Jupiter ERP offers that path on request with identity verification and a setup fee; it is not a silent default.

Until then, file import keeps you compliant with a simple operating rhythm: download statement, import, match, lock periods when ready. That rhythm already removes the classic failure mode of invoices left open for weeks after the money arrived.

If you are evaluating tools, ask whether matching works from a statement file, which formats are supported, and whether partial payments are first-class. Jupiter ERP offers file-first matching, CSV/CAMT/MT940, partials in suggestions, and paid status after you match the statement.

Put invoice numbers in the payment reference and, where useful, a GiroCode on the PDF so remittances are easier to suggest. Collective transfers will still need a human eye. Prefer an open line over a silent wrong match: correcting a bad assignment later costs more than leaving it open for a day.