PRODUCT CAPABILITIES
What’s in scope.
01
Vendor reconciliations
Match supplier statements, apply deductions and generate payments from reconciliations. Statement and payment-advice communication can remain connected to the work being performed on the supplier account.
02
Debtor collections
Record collection notes, customer interactions, reasons for non-payment and follow-up dates. Shared visibility of outstanding accounts helps the collections team maintain continuity as work moves between colleagues.
03
Forward exchange contracts
Record foreign exchange contract purchases and connect the relevant documents. Applying the appropriate exchange information to inventory receipts supports the treatment of imported goods within the costing process.
04
Landed cost
The published Landed Cost concept allocates freight, tariffs and related charges to shipments. Its Help page remains marked pre-release; confirm production availability and the supported workflow before including this module in an implementation.
Choose the modules around the process gap
Braintree can scope the required modules around the supplier, customer and import workflows already running in Business Central. Multi-company requirements, user responsibilities and supporting records should be identified during setup.
✓
Identify the reconciliation or collections work still managed separately.
✓
Map import charges and foreign-exchange documents to shipments.
✓
Agree ownership of deductions, follow-ups and cost allocation.
✓
Confirm the module combination, configuration and support requirements.
THE PRODUCT IN PRACTICE
Start from the operational dashboard
The product overview shows entry points for vendor reconciliation, debtor collections and forward exchange contracts. Confirm the available release and applicable modules during scoping.
Read the workflow guide
01
Select the process that needs attention
Trade Assistant groups focused Business Central tools for vendor reconciliation, debtor collection, forward exchange contracts and landed cost. The product overview allows modules to be considered individually or as a suite. That makes the practical starting point a process gap: a supplier statement maintained separately, collection notes held outside the account, or import-cost information that is difficult to connect to the purchase.
Braintree can scope the module combination around those gaps. Each area uses different records and responsibilities, so the engagement should identify the finance, collections and purchasing owners before assuming the entire suite belongs in one rollout.
02
Base the payment on a reconciled supplier account
The vendor-reconciliation module records the supplier’s statement against the organisation’s creditor ledger. It supports matching transactions, identifying missing documents or value differences, recording deductions and deciding the amount to pay. The documented output includes a remittance advice showing the transactions settled and a reconciliation between the statement and ledger balances.
Configuration includes administrator setup, numbering and deduction codes. Deductions can use a specified amount or percentage and the relevant account. The Help guide describes a simple line-management workflow and a workflow based on standard Business Central templates. Approval responsibilities and payment batches should therefore be established before the module is used to generate payments.
03
Keep the invoice and the follow-up together
The debtor-collection dashboard can be filtered by customer, salesperson, collections administrator and overdue status, using the selected ageing date and method. Users can drill into the transactions behind the balances. A customer-level note records the broader account situation, while collection notes capture information about particular invoices.
The invoice-level workflow records disputes, reason codes and promises to pay, including the proposed amount and date. The guide also documents an Excel age-analysis report and a document search that locates collection notes containing a particular invoice reference. This supports continuity between colleagues without turning a promised payment into evidence that cash has been received.
04
Connect purchased currency cover to the purchase
The forward-exchange-contract module records a contract, releases and posts it, then links eligible purchase documents. The documented selection uses the contract currency and expiry conditions. A purchase can be assigned to more than one open contract where necessary, and the contract balance changes as documents are linked.
When a linked purchase order is received, the guide describes use of the applicable contract exchange rate for stock costing. Where multiple contracts apply, the documented process averages the rate. Receipt and invoice postings update the contract ledger. This is an operational record of purchased cover and its allocation; the extension should not be presented as advice to enter a currency contract or as protection against every exchange-rate risk.
05
Confirm the available release before scoping landed cost
The product page describes applying freight, tariffs and foreign-currency costs to shipments. The related Help page is still labelled a pre-release announcement and describes interim estimates for supplementary costs, with accruals before final supplier invoices. A planned release date is not proof that a current production version includes the capability.
Braintree should confirm the module’s current availability, supported release and demonstrated workflow before it enters a delivery commitment. The review should identify the charges to be estimated, how they relate to shipments and how final costs are reviewed. This keeps the costing requirement concrete while preserving the boundary of the available evidence.
06
Agree the controls at each handover
The module assessment should use sample supplier statements, overdue invoices and import documents from the processes in scope. The published setup and support offer can then be translated into a defined engagement.
Choose the required modules and confirm their current release and licensing scope.
Allocate reconciliation approval, deduction, collection and contract-maintenance responsibilities.
Configure the relevant numbering, user setup and payment batches.
Validate account reconciliation, invoice follow-up and receipt-costing examples.
Define support responsibilities and the evidence needed to accept each module.
EVIDENCE & DOCUMENTATION
See the work in context.
Invoice-level collection documentation
The guide shows customer filters, ageing drill-down, dispute reasons, promised payments, Excel age analysis and searches across collection notes.
Explore the documentation
Contract allocation and posting documentation
The guide records the connection between posted contracts, eligible purchase documents, receipt costing and contract-ledger updates.
Explore the documentation
BEFORE YOU DECIDE



