TautivaHelp

Collections

Record customer payment obligations

Record a payment obligation only when it is backed by a genuine record from an external billing system.

♪ Collection, Finance license ♪# 3, 5 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

Valid billing source, correct customer, and permission to create obligation.

Step-by-step instructions

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

  1. Open Collections, then click Register obligation.

  2. Select Customer segment: Business (B2B) or Individual.

  3. In Find existing customer, search for an existing customer.

  4. For B2B, determine the Billing contact / customer and Business account with the correct relationship.

  5. Fill in Source system and External invoice / billing reference according to the official source.

  6. Fill in Obligation description, Original amount, Currency, and Due date.

  7. Select Assigned collection agent, review the data again, then save via Register obligation.

Open the page in Tautiva

PRACTICAL EXAMPLE

Example from daily work

Example: Invoice CONTOH-2026-001 for a business customer is recorded with the nominal value according to the original system, not an estimated number.

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

Changes or information are visible on the screen according to the actions taken.

Important notes

  • For B2B, the billing contact must be connected to the selected business account.
  • Do not create sample bills in the operational workspace.

If something goes wrong

  • Reference number rejected? Check for duplication on the source and customer.

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.