A bunker delivery can finish while the office is still trying to connect the evidence. The electronic delivery note reaches one mailbox, the nomination sits in another system and finance is waiting for a reference that appears differently on the supplier invoice. Digital documents have replaced paper, but the commercial workflow still depends on someone recognising the voyage.
For a Singapore marine-fuel business, the useful software project is the connection between the signed operational record and the people who must act on it. That connection should preserve authoritative documents, explain mismatches and prevent an integration from quietly turning a disputed quantity into an approved payable.
Build around the approved digital-bunkering process
MPA's digital bunkering guidance states that suppliers provide digital bunkering and issue e-BDNs by default from 1 April 2025. It also says operators and suppliers must use MPA-whitelisted solutions. A custom office integration should connect to the selected solution and its permitted interfaces; it should not be presented as an unapproved replacement for that regulated workflow.
The MPA crew guide shows distinct preparation, review, signature and final-document steps. That sequence is useful context for integration design. Receiving a file does not establish that every operational and commercial question around the delivery is closed.
Keep the distinction visible. Your office platform can say that a final document was received and matched to a nomination while separately showing a commercial query. A signed record and an internal approval serve different purposes and should have different identifiers, timestamps and owners.
The matching problem starts before delivery
Begin with a nomination identity that survives amendments. Link the customer, supplier, vessel identifier, fuel product, intended operation and applicable commercial references. Store changes as revisions rather than overwriting a single row. A late change to delivery details should not make the original instruction disappear.
An illustrative mismatch is a nomination using an internal vessel nickname while the delivery document carries the official vessel identity. Another is an invoice covering several deliveries while the receiving system assumes one invoice means one e-BDN. These are data-model questions to resolve before choosing a document-extraction tool.
Ask the integration partner to show how a person resolves an uncertain match. Suggested candidates are useful, but the reviewer needs to see the evidence behind them. Record the chosen match and the reason. A confidence score without the underlying references is not an adequate explanation for finance.
Preserve quantities with their meanings
Quantity is not a free-floating decimal. Record the source document, stated unit, relevant product and the role the value plays in the workflow. Keep nominated, delivered and invoiced quantities distinct. Any conversion or calculation should have an explicit rule and enough context for an authorised reviewer to check it.
The integration should not attempt to adjudicate a technical measurement dispute by selecting whichever number makes the invoice balance. Route unresolved differences to the responsible operational and commercial people. Preserve the original values and their sources, even when a later adjustment settles the issue.
In the user interface, put the exception beside the action. A finance reviewer should see whether the issue is a missing reference, a document-version mismatch or a substantive quantity query. These cases need different owners and should not all be represented by the same red status.
Give AI extraction a narrow, reviewable role
If some supporting files still arrive as PDFs or scans, AI-assisted extraction can propose references and line items for matching. That is an engineering option, not a substitute for structured data from the chosen digital-bunkering provider. Prefer the structured source when available and contractually accessible.
For extracted fields, retain a link to the exact page and visible source. Treat ambiguous units and partially readable identifiers as review items. Never let a model rewrite a signed delivery note or infer a missing approval. The advantage should be less clerical searching, with a traceable route back to the original record.
Evaluate on your permitted document sample, including amended nominations, multi-delivery invoices and files with similar vessel names. Measure the rate at which the system links the wrong operation, not only the percentage of characters it reads correctly. A perfect transcription attached to the wrong delivery is still a serious workflow error.
Make the exception queue usable across teams
Every exception needs an owner, current explanation and next action. Separate requests awaiting a supplier response from items finance can resolve internally. Include who last changed the state and what evidence was added. A conversation hidden in one employee's inbox should not determine whether the next employee can release the invoice.
Permissions matter because shipowners, traders, suppliers and surveyors do not necessarily share access to the same commercial terms. Design access around the actual organisations and relationships. Test exports as carefully as screens: a broadly shared spreadsheet can undo careful portal permissions.
MPA provides an e-BDN enquiry service for checking specified delivery information. Use the authorised verification process where appropriate, and record what was checked. Do not build automated CAPTCHA bypasses or assume that a public enquiry page grants bulk integration access.
Scope one complete reconciliation journey
The first release can start with one digital-bunkering solution, one receiving finance system and a defined set of document types. Deliver an identity map, controlled imports, reviewable matching, an exception queue and an export of the final reconciliation evidence. Confirm how late documents and corrected references are handled after a period is closed.
Ask the vendor to demonstrate an unmatched document becoming a reviewed, explained record without editing its source. Also test repeated imports and a temporary provider outage. The workflow should resume without duplicating a payable or losing the reviewer discussion.
Our integration statement-of-work guide and data-governance guide can help define the boundaries. TuniCyberLabs' custom software development connects operational evidence with business systems. Discuss a maritime reconciliation project with your selected e-BDN provider, current finance system and a redacted example of a delivery that required manual investigation.