Reference

Seven commands, and the reason for the ones that aren't there

You type a slash in the chat, answer two or three questions, and a file comes down. Every row carries the reference to the document it came from.

A command isn't a typing shortcut: it's a finished working paper. Wurz reads the CFDI invoices you already uploaded, builds the table, and delivers it in Excel, Word, or PDF — with a column that says, row by row, which document each figure came from.

The catalog

What each command generates

All of them ask for the period. The Excel ones run on your CFDIs' XML files, without depending on a PDF reading well.

/ivaExcel

VAT working paper

The month's tie-out: VAT charged and collected, creditable VAT paid, and — above all — what doesn't reconcile.

It asks you: The period, the taxpayer, the calculation basis, and whether you break out the 8% rate.
It delivers: One row per invoice with its taxable base, VAT by rate, exempt and withheld amounts, plus the reference to the document each row came from.

By default it calculates on a CASH-FLOW basis, not accrual: an installment (PPD) invoice without its payment receipt doesn't enter the month. That's the number-one reason a VAT working paper doesn't tie out.

/diotExcel

Third-party operations summary (DIOT)

Your month's suppliers already grouped with their VAT, ready to capture into the DIOT return.

It asks you: The period, the taxpayer, and whether you separate non-creditable VAT.
It delivers: One row per third party with their tax ID (RFC), operation type, transaction value by rate, creditable VAT paid, withheld VAT, and returns and discounts.

Non-creditable VAT goes in its own column because the return asks for it that way. It comes out separated unless you say you don't need it.

/repExcelalso /complementos

Installment invoices missing their payment receipt (REP)

Which installment invoices are still missing their REP, and who to chase for it — or who has to issue it.

It asks you: The period, whether the pending item is yours or the supplier's, and the taxpayer.
It delivers: Each invoice with its UUID, the matching receipt if found, the amount paid, the outstanding balance, days elapsed, and the status.

It separates received from issued invoices because they are two different jobs: one you chase with the supplier, the other the taxpayer has to issue themselves.

/faltantesExcelalso /pendientes

What documentation is missing to close the month

The gaps in the file: what's not there, why its absence shows, and who to ask for it.

It asks you: The period, the taxpayer, and what you want to review.
It delivers: Each missing item with its priority, the amount involved, the tax affected, why it was detected, who to request it from, and the suggested action.

The “why it was detected” column exists so you don't have to trust: a missing item that doesn't explain how it was deduced can't be defended before the client.

/cfdiExcelalso /comprobantes

CFDI inventory for the period

The table of all your invoices for the period, with taxes itemized.

It asks you: The period, whether issued or received, the taxpayer, and the invoice type.
It delivers: Eighteen columns per invoice: UUID, series and folio, dates, tax ID and legal name of both parties, CFDI usage code, payment method and form, currency, and taxes.

Issued and received never come out in the same table. Mixing them merges two different working papers and forces you to separate them again by hand.

/requerimientoWordalso /carta

Documentation request letter

The letter asking your client for what's missing from the period, editable before you send it.

It asks you: The recipient, the period, the deadline if there is one, and the tone.
It delivers: A Word document with heading, purpose, the list of requested documents, and the closing.

It comes out in Word and not PDF on purpose: it's a letter you're going to sign and probably adjust, not a closed deliverable.

/resumenPDFalso /reporte

Period summary for the client

The closing report you send your client, ready to deliver.

It asks you: The period, the taxpayer, and who you're writing it for.
It delivers: A PDF with how the period closed, the figures, the pending items, and what's next.

The tone changes with the reader: you don't explain things the same way to a small-business owner as to another accountant.

The criterion

The rule that decides whether a command gets in

There are three, and none of them is “if it fits the roadmap.”

The data has to be in your documents

Wurz doesn't have the tax authority's portal, an ERP, or your online banking. It only reads what you uploaded. A command that “sometimes can't” is worse than one that doesn't exist, because it teaches you to distrust the rest.

Wurz delivers the input, not the tax

Wurz provides the verified rows. You provide the judgment and the entry. None of these commands tells you how much to pay: they give you the working paper with which you decide.

Every row carries its origin

Every row of every table carries the reference to the document it came from. A row without a verifiable origin is exactly what you can't put in a working paper, because you can't defend it in an audit.

The limits

What Wurz doesn't do, and why

Eighteen commands were studied and seven made it. These are the ones left out, with the reason — so you know before paying, not after.

/cancelados

Cancellation status doesn't live in the XML: it lives in the tax authority's lookup service. Wurz doesn't query it, so it can't assert it.

/opinion

The tax-compliance opinion is issued by the tax authority (SAT). It can't be deduced from your invoices.

/efos

The 69-B blacklist is a registry published by the authority and changes on its own. Cross-checking against stale data is worse than not checking.

/declaracion

Filing is an act before the authority, with responsibility resting on whoever signs. Wurz prepares the input; it doesn't file.

/depreciacion

It depends on judgment calls and an asset history that isn't in the period's invoices.

/conciliacion

It's worth as much as the rest or more, and it still didn't make it: its input is a bank PDF with wildly variable formats. A star command that gets 70% of the rows right does more damage than five that are always right.

The pattern is the same across all six: either the data isn't in your documents, or the responsibility belongs to whoever signs. A command that's right almost always isn't a useful command — it's one that forces you to double-check all seven by hand, just in case.

How Wurz works Is it safe to upload client data to an AI?

Try it with your real documents

Upload a handful of receipts from your most demanding client and ask the question that normally takes you half an hour. That's how you'll know if it's worth it.

Try Wurz Talk to us

No credit card. Nothing to install.