TautivaHelp

Collections

Correct imported invoice CSV files

Follow the invoice source requirements for CSV columns, file size, and corrections.

♪ Collection Admin, Finance# 5, 8 minutes #Last checked October 13, 2026.
Supplies record: Some actions depend on role and data conditions, and have not been tested by saving / sending data. Use this as a check guide, instead of proof of transaction testing.

Before you start

Login to the correct workspace and have the necessary permissions according to your role. Use only valid data and communication.

Step-by-step instructions

Follow these steps in order. You can keep this guide open while working in another Tautiva tab.

  1. Open Collections > External invoice sources.

  2. Find the Required CSV header section and match the column names and order in your file.

  3. Check if the file contains a maximum of 500 invoice lines and is no larger than 256 KiB as per the audit guidelines.

  4. Ensure the invoice number, date, amount, and revision follow the displayed contract.

  5. Test with Validate & import snapshots after verifying the data.

  6. If the batch fails, read the validation errors, fix the source file, and repeat in a controlled manner.

Open the page in Tautiva

PRACTICAL EXAMPLE

Example from daily work

Example: CSV containing 540 lines must be separated into valid batches before being sent; do not discard 40 lines without documentation.

This is a fictional training example. No real customer data was used.

The real page view of the Collections in Tautiva, recorded October 13, 2026.
Screenshot of Tautiva application taken at October 13, 2026; sensitive information is disabled if there are. Screen settings can change with screen sizes and product updates.

Expected result

Steps and results can be reviewed in the relevant module; send/save actions require SOP and permission.

Important notes

  • Rejected batches should not save partial data.
  • Revisions for the same invoice should be higher than the previous version.

If something goes wrong

  • Header mismatch: download or copy the structure called by the Required CSV header screen.
  • Revision rejected: check the latest changes to the invoice, not just incrementing the number without explanation.
  • Exceeding data limit: split the export into suitable batches and maintain consistent references.

This guide describes the interface reviewed on 13 October 2026. Documentation testing did not send real messages, invite users, process payments, or modify real customer records.