/ 4 min read / business license / supplier verification / entity roles
Supplier Sends Two Business Licenses for One Order
Two licenses in one file require role mapping before the buyer treats the supplier as verified.
What to check in the order file
Supplier Sends Two Business Licenses for One Order starts as a small exception inside a live order. The buyer sees two business licenses in one order file, then checks whether one field, message, or document no longer agrees with the earlier file.
The buyer needs to decide which company sells, manufactures, exports, certifies, and receives payment.
Check both business licenses, quotation, PI, factory photos, certificate holder name, export declaration draft, and bank beneficiary.
A supplier may send one license for the factory and another for the trading office without naming the role of each entity.
Ask one control question before deposit release: can the buyer place every company name into a role table?
Two licenses in one file require role mapping before the order owner treats the supplier as verified. Another member of the team should be able to verify the answer from the file before supplier approval or production release. Put that result in the supplier sends order note for the current PO.
Open the business record, legal and trade names, PO, invoice issuer, factory address, and payment beneficiary together. Mark the first changed field and keep the earlier version beside the record the importer plans to use. The comparison should show who supplied the revision, when it arrived, and which order step depends on it. Carry the result into the supplier verification instruction used by the next team.
Make the decision before the next handoff
Familiar commercial explanations can hide a real mismatch. Ask which company, record, quantity, model, payment, or shipment the answer covers, and record when the answer applies only to this order. The entity roles file should show how this point was resolved.
Assign the file to sourcing, finance, and the person maintaining the approved-supplier file. The owner does not need every chat message, but does need the final document, supplier answer, importer decision, and next checkpoint. Name this point in the business license closeout rather than leaving it in chat.
The unresolved risk is that the importer may rely on one company while another company sells, produces, signs, or receives payment. State whether the exception covers one shipment, one payment, one model, or the wider vendor relationship. A one-order decision should not silently become standing decision. Put that result in the supplier sends order note for the current PO.
Use the checklist as a closing test: list both entities, assign each role, compare certificate holder, and check bank beneficiary. Record who completed each step and retain the evidence beside the record it supports instead of leaving a general note that the supplier was checked. Use the entity roles record to show who accepted the result and on what date.
Give the exception an end point, such as receipt of a corrected document, payment confirmation, inspection, broker acceptance, warehouse receipt, or claim settlement. State the remaining limit in the business license note before the file is closed.
Public guidance can frame the business license check, but it cannot establish the facts of this order. The importer's PO, invoice, beneficiary record, packing list, product evidence, broker reply, and shipment file remain the deciding records. The supplier verification file should show how this point was resolved.
If the issue returns, begin with the prior note. It should show which file to request first and which assumption caused the earlier delay. Record the outcome with the supplier sends order evidence before handoff.
Close the record for the next order
Retain the revision path visible. The folder should show which version was rejected, which version controls, and whether anyone outside sourcing still holds an obsolete copy. Link the answer to the business license checkpoint for this order.
Record one of three outcomes: approve, approve with a stated condition, or hold. Name the evidence supporting that outcome and the event that would force the purchasing team to reconsider it. State the remaining limit in the supplier verification note before the file is closed.
Send the controlling record to every team that will act on it. Approval is incomplete when finance, logistics, the warehouse, or the broker continues from an older version. Keep the supporting file beside the entity roles entry in the order folder.
When the same exception affects several orders, add the field to the counterparty baseline. Repeated problems belong in onboarding, PO wording, inspection scope, payment approval, or broker instructions. Keep the supporting file beside the supplier sends order entry in the order folder.
Preserve evidence in the format closest to the original event: source PDF, email, photo, receipt, broker reply, or warehouse record. A summary should point back to those files rather than becoming the only record left in the folder. Name this point in the supplier verification closeout rather than leaving it in chat.
The closeout needs both completion and limits. Completion means the controlling file is stored and the next owner has it; the limit states what the buyer did not verify or approve. The next reviewer should find the answer under entity roles without reopening the whole case.
Working checklist
- List both entities.
- Assign each role.
- Compare certificate holder.
- Check bank beneficiary.
- Save supplier role statement.