Banking
Match incoming payments to the right documents.
Import bank transactions as CSV, CAMT XML, or MT940, or capture them manually, link to open documents, and run bulk automatic matching, including partial payments.
These are the points this feature covers day to day.
The workflow in Jupiter ERP, on this page.
Background, typical workflows, and concrete panel capabilities, more detail than the summary above.
Import bank statements as CSV, CAMT XML, or MT940. For CSV, map columns, review the preview, and import the transactions. Record or edit individual payments manually when no export is available.
Link open transactions to invoices, credit notes, and dunning, including partial payments. Document payment status updates accordingly.
Jupiter ERP suggests matches from amount and document number in the payment reference. You review the list and post in bulk: faster than reconciling every line in Excel, without black-box automation you cannot control. Direct debits you previously exported as pain.008 are matched here once they appear on the statement.
Statements arrive as CSV, CAMT, or MT940, or as individual manual entries. You then match them to open documents, one by one or in a batch from suggestions.
A statement file from online banking is enough (CSV, CAMT, or MT940), regardless of the institution.
Invoice payment status updates through the match. Reports, open items, and the cash-basis statement then read the same state.
The main building blocks at a glance, complemented by the longer description above.
Read CSV, CAMT XML, and MT940. For CSV, map columns, preview rows, and import transactions into the account.
Suggest open transactions with matching documents and assign in bulk.
Capture individual payments, edit them, and assign to documents later.
Maintain business accounts centrally and keep balances in view.
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.
