Skip to content

MK Trade, Cost, Rate And Document Outputs — Operator Runbook

Purpose

  • Status: SOURCE-RECONCILED OPERATOR DRAFT / ROLE, ACCOUNTING, TEMPLATE, WIKI AND FIELD REVIEW REQUIRED - Audience: MK Trade/Accounting reviewer, Brokerage/Shipping operator, Outbound Cost operator, Booking/Packing operator, Document reviewer, Manager/Recovery and Support - Sou

Who does this

Whoever owns this job.

Before you start

  • You have the right account (see Permissions and Access).
  • The record and date you are working on are correct.

  • Words you do not know are in the Glossary.

  • Status: SOURCE-RECONCILED OPERATOR DRAFT / ROLE, ACCOUNTING, TEMPLATE, WIKI AND FIELD REVIEW REQUIRED

  • Audience: MK Trade/Accounting reviewer, Brokerage/Shipping operator, Outbound Cost operator, Booking/Packing operator, Document reviewer, Manager/Recovery and Support
  • Source baseline: qa@d96498360bb9c3541a1b5f862284596a7ed217b9
  • Process reconciliation: MK_TRADE_COST_RATE_DOCUMENT_OUTPUTS_RECONCILIATION.md
  • Rebuild packet: MK_TRADE_COST_RATE_DOCUMENT_OUTPUTS_CAPABILITY_REBUILD_PACKET.md
  • Important: this repository Runbook is not published Wiki content and does not authorize accounting, provider, DB, role, file, Wiki, deployment or Production effects.

1. Core Rules

Trade label
!= accounting close

Trade CSV
!= provider/file delivery

Export Brokerage success
!= every child reconciled

Cost saved
!= accounting confirmed

Rate response
!= every intended item updated

Document rendered/printed
!= approved, stored, emailed or completed

After every write, reread the exact authoritative owner records. After every output, compare the rendered projection with the current source.

Never use these as sole completion evidence:

  • a success toast;
  • one derived status;
  • one returned count;
  • the latest AP row;
  • a downloaded CSV;
  • a browser print dialog;
  • a document title or invoice number label;
  • an AI extraction proposal;
  • an Export reference without a child manifest;
  • a page-local edited value that was not reread from the server.

2. Roles

2.1 Trade/Accounting reviewer

Owns:

  • Trade filters and exact query time;
  • source-class reconciliation;
  • explanation of AP/AR/margin differences;
  • discrepancy escalation.

Does not own:

  • source correction through Trade;
  • accounting close/settlement;
  • Export child creation;
  • Cost/Rate writes without assigned capability.

2.2 Brokerage/Shipping operator

Owns:

  • reviewed Export Brokerage input;
  • explicit Booking selection;
  • Create once;
  • complete child readback;
  • safe cancel request;
  • unknown-result escalation.

Does not own:

  • arbitrary child deletion;
  • progressed child compensation outside current guard;
  • AI approval;
  • blind retry.

2.3 Outbound Cost operator

Owns:

  • inventory of all order-linked AP rows;
  • exact cost target and mutable state;
  • complete intended header/line input;
  • post-save/sibling/file/Trade readback.

2.4 Booking/Packing operator

Owns:

  • exact Booking/Sales item rate intent;
  • server reread before print;
  • Packing output source comparison.

2.5 Document reviewer

Owns:

  • source/template/fallback comparison;
  • intended scope and recipient/custody decision;
  • human print/reprint decision.

Does not own source correction from the printed page.

2.6 Manager/Recovery and Support

Owns only separately assigned recovery:

  • identify exact current owner and committed boundary;
  • coordinate child/cost/rate/source correction;
  • preserve before/after/request IDs;
  • prevent replay of unknown results;
  • confirm cleanup and residual state.

3. Trade Summary Procedure

3.1 Before opening

Confirm:

  • correct MK tenant/profile;
  • assigned Trade/Accounting role;
  • intended date window and timezone;
  • expected equipment/container/reference;
  • whether the purpose is review, discrepancy investigation or CSV export.

3.2 Review list

  1. Open Trade Summary / Deal Ledger through the normal menu.
  2. Set date/status/search filters.
  3. Record query time and filters.
  4. Locate the exact equipment/deal row.
  5. Record:
  6. equipment ID/container;
  7. Purchase and Sales references;
  8. link counts;
  9. Booking/logistics fields;
  10. AP, AR, margin and display status.
  11. Do not interpret CLOSED or CLAIMED as a saved accounting state.

3.3 Review detail and sources

  1. Open exact detail.
  2. Compare all visible transaction lines with header AP/AR totals.
  3. Inspect source classes separately:
  4. equipment AP;
  5. equipment AR;
  6. outbound-order AP;
  7. Purchase/Sales/Booking relationships.
  8. Stop when header cannot be explained from available source.
  9. Record deleted/ambiguous/multiple-link evidence.
  10. Route correction to the source owner; Trade remains read-only.

