Documents at Trio: how to find any transaction in seconds

Every financial operation has that moment. The customer says they paid, the support team asks whether the money came in, accounting asks for the receipt of a transfer made three weeks ago, and the auditor wants to know why an entry shows one amount while the account statement shows another.

At most companies, that moment turns into a small rescue mission. Someone opens the statement, exports a spreadsheet, cross-checks it against the internal system, searches their email and, with luck, finds the right record in a few minutes. When volume is high, those minutes multiply across dozens of requests a day.

Trio’s Documents area exists precisely to eliminate that search. It turns every account movement into a record that the people who need the information can look up, trace and search, without depending on the tech team and without exporting anything.

If your company already uses Trio, this is probably the feature that saves the most time day to day, and the one that tends to be least explored.

What a document is at Trio

The concept is simple: at Trio, a document is the formal record of a transaction. Whenever money comes in, goes out, is refunded or moves between the company’s own accounts, the platform generates a matching record with its own identifiers, counterparty data, amount, date, status and the full processing history.

In other words, the document is not the account statement and it is not the receipt. It is the source of truth for that specific transaction, and the receipt is just one of the things you can extract from it.

This logic translates into four types:

Incoming: everything that increases the account balance, such as deposits and credits received.
Outgoing: everything that generates a debit, such as payments and transfers made.
Refunds: reversals related to an original transaction.
Transfers between internal accounts: movements between the company’s own accounts within Trio.

The practical advantage of this organization is that it mirrors how the finance team thinks. Nobody looks for “a line on the statement.” People look for a receipt of funds, a payment or the refund of a specific amount.

How to find a document in seconds at Trio

This is the part that tends to change the routine of people who run the account every day.

On the incoming and outgoing screens, search isn’t limited to amount or date. You can search by four identifiers, and each one answers a different kind of question:

ID: the document’s identifier within Trio.
External ID: the code your company defines and sends along with the transaction.
Receipt: the transaction’s end-to-end identifier in the payment ecosystem (E2E).
CPF or CNPJ: the counterparty’s individual or company tax ID.

The receipt is the transaction’s end-to-end identifier

In Pix, Brazil’s instant payment system, every transaction gets a unique identifier called the EndToEndId, or end-to-end identifier. It is generated by the payer’s institution when the transaction is initiated, and it gets that name because it is the only identifier that follows the transaction throughout its journey, from the paying bank’s system, through the Central Bank’s SPI (Instant Payment System), to the receiving bank’s system. It has to be unique and can never repeat in any other transaction.

What matters for the team’s routine is that this code is the same at every end: it appears on the receipt your customer sees in their bank app, in the transaction record at the Central Bank and in the document inside Trio. When someone sends a screenshot of the receipt, you have in hand exactly the key that locates that transaction, no matter which institution originated the payment.

It is also the reference used in refunds and dispute processes, which makes it the natural identifier in any conversation about a specific transaction, whether with the customer, another bank or the auditors.

Note the division of roles between the search fields: the ID is Trio’s identifier, the external ID is your company’s identifier and the receipt is the payment ecosystem’s identifier. Having all three available means anyone in the conversation can reach the same document starting from the information they have.

Filters that narrow the search

Add to that the period filters, which range from quick shortcuts such as today, yesterday and last week to custom ranges, plus filters by status and amount. The list shows up to 50 records per page, with the counterparty’s name and tax ID, date, time, amount and status.

The classic situation changes shape. The customer gets in touch saying they sent the Pix and shares the receipt. Instead of exporting the day’s statement and hunting line by line, support pastes the end-to-end identifier into the search and opens the matching document. The answer goes out in the same conversation.

The external ID is the field that connects Trio to your system

The external ID is an identifier your company defines and sends along with the transaction, either via API or when creating a QR code. It can be the order number, the contract code, the user’s ID on your platform or any key that already exists in your system.

When this field is filled in consistently, reconciliation stops being a cross-checking job and becomes a direct lookup. You take the order number from your ERP, paste it into Trio’s search and land on the exact document.

A marketplace, for example, can tie each payout to the corresponding seller. A school can link each payment received to an enrollment. An operation with a high volume of withdrawals can trace each request to its final record in the account.

