A clearer view
before you start.

Public BDN360 sign-in and registration are not open yet. Request access so the team can confirm your company, workspace scope and timing. Customer follow-up, sourcing, trade, delivery and customer-invoice accounting are prepared for arranged workspaces. Voyage-aware studies remain an internal preview; AP matching and direct accounting, Peppol and eBDN connections remain planned. Gmail and Microsoft 365 history requires administrator setup and provider consent. Alternative-fuel records remain limited to an enabled scope.

Email an access request as a Physical supplier, Bunker trader or Bunker buyer. When public access opens, company-first registration will create the company with its first owner, who can then invite colleagues into that same company. Roles, paid seats, supplier approval and workflow capabilities remain separate controls. Independent bunker brokers can register interest by email.

BDN360 is designed for small and midsize European bunker suppliers and traders, with connected workflows for shipowners and buyers, operations teams, finance staff and accountants. Commercial managers can follow sales attribution, team targets, receivables and margin across the book. Independent bunker brokers can register interest while the launch remains focused on suppliers, traders and buyers.

Yes. Record manual enquiries, offers and external acceptance alongside marketplace requests and quotes. A desk sale keeps its real customer and accepted terms, then connects to purchases, deliveries, invoicing and reconciliation. The external customer does not need a marketplace account.

Assign the account owner, choose a cadence or exact next contact, and keep promises, waiting states, pauses and temporary cover visible in the daily desk. Call, WhatsApp and Email starters stay editable, and opening one records nothing. Save the real outcome afterward. Confirmed replies remain visible until review. Due work can appear in Action Inbox and a private daily in-app reminder; BDN360 does not send an automatic customer message.

Yes, when a workspace administrator configures the provider and each user grants consent. The optional connection imports Inbox and Sent metadata only for known customer contacts, including subject and contact time. Message bodies stay in the mailbox. BDN360 does not send email, and unrelated or ambiguous messages are not attached to a customer.

Record supplier replies from email, WhatsApp or calls and preserve each quote revision. Compare prices beside partial quantities, missing costs, expiry and currency assumptions. Private estimated margin stays pinned to the supplier and customer revisions behind it. Supplier acceptance creates purchase commitments, customer acceptance creates the sale separately, and the trader links both sides to the stem when they are ready.

No. The accountant workflow starts with issued customer invoice and credit PDFs, structured CSV tables, a package manifest and totals by currency. Your accountant can review and post those customer items manually, record acceptance or rejection and return references and reconciliation evidence. Direct ERP connections and system-specific templates remain planned until the receiving system is validated. AP item return is not supported.

Quoted margin uses the accepted commercial terms and expected costs. Accrued margin incorporates recorded deliveries and accrued costs. Reconciled margin uses the approved cost coverage, matched supplier invoices, credits, allocations and FX policy. Each view shows what it includes and what is still missing, so a partial result cannot be mistaken for a complete profit figure.

A self-serve four-way AP matching and exception workspace is planned. Its intended review connects the purchase commitment, effective delivery or BDN, required quality and quantity evidence, and supplier invoice. The current customer-invoice accountant return does not support AP items.

Quote, BDN and invoice extraction proposes structured facts for a person to review. Reviewers can inspect the original file, source page, uncertain fields and previous corrections before accepting data. Uploaded signatures and certificates remain evidence to assess; extraction does not establish their authenticity.

Keep the affected order or delivery, BDN, survey, laboratory and sample records together. Assign responsibility, track contract-specific notice deadlines, preserve notices and receipt evidence, and keep the current settlement offer visible. Financial-effect closure and extended claims-metrics screens remain planned. The responsible parties retain control of liability, withholding and settlement decisions.

Alternative-fuel records are enabled by confirmed product, pathway, port and delivery mode. Current scoped records cover typed product and qualification details, quantity allocation and correction, supported transaction binding and consumption context. A full fuel lifecycle, external acceptance, registry work and partner exchange remain planned. Additional fuels are enabled individually after their scope is confirmed.

No. It keeps evidence records and qualified planning assumptions distinct from external outcomes. Certificates, consignment records, allocated quantities and consumption context can be recorded within an enabled scope. External certification, registry acceptance and verification remain separate, and a full sustainability lifecycle remains planned.

No. They remain planned until the receiving system, provider and evidence contract are validated. The current customer-invoice accountant handoff uses issued PDFs, structured CSV tables and an item manifest without requiring a connector. BDN uploads and reviewed files remain the starting point.

Workspace roles and organization boundaries determine access. Supplier purchase costs and margins remain private to authorized users. Buyers, operations, finance and accountants receive the views and actions appropriate to their work. Each principal controls its own screening decisions, with separate makers and checkers where required. Supplier approval for matching covers the declared supply scope; it is not a KYC or credit endorsement.

No. Payment evidence, invoice issuance, customer dispatch, accountant receipt and external posting are separate events. Recording or exporting a transaction does not initiate a bank transfer or establish that a receiving accounting system posted it. Restricted supplier-beneficiary changes require one authorized person to propose the change and another to review it; that review does not verify the bank account or move money.

An agreed pilot includes 90 days of complimentary Professional seats for the approved roster, with no bunker transaction fee. The pilot does not silently convert to a paid subscription. The team agrees the workspace scope, responsibilities and any later commercial terms with you.