Quick answers
- Can SignalEDI help me connect to BHP Supplier Network?
- SignalEDI helps prepare mappings, sample validation, and the workflow required for your BHP Supplier Network program. Scope is confirmed during setup. Production connection requires the applicable partner approval; this guide is not evidence of a live connection or certification.
- What determines the BHP Supplier Network onboarding timeline?
- The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule. Agree the schedule after requirements and testing scope are confirmed. This is not a guaranteed go-live date.
- Which ERP systems can I use for BHP Supplier Network?
- Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Plan the integration workflow
SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.
1. Your business system
Identify the source records, system edition, data owner, and allowed access.
2. SignalEDI preparation
Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.
3. Partner testing and approval
Complete the partner-controlled tests and retain permission before enabling live exchange.
Conceptual workflow only. A diagram or catalog listing does not establish certification or an active production connection.
Build your onboarding checklistPublic sources reviewed 2026-11-09
What the public record confirms
- BHP's supplier page separates Global Contract Management System onboarding from SAP Business Network transactions. It describes a free Standard account as the minimum network account for electronic trading and also recognizes alternative methods for suppliers not transacting through the network.
- BHP's October 2025 SAP Business Network FAQ distinguishes goods, services and Evaluated Receipt Settlement arrangements. Under an applicable ERS agreement, BHP generates the invoice after the relevant receipt or approved service entry; the supplier does not issue a competing invoice for that process.
- The same FAQ warns that network functionality and exclusions vary by country or functional area. SAP's own documentation describes cXML and EDI routing capabilities, but those platform options do not prove that every option is enabled for your BHP account.
- Public sources were reviewed on November 9, 2026. Current account business rules, Australian asset-specific addenda, routing setup and production approval were not accessed. This is supplier-process guidance, not a direct BHP connection claim, SAP certification or evidence of a SignalEDI partnership.
Document and workflow scope
Use the cited source boundaries below, then confirm your current assigned program: Exact specifications come from your partner packet. Treat this as a planning checklist, not a substitute for the current implementation guide.
- Supplier relationship record: identify the BHP purchasing entity, Australian asset or office, supplier identity, network account and purchasing contact. Keep GCMS profile maintenance separate from the network relationship that carries purchase orders and transactional documents.
- Order and confirmation scope: record the order type, buyer line references, units, service descriptions, permitted changes and remaining value. Obtain the BHP-specific instructions associated with the relationship instead of assuming that every feature displayed by SAP Business Network is suitable for BHP.
- Receipt and service evidence: determine whether completion is represented by goods receipt, a service entry sheet or another approved process. Keep the underlying delivery or service evidence linked to its purchase order, and assign an owner for rejected or outstanding claims.
- Invoice and settlement design: explicitly choose the applicable manual invoice, permitted automated invoice or ERS process. Confirm who creates the financial document and which receipt or approval permits it, so an ERP-generated invoice cannot duplicate a buyer-created settlement.
Connectivity and testing requirements
Connectivity
Confirm whether the current BHP Supplier Network program uses AS2, SFTP, VAN, or another named transport.
Onboarding window
Not verified on this page.
Certification focus
The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule.
- BHP's supplier page separates Global Contract Management System onboarding from SAP Business Network transactions. It describes a free Standard account as the minimum network account for electronic trading and also recognizes alternative methods for suppliers not transacting through the network.
- BHP's October 2025 SAP Business Network FAQ distinguishes goods, services and Evaluated Receipt Settlement arrangements. Under an applicable ERS agreement, BHP generates the invoice after the relevant receipt or approved service entry; the supplier does not issue a competing invoice for that process.
- The same FAQ warns that network functionality and exclusions vary by country or functional area. SAP's own documentation describes cXML and EDI routing capabilities, but those platform options do not prove that every option is enabled for your BHP account.
- Public sources were reviewed on November 9, 2026. Current account business rules, Australian asset-specific addenda, routing setup and production approval were not accessed. This is supplier-process guidance, not a direct BHP connection claim, SAP certification or evidence of a SignalEDI partnership.
Questions to resolve from the current buyer packet
- Confirm the Australian BHP entity, asset and order type with the purchasing contact. Do not assume that instructions for another country or a different functional area apply to the same network account.
- Review the account relationship and current BHP-specific business rules. Identify the approved document route, message format and commercial account implications before treating cXML or EDI as the selected implementation.
- Make invoice ownership explicit for each relevant order. Record ERS applicability and any approved automated-invoice setting as business decisions, not technical defaults that an integration can enable without review.
- Map order, line, receipt, service-entry and invoice references across the ERP and network. Preserve partial quantities or remaining values using the assigned rules rather than trying to infer them from a payment status.
- Define exception ownership for an unconfirmed order, missing receipt, rejected service claim and rejected invoice. These represent different stages; a successful upload should not mark the underlying obligation complete.
- Retain testing and approval evidence for the actual relationship before production. Use safe examples, record unresolved account-specific questions and verify the support route for business issues as well as network problems.
How SignalEDI handles it
- Prepare a versioned mapping and testing checklist from the requirements you provide.
- Validate synthetic or scrubbed samples before partner testing.
- Review acknowledgement and exception handling before production cutover. Scope is confirmed during setup.
Review mapping and validation in the self-serve workspace before partner testing. Developer quickstart
Pricing
SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.
Compare current plansPractice the workflow before partner testing
These are recommended preparation exercises, not additional partner requirements or a customer success story. Use synthetic or scrubbed samples and adapt each exercise to the current guide assigned to your program.
Choose the correct goods or service path
Create one synthetic material order and one service order for the same supplier. Map the completion evidence required by the assigned account instructions and identify the owner who confirms it. Include a mistakenly classified example to test whether the workflow notices the difference before invoicing.
What a useful result looks like
Each order follows the appropriate business process with its source references intact. A service completion is not represented as a warehouse receipt merely to fit an existing adapter. Missing or contradictory classification produces a clear question for the purchasing owner rather than an invented network rule.
Prevent duplicate ERS invoicing
Mark a synthetic order as covered by the confirmed ERS arrangement and simulate its completion. Examine what the ERP would normally generate, then trace the incoming buyer-created financial record. Compare that scenario with a non-ERS order without changing any live account setting.
What a useful result looks like
The integration distinguishes invoice ownership and prevents two claims for the same obligation. Accounting can reconcile the buyer-created record to the original order and completion evidence. This test does not authorize joining ERS, accepting terms or enabling an automated-invoice feature.
Handle a rejected service claim
Model a service entry that has been submitted but receives a known rejection, with a reason requiring corrected supporting information. Record the original references and the approved resubmission behavior from the current BHP guide. Separately model an entry whose outcome is still unknown.
What a useful result looks like
A confirmed rejection follows a traceable correction path, while an uncertain outcome is checked before a second claim is sent. The team can distinguish missing evidence, pending approval and network transmission failure. No invoice is represented as payable solely because a technical submission succeeded.
Keep network routing scoped to the relationship
Review a proposed ERP-to-network route using synthetic purchase orders from two buyers. Show how the BHP relationship, account configuration and document rules are selected. Introduce a document that is supported by the platform but has not been confirmed for the BHP account.
What a useful result looks like
Only approved document scope proceeds for the intended buyer relationship. Platform-wide functionality does not silently become a BHP mandate or entitlement. Readiness evidence names the account, route and remaining dependencies, with production acceptance and actual financial processing kept outside this advisory exercise.
Common integration questions
- Can I keep my existing ERP or accounting system?
- Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
- Does validation mean my partner has approved production?
- No. Passing document validation checks your sample against the configured rules. Partner certification, enrollment, transport approval, and permission to send live documents are separate steps controlled by the applicable partner program. Use synthetic or scrubbed samples while preparing and keep the approval evidence before switching to production.
- Where can I see SignalEDI pricing?
- SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.
Authoritative sources
Source review date: 2026-11-09. Links below establish only the facts described; your current buyer-issued materials remain authoritative for program-specific technical requirements.
- BHP new and existing supplier guidance — BHP
Supports: GCMS and SAP Business Network roles, Standard account guidance and alternative transaction paths; reviewed November 9, 2026.
- BHP SAP Business Network FAQ, October 2025 — BHP
Supports: Goods/services distinctions, ERS invoice ownership and regional functionality limitations; dated source requires current account confirmation.
- SAP Business Network supplier connectivity — SAP
Supports: Platform-level cXML and EDI routing capabilities; not evidence of BHP account enablement.
BHP Supplier Network questions
- Does BHP Supplier Network mean a direct EDI connection to BHP?
- Not necessarily. Identify the approved supplier relationship and transaction route first. SAP Business Network offers different ways to exchange documents, while BHP also publishes onboarding and alternative-process guidance. Platform capability alone does not establish your enabled format, account terms or current BHP requirements. Obtain those details before committing to an implementation.
- Should a BHP Supplier Network supplier always submit an invoice?
- No. First determine whether the order falls under an ERS agreement or another approved settlement method. BHP's dated FAQ explains buyer-generated invoicing for ERS. Confirm the current rule for the relevant asset and order, then configure a clear invoice owner so the supplier's ERP does not create a duplicate claim for the same goods or services.
- Why might a BHP Supplier Network transaction remain unresolved after upload?
- The underlying order, receipt, service claim or invoice may still need a business decision. Track those stages independently and use the purchasing contact or network support route appropriate to the problem. The exercises below help expose missing evidence and duplicate-risk scenarios, but they do not replace BHP acceptance or establish production permission.
Related EDI resources
- Customer requires EDI guide turns the buyer packet into a scoped implementation checklist.
- QuickBooks EDI integration explains supported accounting workflows. Confirm system edition and document scope; it does not establish a connector for this program.
- Managed EDI onboarding is an optional paid path when your team wants help coordinating the scoped partner workflow.
- Walmart EDI requirements covers publicly documented supplier interfaces and buyer-packet boundaries for Walmart programs.
- EDI requirements checker drafts a local readiness checklist without saving buyer data.
Prepare your side for partner testing
SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.
Connect nowTopics: BHP Supplier Network EDI requirements · BHP Supplier Network supplier EDI · BHP Supplier Network EDI AU