Payments
Pay vendor invoices without a bank portal
Approved invoices are bundled as pain.001 and transmitted to your bank via EBICS. With four-eyes approval if you want it.
Your bank and eBill, right inside the ERP.
Payments go to the bank via EBICS, statements come back on their own and are reconciled, invoices reach your customers as eBill in their e-banking. No bank portal, no files by hand.
EBICS
Payments that never leave the books.
EBICS is the Swiss banks’ standard for exchanging data with corporate clients. ewws uses it both ways: orders out, statements in. From the Start edition.
Direct debits
Collections as pain.008
Recurring receivables are collected by direct debit. The files are built from the open items, nothing retyped.
Statements
camt.053 and camt.054 reconciled
ewws fetches statements and notifications itself and matches payments to open items, including batch bookings. Anything that does not fit becomes a proposal to review.
eBill
Invoices where your customers pay: in e-banking.
eBill is the Swiss way of receiving invoices. ewws connects to the eBill network through PostFinance’s B2B interface. From the KMU edition.
Send
Invoice as eBill
An invoice created in ewws reaches the customer’s e-banking as eBill. Status and delivery are visible on the invoice.
Receive
Supplier invoices as eBill
Incoming eBill invoices land in ewws as vendor invoices, ready for approval and payment via EBICS.
Enrolments
Customers enrol themselves
When a customer enrols for your eBill in their e-banking, they appear in a worklist in ewws and are matched to the customer master. Cancellations likewise.
From bank statement to posting
You see what happens with the money in the books, not in a bank portal.
In ewws, bank statements are not files to retype but postings with matching, approval and warnings.
Bank reconciliation
Payments find their invoice
Every credit from camt.053 and camt.054 is matched to the open invoice, batch payments are split across several invoices. Whatever stays unclear becomes a proposal to review.
Payment approval
Four eyes before every payment
Payment runs are prepared and approved by a second person before the pain.001 goes to the bank. Who approved what and when is in the journal.
Banking anomalies
Irregularities before they get expensive
Duplicate payments, unusual amounts and new payees are flagged before the payment is approved.
Liquidity forecast
Know what is on the account in 30 days
Open receivables, due payables and recurring payments form the preview of your liquidity, by account and week.
Swiss formats at the core
The formats of the Swiss banks, without an add-on module.
ewws speaks the language of Swiss payments from the Start edition. None of it is bought in.
QR-bill
Invoice with payment part and reference
Every invoice carries the Swiss QR Code with QR reference. Incoming payments are matched to the invoice automatically via the reference.
ISO 20022
pain.001, pain.008, camt.053, camt.054
Payment orders, direct debits, statements and notifications in the standard of the Swiss financial infrastructure.
Direct debit
Collect receivables instead of dunning
For subscriptions and recurring invoices, ewws builds the direct debit file from the open items and posts the receipt on return.
Foreign currencies
EUR and USD with rate valuation
Invoices and payments in foreign currency are posted at the daily rate, exchange differences are posted automatically on settlement.
How it works for you
Three steps from bank connection to daily operation.
The path is guided in ewws. No file by hand, no second tool.
Step 1
Set up bank access
You enter your bank’s EBICS access in ewws, print the initialisation letter and activate the access. Guided, with every step checked.
Step 2
Approve the payment run
Due vendor invoices become a payment run, a second person approves, ewws transmits the file to the bank.
Step 3
Reconcile the statement
The bank delivers statements and notifications, ewws fetches them, matches and closes the open items. You only review the proposals.
Ready for your bank connection.
Bank access is set up in ewws with a guided initialisation. After that, payments run from the ERP.