One important operational detail for anyone using batch payments: the external ID is unique for 24 hours, and resending the same identifier within that window causes processing to fail.

What’s inside a document

Finding the record is half the job; the other half is understanding what happened to it. That’s why, when you open a document, the platform presents the transaction in layers: the stages it went through, the transactions involved, the payment information, the reference to the QR code that originated the receipt, the associated refunds and the events sent by webhook.

When a payment doesn’t show up in the internal system, the question is usually: was the problem in the transaction or in the notification? Seeing the event history inside the document itself answers that without opening a ticket and without relying on third-party logs.

For teams that settle at scale, this end-to-end traceability shortens the time between spotting a problem and explaining what happened.

Receipts and refunds without leaving the screen

On the outgoing screen, each row’s action menu brings together three operations that tend to eat up unnecessary time:

View details of the transaction
Generate a payment receipt
Request a refund

The receipt is the most frequent request in any finance department. A supplier who bills again, accounting that needs to attach it to an entry, a customer asking for formal confirmation. Instead of calling on the team that manages the account, anyone with lookup access generates the document directly.

Being able to request a refund in the same place matters too. The transaction’s context is already on screen, which reduces the risk of reversing the wrong amount.

From the individual transaction to the consolidated view

Documents answer specific questions. For broad questions, the platform offers two other entry points that work together with this area.

The account statement gives you the history of movements, with filters by period, bank account and virtual account, and lets you download the data as CSV or PDF for external analysis or to send to accounting.

Reports cover the official layer. The balance and movement summary shows the opening balance, closing balance, movements and fees for the period. The audit confirmation letter (carta de circularização) is the document used to confirm balances in external audits, the request that tends to hold up finance teams at year-end close.

The combination works well because each layer answers a different kind of question. The document explains a transaction. The statement explains a period. The report proves a position.

Lookups for the whole team, money movement for those with approval authority

In practice, this is the biggest objection we hear when a company considers letting its support team look up transactions. And the concern is legitimate. “Internet banking” and “access for the support team” are phrases that, together, sound like risk.

The confusion arises because, on many platforms, getting into the account means seeing the whole account. Not at Trio. Access is defined by profile, and the Support profile was designed for exactly this scenario: looking up documents, and nothing more.

A user with the Support profile cannot:

Execute any transaction, whether Pix, TED (wire transfer), boleto (bank payment slip) or internal transfer
Approve pending payments
View account balances
Access the account statement or movement charts
Issue financial reports
Manage users, permissions, API keys or webhooks
Change any system setting

What this user can do is look up documents and counterparties, in read-only mode. They find a specific transaction, check its status, see what stage it’s in and answer whoever asked. They can’t see the company’s financial position and have no way to move money.

In day-to-day terms: the support analyst sees that a customer’s R$250 payment was settled at 2:32 PM. They don’t see how much cash the company has, how much came in that day or how the balance changed over the month.

As a result, widening lookup access stops being a risk decision and becomes an efficiency decision. The team that gets the question answers it on first contact, and the finance team stops acting as an inquiry desk.

Three habits to get more out of it starting today

If your company already has a Trio account, three simple adjustments usually bring immediate gains:

Standardize the external ID. Decide which key from your system goes into this field and keep the pattern across every integration. That’s what turns search into reconciliation.
Give lookup access to the people who answer questions. Customer service, support and tech teams with the right profile can resolve most everyday questions on their own.
Check the document before opening a ticket. Stages, transactions involved and webhook events explain most questions about a specific transaction.

Financial infrastructure is also organized information

Processing payments well is the start. What sustains an operation at scale is being able to explain every movement: to the customer, to accounting, to the auditor and to your own team.

At Trio, we built the Documents area on that premise: every transaction becomes a complete, traceable record, accessible to whoever needs the information, when they need it.

To learn how each screen works in detail, see the platform user manual (in Portuguese). To connect this information to your systems, Trio’s API documentation covers the endpoints, webhook events and test environment available to your tech team.

And if your company is still evaluating a corporate account built for high transaction volumes, talk to our team and see how we can support the evolution of your financial operation.