Recording purchases from XML: from entering an invoice to reviewing and approving

Imagine a large supplier invoice with dozens of items, quantities, codes, costs and taxes. Now imagine typing every line again before inventory can be received.

That process feels small with five lines. With a large invoice it can consume a significant part of the morning.

The information already exists

In Mexico, the electronic invoice already carries structured information in XML. Retyping data that a machine can read means asking a person to reproduce information that already exists.

In the operation that gave rise to Metrify, some purchases could take close to half a day. The change is easy to explain:

drop XML → review → approve

The system still has to match concepts to the internal catalog and validate quantities, costs and company rules. The difference is that the person moves from data entry to review.

The gain is not only time

Manual re-entry creates more places where a purchase can fail: a mistyped quantity, wrong cost, omitted line or bad product match. Reducing re-entry helps the supplier invoice, recorded purchase and inventory receipt tell the same story.

The value appears when XML purchasing is connected to the rest of the ERP for distributors, not when it exists as an isolated importer.