Skip to Content
Docs

Invoices and payments

Sales and purchase invoices from draft to posted entry, credit notes, settlement, and payment reminders signed by a person.

An invoice in Tosven is a document and a journal entry at once. Posting it freezes its content, books it line by line and opens an item that a payment later closes. This page follows sales and purchase invoices from draft to payment, and explains how Collections agent handles reminders.

Sales invoices

A sales invoice starts as a draft. You can create it by hand, or it arrives from Customers when a quote is accepted. A draft can be edited or deleted and has no number.

Posting does the following, in one step:

Validate

Every line needs a tax code that resolves to a rate and a VAT box. If one line cannot be mapped, the whole invoice is refused. Half an invoice never reaches the books.

Number

The invoice takes the next number in its series, for example INV-2026-0418. A refused invoice does not use up a number.

Freeze

The customer and seller details, the VAT breakdown per rate and the payment reference are fixed on the document. Later changes to the customer record do not reach an issued invoice.

Book

The journal entry is posted with the receivable on the customer.

The payment reference is a Finnish reference number with a check digit. It is what allows a bank payment to settle the invoice automatically. See Bank and reconciliation.

Purchase invoices

A purchase invoice keeps the supplier's own invoice number. Tosven refuses a second invoice with the same supplier and number, and sends a same-number invoice with different content to a person.

Ledger agent proposes the expense account and the VAT code, with its reason and confidence. For BIL-2026-0733 from Vesta Logistics Oy, 12.400,00 € net at 25,5 % and 15.562,00 € gross, Sara Nyström compares the proposal with the attached invoice and posts it. The original file stays attached to the voucher.

Agents at the lowest autonomy levels only write and edit drafts. Approving, posting and cancelling need a higher level or a person. See Autonomy levels.

On the way

Sending and receiving e-invoices (Finvoice, Peppol) is built and being taken live. A payment run for supplier invoices is planned. Neither is in production use today.

Credit notes

A posted invoice is not edited. You correct it with a credit note that references the original invoice. The credit note reverses exactly the shares it credits, VAT included, and inherits the currency and exchange rate of the original.

A credit note is not a payment. It reduces the open amount of the invoice, and the reminder logic treats it accordingly.

Settlement

The open amount of an invoice is not a stored field. It is what remains after the payments and credits matched against it.

  • Full payment. The invoice is closed, and everyone who can see the deal in Customers sees it as paid.
  • Partial payment. The invoice stays open with the remainder.
  • Foreign currency. The realised exchange difference is booked when the payment is matched.
  • Undo. A match can be undone. Entries made by the match are reversed with it.

Payment reminders

Collections agent watches overdue sales invoices and prepares reminders. It is a rule-based agent: the schedule is deterministic and no language model writes the letter. Live in the pilot

Reminders are switched off until a company turns them on. The schedule then has at most three steps: a friendly reminder, a payment reminder and a final reminder. For Finland the first step comes no earlier than 14 days after the due date, with at least 14 days between steps. A country without verified rules has no automatic schedule, only manual reminders.

Each reminder is a decision card. The card shows the invoice and customer, the days overdue, the open balance with payments and credits itemised, the step, the full letter in the recipient's language and the address it will go to. A person signs it. What was approved is what is sent, byte for byte. See Decisions and approvals.

What the agent does not do:

  • It charges no reminder fees and no interest.
  • It does not hand a case to a collection agency. After the final step the invoice is flagged for manual follow-up and a task is created for a person.
  • It does not continue automatically after a partial payment. It proposes an open-balance letter for review.
  • It does not send to an address that bounced. The customer is marked unreachable and a person gets a task.
  • It never reaches L3. Reminders launch as review-only, and the final step, disputed invoices and the first letter to a customer always need a person.

Controls on an invoice

Three controls are available per invoice:

  • Pause. Stops reminders until someone lifts the pause, with a note.
  • Promise to pay. Snoozes reminders until the promised date and resumes after it.
  • Dispute. Stops every reminder channel at once. Only a person can place it, with a reason.

The invoice shows its reminder history and the date of the next automatic reminder. That date is calculated by the same rule the agent uses, so the screen never promises a letter that will not be sent. Letters go out between 08:00 and 10:00 on the company's local clock, and never on the due date itself.

Invoices brought in by migration start paused.

Next steps

On this page