Singapore e-BDN Checks Before Invoice Approval

Key takeaways

• Connect the order, final e-BDN and invoice to the same transaction.
• Distinguish document authenticity from agreement on the invoice amount.
• Track authorised corrections without overwriting the original evidence.
• Verify payment instructions through the buyer's established controls.

Use Singapore's verification context correctly

MPA provides an e-BDN record enquiry system to verify electronic delivery-note data against information transmitted to the authority. MPA digital bunkering

That local facility addresses an important evidence question: whether the received data corresponds to the transmitted record. It should not be described as confirming the buyer's complete contract or approving a particular invoice for payment.

For a current transaction, the document reconciliation status is not provided; obtain current verified information. State whether the final order, delivery reference and invoice have been matched, and identify any unresolved exception. An authentic record can still require commercial reconciliation.

Build a transaction chain rather than a folder

Start with the confirmed order reference, vessel identity and delivery description. Match these to the final e-BDN and then to the invoice. A folder containing all three documents is not enough if the records refer to different supplies or grades.

Where an order includes separate fuel grades, keep the quantities and price lines distinguishable. A supplier may invoice the package together, but the reconciliation should still show how each delivered amount maps to the relevant agreed price.

Identify the final document status. A preliminary file sent during the call should not silently become the invoice basis when a later authorised record exists. Record which version is being used and why, especially where a correction affects quantity or identity.

Separate delivery facts from price terms

The e-BDN can support the delivery side of the comparison. The order and agreed amendments support the price, currency and charge structure. The invoice should connect those two sets of evidence clearly.

Check whether a fixed delivery charge is already included in the quoted price. A separate invoice line may be correct under one purchase and duplicate an inclusion under another. Resolve the actual wording rather than applying a general assumption about Singapore charges.

A changed quantity may also affect a quoted minimum or tier. Use the agreed mechanism and preserve the relevant calculation. Do not infer a new price from the delivered quantity unless the purchase terms provide that basis.

Document questions and their commercial limits

Where a discrepancy has contractual significance, check the current text and obtain appropriate review. Administrative matching should not be mistaken for determining rights.

Treat corrections as a linked sequence

If the supplier corrects a delivery record or invoice, retain the original and the authorised replacement with the stated reason. Link any credit note to the affected invoice rather than subtracting an unexplained amount from the payment schedule.

Confirm whether the correction changes only an administrative field or also the amount due. A corrected vessel reference and a corrected delivered quantity can have different consequences. The desk should explain the effect without assuming that every replacement document requires the same action.

Use the actual payment deadline while resolving the issue. An internal review status does not necessarily alter an external due date. Escalate the exception through the buyer's process rather than leaving a disputed invoice unattended.

Fictional case: authentic delivery data, duplicated charge

A fictional buyer receives a Singapore e-BDN whose data matches the relevant record enquiry. The invoice uses the same vessel, grade and quantity, so the first reviewer marks the purchase ready for payment.

A price comparison reveals a separate delivery charge even though the confirmed offer included that service. The buyer asks the supplier to reconcile the invoice with the order, and the supplier issues a corrected commercial document.

The authentic e-BDN remains useful and unchanged. The error concerned the invoice's charge boundary, demonstrating why delivery verification and price reconciliation are complementary checks rather than substitutes.

Finish with a usable approval note

The approval note should identify the matched documents, calculation basis and any resolved exception. Where an issue remains open, state its amount or scope and the responsible decision-maker instead of presenting the whole transaction as clean.

Keep bank-detail verification separate. A document match does not authenticate an unexpected change to the beneficiary or payment route. Follow the established independent verification process before acting on such a change.

Common mistakes

Do not describe MPA record verification as invoice approval. Other errors include matching only the vessel name, using a preliminary delivery file, paying a duplicated inclusion and deleting superseded documents. A valid e-BDN does not remove the need to check the price agreement or an unexpected payment instruction.

Where Zeaclub fits

Zeaclub supports agentic, AI-assisted operations with a human in control.

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Explore Zeaclub

Visit the Zeaclub website