A shipment may be sold at the right price and still suffer delays, late payments or responsibility disputes when information is not handed over correctly between Sales, Operations and Accounting. Sales holds the customer commitment; Operations holds the execution conditions and actual exceptions; Accounting controls cash flow, invoices and receivables/payables. When the three functions work from different data versions, a small change in schedule, service scope, surcharge or payment term can distort the entire plan. This article provides a handover matrix for B2B import shipments, particularly industrial machinery, equipment and components, defining mandatory data, ownership, evidence of acceptance and control gates before the job moves to the next stage.

Operational reference for importers, logistics teams, operations and finance.

QUICK FACTS

One Job ID

All commercial, operational and financial data must reference one job.

Acceptance is required

The receiving function confirms completeness or records gaps.

Scope and cost stay connected

Sell, buy and exception amounts are reviewed together.

Closure is mandatory

POD, actual cost, invoices and balances are required to close.

SCOPE OF APPLICATION

This article applies to B2B import shipments involving Sales, Operations and Accounting, with emphasis on industrial machinery, equipment and components moved by sea, air or road. It can also support exports after adjusting document flow, booking ownership and payment terms.

Project cargo, dangerous goods, temperature-controlled cargo, EPE/FDI, entrusted imports and controlled goods require additional technical, insurance, licence, tax, cash-flow and approval fields.

KEY TERMS

Term	Meaning	Operational role
Handover	Transfer of information and responsibility from one function to another.	Creates an evidenced control point rather than an informal verbal exchange.
Job File / Job ID	A unique reference for one shipment or service order.	Connects quotation, transport documents, costs, invoices and balances to one record.
Scope of Service	The agreed inclusions, exclusions and conditions.	Defines what Operations may execute and what Accounting may book.
Cost Sheet	Forecast and actual sell/buy amounts by charge item.	Controls margin, surcharges and out-of-scope changes.
Pre-alert	Shipment data and documents sent before arrival.	Used by Operations for readiness and by Accounting for payment/invoicing planning.
Debit Note	A payment request issued by an agent or vendor.	Supports a payment request; it is not automatically a tax invoice or sufficient accounting document, and must be checked against scope, contract and internal approval.
Acceptance	Confirmation that the receiving function can take over the job.	May be conditional, with missing items, owner and deadline recorded.
Change Log	History of changes to schedule, scope, price, documents or customer instructions.	Keeps all functions on the latest approved version.

HOW THE THREE-FUNCTION HANDOVER WORKS

A handover is not merely forwarding a chat or folder. It transfers processing authority, update duties and escalation responsibility over one data set. Sales owns the accuracy of the commercial promise; Operations converts it into an executable plan; Accounting converts validated data into payments, invoices, balances and reporting.

The flow is not strictly one-way. When Operations finds a booking change, surcharge or missing document, the information must return to Sales for customer management and go to Accounting for cash-plan adjustment. A robust process therefore contains a feedback loop.

Control point: Data is considered handed over only when version, sender, receiver, time, evidence and acceptance status are identifiable.

INFORMATION AND RESPONSIBILITY MATRIX

Information group	Required data	Sales	Operations	Accounting	Evidence
Customer and legal entity	Legal name, tax ID, billing address, contacts, contract/PO.	Initiates and validates with customer.	Confirms the entity receiving the service.	Sets invoice and credit-control data.	CRM, contract, approval email.
Cargo profile	Description, model, quantity, packages, weight, dimensions/CBM, cargo condition.	Collects complete and specific data.	Checks transport, packing, customs and equipment feasibility.	Uses data to reconcile charges and supporting documents.	RFQ, Invoice, Packing List, catalogue.
Commercial terms and route	Incoterm, pickup, POL/POD, delivery point, ready date, mode and deadline.	Locks the commercial promise.	Validates booking, cut-off and feasible timeline.	Reconciles revenue/cost components and invoice or recognition milestones against the contract, acceptance evidence, accounting policy and applicable rules; these must not be inferred from Incoterms alone.	Approved quotation, booking, scope email.
Selling price and payment terms	Charge items, whether VAT is included or excluded, currency/exchange basis, validity, deposit and due date.	Owns the customer-approved version.	Does not commit out-of-scope costs without escalation.	Determines tax and invoicing treatment under applicable rules; sets receivables, collection plans and overdue alerts.	Approved quote, contract, payment terms.
Buy cost and vendors	Agent/vendor, buy rate, currency, local charges, free time, payment conditions.	Hands over the rate source used for pricing.	Books against the correct source and updates actual cost.	Matches debit notes, payment request and accounting entries.	Rate sheet, vendor quote, debit note.
Documents and compliance	Invoice, Packing List, B/L/AWB, C/O, licences, catalogue and labels.	Secures document commitments from customer/supplier.	Checks transport/customs data and missing-document deadlines.	Submits payment or recognition only when required evidence is available; any gap must be recorded and approved under the exception authority.	Document checklist, pre-alert, customs file.
Exceptions and approvals	Surcharges, schedule changes, B/L amendments, storage and other extra costs.	Notifies customer and obtains commercial approval.	Records cause, evidence and corrective plan.	Checks approval before payment or additional invoicing.	Change log, approval email, incident record.
Job closure	POD, customs declaration, input/output invoices, balances and forecast variance.	Confirms service commitment completion.	Completes operational evidence and final actual cost.	Reconciles revenue, cost, AR/AP and closes the job.	POD, final cost sheet, reconciliation.

DOCUMENTS AND DATA TO CHECK

For industrial machinery, equipment and components, a generic product name is rarely sufficient for transport planning or document review. Every item should be tied to its issuing source and intended process step.

