TautivaHelp

Collections

Handle disputed customer invoices

A disputed invoice needs clear notes and verification, not repeated collection pressure.

♪ Collection, Finance, Supervisor ♪# 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

Log in to the correct workspace and have the necessary permissions based on 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 search for the relevant customer or obligation.

  2. Check the invoice reference, value, currency, due date, and communication history.

  3. If the customer disputes, document the reason and evidence internally.

  4. Use the available dispute status or control if your role allows it.

  5. Put on hold any collection actions that do not follow SOP until the dispute is reviewed.

  6. Coordinate the review results with Finance and follow up when a decision is made.

Open the page in Tautiva

PRACTICAL EXAMPLE

Example from daily work

Example: the customer claims to have received a credit note; Collection must check the document with Finance.

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

  • Do not modify the invoice amount to force a completed status.
  • Always separate invoice value disputes from payment claims.

If something goes wrong

  • Dispute status is not available: do not replace it with another status arbitrarily; escalate to a supervisor.
  • Customer documents differ from the source system: request reconciliation before responding.

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.