3.4 Export CSV

  1. Reconcile the visible projection first.
  2. Confirm current filters and source fingerprint.
  3. Export once.
  4. Treat the file as a local copy of the current projection.
  5. Do not label it as QBO import, settlement, approval or retained system file.

3.5 Trade recovery

Problem Reread first Safe action Do not do
header/detail mismatch source breakdown and transaction classes record unresolved difference; source-owner review edit through Trade
wrong/multiple links all candidate links and deleted flags stop attribution accept MAX/latest link
stale CSV current filters/query/source export a new reviewed copy reuse old file as current
module/page denial current menu/API access role/config owner review direct URL bypass

4. Export Brokerage Procedure

4.1 Before Create

Confirm:

  • feature and required modules are enabled;
  • operator has assigned capability;
  • source document was reviewed manually;
  • vendor/customer/reference are correct;
  • Ocean flow has the exact selected active Booking;
  • every container, size, seal, time and line is correct;
  • commodity, quantity, weight, rate and UOM agree;
  • the supported line/container shape is accepted for the current Runtime;
  • no existing child set already represents the request.

AI extraction is only a proposal. Correct every field before Create.

4.2 Create once

  1. Record all input and source IDs.
  2. Submit Create once.
  3. Preserve the response or timeout evidence.
  4. On success, capture all returned IDs.
  5. Reread:
  6. Inbound Purchase header/items;
  7. Transload;
  8. Inventory Lot and remaining balance;
  9. Booking and reverse links;
  10. every Outbound order/item;
  11. Equipment/Equipment Load;
  12. Allocations.
  13. Confirm generated/pre-existing child disposition.
  14. Do not continue to downstream work when balance, pointer or child identity is unexplained.

4.3 Create response missing

Do not press Create again.

Search using:

  • exact reference;
  • container numbers;
  • selected Booking;
  • generated markers when available;
  • Purchase/Outbound child relationships;
  • Inventory Lot/Allocation links.

Classify:

ABSENT
COMMITTED
PARTIAL_CONFLICT
UNKNOWN

Retry only after proving the original did not commit.

4.4 Cancel

  1. Identify the exact generated child set.
  2. Confirm current Inbound and all Outbound IDs.
  3. Review Scale/equipment/transload/inventory ledger/allocation/cost/downstream evidence.
  4. Stop when any child has progressed beyond the accepted compensation boundary.
  5. Submit Cancel once.
  6. Reread every child and preserved pre-existing Booking/Equipment.
  7. Record residual markers/pointers or balances.

Cancel is not a general delete tool.

4.5 Cancel response missing

Reread the complete child manifest. Do not repeat Cancel until proving the prior compensation did not commit.

4.6 Export escalation packet

Collect:

  • tenant/profile/operator;
  • input/reference/Booking/container;
  • response/timeout time;
  • every child ID;
  • generated marker evidence;
  • Lot/Allocation balances;
  • progressed blockers;
  • current child disposition;
  • retries already attempted.

Do not include credentials or unrestricted source documents.

5. Outbound Cost Procedure

5.1 Inventory before edit

  1. Open exact Outbound Sales order.
  2. List every active AP transaction linked to the order.
  3. Record each transaction:
  4. ID;
  5. status;
  6. header metadata;
  7. lines;
  8. files/links;
  9. likely business owner.
  10. Identify the exact Outbound Cost target.
  11. Stop if ownership is ambiguous or multiple workflows share the same order.

5.2 Create or update

  1. Confirm target is new or mutable.
  2. Capture complete existing header/line baseline.
  3. Enter the complete intended cost set.
  4. Submit once.
  5. Reread:
  6. exact target header;
  7. complete lines;
  8. status;
  9. sibling AP rows;
  10. file links;
  11. Trade Summary projection.
  12. Verify no omitted metadata/line was unintentionally cleared.

5.3 Delete

  1. Confirm exact transaction ID and mutable status.
  2. Review files and sibling AP implications.
  3. Delete once.
  4. Reread target, lines, files, siblings and Trade.
  5. Do not delete physical file objects from this procedure.

5.4 Cost recovery

Problem Reread Safe action
multiple AP candidates all headers/lines/files accounting owner identifies target
immutable rejection target status use approved accounting correction path
response loss all order AP rows retry only proven absent command
metadata/line overwrite before/after baseline separately reviewed restoration
file orphan file object/link owner repair through document process

6. Packing Rate Procedure

6.1 Baseline

Before editing, record:

  • Booking ID;
  • Sales order and item IDs;
  • current persisted rate;
  • display rate and UOM/base;
  • intended rate and source;
  • current document scope.

6.2 Correct rate

  1. Edit only the intended Rate field.
  2. Do not treat Amount edit as saved data.
  3. Wait for the current request result.
  4. Reopen Packing and source Outbound rows.
  5. Verify every intended item ID and persisted rate.
  6. Print only after authoritative reread.

