--- title: "Reconcile Freight Rates and Dwell Times Before Issuing Credits" description: "Reconcile Freight Rates and Dwell Times Before Issuing Credits. Review practical exception decisions, evidence checks, and a copyable Genie job description." canonical: https://www.stacksync.com/blog/reconcile-freight-rates-and-dwell-times-before-issuing-credits last_modified: 2026-09-21 --- # Reconcile Freight Rates and Dwell Times Before Issuing Credits > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md To audit detention or dwell-related charges, first determine which recorded events start and stop the billable interval under the applicable agreement. Author Ignacio Malpartida · GTM Engineer Published September 15, 2026 Updated September 21, 2026 Read time 7 min read APP TIPS ## Dwell time needs a contractual definition To audit detention or dwell-related charges, first determine which recorded events start and stop the billable interval under the applicable agreement. Gate arrival, check-in, unloading, and gate departure may be different timestamps. The subtraction is easy; selecting the right events is the substantive part of the dispute. Convert the timestamps to a consistent timezone and preserve their original references. Look for missing events, manual corrections, and records that cross midnight. If the departure precedes arrival after timezone normalization, treat the data as inconsistent. Do not repair it by assuming a day or adding a convenient duration. ![Departure missing: Request operational evidence. No guessed dwell interval.; Rate version unclear: Identify applicable agreement. No current-rate substitution.; Existing credit covers dispute: Surface its application status. No second credit.](https://www.stacksync.com/images/blog-highlights/genies-freight-invoice-disputes-exceptions.webp) *Departure missing: Request operational evidence. No guessed dwell interval.; Rate version unclear: Identify applicable agreement. No current-rate substitution.; Existing credit covers dispute: Surface its application status. No second credit.* ## Evidence needed to resolve the exception Use this exception guide when reviewing a proposed Genie workflow or investigating a case that cannot proceed confidently. The tables describe operational decisions to configure in your environment. They are not claims that a connected application automatically supplies your organization’s policies, identity mappings, or approval process. | System or owner | Evidence and responsibility | | --- | --- | | Zendesk | Disputed charges, requests for clarification, and the confirmed resolution. | | NetSuite | Invoice lines, existing customer credits, and finance-approved credit memos. | | Postgres | Agreed rate records and shipment arrival/departure evidence. | | Finance | Approval of any new credit memo and its accounting treatment. | Required context for this workflow design. ## Make the adjustment reproducible For an illustrative agreement with sixty minutes free and thirty dollars per subsequent thirty-minute block, a recorded ninety-minute stay produces thirty dollars of chargeable time, assuming that block rule applies. If the invoice charges sixty dollars for the same line, the proposed adjustment is thirty dollars before any finance-reviewed tax treatment. These figures illustrate the method, not a standard freight tariff. Attach the rate clause, event references, elapsed time, free allowance, chargeable units, and multiplication. If the contract uses started blocks, daily caps, or other terms, apply those actual terms. Do not carry the illustrative rule into a live case. ## Resolve the financial remainder, not the historical complaint twice Check whether an existing credit already covers the calculated discrepancy. Its existence and its application to an invoice are separate facts. Finance may need to review an unapplied credit rather than authorize a second one. Search by the invoice relationship and covered charge as well as the customer. When evidence supports only part of the dispute, separate the supported adjustment from the remaining question. Zendesk can record that a rate mismatch is established while the timing issue awaits a missing departure record. Keep the customer informed of confirmed progress, but obtain finance approval before creating a new credit memo and report its confirmed ID only after the write is verified. ## Decision table for common exceptions Use the condition in the first column to choose the next action. The final column describes the boundary that must remain true while the case is unresolved. Apply the organization’s actual policy and source records to the live case; do not treat an illustrative condition as proof that the condition exists. | Observed condition | Next action | Required boundary | | --- | --- | --- | | Departure missing | Request operational evidence | No guessed dwell interval | | Rate version unclear | Identify applicable agreement | No current-rate substitution | | Existing credit covers dispute | Surface its application status | No second credit | | Finance decision pending | Keep proposal pending | No memo created | Exception decisions for freight invoice disputes. ![The underlying freight invoice disputes process: scope the dispute, collect applicable evidence, calculate the proposal, check and approve credits, confirm the resolution.](https://www.stacksync.com/images/blog-diagrams/genies-freight-invoice-disputes.webp) *The underlying freight invoice disputes process: scope the dispute, collect applicable evidence, calculate the proposal, check and approve credits, confirm the resolution.* ## Illustrative exception and recovery Finance already issued a thirty-dollar credit, but it has not been applied to the invoice. A repeat dispute should surface that credit and its status to finance, not create another thirty-dollar memo. This example uses fictional records to show the decision logic. It is not a customer case study or a claim of measured results. In a live case, retain the actual record IDs and evidence behind each statement, and replace all illustrative quantities or timing assumptions with the approved operational inputs. ## What to record before resuming A finance review packet with invoice lines, applicable rate clauses, normalized event times, a reproducible adjustment calculation, existing-credit checks, and the confirmed resolution. Preserve the original finding and the evidence that resolves it. Record which person or system supplied the clarification, which proposal it applies to, and the action now permitted. Do not erase the uncertainty from the history: a later reviewer needs to understand why the case paused and why it resumed. ![Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.](https://www.stacksync.com/images/blog-diagrams-mermaid/genies-freight-invoice-disputes.webp) *Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.* ## Boundaries that remain in force - Use the rate agreement applicable to the shipment and service date. - Calculate proposed adjustments from recorded events, with no invented free-time rule. - Check existing credits and require finance approval before any new credit memo. - Update Zendesk only with the confirmed resolution and record references. ## Review the case before restarting First verify that the new evidence resolves the original blocker rather than a different issue. Then check whether the case, source records, or proposed action changed during the wait. A response attached to the right ticket can still be insufficient if it refers to an earlier proposal or leaves a required quantity, identity, or approval unresolved. Run the relevant row from the decision table as a review scenario. Confirm that the job stops at the required boundary, asks for the specified information or decision, and resumes from the confirmed state. If a write or message may already have succeeded, inspect its destination before repeating it; if this job only prepares a draft or report, verify that it stays within that output scope. - Disputes with reproducible line-level calculations - New credits with explicit finance approval - Duplicate credits prevented or detected Track unresolved cases by their actual blocker and owner. A case waiting for clarification needs a different next action from one waiting for a confirmed result. Review the evidence when the state changes, and keep any still-unresolved completion condition visible instead of treating a successful intermediate step as the end of the work. ## Give your Genie a job description Copy the job description below. It preserves the scope and decision boundaries of this use case. Configure the referenced systems, record relationships, policies, and approval owners in your workspace before enabling the job. Freight invoice disputes · Medium Investigate freight invoice disputes received in Zendesk. Compare the NetSuite invoice with agreed rates and recorded arrival and departure times in Postgres. Explain any discrepancy and calculate the proposed adjustment. Check whether a credit already exists, then ask finance to approve any new credit memo before creating it. Update the ticket with the confirmed resolution. Paste this into “Give your Genie a job description.” [Explore Stacksync Genies](https://www.stacksync.com/ai-agents). ## Apply this in beverages: distributor order and freight policy For beverage deliveries, the finance review begins with the freight terms and receiving window actually approved for the distributor order. The linked guides connect those commitments to logistics evidence and keep a requested delivery time distinct from an accepted appointment. | Record to reconcile | Responsible owner | Rule to preserve | | --- | --- | --- | | Distributor order | Sales operations | Preserve requested quantities, destination, date, and commercial reference. | | Freight policy | Commercial owner | Own the applicable threshold, unit, terms, and approved exceptions. | | Receiving window | Logistics | Confirm destination-specific time and date requirements with current evidence. | An exception to plan for: **Order quantity drops below threshold**. Reassess freight terms before release instead of inheriting the earlier approval. Acceptance check for the pilot: freight approval identifies the order amount or quantity it covers. The [beverages hub](https://www.stacksync.com/industry/cpg/beverages) connects the broader operating context. These guides develop the specific record mappings and decisions for this application: - [Beverage Distributor Order Workflows: Check Freight Thresholds and Delivery Windows](https://www.stacksync.com/blog/beverage-distributor-order-workflows-check-freight-thresholds-and-delivery-windows) - [AI Agents for Beverage Brands: Investigate Distributor Delivery Claims](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) - [Distributor Delivery-Window Automation for Beverage Brands](https://www.stacksync.com/use-case/distributor-delivery-window-automation-for-beverage-brands) ## Related workflow and integration guides - [Investigate Freight Invoice Disputes Across NetSuite and Postgres](https://www.stacksync.com/blog/investigate-freight-invoice-disputes-across-netsuite-and-postgres) - [All Genies workflow examples](https://www.stacksync.com/ai-agents#genies-use-cases) - [When a workflow should escalate to a person](https://www.stacksync.com/blog/human-in-the-loop-automation-when-to-escalate) - [Resolve Partial Deliveries and Missing Delivery Documents](https://www.stacksync.com/blog/resolve-partial-deliveries-and-missing-delivery-documents) - [Confirm Rescheduled Deliveries Without Premature Booking Promises](https://www.stacksync.com/blog/confirm-rescheduled-deliveries-without-premature-booking-promises) - [Zero-ETL Is Not Two-Way Sync: Aurora PostgreSQL and NetSuite](https://www.stacksync.com/blog/two-way-sync-aurora-postgresql-netsuite) - [Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [Netsuite integrations](https://www.stacksync.com/connectors/netsuite) ## Implementation references These first-party references document the underlying records and interfaces. The cross-system sequence, approvals, and completion rules in this article are a proposed operational configuration; validate them against your connected workspace before enabling it. - [NetSuite: issuing a customer credit memo](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1311510.html) - [Zendesk: ticket comments and visibility](https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/) FAQ ## Frequently asked questions What does the freight invoice disputes workflow produce? A finance review packet with invoice lines, applicable rate clauses, normalized event times, a reproducible adjustment calculation, existing-credit checks, and the confirmed resolution. What should happen when the evidence is incomplete? Keep the affected action pending and obtain the missing source evidence or required decision. Update Zendesk only with the confirmed resolution and record references. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Investigate Freight Invoice Disputes Across NetSuite and Postgres 8 min read read](https://www.stacksync.com/blog/investigate-freight-invoice-disputes-across-netsuite-and-postgres) [App tips AI Agents for Beverage Brands: Investigate Distributor Delivery Claims 5 min read read](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) [App tips Broken Cases and Disputed Delivery Windows: Exception Handling for Beverage Claim Agents 5 min read read](https://www.stacksync.com/blog/broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)