Taremint turns the vendor documents you already receive — email, WhatsApp, scans, PDFs, photos — into trusted, compliance-ready transactions before they reach QuickBooks or regulatory reporting. Built on the Texas border, designed for recyclers with repeat industrial and cross-border vendors.
One intake core · state-specific output · Texas first
The problem
Between the scale, the back office, and whatever your state requires, the paperwork leaks. Documents arrive in five formats across five channels, Spanish fields get re-keyed by hand, and nobody can prove — quickly — that the record behind a given load is complete. The competition here is not other software. It is the manual back-office.
WhatsApp photos, email attachments, PDFs, scanned tickets, handwritten notes. Every vendor a different format, and none of them match your books. Asking vendors to change how they send is the one thing that never works.
Names, weights, commodities, seller IDs, vehicles, tickets, prices — copied one line at a time. The backlog grows the week whoever does it is out.
The books don't match the yard, the yard doesn't match the manifest, and the close slips while someone reconciles it all by hand. Owners in the corridor describe this in weekends, not hours.
When someone asks what backed a transaction — an auditor, an inspector, a buyer in diligence — the answer lives in an inbox, a phone, and someone's memory. One missing field turns a routine question into a problem.
What it does
Taremint sits upstream of your ERP, your accounting, and your state reporting — not in place of any of them. It makes the evidence trustworthy before it becomes a number anyone relies on. It is not an OCR tool, a translation service, or a scrap-yard ERP.
Documents arrive through the channels your vendors already use. The original evidence is preserved exactly as sent, so there is always something to point at later.
AI-assisted extraction with human review and deterministic validation. Bilingual industrial terminology is normalized to canonical concepts, and every value carries where it came from and how confident the read was.
Uncertainty routes to a person instead of finalizing silently. What comes out the other side is an approved, immutable transaction revision — and the output systems are projections of it, never the owners of it.
Live · working today · Pilot · running with design partners · Planned · on the roadmap, not built
How it works
Transaction integrity
Extraction confidence and transaction integrity are different questions. Taremint can read a document flawlessly and still tell you the transaction deserves a second look — an unfamiliar sender for a known vendor, a From/Reply-To mismatch, a plate nobody has seen, copper from a vendor who only ever sends ferrous, a load several times their normal range.
An external identity resolves to an authorized vendor before media is accepted. Unknown senders are quarantined and logged — never silently processed, never silently dropped.
Signals about where a document actually came from, surfaced rather than assumed.
What is normal for this vendor — materials, volumes, vehicles — and what isn't.
Taremint helps identify unusual or inconsistent transactions. It does not prevent fraud or cargo theft, and no software honestly can. What it does is surface the signal early enough for a person to check.
Design targets
The advantage
When a reviewer corrects a field, that correction is recorded as a feedback event — it does not silently rewrite how documents are read. Feedback accumulates into a candidate vendor pattern, that candidate is evaluated against historical documents, and it is published only if it actually improves extraction. One bad correction cannot degrade anyone's results.
Bilingual by default
Most software assumes English and bolts translation on afterward. Taremint normalizes bilingual industrial terminology to canonical concepts: flete, peso bruto, peso neto, tara, ASR, chatarra ferrosa. The concept is stable; the wording the vendor used is preserved alongside it.
MAQUILA: Componentes JUR-018 FECHA: 22-ABR-2026 PESO BRUTO: 22,140 kg TARA: 3,720 kg PESO NETO: 18,420 kg MATERIAL: chatarra ferrosa, fluff FLETE: 1,240 MXN
vendor: MAQ-JUR-018 date: 2026-04-22 gross_weight_kg: 22140 tare_kg: 3720 net_weight_kg: 18420 material_concept: FERROUS_SCRAP freight_mxn: 1240
Security & trust
SOC 2 readiness is treated as a requirement from day one rather than a later phase — it cuts through identity, change management, storage, operations, and incident response. Readiness means controls that actually operate and leave evidence.
Application authorization is the primary boundary, with database row-level security as defense in depth behind it. Isolation is proven by an automated cross-tenant test, not asserted.
Original documents are stored versioned and encrypted. Approved transactions are immutable — corrections create new revisions rather than overwriting.
Append-only audit events for connection changes, intake, quarantine, reviewer edits, approvals, and output attempts.
Duplicates, rejected senders, missing evidence, parse failures, and sync failures are all explicit states with timelines. Nothing disappears.
Taremint is not SOC 2 certified and does not claim to be. A SOC 2 report requires an independent CPA examination, and until one exists the honest word is ready, not compliant.
Founder
Pilot program
Taremint is pre-revenue and onboarding a small number of design partners. Pilots are scoped in a conversation — your volume, your channels, your state — because the pricing model is being rebuilt and we would rather quote you nothing than quote you something we intend to change.
What is working today: intake and bilingual extraction, running with design partners. What is not built yet: compliance validation, QuickBooks sync, and state export packaging. We label every capability Live, Pilot, or Planned for exactly this reason.
FAQ
The fastest way to find out whether this is real is to send a document and see what comes back. Founder-direct reply within one business day. No deck required.