Purchasing, bank & payments

Each line retains its account and VAT rate. Explicit line amounts must match the invoice total.

Delivered quantities, order status and stock receipts are saved together. An inventory lock rolls back the entire receipt.

A sales invoice and its ledger item form one suggestion and are settled together, including previously displayed ledger suggestions.

Selected unchanged prepared items can be released after a documented bank rejection. Successful payments remain intact; released items require new approval.

Open supplier credits can be explicitly offset against later CHF invoices from the same supplier. Both items and the journal entry are saved together; approvals remain required.

A QMS block prevents placing the order. Only QMS supplier management permission allows a justified exception for this order; the person, order and reason are logged.

iOS provides Done above the keyboard and a fixed Send action. Manual changes remove the recognition badge. Android filters accounts by name or number; accruals show both.

Your company’s receipt-free limit applies. Describe the expense and why no receipt is available. If a receipt is required, your entries are kept so you can add one.

New purchasing settings use CHF 1’000 as the dual approval threshold. Existing settings are preserved. Without a threshold the person entering may approve.

Receives invoices by e-mail, upload or scan, reads the QR code and text and proposes supplier, account, VAT code, cost centre, due date and payment reference – per line item if there are several. The primary action posts the suggestion and changes after editing booking fields. “Post and save a rule” also saves a rule for the selected scope. Without automation, future invoices remain subject to review; automation requires an amount limit.

Search accounts by number or name; recently used supplier accounts appear first. VAT codes show descriptions and rates. Recognised rates take priority over old defaults without VAT. Legacy rules use the current number in place of documented old invoice numbers.

Record purchase orders to suppliers and convert them into a supplier invoice, generate recurring expenses and post approved expense claims.

Import the company card statement, attach receipts and post each transaction or mark it as private.

Record expenses with a receipt, submit them and follow their status. Line managers or accounting approve; your own claim is always approved by someone else.

Approve or block open supplier invoices and output due, approved invoices in a payment run as a payment file (pain.001).

A valid company IBAN is required when creating a payment run. The notice links to the existing bank account settings.

Approval checks, archive reference, payment order, payable items and run completion are saved together. Concurrent execution and changes to the checked data cannot create a second payment file.

Import bank statements (camt.053) and credit advices (camt.054) and match each transaction, with a suggestion, to open invoices or to a rule.

A QR-IBAN is a special IBAN that your bank issues for QR bills with a QR reference. You only need one if you have been given one; otherwise leave the field empty. For the QR bill your normal Swiss IBAN is enough; the payment part then carries an RF reference (Creditor Reference), which is used to match incoming payments to invoices.

Reads bank statements (camt.053/054/052) and matches incoming payments to invoices, connects accounts directly via EBICS or bLink and transmits approved payment files (pain.001).