Import Cost/revenue allocation (voucher rows)

Prerequisites

• The accounting system is master
• Project is created. Voucher rows can only be posted to existing projects in Next. Therefore, make sure the project is created before posting voucher rows.

Relevant endpoints

Create voucher row: POST voucher/row/ or POST voucher/row/batch

To create a single voucher row, use POST voucher/row/. When creating multiple voucher rows, the POST voucher/row/batch endpoint is recommended instead.

Which voucher rows should be handled?

• Most often, not all accounting series (number ranges) are relevant to post in Next. Therefore, it is recommended to include only the series requested by the customer.
• Also make sure that cost and revenue posts are handled correctly.
  • If revenue: set revenuetransaction = true
  • If cost: set revenuetransaction = false
• If preliminary postings are used for supplier invoices upon arrival, decide whether preliminary postings should be posted to Next. If the decision is to post to Next, the logic should be according to below.
  • Preliminary posting: set invoiceable = false
  • Reversal of preliminary posting: set invoiceable = false
  • Final posting: set invoiceable = true (if it should be included in customer invoices; otherwise, false)
    Please note that all voucher rows marked as invoiceable = false will get a markup of -100% and earned revenue = 0.00 in Next, according to the built-in logic in Next.
• It is recommended to only import voucher rows that have been posted to budgetary accounts (resultatkonton)

If historical data should be available in Next, decide which transactions to import and for what period. Also coordinate with the assigned application consultant from Next on when to run this job.

To connect one or more imported voucher rows with a PDF/image, see info in this section

Internal vs external voucher rows

When creating a voucher row through the API, the transactiontype field is automatically set to 'External'; that is, it is marked as created by an external system.
When fetching voucher rows, the API will not return internal voucher rows by default. They have transactiontype field = 'Internal'. If you want to fetch internal voucher rows as well, use the parameter include_internal in the endpoint GET /voucher/row/

Boolean includeinreport

Read more about how to use the boolean for which voucher rows to include in reports: Include in report.