6.3 Partial or unknown result

  1. Reread every intended item.
  2. Classify each as updated, unchanged, stale, denied or missing.
  3. Retry only exact unchanged eligible items.
  4. Stop when another actor changed a rate or the valid value is unclear.

6.4 Rate recovery limits

  • no direct DB edit;
  • no broad Booking/item ID list;
  • no zero/negative correction without accepted business policy;
  • no print from an unresolved local display;
  • no inference from updated count alone.

7. Packing Document Procedure

7.1 Verify source

Confirm:

  • Booking and linked Outbound Sales;
  • exact container/equipment load scope;
  • Seal/reference/load values;
  • equipment commodities and Outbound items;
  • rates/UOM;
  • parties, ports, terms and dates.

7.2 Render

  1. Open Packing List through Booking Detail.
  2. Select all containers or one exact equipment load.
  3. Identify whether the output uses equipment commodity or full-output fallback.
  4. Compare every row and fixed/template value with source.
  5. Stop on unexpected fallback or fixed-value conflict.

7.3 Transient edits and print

  • textarea/amount edits affect the browser output only;
  • rate correction belongs to the separate Rate process;
  • confirm persisted rate before print;
  • browser print creates no file, email, Booking flag or approval state.

7.4 Recovery

On source change or print ambiguity, reopen and reconcile. The document owner decides replacement/reprint.

8. Purchase Local Invoice Procedure

8.1 Verify source

Confirm exact Purchase order, shipper, item quantity/weight/UOM/rate, trucking fee, credit and relevant dates.

8.2 Reconcile formulas

MT   NET_WEIGHT * RATE / 2204.590
LT   NET_WEIGHT * RATE / 2240.000
ST   NET_WEIGHT * RATE / 2000.000
EACH QUANTITY * RATE
other NET_WEIGHT * RATE

Confirm total:

item amounts + trucking fee - credit

Stop on unknown UOM or accounting disagreement.

8.3 Print

The displayed order number is currently an invoice label, not an independent invoice record. Print is browser-only. Record custody externally only under an accepted procedure.

8.4 Access warning

Current direct page access and API/module/config gates are not proven equivalent. Use the normal menu/popup path and stop on unexpected direct-page access behavior.

9. Booking Confirmation Procedure

9.1 Verify source

Confirm Booking, parties, terminals, vessel, dates, ports, commodity/container fields and optional Sales link.

9.2 Render

  1. Open Booking Confirmation through the normal role-protected Booking path.
  2. Compare every source and fixed/template field.
  3. Verify whether linked Sales reference replaces displayed PO context.
  4. Confirm current-date/template drift is understood.
  5. Stop on ignored/mismatched special instructions or branding.

9.3 Print

Browser print does not confirm or approve the Booking and creates no durable output state.

10. Sales Weight Ticket Procedure

10.1 Verify source

Confirm:

  • exact Sales order;
  • item quantity/gross/tare/net/UOM;
  • Booking/reference;
  • equipment/container/seal;
  • whether a physical Scale Ticket exists separately.

10.2 Render

Open the order-owned Sales Weight Ticket from the normal Outbound path. Reconcile raw totals and equipment values.

Required rule:

Sales Weight Ticket
!= Physical Scale Ticket

The output can exist without physical Scale evidence.

10.3 Print

Cancel the auto-opened print dialog if review is incomplete. Mixed UOM or aggregate equipment ambiguity blocks distribution. Print creates no stored result.

11. Common Unknown-Result Decision

READ OR CSV FAILED
-> rerun current query and compare source fingerprint

EXPORT/COST/RATE WRITE UNKNOWN
-> reread exact business records and request/job identity
-> retry only proven absent/missing owner command

PRINT UNKNOWN
-> no system acknowledgement exists
-> reopen current projection
-> human owner decides reprint/replacement

12. Current Versus Target Content

Current procedures describe source-reconciled PHP behavior. The following remain future-only until implemented and released:

  • durable Export Job/result lookup;
  • request-token idempotency;
  • typed Outbound Cost subtype;
  • per-item rate result/history;
  • React Trade/Export/Cost/Rate/Document workspaces;
  • durable document snapshot/file/delivery;
  • PostgreSQL.

Do not publish them as current Wiki controls.

13. Required Runtime/Field Verification

Before this Runbook becomes accepted current Wiki content, verify:

  • exact current menu labels and role paths;
  • Trade list/detail/source formulas;
  • Export one-create/cancel/response-loss fixtures;
  • Cost multiple AP and metadata preservation;
  • Rate partial/stale/print race;
  • each direct document role/config/tenant path;
  • formulas/fallback/template fields;
  • browser print behavior;
  • no unintended DB/file/provider write;
  • exact cleanup.

Current evidence ceiling remains repository source reconciliation.

---

Source: docs/runbooks/MK_TRADE_COST_RATE_DOCUMENT_OUTPUTS_OPERATOR_RUNBOOK.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.