Document/data	Issuer	Used for	Fields that must match
Customer-approved quotation	Sales	Job opening and scope lock	Version, validity, currency, VAT inclusion/exclusion, inclusions/exclusions and payment terms
RFQ/cargo data	Sales/Customer	Booking, transport and customs	Description, model, packages, gross/net weight, dimensions/CBM, pickup, ready date
Booking/transport plan	Operations/Agent/Carrier	Milestone tracking	Booking no., ETD/ETA, cut-off, vessel/flight, route, free time
Pre-alert and documents	Operations/Agent/Shipper	Arrival and customs preparation	B/L/AWB, Invoice, Packing List, C/O, arrival notice and permits
Cost sheet	Sales + Operations	Margin and exception control	Sell/buy rates, currency, exchange rate, forecast/actual, approval owner
Debit note, supplier invoice or supporting document	Agent/Vendor	Payment and booking	Job ID, service, amount, currency, bank details, due date, document type and supporting files
Billing instruction	Sales/Customer + Accounting	Customer invoicing	Sales/customer provides legal entity, tax ID and address; Accounting determines or verifies invoice description, tax treatment and issue timing under applicable rules
POD and completion file	Operations	Reconciliation and closure	Delivery date, receiver, condition, customs docs and final cost

RECOMMENDED HANDOVER PROCESS

Create the Job ID and source of truth

Sales opens the record after customer approval. All quotations, RFQs, contracts, emails, documents and changes use the same Job ID.

Lock the commercial scope

Sales states inclusions, exclusions, price, currency/exchange basis, whether VAT is included or excluded, validity, payment terms, deadline and pricing assumptions.

Sales-to-Operations handover and acceptance

Operations checks completeness. Missing data is returned as a list; urgent execution is recorded as conditional acceptance with an owner and deadline.

Execution and change-log control

Operations updates booking, ETD/ETA, cut-off, pre-alert, documents, exceptions and actual cost. Price or commitment impacts are escalated to Sales.

Preliminary financial handover

After booking or when a payment obligation arises, Sales/Operations sends the cost sheet, vendor, forecast debit note, due date, billing data and collection plan.

Reconcile before payment and invoicing

Accounting matches Job ID, scope, approval, currency, document type and invoicing conditions. Out-of-scope amounts or incomplete evidence may proceed only through the defined exception-approval mechanism.

Close and archive the job

Operations completes POD and actual costs; Sales confirms delivery of commitments; Accounting reconciles revenue, cost and AR/AP.

COMMON RISKS AND ERRORS

Error	Impact	Control
Handover is only in chat and not updated in the job file	Operations or Accounting uses an obsolete version.	Maintain one source of truth and update the change log.
Sales hands over a lump-sum price without scope breakdown	Teams cannot identify authorised purchase or extra billing.	Split sell/buy rates by charge and state inclusions/exclusions.
Operations accepts a job with missing cargo data	Wrong equipment, loading plan or specialist documents.	Use conditional acceptance with missing items and deadline.
Debit note has no Job ID or supporting reference	Wrong job, duplicate payment or currency error.	Do not submit or release payment without Job ID, vendor, service detail and approval evidence, unless an authorised exception is documented and traceable.
Extra cost is reported too late to Sales	Customer approval is lost and margin is reduced.	Escalate the exception when detected, not at job end.
Accounting is informed only after cargo arrival	Cash planning, vendor payment or invoicing is delayed.	Provide preliminary financial handover after booking and before ETA.
No formal job-closing step	Missing documents, unbooked cost and unreconciled balances.	Close only after POD, actual costs, invoices and AR/AP reconciliation.

OPERATING SOURCES AND REFERENCES

This checklist follows the logic of import and export shipment SOPs: Sales collects data, prices the job and coordinates the agent; Operations manages booking, pre-alert, documents and delivery; Accounting plans payments, processes debit notes, issues service invoices and reconciles balances.

Reference	Role	Application note
Import transaction SOP	Pricing, agent coordination, pre-alert, arrival notice and payment flow.	Adapt to company structure and shipment type.
Export shipment SOP	Document preparation, loading supervision, customs, transport monitoring and completion.	Supports export flow and physical handover evidence.
Quotation/Contract/PO	Controls scope, selling price, payment terms and customer commitment.	Use the approved and traceable version.
Booking/Pre-alert/Debit Note/POD	Provides execution evidence, support for a payment request and delivery result; a Debit Note does not automatically replace a valid invoice or accounting document.	Must reference Job ID and agreed scope.

Note: There is no single mandatory handover form for every enterprise. Internal records should align with contracts, financial controls, accounting systems and approval authority.

FAQ

Does each function need a separate form?

Not necessarily. A shared job file is usually stronger, provided each function owns defined fields and changes are traceable.

Can Operations reject a handover?

Yes, or accept it conditionally when missing data affects booking, customs, cost control or compliance. The gap and deadline must be recorded.

When should Accounting receive the handover?

Do not wait for arrival. Preliminary data should be shared after booking or when a payment obligation arises, then refreshed before ETA and upon exceptions.

Who is responsible for an unquoted surcharge?

Separate operational cause, approval authority and commercial responsibility. The person receiving the debit note is not automatically responsible.

Can group chat replace a handover record?

Chat can support evidence but should not be the source of truth. Critical data belongs in the job file, an approval email or management system.

When is a job complete?

After service delivery, operational evidence, actual cost lock, invoice processing and AR/AP reconciliation are completed.

APPLICATION NOTE: A checklist only works when update rights, response deadlines and approval rules are defined. Add Compliance, Customs or Technical roles for licences, C/O, specialist inspections, insurance or technical cargo.

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B

MACHINERY

HOUSEHOLD GOODS

COSMETICS – PERSONAL CARE