TautivaHelp

Collections

Distinguish CSV snapshots, obligations, and verified payments

Do not add figures from different invoice and obligation lists as though they were verified debt totals.

♪ Collection, Finance, Owner ♪# 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 and understand that the Collection queue is a list of obligations recorded through the workflow.

  2. Open External invoice sources and view imported snapshots as copies from external sources.

  3. Open the Operations dashboard to view the two groups separately.

  4. Compare invoice references with the accounting system or official documents.

  5. Check paid claims along with independent payment evidence.

  6. Report results only as a checking status if there is no settlement evidence.

Open the page in Tautiva

PRACTICAL EXAMPLE

Example from daily work

Example: 20 invoices from CSV and 7 active obligations do not mean there are 27 unique bills; one invoice may appear in two different contexts.

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

Expected result

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

Important notes

  • Paid claims in CSV do not guarantee receipt of money.
  • Do not refer to the total snapshot CSV as audited debt.

If something goes wrong

  • Two numbers are not the same: check the scope of the source, filter, and import date.
  • Expired/stale data: check the Source import freshness and request the latest file.

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.