Skip to content

Importing and checking the report

Unit adminOrganisation admin

Where to find it:Invoicingthe unit

A month’s invoicing starts from the municipality’s service voucher report. When you import the report, Knuut makes an invoice batch from it for the unit. A batch goes through three steps: Check the report, Compute and review the invoices and Finalize the invoices. This page covers the first step.

  1. Download the month’s service voucher report from eVaka as a CSV file.
  2. Open Invoicing and the unit.
  3. Drag the file onto Import the service voucher report, or press Pick a file.
  4. Knuut opens a new invoice batch. Its status is Draft.
  • Knuut works out the billing month from the report’s Alkaen (start) column.
  • The report can also list children of your organization’s other units. Knuut matches rows only to this unit’s children, so other units’ rows stay Unmatched. Leave them out of invoicing. Each unit imports the same file into its own batch.
  • The file stays with the batch.
  • If the same month already has a batch, Knuut says so under Worth knowing. Delete the extra batch so the family is not invoiced twice.

The report must be the eVaka service voucher report, separated by semicolons. It has the columns Etunimi, Sukunimi, Ryhmä, Huomio, Alkaen, Päättyen, Päivät, Palveluntarve, Tuen tarve, Ps korkein arvo, Omavastuu and Ps arvo / kk. If the file cannot be read, Knuut tells you why. If needed, save it again in CSV format.

Invoice batch 09/2026DraftDelete batch
1. Check the report
1Fix before computingChildren with no invoice recipient: 1Set invoice recipients
#Name on the reportChildDaysOwn shareState
1Aalto EinoAalto Eino22€180.00Matched
2Berg Ella-22€210.002Unmatched3Match to child
3Castrén Oona-9€95.00Left out4Undo the decision
The sketch shows where things are on the screen. Knuut looks a little different, but the names are the same.Scroll the sketch sideways to see all of it.

Knuut matches the report rows to the unit’s children by name. Press Show the report rows to see them.

  • 1Fix before computing: the list of things to sort out before the invoices can be computed. See what blocks finalize.
  • 2State: Matched, Unmatched, Left out or Deferred. Every row must be something other than Unmatched.
  • 3Match to child: choose who the row belongs to.
  • 4Undo the decision: puts the row back to Unmatched.

The Days column shows months that were not full. The co-payment is invoiced exactly as it is on the report and is not prorated by days.

  1. Press Match to child on the row.
  2. Pick the child under Suggestions, or look the child up under Search by the child's name.
  3. Leave Remember this name next month ticked, so the same name matches this child on its own from now on.
  4. Press Match to child.

If the child is not in Knuut yet, press Add a child, add the child and come back to the batch.

  • Leave out of invoicing: the row does not go on an invoice. Write why under Reason and press Leave out. Use this, for example, for another unit’s child on the report.
  • Defer to the next batch: the row does not go on this month’s invoice. Use this when the row needs looking into before it is invoiced.

The Worth knowing section lists things that do not block invoicing but are worth checking. For example, the group on the report can differ from the child’s group in Knuut.

The Children missing from the report section lists the unit’s children who are not on the report. They are not invoiced from this batch. Check that this is right.