Why a manual IGV close takes a week
Hi, I'm Felipe from Tolmin, and in this video we'll see how to run a purchase IGV analysis in just a few minutes.
A typical IGV close usually looks like this: the team working for a week, bouncing a spreadsheet back and forth over email with the client, with comments piling up on each transaction. It takes a lot of time. This is where Tolmin comes in, helping automate much of this process.
The two agents: Tolmin Intelligence and the Connection Agent
The platform runs on two agents. One is Tolmin Intelligence and the other is the Connection Agent. The first helps us analyze transactions, assesses tax risks and explains each issue — that's the focus of this video.
The second is the Connection Agent, which assists your team in communicating with the client. It's trained on your own business rules to know when your team should step in. We'll see this a bit later.
Creating the client and validating the RUC against SUNAT
Let's start by creating the client. In this case we'll use General Motors Perú as an example, and Tolmin guides us through a series of steps. We just enter the name, the country and the RUC.
When we enter the RUC, Tolmin automatically validates it against SUNAT. In a couple of seconds we have the legal name, the taxpayer status, the economic activity, the address, and so on. Optionally, we can connect Google Drive or Microsoft to sync our files; for now we'll skip that.
Uploading the file and processing the transactions
Now we upload our transaction file. We select April as the month to analyze, choose Purchase IGV and upload our CSV file. If the file has data for several months it doesn't matter: since we already selected April, Tolmin only focuses on analyzing that month and keeps the rest in memory in case you want it for a future analysis.
Tolmin is processing the transactions, standardizing them and cross-checking each voucher against the XMLs. We wait a moment for this to complete.
The results dashboard and prioritized alerts
Finally, here is the result: a dashboard with all the validations for General Motors Perú, for April 2026. In this case there are no detracciones or DUAs, but we do have issues in the CPE, the sequence and the discrepancies (glosas) that the team needs to review.
On the right panel are the alerts prioritized by IGV difference. We see the vouchers, the supplier and the exact amount, and as the team resolves the issues, they drop off the list. Below are the PDT 621 boxes with the purchase totals already ready for filing.
Communicating with the client: the Connection Agent
When the team is done, it sends this analysis to its client, and here's where the Connection Agent comes in. Instead of the day-to-day email bouncing a spreadsheet full of comments, it assists the communication: it drafts messages, helps answer questions and follows up on pending items. The team stays in control and decides when to step into the process.
The client eventually approves or rejects the documents in their portal. Once everything is approved, the next step is simply to submit it to SUNAT.
Tolmin Copilot and submitting to SUNAT
If any question comes up during the analysis, no problem: on the left is Tolmin Copilot, which has the full project context and answers your questions on the spot. Once the analysis is complete, all that's left is to submit the file to SUNAT.
That's it: from analyzing the file to managing communication with the client and resolving questions as they arise, all in one place. If you'd like to see this same process with your own data, feel free to book a demo at usetolmin.com.
