Good documentation practices (GDocP) are the rules for recording evidence you can defend: who, when, what happened, and how corrections keep the trail. In Mexico–US freight that is not a plant SOP — it is the trip file accounts payable uses before paying.
The ALCOA frame (Attributable, Legible, Contemporaneous, Original, Accurate) turns data integrity into proof of delivery (POD), GPS, the Mexican digital tax invoice (CFDI), and Carta Porte 3.1. If the record fails ALCOA, the truck may have arrived — and you still lack a sound basis to release payment. When you audit 100% of a pilot flow, the published pattern is recovering 5–7% of freight spend because “almost good” evidence let unsupported charges through.
- 5 integrity attributes for the record
- ALCOA
- Do / Don’t on dock and tower
- 10 rules
- rate · CFDI · CP · GPS · POD
- 5 docs
- pattern auditing 100% of the pilot
- 5–7%
Trip-file cluster: POD convention · pre-pay audit · freight journey.
What good documentation practices are
In regulated industries, GDocP grew with data integrity (ALCOA / ALCOA+). For Mexico–US shippers and logistics operators, the same bar applies to operational and fiscal transfer records: you do not need a lab to require that the POD shows who signed and when.
Do not confuse this with pharmaceutical Good Distribution Practices (GDP): that is another framework. Here the object is the trip record — paper, photo, ePOD, or XML — and whether it is credible.
Order-to-pay context: Mexico freight journey. If your “digitization” is still a human bridge between WhatsApp and Excel, read fake digitization.
Why they matter in freight (accounts payable)
Money is decided with evidence. Without documentation rules, the tower “confirms” deliveries in chat and finance pays on samples: invented detention, mis-tied rates, and illegible PODs follow.
Blurry POD via WhatsApp
Documentation failure: Not legible / not a usable original
Accounts payable impact: Cannot validate receipt; pay blind or dispute late
“Warehouse” signature, no name
Documentation failure: Not attributable
Accounts payable impact: No witness for chargebacks or rejects
POD time ≠ GPS window
Documentation failure: Not contemporaneous / not accurate
Accounts payable impact: Detention or Late without cross-check
CFDI not tied to trip ID
Documentation failure: Not consistent / incomplete
Accounts payable impact: Duplicates and payments for trips tower never ran
“Clean” PDF rewrite
Documentation failure: Not original (obliteration)
Accounts payable impact: You lose the error trail; internal audit without cause
Cross-check playbook: CFDI + Carta Porte + GPS + POD audit. Scale and sampling: pre-pay audit at volume.
ALCOA letter by letter (Mexico examples)
ALCOA is the data-integrity acronym. Below, each letter with a DC, dock, or accounts payable example — not a pharma lot record.
A — Attributable
Means: You know who recorded and signed
Mexico–US freight example: Named DC receiver on the POD
Typical miss: Shared carrier login; “signing for a colleague”
L — Legible
Means: Readable without guessing
Mexico–US freight example: Sharp scan or structured ePOD fields
Typical miss: Dark photo; internal abbreviations with no glossary
C — Contemporaneous
Means: Recorded when it happens
Mexico–US freight example: Timestamp at dock close; GPS in the delivery window
Typical miss: POD filled next day “from memory”
O — Original
Means: First capture or true copy kept
Mexico–US freight example: First PDF/photo tied to the ID; or ePOD with audit trail
Typical miss: Only a rewritten Excel “summary” remains
A — Accurate
Means: Reflects what was observed
Mexico–US freight example: Pallets/weight/time match rate and any reject
Typical miss: Marking “complete” when there was a short
ALCOA+ adds Complete (include deviations and rejects), Consistent (same story across tower, GPS, and fiscal), Enduring (retain per your policy / operational fiscal retention), and Available (retrieve in minutes for a dispute). We do not invent foreign fines: in Mexico the operable focus is SAT/Carta Porte plus defense to the customer and to accounts payable.
Do / Don’t: 10 recordkeeping rules
Ten pairs for tower, dock, and accounts payable. Freight evidence rules — not a generic template from another industry.
1
Do: Sign and date every critical entry (POD, reject, correction)
Don’t: Leave “to sign later” or blank signature lines
2
Do: Use a permanent medium (ink / system with history)
Don’t: Pencil, white-out, or erasure that hides the original text
3
Do: Correct with a single line, initials, date, and reason (or a digital version)
Don’t: Scribble until illegible, rewrite “clean,” or delete the source file
4
Do: Record at the moment of the event (dock, appointment, delivery)
Don’t: Backdate, post-date, or reconstruct the trip days later
5
Do: Mark N/A on controlled blank fields
Don’t: Leave gaps someone can fill later with no trail
6
Do: One user = one person; role-based permissions
Don’t: Shared passwords or signing “on behalf of” without mandate
7
Do: Keep the source record tied to the trip ID
Don’t: Only a chat summary or an Excel with no link
8
Do: Tie photo/POD/GPS to the same ID as rate and CFDI
Don’t: Orphan WhatsApp evidence with no shipment number
9
Do: Second review before releasing material payment
Don’t: Same person creates the evidence and approves the payment
10
Do: Document the reason for every correction
Don’t: Silent changes to amounts, times, or delivery status
Trip documents (the file)
The minimum file joins five pieces to the same ID. Each answers a different question; none replaces another.
Rate confirmation
What it proves: Agreed price and terms
Typical owner: Traffic / freight buy
Key ALCOA rule: Original + attributable (who accepted)
CFDI (income/transfer)
What it proves: Fiscal voucher for the service or transfer
Typical owner: Issuer / AP verifies
Key ALCOA rule: Accurate + consistent with the trip
Carta Porte 3.1
What it proves: Transfer complement in national territory (when it applies)
Typical owner: Issuer; buyer verifies pre-pay
Key ALCOA rule: Complete (catalogs) + contemporaneous to dispatch
Useful GPS
What it proves: Location / geofence in the window
Typical owner: Tower / monitoring
Key ALCOA rule: Contemporaneous + available when disputing
POD / ePOD
What it proves: Who received, when, what, and in what condition
Typical owner: Consignee dock + carrier capture
Key ALCOA rule: Attributable + legible + original
Go deeper: POD, Carta Porte, and invoice · Carta Porte vs POD: what each proves · what is Carta Porte.
Paper vs digital: what passes
“Digital” is not automatically ALCOA. An ePOD with a unique user and timestamp usually wins; an illegible chat PDF usually loses — even if it traveled by phone.
Paper POD
When it passes: Ink, named signature, time, legible, faithful scan on the ID
When it fails: Pencil, white-out, illegible signature, sheet with no trip
Action: Scan on delivery day — not “later if we have time”
Photo / PDF via WhatsApp
When it passes: Only as transport into the TMS trip file
When it fails: If it is the only file and never indexed to the ID
Action: Upload to the trip; chat is not the master archive
ePOD / app capture
When it passes: Unique user, optional geolocation, required fields
When it fails: Shared login; editable with no trail
Action: Require change history and reason
CFDI / Carta Porte XML
When it passes: Valid UUID and cross-check vs rate/trip
When it fails: Courtesy PDF without XML; nodes that don’t cover the route
Action: Validate before scheduling payment
Capture adoption: what is ePOD · shipper POD convention.
How to implement in tower and DC
Do not start by rewriting three years of history. Start with the corridor that hurts accounts payable most and make new records born right.
Order
Record, trust, and scale
Define
What counts
Train
Dock and tower
Enforce
Fields on ID
Audit
100% of pilot
Scale
More lanes
- Define: one page on what counts as a valid POD (minimum fields) and what accounts payable rejects.
- Train: dock, tower operators, and analysts — with your corridor examples, not theory.
- Enforce in system: no trip close without ID, usable POD, or fiscal cross-check when it applies.
- Audit 100% of the pilot: sampling teaches little when the error is systematic.
Operable checklist
Use this on the corridor pilot. Each item is binary: pass or return to tower/dock.
Elige un paso para ver el detalle
Detalle del paso · 01
Unique ID
Extended invoice checklist: 15-point pre-pay checklist.
What OCL executes with the file
OCL Cargo is an autonomous TMS with computer-use agents (they operate screens and portals like an analyst). It does not ask you to replace your TMS on day one: it coexists, builds the file, and leaves exceptions to your team.
- Pre-pay cross-check of rate + CFDI + Carta Porte + GPS + POD on the same trip.
- POD capture tied to the ID (fewer orphan chat proofs).
- OCL can stamp invoice and Carta Porte when the fiscal scope of the flow requires it — we do not deny stamping; deductibility remains a call with your tax advisor.
- Audit 100% of the pilot universe: published 5–7% spend pattern (logistics operator case).
Key takeaways5 points
- Good documentation practices (GDocP) = rules so the record is attributable, legible, contemporaneous, original, and accurate (ALCOA) — in freight, applied to the trip file.
- Accounts payable should not release if signature, time, legibility, or the shared trip ID (rate · CFDI · Carta Porte · GPS · POD) is missing.
- Correct without obliteration: the error must stay visible; every change with who, when, and why.
- Ten Do/Don’t rules cover signature, contemporaneous capture, blank fields, unique login, and second review before pay.
- OCL audits 100% of the pilot file, can stamp invoice and Carta Porte, and coexists with your TMS; 5–7% spend pattern when evidence closes.
Would your file pass ALCOA tomorrow?
Related reading
Frequently asked questions
Rules for creating and keeping defensible evidence: who recorded, when, what was observed, and how corrections keep the trail. In Mexico–US freight they apply to the trip file (rate confirmation, CFDI, Carta Porte, GPS, and proof of delivery) — not only plant SOPs.
ALCOA is five integrity attributes: Attributable, Legible, Contemporaneous, Original, and Accurate. If the POD or GPS fails those attributes, accounts payable lacks a solid basis to release or hold payment. ALCOA+ adds Complete, Consistent, Enduring, and Available.
No. GDocP (Good Documentation Practices) are recordkeeping and data-integrity rules. Pharmaceutical Good Distribution Practices are a different cold-chain/quality framework. Here we mean GDocP applied to the transport trip file.
Without obliteration: on paper, a single line that leaves the error readable, plus initials, date, and reason; digitally, a version or comment with who, when, and why. Never white-out, opaque scribble, or a “clean rewrite” that discards the source. See the POD convention.
The person who received (or rejected) at the consignee DC or dock, identifiable by name/role with date-time. Not a generic “warehouse” signature or a shared carrier login. Field detail: what is POD.
Yes — if it is legible, attributable, contemporaneous, and tied to the trip ID. A blurry WhatsApp PDF with no signature or time fails ALCOA even if it is “digital.” An ePOD with unique user, timestamp, and usable photo is usually easier to audit. Compare ePOD.
Not on day one. OCL builds and audits the trip file (rate + CFDI + Carta Porte + GPS + POD), can stamp invoice and Carta Porte when fiscal scope applies, and coexists with your system of record. Your team on exceptions. Typical pilot 6–8 weeks; 5–7% pattern when auditing 100% of the flow (3PL case).