Amazon FBA and Brightpearl
Integration Agency & Consultants
At scale, the gap between Amazon payouts and Brightpearl accounts creates reconciliation debt that hides your true net margin. When Amazon FBA handles fulfilment, the commercial pressure shifts from shipping logic to financial accuracy. Success requires capturing complex settlement data, including variable FBA fees and international VAT, directly into the Brightpearl ledger to ensure the bank account actually matches the settlement report. If these deductions are not mapped to specific nominal codes, revenue figures remain inflated and the financial trust boundary collapses during month-end close.
Auditing marketplaces and ERP system gaps
We connect your Amazon FBA and Brightpearl integrations with expertise across Marketplaces and ERP systems. Our consulting services are invaluable, offering a thorough system audit to uncover inefficiencies and integration gaps. This enables our consultants and your team to take decisive action, ensuring your Amazon FBA, Brightpearl, ERP, and Marketplaces work together efficiently. With our audits, your tech ecosystem runs smoothly, supporting excellent customer experiences and reliable operations across all platforms.
Solution Design
The design treats Brightpearl as the master for inventory and accounting, while Amazon FBA acts as the fulfillment event owner. A primary design decision involves the processing of Amazon Settlement Reports. We typically automate the parsing of settlement files into Brightpearl journals to capture variable fees and tax accurately. One critical trade-off is the frequency of settlement sync. While frequent fee capture provides granular visibility, we often recommend batching entries to align with Amazon’s payout cycle, which reduces journal volume and simplifies bank reconciliation. This ensures finance closes the month with figures that actually match the bank account, while operations rely on Brightpearl for a consolidated view of FBA stock levels.
Mapping settlement files to accounting ledgers
The integration synchronises Amazon FBA shipments into Brightpearl as sales orders and automates the posting of settlement files. Brightpearl remains the authoritative master for inventory and financial ledgers. When Amazon fulfills an order, the status flows back to Brightpearl to trigger the accounting events. The core of this integration is the settlement parsing logic. Rather than just importing total payout figures, the system maps individual fee lines, including commissions and storage costs, directly to Brightpearl nominal codes. Monitoring is embedded at the journal level, ensuring that any unmapped fee types or reserve balances are detected before they cause a reconciliation gap in your bank account.
Secure orchestration across the tech stack
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Amazon FBA, Brightpearl, Marketplaces, and ERP systems. This approach simplifies connecting Amazon FBA and Brightpearl with Marketplaces and ERP platforms, ensuring data integrity and compliance. IPaaS platforms reduce manual effort, support scalability, and maintain robust security, making integrations reliable and future-proof for businesses handling sensitive data.
Surfacing Amazon fee and reconciliation exceptions
Standard dashboards often miss the discrepancies between Amazon's reported revenue and actual cash in the bank. Hidden issues, like incorrectly recorded FBA returns or unrecognised storage fees, compound over time into manual reconciliation debt. We provide visibility into these settlement exceptions, surfacing unmapped fee codes or timing mismatches as they happen. This allows finance to address issues intra-month rather than discovering a variance during the close. Our monitoring focuses on data integrity across the settlement cycle, ensuring that every deduction by Amazon is accounted for in a corresponding Brightpearl journal entry.
Finance and operations workflow handover training
Handover focuses on how finance and ops teams manage the settlement cycle. We train finance to reconcile the Amazon settlement report against Brightpearl bank accounts, ensuring they can identify and map non-order fees like FBA storage and advertising spend. Operations teams learn to monitor fulfillment status and manage inventory adjustments where warehouse figures differ from the accounting ledger. We provide operational documentation that details exception ownership and daily check routines, rather than technical manuals. Training is anchored in your specific nominal mapping and settlement workflow, ensuring the team knows exactly how to read alerts and resolve reconciliation gaps before they compound into month-end debt.
Active monitoring of settlement data integrity
Post-launch support moves beyond technical fixes to ongoing operational ownership. We monitor the settlement sync regularly to catch new fee types or changes before they impact your month-end close. Our team acts as an escalation point for complex reconciliation issues, ensuring that when reporting structures change, your Brightpearl records are adjusted accordingly. This ensures that the integration remains a reliable source of financial truth, supported by a team that understands the commercial consequences of a broken settlement flow.
Common failures
Incomplete reconciliation of Amazon settlement reports
Operational impact: The finance team sees inflated revenue figures in Brightpearl because Amazon fees, advertising costs, and rolling reserves are not posted as corresponding journals. This breaks the order-to-cash reconciliation process, creating weeks of manual accounting work to match payouts to sales orders and balance the nominal ledgers.
Prevention / Action: The integration logic must be designed to parse the entire Amazon Settlement Report, not just the net payout total. Each fee type and deduction requires explicit mapping to a dedicated nominal code in Brightpearl. This process should automate the creation of bank receipts for the final payout and separate journals for all fee deductions, ensuring a fully reconciled state without manual intervention.
Inventory sync failures due to SKU mismatch
Operational impact: If the product SKU in Brightpearl does not exactly match the Merchant SKU (MSKU) in Amazon Seller Central, inventory level updates will consistently fail. This leads to incorrect stock availability on the Amazon listing, causing overselling and cancelled FBA orders or underselling and lost revenue. It creates reactive, manual work for merchandising and operations teams to diagnose and fix the failing SKUs.
Prevention / Action: Establish Brightpearl as the single source of truth for all product and SKU data from the outset. Implement a strict operational process where SKUs are always created and governed in Brightpearl before being pushed to Amazon. The integration itself should feature robust exception handling to immediately flag any SKUs that fail to sync, allowing for quick resolution rather than letting errors build up.
FBA and merchant-fulfilled orders are not differentiated
Operational impact: When Amazon FBA orders are downloaded into Brightpearl without being correctly flagged as externally fulfilled, the operations team may mistakenly attempt to ship them. This creates unnecessary Goods Out Notes, allocates stock that does not need allocating, and causes confusion in the warehouse. It also means FBA shipments are not correctly recorded in Brightpearl, leading to inaccurate sales and fulfilment reporting.
Prevention / Action: The integration must interrogate the 'fulfilment-channel' source for every Amazon order upon download. Orders flagged 'AFN' (Amazon Fulfilled) must be routed to a specific workflow in Brightpearl that creates and closes a sales order without triggering a fulfilment request. 'MFN' (Merchant Fulfilled) orders should proceed through the standard pick, pack, and dispatch process as normal.
FBA return and refund processing gaps
Operational impact: Amazon manages the physical return of FBA orders, but if the integration fails to create the corresponding sales credit in Brightpearl, the process is incomplete. This overstates revenue, leaves customer accounts unresolved, and means returned inventory is not correctly logged back into sellable stock. It forces the finance and CX teams into a reactive, manual process to investigate refund queries and adjust accounts.
Prevention / Action: Design a scheduled process to listen for FBA return and refund notifications from Amazon. On receipt, the integration's logic should automatically find the original sales order and generate a corresponding sales credit in Brightpearl. This ensures that the financial and inventory consequences of the return are captured in the system of record correctly and in a timely manner.
Frequently asked questions
Why is our net margin inaccurate in Brightpearl for Amazon sales?
Most integrations only sync sales orders, ignoring the fees deducted before the payout reaches your bank. To find your true net margin, the integration must parse the Amazon Settlement Report to create journal entries for FBA storage, referral fees, and PPC spend. Without this, your revenue in Brightpearl is inflated and does not reflect the cash actually received.
How are Amazon settlement fees mapped to the chart of accounts?
The integration automates the posting of the settlement file into Brightpearl journals. It maps specific Amazon fee categories to your corresponding nominal codes. This closes the gap between the bank statement and the ERP, ensuring non-order deductions like warehouse storage or reserve balances are accounted for.
What happens if Amazon MSKUs and Brightpearl SKUs do not match?
Mismatched identifiers cause source-of-truth ambiguity. In many implementations, a mapping table links the Brightpearl item record to the Amazon MSKU. This ensures inventory levels stay in step even if your internal SKU naming differs from the Amazon listing.
How does the integration separate FBA from Merchant-Fulfilled (FBM) orders?
The integration identifies the fulfilment source at the point of order creation. FBA orders are typically posted as sales orders but flagged to prevent a duplicate Goods Out Note (GON) being issued to your own warehouse. Merchant-fulfilled orders flow into your standard Brightpearl fulfilment workflow for manual pick and pack.
How are FBA customer returns and VAT liabilities managed?
Amazon manages the physical return, but the financial adjustment must happen in Brightpearl to keep VAT reporting accurate. In most setups, the integration automates the creation of sales credits and inventory adjustments once the relevant events are confirmed in the settlement cycle.